1 Changes in version 0.2.4.17-rc - 2013-09-0x
4 - Relays now process the new "NTor" circuit-level handshake requests
5 with higher priority than the old "TAP" circuit-level handshake
6 requests. We still process some TAP requests to not totally starve
7 0.2.3 clients when NTor becomes popular. A new consensus parameter
8 "NumNTorsPerTAP" lets us tune the balance later if we need to.
9 Implements ticket 9574.
12 - If the circuit build timeout logic is disabled (via the consensus,
13 or because we are an authority), then don't build testing circuits.
14 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
15 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
16 previously they did not, which prevented them from receiving
17 successful connections from relays for self-test or bandwidth
18 testing. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
19 - When a relay is extending a circuit to a bridge, it needs to send a
20 NETINFO cell, even when the bridge hasn't sent an AUTH_CHALLENGE
21 cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
22 - If the time to download the next old-style networkstatus is in
23 the future, do not decline to consider whether to download the
24 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
28 - Avoid double-closing the listener socket in our socketpair
29 replacement (used on Windows) in the case where the addresses on
30 our opened sockets don't match what we expected. Fixes bug 9400;
31 bugfix on every released Tor version. Found by Coverity.
33 o Minor fixes (config options):
34 - Avoid overflows when the user sets MaxCircuitDirtiness to a
35 ridiculously high value, by imposing a (ridiculously high) 30-day
36 maximum on MaxCircuitDirtiness.
37 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
38 message is logged at notice, not at info.
39 - Warn and fail if a server is configured not to advertise any
40 ORPorts at all. (We need *something* to put in our descriptor,
41 or we just won't work.)
44 - Update to the August 7 2013 Maxmind GeoLite Country database.
47 Changes in version 0.2.4.16-rc - 2013-08-10
48 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
49 series. It fixes several crash bugs in the 0.2.4 branch.
52 - Fix a bug in the voting algorithm that could yield incorrect results
53 when a non-naming authority declared too many flags. Fixes bug 9200;
54 bugfix on 0.2.0.3-alpha.
55 - Fix an uninitialized read that could in some cases lead to a remote
56 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
57 Anybody running a hidden service on the experimental 0.2.4.x
58 branch should upgrade. (This is, so far as we know, unrelated to
60 - Avoid an assertion failure when processing DNS replies without the
61 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
62 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
63 0.2.4.15-rc. Found by stem integration tests.
66 - Fix an invalid memory read that occured when a pluggable
67 transport proxy failed its configuration protocol.
68 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
69 - When evaluating whether to use a connection that we haven't
70 decided is canonical using a recent link protocol version,
71 decide that it's canonical only if it used address _does_
72 match the desired address. Fixes bug 9309; bugfix on
73 0.2.4.4-alpha. Reported by skruffy.
74 - Make the default behavior of NumDirectoryGuards be to track
75 NumEntryGuards. Now a user who changes only NumEntryGuards will get
76 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
77 - Fix a spurious compilation warning with some older versions of
78 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
81 - Update to the July 3 2013 Maxmind GeoLite Country database.
84 Changes in version 0.2.4.15-rc - 2013-07-01
85 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
86 series. It fixes a few smaller bugs, but generally appears stable.
87 Please test it and let us know whether it is!
90 - When receiving a new configuration file via the control port's
91 LOADCONF command, do not treat the defaults file as absent.
92 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
95 - Issue a warning when running with the bufferevents backend enabled.
96 It's still not stable, and people should know that they're likely
97 to hit unexpected problems. Closes ticket 9147.
100 Changes in version 0.2.4.14-alpha - 2013-06-18
101 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
102 present in 0.2.4.13-alpha.
105 - When we have too much memory queued in circuits (according to a new
106 MaxMemInCellQueues option), close the circuits consuming the most
107 memory. This prevents us from running out of memory as a relay if
108 circuits fill up faster than they can be drained. Fixes bug 9063;
109 bugfix on the 54th commit of Tor. This bug is a further fix beyond
110 bug 6252, whose fix was merged into 0.2.3.21-rc.
112 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
113 where we tried to solve this issue simply by imposing an upper limit
114 on the number of queued cells for a single circuit. That approach
115 proved to be problematic, since there are ways to provoke clients to
116 send a number of cells in excess of any such reasonable limit. Fixes
117 bug 9072; bugfix on 0.2.4.13-alpha.
119 - Limit hidden service descriptors to at most ten introduction
120 points, to slow one kind of guard enumeration. Fixes bug 9002;
121 bugfix on 0.1.1.11-alpha.
124 Changes in version 0.2.4.13-alpha - 2013-06-14
125 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
126 vulnerabilities, makes socks5 username/password circuit isolation
127 actually actually work (this time for sure!), and cleans up a bunch
128 of other issues in preparation for a release candidate.
130 o Major bugfixes (robustness):
131 - Close any circuit that has too many cells queued on it. Fixes
132 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
133 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
134 - Prevent the get_freelists() function from running off the end of
135 the list of freelists if it somehow gets an unrecognized
136 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
138 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
139 when an exit connection with optimistic data succeeds immediately
140 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
142 - Fix a directory authority crash bug when building a consensus
143 using an older consensus as its basis. Fixes bug 8833. Bugfix
147 - Avoid a memory leak where we would leak a consensus body when we
148 find that a consensus which we couldn't previously verify due to
149 missing certificates is now verifiable. Fixes bug 8719; bugfix
151 - We used to always request authority certificates by identity digest,
152 meaning we'd get the newest one even when we wanted one with a
153 different signing key. Then we would complain about being given
154 a certificate we already had, and never get the one we really
155 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
156 resource to request the one we want. Fixes bug 5595; bugfix on
158 - Follow the socks5 protocol when offering username/password
159 authentication. The fix for bug 8117 exposed this bug, and it
160 turns out real-world applications like Pidgin do care. Bugfix on
161 0.2.3.2-alpha; fixes bug 8879.
162 - Prevent failures on Windows Vista and later when rebuilding the
163 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
164 bugfix on 0.2.4.12-alpha.
167 - Fix an impossible buffer overrun in the AES unit tests. Fixes
168 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
169 - If for some reason we fail to write a microdescriptor while
170 rebuilding the cache, do not let the annotations from that
171 microdescriptor linger in the cache file, and do not let the
172 microdescriptor stay recorded as present in its old location.
173 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
174 - Fix a memory leak that would occur whenever a configuration
175 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
176 - Paste the description for PathBias parameters from the man
177 page into or.h, so the code documents them too. Fixes bug 7982;
178 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
179 - Relays now treat a changed IPv6 ORPort as sufficient reason to
180 publish an updated descriptor. Fixes bug 6026; bugfix on
182 - When launching a resolve request on behalf of an AF_UNIX control
183 socket, omit the address field of the new entry connection, used in
184 subsequent controller events, rather than letting tor_dup_addr()
185 set it to "<unknown address type>". Fixes bug 8639; bugfix on
188 o Minor bugfixes (log messages):
189 - Fix a scaling issue in the path bias accounting code that
190 resulted in "Bug:" log messages from either
191 pathbias_scale_close_rates() or pathbias_count_build_success().
192 This represents a bugfix on a previous bugfix: the original fix
193 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
195 - Give a less useless error message when the user asks for an IPv4
196 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
200 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
201 to tolerate bug 8093 for now.
202 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
203 in directory authority votes to describe whether they have enough
204 measured bandwidths to ignore advertised (relay descriptor)
205 bandwidth claims. Resolves ticket 8711.
206 - Update to the June 5 2013 Maxmind GeoLite Country database.
208 o Removed documentation:
209 - Remove some of the older contents of doc/ as obsolete; move others
210 to torspec.git. Fixes bug 8965.
212 o Code simplification and refactoring:
213 - Avoid using character buffers when constructing most directory
214 objects: this approach was unwieldy and error-prone. Instead,
215 build smartlists of strings, and concatenate them when done.
218 Changes in version 0.2.4.12-alpha - 2013-04-18
219 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
220 process for lengthening the guard rotation period, makes directory
221 authority opinions in the consensus a bit less gameable, makes socks5
222 username/password circuit isolation actually work, and fixes a wide
223 variety of other issues.
226 - Raise the default time that a client keeps an entry guard from
227 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
228 2012 paper. (We would make it even longer, but we need better client
229 load balancing first.) Also, make the guard lifetime controllable
230 via a new GuardLifetime torrc option and a GuardLifetime consensus
231 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
232 - Directory authorities now prefer using measured bandwidths to
233 advertised ones when computing flags and thresholds. Resolves
235 - Directory authorities that have more than a threshold number
236 of relays with measured bandwidths now treat relays with unmeasured
237 bandwidths as having bandwidth 0. Resolves ticket 8435.
239 o Major bugfixes (assert / resource use):
240 - Avoid a bug where our response to TLS renegotiation under certain
241 network conditions could lead to a busy-loop, with 100% CPU
242 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
243 - Avoid an assertion when we discover that we'd like to write a cell
244 onto a closing connection: just discard the cell. Fixes another
245 case of bug 7350; bugfix on 0.2.4.4-alpha.
247 o Major bugfixes (client-side privacy):
248 - When we mark a circuit as unusable for new circuits, have it
249 continue to be unusable for new circuits even if MaxCircuitDirtiness
250 is increased too much at the wrong time, or the system clock jumps
251 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
252 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
253 which have resolved to internal addresses") is set, apply that
254 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
255 - When an exit relay rejects a stream with reason "exit policy", but
256 we only know an exit policy summary (e.g. from the microdesc
257 consensus) for it, do not mark the relay as useless for all exiting.
258 Instead, mark just the circuit as unsuitable for that particular
259 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
260 - Allow applications to get proper stream isolation with
261 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
262 username/password authentication also offer "no authentication". Tor
263 had previously preferred "no authentication", so the applications
264 never actually sent Tor their auth details. Now Tor selects
265 username/password authentication if it's offered. You can disable
266 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
267 bug 8117; bugfix on 0.2.3.3-alpha.
269 o Major bugfixes (other):
270 - When unable to find any working directory nodes to use as a
271 directory guard, give up rather than adding the same non-working
272 nodes to the directory guard list over and over. Fixes bug 8231;
273 bugfix on 0.2.4.8-alpha.
276 - Reject as invalid most directory objects containing a NUL.
277 Belt-and-suspender fix for bug 8037.
278 - In our testsuite, create temporary directories with a bit more
279 entropy in their name to make name collisions less likely. Fixes
281 - Add CACHED keyword to ADDRMAP events in the control protocol
282 to indicate whether a DNS result will be cached or not. Resolves
284 - Update to the April 3 2013 Maxmind GeoLite Country database.
286 o Minor features (build):
287 - Detect and reject attempts to build Tor with threading support
288 when OpenSSL has been compiled without threading support.
290 - Clarify that when autoconf is checking for nacl, it is checking
291 specifically for nacl with a fast curve25519 implementation.
293 - Warn if building on a platform with an unsigned time_t: there
294 are too many places where Tor currently assumes that time_t can
295 hold negative values. We'd like to fix them all, but probably
298 o Minor bugfixes (build):
299 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
300 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
301 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
302 - Add the old src/or/micro-revision.i filename to CLEANFILES.
303 On the off chance that somebody has one, it will go away as soon
304 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
305 - Build Tor correctly on 32-bit platforms where the compiler can build
306 but not run code using the "uint128_t" construction. Fixes bug 8587;
307 bugfix on 0.2.4.8-alpha.
308 - Fix compilation warning with some versions of clang that would
309 prefer the -Wswitch-enum compiler flag to warn about switch
310 statements with missing enum values, even if those switch
311 statements have a "default:" statement. Fixes bug 8598; bugfix
314 o Minor bugfixes (protocol):
315 - Fix the handling of a TRUNCATE cell when it arrives while the
316 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
317 - Fix a misframing issue when reading the version numbers in a
318 VERSIONS cell. Previously we would recognize [00 01 00 02] as
319 'version 1, version 2, and version 0x100', when it should have
320 only included versions 1 and 2. Fixes bug 8059; bugfix on
321 0.2.0.10-alpha. Reported pseudonymously.
322 - Make the format and order of STREAM events for DNS lookups
323 consistent among the various ways to launch DNS lookups. Fixes
324 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
325 - Correct our check for which versions of Tor support the EXTEND2
326 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
327 later, when support was really added in version 0.2.4.8-alpha.
328 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
330 o Minor bugfixes (other):
331 - Correctly store microdescriptors and extrainfo descriptors with
332 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
333 Bug reported by "cypherpunks".
334 - Increase the width of the field used to remember a connection's
335 link protocol version to two bytes. Harmless for now, since the
336 only currently recognized versions are one byte long. Reported
337 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
338 - If the state file's path bias counts are invalid (presumably from a
339 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
340 additional checks and log messages to the scaling of Path Bias
341 counts, in case there still are remaining issues with scaling.
342 Should help resolve bug 8235.
343 - Eliminate several instances where we use "Nickname=ID" to refer to
344 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
345 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
346 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
348 o Minor bugfixes (syscalls):
349 - Always check the return values of functions fcntl() and
350 setsockopt(). We don't believe these are ever actually failing in
351 practice, but better safe than sorry. Also, checking these return
352 values should please analysis tools like Coverity. Patch from
353 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
354 - Use direct writes rather than stdio when building microdescriptor
355 caches, in an attempt to mitigate bug 8031, or at least make it
358 o Minor bugfixes (config):
359 - When rejecting a configuration because we were unable to parse a
360 quoted string, log an actual error message. Fixes bug 7950; bugfix
362 - Behave correctly when the user disables LearnCircuitBuildTimeout
363 but doesn't tell us what they would like the timeout to be. Fixes
364 bug 6304; bugfix on 0.2.2.14-alpha.
365 - When autodetecting the number of CPUs, use the number of available
366 CPUs in preference to the number of configured CPUs. Inform the
367 user if this reduces the number of available CPUs. Fixes bug 8002;
368 bugfix on 0.2.3.1-alpha.
369 - Make it an error when you set EntryNodes but disable UseGuardNodes,
370 since it will (surprisingly to some users) ignore EntryNodes. Fixes
371 bug 8180; bugfix on 0.2.3.11-alpha.
372 - Allow TestingTorNetworks to override the 4096-byte minimum for
373 the Fast threshold. Otherwise they can't bootstrap until they've
374 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
375 - Fix some logic errors when the user manually overrides the
376 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
379 o Minor bugfixes (log messages to help diagnose bugs):
380 - If we fail to free a microdescriptor because of bug 7164, log
381 the filename and line number from which we tried to free it.
382 - Add another diagnostic to the heartbeat message: track and log
383 overhead that TLS is adding to the data we write. If this is
384 high, we are sending too little data to SSL_write at a time.
385 Diagnostic for bug 7707.
386 - Add more detail to a log message about relaxed timeouts, to help
388 - Warn more aggressively when flushing microdescriptors to a
389 microdescriptor cache fails, in an attempt to mitigate bug 8031,
390 or at least make it more diagnosable.
391 - Improve debugging output to help track down bug 8185 ("Bug:
392 outgoing relay cell has n_chan==NULL. Dropping.")
393 - Log the purpose of a path-bias testing circuit correctly.
394 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
396 o Minor bugfixes (0.2.4.x log messages that were too noisy):
397 - Don't attempt to relax the timeout of already opened 1-hop circuits.
398 They might never timeout. This should eliminate some/all cases of
399 the relaxed timeout log message.
400 - Use circuit creation time for network liveness evaluation. This
401 should eliminate warning log messages about liveness caused
402 by changes in timeout evaluation. Fixes bug 6572; bugfix on
404 - Reduce a path bias length check from notice to info. The message
405 is triggered when creating controller circuits. Fixes bug 8196;
406 bugfix on 0.2.4.8-alpha.
407 - Fix a path state issue that triggered a notice during relay startup.
408 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
409 - Reduce occurrences of warns about circuit purpose in
410 connection_ap_expire_building(). Fixes bug 8477; bugfix on
413 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
414 - If we encounter a write failure on a SOCKS connection before we
415 finish our SOCKS handshake, don't warn that we closed the
416 connection before we could send a SOCKS reply. Fixes bug 8427;
417 bugfix on 0.1.0.1-rc.
418 - Correctly recognize that [::1] is a loopback address. Fixes
419 bug 8377; bugfix on 0.2.1.3-alpha.
420 - Fix a directory authority warn caused when we have a large amount
421 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
422 - Don't log inappropriate heartbeat messages when hibernating: a
423 hibernating node is _expected_ to drop out of the consensus,
424 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
425 bugfix on 0.2.3.1-alpha.
426 - Don't complain about bootstrapping problems while hibernating.
427 These complaints reflect a general code problem, but not one
428 with any problematic effects (no connections are actually
429 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
431 o Documentation fixes:
432 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
433 names match. Fixes bug 7768.
434 - Make the torify manpage no longer refer to tsocks; torify hasn't
435 supported tsocks since 0.2.3.14-alpha.
436 - Make the tor manpage no longer reference tsocks.
437 - Fix the GeoIPExcludeUnknown documentation to refer to
438 ExcludeExitNodes rather than the currently nonexistent
439 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
442 - The tor-tsocks.conf is no longer distributed or installed. We
443 recommend that tsocks users use torsocks instead. Resolves
447 Changes in version 0.2.4.11-alpha - 2013-03-11
448 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
449 more robust, makes hidden service authentication work again, and
450 resolves a DPI fingerprint for Tor's SSL transport.
452 o Major features (directory authorities):
453 - Directory authorities now support a new consensus method (17)
454 where they cap the published bandwidth of servers for which
455 insufficient bandwidth measurements exist. Fixes part of bug 2286.
456 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
457 serve any v2 directory information. Now we can test disabling the
458 old deprecated v2 directory format, and see whether doing so has
459 any effect on network load. Begins to fix bug 6783.
460 - Directory authorities now include inside each vote a statement of
461 the performance thresholds they used when assigning flags.
462 Implements ticket 8151.
464 o Major bugfixes (directory authorities):
465 - Stop marking every relay as having been down for one hour every
466 time we restart a directory authority. These artificial downtimes
467 were messing with our Stable and Guard flag calculations. Fixes
468 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
470 o Major bugfixes (hidden services):
471 - Allow hidden service authentication to succeed again. When we
472 refactored the hidden service introduction code back
473 in 0.2.4.1-alpha, we didn't update the code that checks
474 whether authentication information is present, causing all
475 authentication checks to return "false". Fix for bug 8207; bugfix
476 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
478 o Minor features (relays, bridges):
479 - Make bridge relays check once a minute for whether their IP
480 address has changed, rather than only every 15 minutes. Resolves
482 - Refactor resolve_my_address() so it returns the method by which we
483 decided our public IP address (explicitly configured, resolved from
484 explicit hostname, guessed from interfaces, learned by gethostname).
485 Now we can provide more helpful log messages when a relay guesses
486 its IP address incorrectly (e.g. due to unexpected lines in
487 /etc/hosts). Resolves ticket 2267.
488 - Teach bridge-using clients to avoid 0.2.2 bridges when making
489 microdescriptor-related dir requests, and only fall back to normal
490 descriptors if none of their bridges can handle microdescriptors
491 (as opposed to the fix in ticket 4013, which caused them to fall
492 back to normal descriptors if *any* of their bridges preferred
493 them). Resolves ticket 4994.
494 - Randomize the lifetime of our SSL link certificate, so censors can't
495 use the static value for filtering Tor flows. Resolves ticket 8443;
496 related to ticket 4014 which was included in 0.2.2.33.
498 o Minor features (portability):
499 - Tweak the curve25519-donna*.c implementations to tolerate systems
500 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
501 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
502 the signs of types during autoconf. This is better than our old
503 approach, which didn't work when cross-compiling.
504 - Detect the sign of enum values, rather than assuming that MSC is the
505 only compiler where enum types are all signed. Fixes bug 7727;
506 bugfix on 0.2.4.10-alpha.
508 o Minor features (other):
509 - Say "KBytes" rather than "KB" in the man page (for various values
510 of K), to further reduce confusion about whether Tor counts in
511 units of memory or fractions of units of memory. Resolves ticket 7054.
512 - Clear the high bit on curve25519 public keys before passing them to
513 our backend, in case we ever wind up using a backend that doesn't do
514 so itself. If we used such a backend, and *didn't* clear the high bit,
515 we could wind up in a situation where users with such backends would
516 be distinguishable from users without. Fixes bug 8121; bugfix on
518 - Update to the March 6 2013 Maxmind GeoLite Country database.
520 o Minor bugfixes (clients):
521 - When we receive a RELAY_END cell with the reason DONE, or with no
522 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
523 status as "connection refused". Previously we reported these cases
524 as success but then immediately closed the connection. Fixes bug
525 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
526 - Downgrade an assertion in connection_ap_expire_beginning to an
527 LD_BUG message. The fix for bug 8024 should prevent this message
528 from displaying, but just in case, a warn that we can diagnose
529 is better than more assert crashes. Fixes bug 8065; bugfix on
531 - Lower path use bias thresholds to .80 for notice and .60 for warn.
532 Also make the rate limiting flags for the path use bias log messages
533 independent from the original path bias flags. Fixes bug 8161;
534 bugfix on 0.2.4.10-alpha.
536 o Minor bugfixes (relays):
537 - Stop trying to resolve our hostname so often (e.g. every time we
538 think about doing a directory fetch). Now we reuse the cached
539 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
540 and 2410 (bugfix on 0.1.2.2-alpha).
541 - Stop sending a stray "(null)" in some cases for the server status
542 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
544 - When choosing which stream on a formerly stalled circuit to wake
545 first, make better use of the platform's weak RNG. Previously,
546 we had been using the % ("modulo") operator to try to generate a
547 1/N chance of picking each stream, but this behaves badly with
548 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
550 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
551 Irix's random() only return 15 bits; Solaris's random() returns more
552 bits but its RAND_MAX says it only returns 15, and so on. Motivated
553 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
555 o Minor bugfixes (directory authorities):
556 - Directory authorities now use less space when formatting identical
557 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
560 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
561 - Avoid leaking memory if we fail to compute a consensus signature
562 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
563 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
565 - Fix a memory leak during safe-cookie controller authentication.
566 Bugfix on 0.2.3.13-alpha.
567 - Avoid memory leak of IPv6 policy content if we fail to format it into
568 a router descriptor. Bugfix on 0.2.4.7-alpha.
570 o Minor bugfixes (other code correctness issues):
571 - Avoid a crash if we fail to generate an extrainfo descriptor.
572 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
574 - When detecting the largest possible file descriptor (in order to
575 close all file descriptors when launching a new program), actually
576 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
577 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
579 - Fix a copy-and-paste error when adding a missing A1 to a routerset
580 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
581 Bugfix on 0.2.4.10-alpha.
582 - Fix an impossible-to-trigger integer overflow when estimating how
583 long our onionskin queue would take. (This overflow would require us
584 to accept 4 million onionskins before processing 100 of them.) Fixes
585 bug 8210; bugfix on 0.2.4.10-alpha.
587 o Code simplification and refactoring:
588 - Add a wrapper function for the common "log a message with a
592 Changes in version 0.2.4.10-alpha - 2013-02-04
593 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
594 certain attacks that flood the network with relays; changes the queue
595 for circuit create requests from a sized-based limit to a time-based
596 limit; resumes building with MSVC on Windows; and fixes a wide variety
599 o Major bugfixes (directory authority):
600 - When computing directory thresholds, ignore any rejected-as-sybil
601 nodes during the computation so that they can't influence Fast,
602 Guard, etc. (We should have done this for proposal 109.) Fixes
604 - When marking a node as a likely sybil, reset its uptime metrics
605 to zero, so that it cannot time towards getting marked as Guard,
606 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
610 - When a TLS write is partially successful but incomplete, remember
611 that the flushed part has been flushed, and notice that bytes were
612 actually written. Reported and fixed pseudonymously. Fixes bug
613 7708; bugfix on Tor 0.1.0.5-rc.
614 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
615 ID: these could be used to create unexpected streams and circuits
616 which would count as "present" to some parts of Tor but "absent"
617 to others, leading to zombie circuits and streams or to a bandwidth
618 denial-of-service. Fixes bug 7889; bugfix on every released version
619 of Tor. Reported by "oftc_must_be_destroyed".
620 - Rename all macros in our local copy of queue.h to begin with "TOR_".
621 This change seems the only good way to permanently prevent conflicts
622 with queue.h on various operating systems. Fixes bug 8107; bugfix
625 o Major features (relay):
626 - Instead of limiting the number of queued onionskins (aka circuit
627 create requests) to a fixed, hard-to-configure number, we limit
628 the size of the queue based on how many we expect to be able to
629 process in a given amount of time. We estimate the time it will
630 take to process an onionskin based on average processing time
631 of previous onionskins. Closes ticket 7291. You'll never have to
632 configure MaxOnionsPending again.
634 o Major features (portability):
635 - Resume building correctly with MSVC and Makefile.nmake. This patch
636 resolves numerous bugs and fixes reported by ultramage, including
637 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
638 - Make the ntor and curve25519 code build correctly with MSVC.
639 Fix on 0.2.4.8-alpha.
642 - When directory authorities are computing thresholds for flags,
643 never let the threshold for the Fast flag fall below 4096
644 bytes. Also, do not consider nodes with extremely low bandwidths
645 when deciding thresholds for various directory flags. This change
646 should raise our threshold for Fast relays, possibly in turn
647 improving overall network performance; see ticket 1854. Resolves
649 - The Tor client now ignores sub-domain components of a .onion
650 address. This change makes HTTP "virtual" hosting
651 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
652 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
653 hosted on the same hidden service. Implements proposal 204.
654 - We compute the overhead from passing onionskins back and forth to
655 cpuworkers, and report it when dumping statistics in response to
656 SIGUSR1. Supports ticket 7291.
658 o Minor features (path selection):
659 - When deciding whether we have enough descriptors to build circuits,
660 instead of looking at raw relay counts, look at which fraction
661 of (bandwidth-weighted) paths we're able to build. This approach
662 keeps clients from building circuits if their paths are likely to
663 stand out statistically. The default fraction of paths needed is
664 taken from the consensus directory; you can override it with the
665 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
666 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
667 and we have GeoIP information, also exclude all nodes with unknown
668 countries "??" and "A1". This behavior is controlled by the
669 new GeoIPExcludeUnknown option: you can make such nodes always
670 excluded with "GeoIPExcludeUnknown 1", and disable the feature
671 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
672 gets you the default behavior. Implements feature 7706.
673 - Path Use Bias: Perform separate accounting for successful circuit
674 use. Keep separate statistics on stream attempt rates versus stream
675 success rates for each guard. Provide configurable thresholds to
676 determine when to emit log messages or disable use of guards that
677 fail too many stream attempts. Resolves ticket 7802.
679 o Minor features (log messages):
680 - When learning a fingerprint for a bridge, log its corresponding
681 transport type. Implements ticket 7896.
682 - Improve the log message when "Bug/attack: unexpected sendme cell
683 from client" occurs, to help us track bug 8093.
686 - Remove a couple of extraneous semicolons that were upsetting the
687 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
688 bugfix on 0.2.2.1-alpha.
689 - Remove a source of rounding error during path bias count scaling;
690 don't count cannibalized circuits as used for path bias until we
691 actually try to use them; and fix a circuit_package_relay_cell()
692 warning message about n_chan==NULL. Fixes bug 7802.
693 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
694 actually link against nacl when we're configured to use it. Fixes
695 bug 7972; bugfix on 0.2.4.8-alpha.
696 - Compile correctly with the --disable-curve25519 option. Fixes
697 bug 8153; bugfix on 0.2.4.8-alpha.
699 o Build improvements:
700 - Do not report status verbosely from autogen.sh unless the -v flag
701 is specified. Fixes issue 4664. Patch from Onizuka.
702 - Replace all calls to snprintf() outside of src/ext with
703 tor_snprintf(). Also remove the #define to replace snprintf with
704 _snprintf on Windows; they have different semantics, and all of
705 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
706 - Try to detect if we are ever building on a platform where
707 memset(...,0,...) does not set the value of a double to 0.0. Such
708 platforms are permitted by the C standard, though in practice
709 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
710 currently support them, but it's better to detect them and fail
711 than to perform erroneously.
714 - Stop exporting estimates of v2 and v3 directory traffic shares
715 in extrainfo documents. They were unneeded and sometimes inaccurate.
716 Also stop exporting any v2 directory request statistics. Resolves
718 - Drop support for detecting and warning about versions of Libevent
719 before 1.3e. Nothing reasonable ships with them any longer;
720 warning the user about them shouldn't be needed. Resolves ticket
723 o Code simplifications and refactoring:
724 - Rename "isin" functions to "contains", for grammar. Resolves
726 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
727 with the natural logarithm function from the system libm. Resolves
731 Changes in version 0.2.4.9-alpha - 2013-01-15
732 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
736 - Fix backward compatibility logic when receiving an embedded ntor
737 handshake tunneled in a CREATE cell. This clears up the "Bug:
738 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
742 Changes in version 0.2.4.8-alpha - 2013-01-14
743 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
744 risks, adds a new stronger and faster circuit handshake, and offers
745 stronger and faster link encryption when both sides support it.
748 - Preliminary support for directory guards (proposal 207): when
749 possible, clients now use their entry guards for non-anonymous
750 directory requests. This can help prevent client enumeration. Note
751 that this behavior only works when we have a usable consensus
752 directory, and when options about what to download are more or less
753 standard. In the future we should re-bootstrap from our guards,
754 rather than re-bootstrapping from the preconfigured list of
755 directory sources that ships with Tor. Resolves ticket 6526.
756 - Tor relays and clients now support a better CREATE/EXTEND cell
757 format, allowing the sender to specify multiple address, identity,
758 and handshake types. Implements Robert Ransom's proposal 200;
761 o Major features (new circuit handshake):
762 - Tor now supports a new circuit extension handshake designed by Ian
763 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
764 circuit extension handshake, later called "TAP", was a bit slow
765 (especially on the relay side), had a fragile security proof, and
766 used weaker keys than we'd now prefer. The new circuit handshake
767 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
768 function, making it significantly more secure than the older
769 handshake, and significantly faster. Tor can use one of two built-in
770 pure-C curve25519-donna implementations by Adam Langley, or it
771 can link against the "nacl" library for a tuned version if present.
773 The built-in version is very fast for 64-bit systems when building
774 with GCC. The built-in 32-bit version is still faster than the
775 old TAP protocol, but using libnacl is better on most such hosts.
777 Clients don't currently use this protocol by default, since
778 comparatively few clients support it so far. To try it, set
779 UseNTorHandshake to 1.
781 Implements proposal 216; closes ticket 7202.
783 o Major features (better link encryption):
784 - Relays can now enable the ECDHE TLS ciphersuites when available
785 and appropriate. These ciphersuites let us negotiate forward-secure
786 TLS secret keys more safely and more efficiently than with our
787 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
788 public relays prefer the (faster) P224 group, and bridges prefer
789 the (more common) P256 group; you can override this with the
792 Enabling these ciphers was a little tricky, since for a long time,
793 clients had been claiming to support them without actually doing
794 so, in order to foil fingerprinting. But with the client-side
795 implementation of proposal 198 in 0.2.3.17-beta, clients can now
796 match the ciphers from recent Firefox versions *and* list the
797 ciphers they actually mean, so relays can believe such clients
798 when they advertise ECDHE support in their TLS ClientHello messages.
800 This feature requires clients running 0.2.3.17-beta or later,
801 and requires both sides to be running OpenSSL 1.0.0 or later
802 with ECC support. OpenSSL 1.0.1, with the compile-time option
803 "enable-ec_nistp_64_gcc_128", is highly recommended.
805 Implements the relay side of proposal 198; closes ticket 7200.
808 - Avoid crashing when, as a relay without IPv6-exit support, a
809 client insists on getting an IPv6 address or nothing. Fixes bug
810 7814; bugfix on 0.2.4.7-alpha.
813 - Improve circuit build timeout handling for hidden services.
814 In particular: adjust build timeouts more accurately depending
815 upon the number of hop-RTTs that a particular circuit type
816 undergoes. Additionally, launch intro circuits in parallel
817 if they timeout, and take the first one to reply as valid.
818 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
819 separate error codes; or at least, don't break for that reason.
820 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
821 - Update to the January 2 2013 Maxmind GeoLite Country database.
823 o Minor features (testing):
824 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
825 (P-256) Diffie-Hellman handshakes to src/or/bench.
826 - Add benchmark functions to test onion handshake performance.
828 o Minor features (path bias detection):
829 - Alter the Path Bias log messages to be more descriptive in terms
830 of reporting timeouts and other statistics.
831 - Create three levels of Path Bias log messages, as opposed to just
832 two. These are configurable via consensus as well as via the torrc
833 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
834 The default values are 0.70, 0.50, and 0.30 respectively.
835 - Separate the log message levels from the decision to drop guards,
836 which also is available via torrc option PathBiasDropGuards.
837 PathBiasDropGuards still defaults to 0 (off).
838 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
839 in combination with PathBiasExtremeRate.
840 - Increase the default values for PathBiasScaleThreshold and
841 PathBiasCircThreshold from (200, 20) to (300, 150).
842 - Add in circuit usage accounting to path bias. If we try to use a
843 built circuit but fail for any reason, it counts as path bias.
844 Certain classes of circuits where the adversary gets to pick your
845 destination node are exempt from this accounting. Usage accounting
846 can be specifically disabled via consensus parameter or torrc.
847 - Convert all internal path bias state to double-precision floating
848 point, to avoid roundoff error and other issues.
849 - Only record path bias information for circuits that have completed
850 *two* hops. Assuming end-to-end tagging is the attack vector, this
851 makes us more resilient to ambient circuit failure without any
852 detection capability loss.
854 o Minor bugfixes (log messages):
855 - Rate-limit the "No circuits are opened. Relaxed timeout for a
856 circuit with channel state open..." message to once per hour to
857 keep it from filling the notice logs. Mitigates bug 7799 but does
858 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
859 - Avoid spurious warnings when configuring multiple client ports of
860 which only some are nonlocal. Previously, we had claimed that some
861 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
864 o Code simplifications and refactoring:
865 - Get rid of a couple of harmless clang warnings, where we compared
866 enums to ints. These warnings are newly introduced in clang 3.2.
867 - Split the onion.c file into separate modules for the onion queue
868 and the different handshakes it supports.
869 - Remove the marshalling/unmarshalling code for sending requests to
870 cpuworkers over a socket, and instead just send structs. The
871 recipient will always be the same Tor binary as the sender, so
872 any encoding is overkill.
875 Changes in version 0.2.4.7-alpha - 2012-12-24
876 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
877 directory mirrors for more robust bootstrapping; fixes more issues where
878 clients with changing network conditions refuse to make any circuits;
879 adds initial support for exiting to IPv6 addresses; resumes being able
880 to update our GeoIP database, and includes the geoip6 file this time;
881 turns off the client-side DNS cache by default due to privacy risks;
882 and fixes a variety of other issues.
884 o Major features (client resilience):
885 - Add a new "FallbackDir" torrc option to use when we can't use
886 a directory mirror from the consensus (either because we lack a
887 consensus, or because they're all down). Currently, all authorities
888 are fallbacks by default, and there are no other default fallbacks,
889 but that will change. This option will allow us to give clients a
890 longer list of servers to try to get a consensus from when first
891 connecting to the Tor network, and thereby reduce load on the
892 directory authorities. Implements proposal 206, "Preconfigured
893 directory sources for bootstrapping". We also removed the old
894 "FallbackNetworkstatus" option, since we never got it working well
895 enough to use it. Closes bug 572.
896 - If we have no circuits open, use a relaxed timeout (the
897 95-percentile cutoff) until a circuit succeeds. This heuristic
898 should allow Tor to succeed at building circuits even when the
899 network connection drastically changes. Should help with bug 3443.
901 o Major features (IPv6):
902 - Tor now has (alpha) support for exiting to IPv6 addresses. To
903 enable it as an exit node, make sure that you have IPv6
904 connectivity, then set the IPv6Exit flag to 1. Also make sure your
905 exit policy reads as you would like: the address * applies to all
906 address families, whereas *4 is IPv4 address only, and *6 is IPv6
907 addresses only. On the client side, you'll need to wait until the
908 authorities have upgraded, wait for enough exits to support IPv6,
909 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
910 ticket 5547, implements proposal 117 as revised in proposal 208.
912 We DO NOT recommend that clients with actual anonymity needs start
913 using IPv6 over Tor yet, since not enough exits support it yet.
915 o Major features (geoip database):
916 - Maxmind began labelling Tor relays as being in country "A1",
917 which breaks by-country node selection inside Tor. Now we use a
918 script to replace "A1" ("Anonymous Proxy") entries in our geoip
919 file with real country codes. This script fixes about 90% of "A1"
920 entries automatically and uses manual country code assignments to
921 fix the remaining 10%. See src/config/README.geoip for details.
922 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
923 Country database, as modified above.
925 o Major bugfixes (client-side DNS):
926 - Turn off the client-side DNS cache by default. Updating and using
927 the DNS cache is now configurable on a per-client-port
928 level. SOCKSPort, DNSPort, etc lines may now contain
929 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
930 cache these types of DNS answers when we receive them from an
931 exit node in response to an application request on this port, and
932 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
933 cached DNS answers of these types, we shouldn't use them. It's
934 potentially risky to use cached DNS answers at the client, since
935 doing so can indicate to one exit what answers we've gotten
936 for DNS lookups in the past. With IPv6, this becomes especially
937 problematic. Using cached DNS answers for requests on the same
938 circuit would present less linkability risk, since all traffic
939 on a circuit is already linkable, but it would also provide
940 little performance benefit: the exit node caches DNS replies
941 too. Implements a simplified version of Proposal 205. Implements
944 o Major bugfixes (other):
945 - Alter circuit build timeout measurement to start at the point
946 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
947 initialization). This should make our timeout measurements more
948 uniform. Previously, we were sometimes including ORconn setup time
949 in our circuit build time measurements. Should resolve bug 3443.
950 - Fix an assertion that could trigger in hibernate_go_dormant() when
951 closing an or_connection_t: call channel_mark_for_close() rather
952 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
954 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
955 7655; bugfix on 0.2.4.6-alpha.
958 - Add a new torrc option "ServerTransportListenAddr" to let bridge
959 operators select the address where their pluggable transports will
960 listen for connections. Resolves ticket 7013.
961 - Allow an optional $ before the node identity digest in the
962 controller command GETINFO ns/id/<identity>, for consistency with
963 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
964 - Log packaged cell fullness as part of the heartbeat message.
965 Diagnosis to try to determine the extent of bug 7743.
967 o Minor features (IPv6):
968 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
969 prefer to hand out virtual IPv6 addresses, since there are more of
970 them and we can't run out. To override this behavior and make IPv4
971 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
972 or DNSPort you're using for resolving. Implements ticket 7571.
973 - AutomapHostsOnResolve responses are now randomized, to avoid
974 annoying situations where Tor is restarted and applications
975 connect to the wrong addresses.
976 - Never try more than 1000 times to pick a new virtual address when
977 AutomapHostsOnResolve is set. That's good enough so long as we
978 aren't close to handing out our entire virtual address space;
979 if you're getting there, it's best to switch to IPv6 virtual
983 - The ADDRMAP command can no longer generate an ill-formed error
984 code on a failed MAPADDRESS. It now says "internal" rather than
985 an English sentence fragment with spaces in the middle. Bugfix on
987 - Fix log messages and comments to avoid saying "GMT" when we mean
988 "UTC". Fixes bug 6113.
989 - Compile on win64 using mingw64. Fixes bug 7260; patches from
991 - Fix a crash when debugging unit tests on Windows: deallocate a
992 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
993 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
996 - The DirServer option is now DirAuthority, for consistency with
997 current naming patterns. You can still use the old DirServer form.
999 o Code simplification and refactoring:
1000 - Move the client-side address-map/virtual-address/DNS-cache code
1001 out of connection_edge.c into a new addressmap.c module.
1002 - Remove unused code for parsing v1 directories and "running routers"
1003 documents. Fixes bug 6887.
1006 Changes in version 0.2.3.25 - 2012-11-19
1007 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1008 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1009 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1010 programmer, and friend. Unstinting in his dedication to the cause of
1011 freedom, he inspired and helped many of us as we began our work on
1012 anonymity, and inspires us still. Please honor his memory by writing
1013 software to protect people's freedoms, and by helping others to do so.
1015 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1016 significantly reduced directory overhead (via microdescriptors),
1017 enormous crypto performance improvements for fast relays on new
1018 enough hardware, a new v3 TLS handshake protocol that can better
1019 resist fingerprinting, support for protocol obfuscation plugins (aka
1020 pluggable transports), better scalability for hidden services, IPv6
1021 support for bridges, performance improvements like allowing clients
1022 to skip the first round-trip on the circuit ("optimistic data") and
1023 refilling token buckets more often, a new "stream isolation" design
1024 to isolate different applications on different circuits, and many
1025 stability, security, and privacy fixes.
1028 - Tor tries to wipe potentially sensitive data after using it, so
1029 that if some subsequent security failure exposes Tor's memory,
1030 the damage will be limited. But we had a bug where the compiler
1031 was eliminating these wipe operations when it decided that the
1032 memory was no longer visible to a (correctly running) program,
1033 hence defeating our attempt at defense in depth. We fix that
1034 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1035 is unlikely to optimize away. Future versions of Tor may use
1036 a less ridiculously heavy approach for this. Fixes bug 7352.
1037 Reported in an article by Andrey Karpov.
1040 - Fix a harmless bug when opting against publishing a relay descriptor
1041 because DisableNetwork is set. Fixes bug 7464; bugfix on
1045 Changes in version 0.2.4.6-alpha - 2012-11-13
1046 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1047 makes our defense-in-depth memory wiping more reliable, and begins to
1048 count IPv6 addresses in bridge statistics,
1051 - Fix an assertion failure that could occur when closing a connection
1052 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1054 - Tor tries to wipe potentially sensitive data after using it, so
1055 that if some subsequent security failure exposes Tor's memory,
1056 the damage will be limited. But we had a bug where the compiler
1057 was eliminating these wipe operations when it decided that the
1058 memory was no longer visible to a (correctly running) program,
1059 hence defeating our attempt at defense in depth. We fix that
1060 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1061 is unlikely to optimize away. Future versions of Tor may use
1062 a less ridiculously heavy approach for this. Fixes bug 7352.
1063 Reported in an article by Andrey Karpov.
1066 - Add GeoIP database for IPv6 addresses. The new config option
1068 - Bridge statistics now count bridge clients connecting over IPv6:
1069 bridge statistics files now list "bridge-ip-versions" and
1070 extra-info documents list "geoip6-db-digest". The control protocol
1071 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1072 implementation by "shkoo", addressing ticket 5055.
1075 - Warn when we are binding low ports when hibernation is enabled;
1076 previously we had warned when we were _advertising_ low ports with
1077 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1078 - Fix a harmless bug when opting against publishing a relay descriptor
1079 because DisableNetwork is set. Fixes bug 7464; bugfix on
1081 - Add warning message when a managed proxy dies during configuration.
1082 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1083 - Fix a linking error when building tor-fw-helper without miniupnp.
1084 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1085 - Check for closing an or_connection_t without going through correct
1086 channel functions; emit a warning and then call
1087 connection_or_close_for_error() so we don't assert as in bugs 7212
1089 - Compile correctly on compilers without C99 designated initializer
1090 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1091 - Avoid a possible assert that can occur when channel_send_destroy() is
1092 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1093 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1094 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1095 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1096 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1098 o Code simplification and refactoring:
1099 - Start using OpenBSD's implementation of queue.h, so that we don't
1100 need to hand-roll our own pointer and list structures whenever we
1101 need them. (We can't rely on a sys/queue.h, since some operating
1102 systems don't have them, and the ones that do have them don't all
1103 present the same extensions.)
1106 Changes in version 0.2.4.5-alpha - 2012-10-25
1107 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1108 two important security vulnerabilities that could lead to remotely
1109 triggerable relay crashes, fix a major bug that was preventing clients
1110 from choosing suitable exit nodes, and refactor some of our code.
1112 o Major bugfixes (security, also in 0.2.3.24-rc):
1113 - Fix a group of remotely triggerable assertion failures related to
1114 incorrect link protocol negotiation. Found, diagnosed, and fixed
1115 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1117 - Fix a denial of service attack by which any directory authority
1118 could crash all the others, or by which a single v2 directory
1119 authority could crash everybody downloading v2 directory
1120 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1122 o Major bugfixes (also in 0.2.3.24-rc):
1123 - When parsing exit policy summaries from microdescriptors, we had
1124 previously been ignoring the last character in each one, so that
1125 "accept 80,443,8080" would be treated by clients as indicating
1126 a node that allows access to ports 80, 443, and 808. That would
1127 lead to clients attempting connections that could never work,
1128 and ignoring exit nodes that would support their connections. Now
1129 clients parse these exit policy summaries correctly. Fixes bug 7192;
1130 bugfix on 0.2.3.1-alpha.
1132 o Minor bugfixes (also in 0.2.3.24-rc):
1133 - Clients now consider the ClientRejectInternalAddresses config option
1134 when using a microdescriptor consensus stanza to decide whether
1135 an exit relay would allow exiting to an internal address. Fixes
1136 bug 7190; bugfix on 0.2.3.1-alpha.
1139 - Only disable TLS session ticket support when running as a TLS
1140 server. Now clients will blend better with regular Firefox
1141 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1143 o Code simplification and refactoring:
1144 - Start using OpenBSD's implementation of queue.h (originally by
1146 - Move the entry node code from circuitbuild.c to its own file.
1147 - Move the circuit build timeout tracking code from circuitbuild.c
1151 Changes in version 0.2.3.24-rc - 2012-10-25
1152 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1153 could lead to remotely triggerable relay crashes, and fixes
1154 a major bug that was preventing clients from choosing suitable exit
1157 o Major bugfixes (security):
1158 - Fix a group of remotely triggerable assertion failures related to
1159 incorrect link protocol negotiation. Found, diagnosed, and fixed
1160 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1162 - Fix a denial of service attack by which any directory authority
1163 could crash all the others, or by which a single v2 directory
1164 authority could crash everybody downloading v2 directory
1165 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1168 - When parsing exit policy summaries from microdescriptors, we had
1169 previously been ignoring the last character in each one, so that
1170 "accept 80,443,8080" would be treated by clients as indicating
1171 a node that allows access to ports 80, 443, and 808. That would
1172 lead to clients attempting connections that could never work,
1173 and ignoring exit nodes that would support their connections. Now
1174 clients parse these exit policy summaries correctly. Fixes bug 7192;
1175 bugfix on 0.2.3.1-alpha.
1178 - Clients now consider the ClientRejectInternalAddresses config option
1179 when using a microdescriptor consensus stanza to decide whether
1180 an exit relay would allow exiting to an internal address. Fixes
1181 bug 7190; bugfix on 0.2.3.1-alpha.
1184 Changes in version 0.2.4.4-alpha - 2012-10-20
1185 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1186 vulnerability introduced by a change in OpenSSL, fixes a remotely
1187 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1188 that will make it easier to test new connection transport and cell
1189 scheduling algorithms.
1191 o New directory authorities (also in 0.2.3.23-rc):
1192 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1193 authority. Closes ticket 5749.
1195 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1196 - Disable TLS session tickets. OpenSSL's implementation was giving
1197 our TLS session keys the lifetime of our TLS context objects, when
1198 perfect forward secrecy would want us to discard anything that
1199 could decrypt a link connection as soon as the link connection
1200 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1201 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1202 - Discard extraneous renegotiation attempts once the V3 link
1203 protocol has been initiated. Failure to do so left us open to
1204 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1205 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1207 o Internal abstraction features:
1208 - Introduce new channel_t abstraction between circuits and
1209 or_connection_t to allow for implementing alternate OR-to-OR
1210 transports. A channel_t is an abstract object which can either be a
1211 cell-bearing channel, which is responsible for authenticating and
1212 handshaking with the remote OR and transmitting cells to and from
1213 it, or a listening channel, which spawns new cell-bearing channels
1214 at the request of remote ORs. Implements part of ticket 6465.
1215 - Also new is the channel_tls_t subclass of channel_t, adapting it
1216 to the existing or_connection_t code. The V2/V3 protocol handshaking
1217 code which formerly resided in command.c has been moved below the
1218 channel_t abstraction layer and may be found in channeltls.c now.
1219 Implements the rest of ticket 6465.
1220 - Introduce new circuitmux_t storing the queue of circuits for
1221 a channel; this encapsulates and abstracts the queue logic and
1222 circuit selection policy, and allows the latter to be overridden
1223 easily by switching out a policy object. The existing EWMA behavior
1224 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1226 o Required libraries:
1227 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1228 strongly recommended.
1231 - Warn users who run hidden services on a Tor client with
1232 UseEntryGuards disabled that their hidden services will be
1233 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1234 attack which motivated Tor to support entry guards in the first
1235 place). Resolves ticket 6889.
1236 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1237 dhill. Resolves ticket 6982.
1238 - Option OutboundBindAddress can be specified multiple times and
1239 accepts IPv6 addresses. Resolves ticket 6876.
1241 o Minor bugfixes (also in 0.2.3.23-rc):
1242 - Don't serve or accept v2 hidden service descriptors over a
1243 relay's DirPort. It's never correct to do so, and disabling it
1244 might make it more annoying to exploit any bugs that turn up in the
1245 descriptor-parsing code. Fixes bug 7149.
1246 - Fix two cases in src/or/transports.c where we were calling
1247 fmt_addr() twice in a parameter list. Bug found by David
1248 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1249 - Fix memory leaks whenever we logged any message about the "path
1250 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1251 - When relays refuse a "create" cell because their queue of pending
1252 create cells is too big (typically because their cpu can't keep up
1253 with the arrival rate), send back reason "resource limit" rather
1254 than reason "internal", so network measurement scripts can get a
1255 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1258 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1259 - Free some more still-in-use memory at exit, to make hunting for
1260 memory leaks easier. Resolves bug 7029.
1261 - When a Tor client gets a "truncated" relay cell, the first byte of
1262 its payload specifies why the circuit was truncated. We were
1263 ignoring this 'reason' byte when tearing down the circuit, resulting
1264 in the controller not being told why the circuit closed. Now we
1265 pass the reason from the truncated cell to the controller. Bugfix
1266 on 0.1.2.3-alpha; fixes bug 7039.
1267 - Downgrade "Failed to hand off onionskin" messages to "debug"
1268 severity, since they're typically redundant with the "Your computer
1269 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1270 - Make clients running with IPv6 bridges connect over IPv6 again,
1271 even without setting new config options ClientUseIPv6 and
1272 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1273 - Use square brackets around IPv6 addresses in numerous places
1274 that needed them, including log messages, HTTPS CONNECT proxy
1275 requests, TransportProxy statefile entries, and pluggable transport
1276 extra-info lines. Fixes bug 7011; patch by David Fifield.
1278 o Code refactoring and cleanup:
1279 - Source files taken from other packages now reside in src/ext;
1280 previously they were scattered around the rest of Tor.
1281 - Avoid use of reserved identifiers in our C code. The C standard
1282 doesn't like us declaring anything that starts with an
1283 underscore, so let's knock it off before we get in trouble. Fix
1284 for bug 1031; bugfix on the first Tor commit.
1287 Changes in version 0.2.3.23-rc - 2012-10-20
1288 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1289 vulnerability introduced by a change in OpenSSL, and fixes a variety
1290 of smaller bugs in preparation for the release.
1292 o New directory authorities:
1293 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1294 authority. Closes ticket 5749.
1296 o Major bugfixes (security/privacy):
1297 - Disable TLS session tickets. OpenSSL's implementation was giving
1298 our TLS session keys the lifetime of our TLS context objects, when
1299 perfect forward secrecy would want us to discard anything that
1300 could decrypt a link connection as soon as the link connection
1301 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1302 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1303 - Discard extraneous renegotiation attempts once the V3 link
1304 protocol has been initiated. Failure to do so left us open to
1305 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1306 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1309 - Fix a possible crash bug when checking for deactivated circuits
1310 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1311 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1313 o Minor bugfixes (on 0.2.3.x):
1314 - Fix two cases in src/or/transports.c where we were calling
1315 fmt_addr() twice in a parameter list. Bug found by David
1316 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1317 - Convert an assert in the pathbias code to a log message. The assert
1318 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1319 bugfix on 0.2.3.17-beta.
1320 - Fix memory leaks whenever we logged any message about the "path
1321 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1323 o Minor bugfixes (on 0.2.2.x and earlier):
1324 - Don't serve or accept v2 hidden service descriptors over a relay's
1325 DirPort. It's never correct to do so, and disabling it might
1326 make it more annoying to exploit any bugs that turn up in the
1327 descriptor-parsing code. Fixes bug 7149.
1328 - When relays refuse a "create" cell because their queue of pending
1329 create cells is too big (typically because their cpu can't keep up
1330 with the arrival rate), send back reason "resource limit" rather
1331 than reason "internal", so network measurement scripts can get a
1332 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1333 - Correct file sizes when reading binary files on Cygwin, to avoid
1334 a bug where Tor would fail to read its state file. Fixes bug 6844;
1335 bugfix on 0.1.2.7-alpha.
1336 - Avoid undefined behaviour when parsing the list of supported
1337 rendezvous/introduction protocols in a hidden service descriptor.
1338 Previously, Tor would have confused (as-yet-unused) protocol version
1339 numbers greater than 32 with lower ones on many platforms. Fixes
1340 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1342 o Documentation fixes:
1343 - Clarify that hidden services are TCP only. Fixes bug 6024.
1346 Changes in version 0.2.4.3-alpha - 2012-09-22
1347 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1348 assertion, resumes letting relays test reachability of their DirPort,
1349 and cleans up a bunch of smaller bugs.
1352 - Fix an assertion failure in tor_timegm() that could be triggered
1353 by a badly formatted directory object. Bug found by fuzzing with
1354 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1357 - Fix a possible crash bug when checking for deactivated circuits
1358 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1359 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1360 - Allow routers to detect that their own DirPorts are running. When
1361 we removed support for versions_supports_begindir, we also
1362 accidentally removed the mechanism we used to self-test our
1363 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1364 bugfix on 0.2.4.2-alpha.
1366 o Security features:
1367 - Switch to a completely time-invariant approach for picking nodes
1368 weighted by bandwidth. Our old approach would run through the
1369 part of the loop after it had made its choice slightly slower
1370 than it ran through the part of the loop before it had made its
1371 choice. Addresses ticket 6538.
1372 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1373 by tor2web clients allows hidden services to identity tor2web
1374 clients through their repeated selection of the same rendezvous
1375 and introduction point circuit endpoints (their guards). Resolves
1379 - Enable Tor to read configuration, state, and key information from
1380 a FIFO. Previously Tor would only read from files with a positive
1381 stat.st_size. Code from meejah; fixes bug 6044.
1384 - Correct file sizes when reading binary files on Cygwin, to avoid
1385 a bug where Tor would fail to read its state file. Fixes bug 6844;
1386 bugfix on 0.1.2.7-alpha.
1387 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1388 bugfix on 0.2.0.3-alpha.
1389 - When complaining about a client port on a public address, log
1390 which address we're complaining about. Fixes bug 4020; bugfix on
1391 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1392 - Convert an assert in the pathbias code to a log message. The assert
1393 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1394 bugfix on 0.2.3.17-beta.
1395 - Our new buildsystem was overzealous about rebuilding manpages: it
1396 would rebuild them all whenever any one of them changed. Now our
1397 dependency checking should be correct. Fixes bug 6843; bugfix on
1399 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1400 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1401 - Correct log printout about which address family is preferred
1402 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1403 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1405 o Minor bugfixes (code cleanliness):
1406 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1407 with large values. This situation was untriggered, but nevertheless
1408 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1409 - Reject consensus votes with more than 64 known-flags. We aren't even
1410 close to that limit yet, and our code doesn't handle it correctly.
1411 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1412 - Avoid undefined behaviour when parsing the list of supported
1413 rendezvous/introduction protocols in a hidden service descriptor.
1414 Previously, Tor would have confused (as-yet-unused) protocol version
1415 numbers greater than 32 with lower ones on many platforms. Fixes
1416 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1417 - Fix handling of rendezvous client authorization types over 8.
1418 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1419 - Fix building with older versions of GCC (2.95, for one) that don't
1420 like preprocessor directives inside macro arguments. Found by
1421 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1422 - Switch weighted node selection rule from using a list of doubles
1423 to using a list of int64_t. This change should make the process
1424 slightly easier to debug and maintain. Needed to finish ticket 6538.
1426 o Code simplification and refactoring:
1427 - Move the generic "config" code into a new file, and have "config.c"
1428 hold only torrc- and state-related code. Resolves ticket 6823.
1429 - Move the core of our "choose a weighted element at random" logic
1430 into its own function, and give it unit tests. Now the logic is
1431 testable, and a little less fragile too.
1432 - Removed the testing_since field of node_t, which hasn't been used
1433 for anything since 0.2.0.9-alpha.
1435 o Documentation fixes:
1436 - Clarify that hidden services are TCP only. Fixes bug 6024.
1437 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1441 Changes in version 0.2.3.22-rc - 2012-09-11
1442 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1446 - Fix an assertion failure in tor_timegm() that could be triggered
1447 by a badly formatted directory object. Bug found by fuzzing with
1448 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1451 - Avoid segfault when starting up having run with an extremely old
1452 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1456 Changes in version 0.2.2.39 - 2012-09-11
1457 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1461 - Fix an assertion failure in tor_timegm() that could be triggered
1462 by a badly formatted directory object. Bug found by fuzzing with
1463 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1464 - Do not crash when comparing an address with port value 0 to an
1465 address policy. This bug could have been used to cause a remote
1466 assertion failure by or against directory authorities, or to
1467 allow some applications to crash clients. Fixes bug 6690; bugfix
1471 Changes in version 0.2.4.2-alpha - 2012-09-10
1472 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1473 raises the default rate limiting even more, and makes the bootstrapping
1474 log messages less noisy.
1477 - Automatically forward the TCP ports of pluggable transport
1478 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1482 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1483 to 1GB/1GB. The previous defaults were intended to be "basically
1484 infinite", but it turns out they're now limiting our 100mbit+
1485 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1486 last time we raised it).
1489 - Detect when we're running with a version of OpenSSL other than the
1490 one we compiled with. This has occasionally given people hard-to-
1492 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1493 versions and capabilities when everything is going right. Resolves
1494 part of ticket 6736.
1495 - Directory authorities no long accept descriptors for any version of
1496 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1497 These versions are insecure, unsupported, or both. Implements
1501 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1502 to start with a triple-underscore so the controller won't touch it.
1503 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1504 - Avoid segfault when starting up having run with an extremely old
1505 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1507 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1508 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1509 - Don't follow the NULL pointer if microdescriptor generation fails.
1510 (This does not appear to be triggerable, but it's best to be safe.)
1511 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1512 - Fix mis-declared dependencies on src/common/crypto.c and
1513 src/or/tor_main.c that could break out-of-tree builds under some
1514 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1515 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1516 6778; bugfix on 0.2.4.1-alpha.
1517 - Fix a harmless (in this case) build warning for implicitly
1518 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1521 - Now that all versions before 0.2.2.x are disallowed, we no longer
1522 need to work around their missing features. Thus we can remove a
1523 bunch of compatibility code.
1526 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1527 TCP ports to forward. In the past it only accepted two ports:
1528 the ORPort and the DirPort.
1531 Changes in version 0.2.4.1-alpha - 2012-09-05
1532 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1533 bridgedb; lets relays use IPv6 addresses and directory authorities
1534 advertise them; and switches to a cleaner build interface.
1536 This is the first alpha release in a new series, so expect there to
1537 be bugs. Users who would rather test out a more stable branch should
1538 stay with 0.2.3.x for now.
1540 o Major features (bridges):
1541 - Bridges now report the pluggable transports they support to the
1542 bridge authority, so it can pass the supported transports on to
1543 bridgedb and/or eventually do reachability testing. Implements
1546 o Major features (IPv6):
1547 - Bridge authorities now accept IPv6 bridge addresses and include
1548 them in network status documents. Implements ticket 5534.
1549 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1550 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1551 to happen. Implements ticket 5535.
1552 - All kind of relays, not just bridges, can now advertise an IPv6
1553 OR port. Implements ticket 6362.
1554 - Directory authorities vote on IPv6 OR ports using the new consensus
1555 method 14. Implements ticket 6363.
1557 o Major features (build):
1558 - Switch to a nonrecursive Makefile structure. Now instead of each
1559 Makefile.am invoking other Makefile.am's, there is a master
1560 Makefile.am that includes the others. This change makes our build
1561 process slightly more maintainable, and improves parallelism for
1562 building with make -j. Original patch by Stewart Smith; various
1563 fixes by Jim Meyering.
1564 - Where available, we now use automake's "silent" make rules by
1565 default, so that warnings are easier to spot. You can get the old
1566 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1568 o Minor features (code security and spec conformance):
1569 - Clear keys and key-derived material left on the stack in
1570 rendservice.c and rendclient.c. Check return value of
1571 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1572 These fixes should make us more forward-secure against cold-boot
1573 attacks and the like. Fixes bug 2385.
1574 - Reject EXTEND cells sent to nonexistent streams. According to the
1575 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1576 we were only checking for stream IDs that were currently in use.
1577 Found while hunting for more instances of bug 6271. Bugfix on
1578 0.0.2pre8, which introduced incremental circuit construction.
1580 o Minor features (streamlining);
1581 - No longer include the "opt" prefix when generating routerinfos
1582 or v2 directories: it has been needless since Tor 0.1.2. Closes
1584 - Remove some now-needless code that tried to aggressively flush
1585 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1586 cell queue logic has saved us from the failure mode that this code
1587 was supposed to prevent. Removing this code will limit the number
1588 of baroque control flow paths through Tor's network logic. Reported
1589 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1591 o Minor features (controller):
1592 - Add a "GETINFO signal/names" control port command. Implements
1594 - Provide default values for all options via "GETINFO config/defaults".
1595 Implements ticket 4971.
1597 o Minor features (IPv6):
1598 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1599 authorities should set if they have IPv6 connectivity and want to
1600 do reachability tests for IPv6 relays. Implements feature 5974.
1601 - A relay with an IPv6 OR port now sends that address in NETINFO
1602 cells (in addition to its other address). Implements ticket 6364.
1604 o Minor features (log messages):
1605 - Omit the first heartbeat log message, because it never has anything
1606 useful to say, and it clutters up the bootstrapping messages.
1607 Resolves ticket 6758.
1608 - Don't log about reloading the microdescriptor cache at startup. Our
1609 bootstrap warnings are supposed to tell the user when there's a
1610 problem, and our bootstrap notices say when there isn't. Resolves
1611 ticket 6759; bugfix on 0.2.2.6-alpha.
1612 - Don't log "I learned some more directory information" when we're
1613 reading cached directory information. Reserve it for when new
1614 directory information arrives in response to a fetch. Resolves
1616 - Prevent rounding error in path bias counts when scaling
1617 them down, and use the correct scale factor default. Also demote
1618 some path bias related log messages down a level and make others
1619 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1620 - We no longer warn so much when generating manpages from their
1623 o Code simplifications and refactoring:
1624 - Enhance our internal sscanf replacement so that we can eliminate
1625 the last remaining uses of the system sscanf. (Though those uses
1626 of sscanf were safe, sscanf itself is generally error prone, so
1627 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1629 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1630 - Move last_reachable and testing_since from routerinfo_t to node_t.
1631 Implements ticket 5529.
1632 - Add replaycache_t structure, functions and unit tests, then refactor
1633 rend_service_introduce() to be more clear to read, improve, debug,
1634 and test. Resolves bug 6177.
1635 - Finally remove support for malloc_good_size and malloc_usable_size.
1636 We had hoped that these functions would let us eke a little more
1637 memory out of our malloc implementation. Unfortunately, the only
1638 implementations that provided these functions are also ones that
1639 are already efficient about not overallocation: they never got us
1640 more than 7 or so bytes per allocation. Removing them saves us a
1641 little code complexity and a nontrivial amount of build complexity.
1644 - Tor maintainers now require Automake version 1.9 or later to build
1645 Tor from the Git repository. (Automake is not required when building
1646 from a source distribution.)
1649 Changes in version 0.2.3.21-rc - 2012-09-05
1650 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1651 series. It fixes a trio of potential security bugs, fixes a bug where
1652 we were leaving some of the fast relays out of the microdescriptor
1653 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1654 and cleans up other smaller issues.
1656 o Major bugfixes (security):
1657 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1658 could use this trick to make their circuits receive cells faster
1659 than our flow control would have allowed, or to gum up the network,
1660 or possibly to do targeted memory denial-of-service attacks on
1661 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1662 from July 2002, before the release of Tor 0.0.0. We had committed
1663 this patch previously, but we had to revert it because of bug 6271.
1664 Now that 6271 is fixed, this patch appears to work.
1665 - Reject any attempt to extend to an internal address. Without
1666 this fix, a router could be used to probe addresses on an internal
1667 network to see whether they were accepting connections. Fixes bug
1668 6710; bugfix on 0.0.8pre1.
1669 - Do not crash when comparing an address with port value 0 to an
1670 address policy. This bug could have been used to cause a remote
1671 assertion failure by or against directory authorities, or to
1672 allow some applications to crash clients. Fixes bug 6690; bugfix
1676 - Remove the upper bound on microdescriptor length. We were hitting
1677 the limit for routers with complex exit policies or family
1678 declarations, causing clients to not use them. Fixes the first
1679 piece of bug 6404; fix on 0.2.2.6-alpha.
1680 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1681 as a relay. Previously, some of our code would treat the presence
1682 of any ORPort line as meaning that we should act like a relay,
1683 even though our new listener code would correctly not open any
1684 ORPorts for ORPort 0. Similar bugs in other Port options are also
1685 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1688 - Avoid a pair of double-free and use-after-mark bugs that can
1689 occur with certain timings in canceled and re-received DNS
1690 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1691 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1692 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1693 - Allow one-hop directory fetching circuits the full "circuit build
1694 timeout" period, rather than just half of it, before failing them
1695 and marking the relay down. This fix should help reduce cases where
1696 clients declare relays (or worse, bridges) unreachable because
1697 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1698 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1700 - Authorities no longer include any router in their microdescriptor
1701 consensuses for which they couldn't generate or agree on a
1702 microdescriptor. Fixes the second piece of bug 6404; fix on
1704 - Detect and reject attempts to specify both "FooPort" and
1705 "FooPort 0" in the same configuration domain. (It's still okay
1706 to have a FooPort in your configuration file, and use "FooPort 0"
1707 on the command line to disable it.) Fixes the second half of bug
1708 6507; bugfix on 0.2.3.3-alpha.
1709 - Make wildcarded addresses (that is, ones beginning with "*.") work
1710 when provided via the controller's MapAddress command. Previously,
1711 they were accepted, but we never actually noticed that they were
1712 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1713 - Avoid crashing on a malformed state file where EntryGuardPathBias
1714 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1715 - Add a (probably redundant) memory clear between iterations of
1716 the router status voting loop, to prevent future coding errors
1717 where data might leak between iterations of the loop. Resolves
1720 o Minor bugfixes (log messages):
1721 - Downgrade "set buildtimeout to low value" messages to "info"
1722 severity; they were never an actual problem, there was never
1723 anything reasonable to do about them, and they tended to spam logs
1724 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1725 - Downgrade path-bias warning messages to "info". We'll try to get
1726 them working better in 0.2.4. Add internal circuit construction
1727 state to protect against the noisy warn message "Unexpectedly high
1728 circuit_successes". Also add some additional rate-limited notice
1729 messages to help determine the root cause of the warn. Fixes bug
1730 6475. Bugfix against 0.2.3.17-beta.
1731 - Move log message when unable to find a microdesc in a routerstatus
1732 entry to parse time. Previously we'd spam this warning every time
1733 we tried to figure out which microdescriptors to download. Fixes
1734 the third piece of bug 6404; fix on 0.2.3.18-rc.
1737 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1738 change when the authority is deciding whether to accept a newly
1739 uploaded descriptor. Implements ticket 6423.
1740 - Add missing documentation for consensus and microdesc files.
1741 Resolves ticket 6732.
1744 Changes in version 0.2.2.38 - 2012-08-12
1745 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1746 attack that could in theory leak path information.
1749 - Avoid an uninitialized memory read when reading a vote or consensus
1750 document that has an unrecognized flavor name. This read could
1751 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1752 - Try to leak less information about what relays a client is
1753 choosing to a side-channel attacker. Previously, a Tor client would
1754 stop iterating through the list of available relays as soon as it
1755 had chosen one, thus finishing a little earlier when it picked
1756 a router earlier in the list. If an attacker can recover this
1757 timing information (nontrivial but not proven to be impossible),
1758 they could learn some coarse-grained information about which relays
1759 a client was picking (middle nodes in particular are likelier to
1760 be affected than exits). The timing attack might be mitigated by
1761 other factors (see bug 6537 for some discussion), but it's best
1762 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1765 Changes in version 0.2.3.20-rc - 2012-08-05
1766 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1767 series. It fixes a pair of code security bugs and a potential anonymity
1768 issue, updates our RPM spec files, and cleans up other smaller issues.
1771 - Avoid read-from-freed-memory and double-free bugs that could occur
1772 when a DNS request fails while launching it. Fixes bug 6480;
1773 bugfix on 0.2.0.1-alpha.
1774 - Avoid an uninitialized memory read when reading a vote or consensus
1775 document that has an unrecognized flavor name. This read could
1776 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1777 - Try to leak less information about what relays a client is
1778 choosing to a side-channel attacker. Previously, a Tor client would
1779 stop iterating through the list of available relays as soon as it
1780 had chosen one, thus finishing a little earlier when it picked
1781 a router earlier in the list. If an attacker can recover this
1782 timing information (nontrivial but not proven to be impossible),
1783 they could learn some coarse-grained information about which relays
1784 a client was picking (middle nodes in particular are likelier to
1785 be affected than exits). The timing attack might be mitigated by
1786 other factors (see bug 6537 for some discussion), but it's best
1787 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1790 - Try to make the warning when giving an obsolete SOCKSListenAddress
1791 a little more useful.
1792 - Terminate active server managed proxies if Tor stops being a
1793 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
1794 - Provide a better error message about possible OSX Asciidoc failure
1795 reasons. Fixes bug 6436.
1796 - Warn when Tor is configured to use accounting in a way that can
1797 link a hidden service to some other hidden service or public
1798 address. Resolves ticket 6490.
1801 - Check return value of fputs() when writing authority certificate
1802 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1803 - Ignore ServerTransportPlugin lines when Tor is not configured as
1804 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
1805 - When disabling guards for having too high a proportion of failed
1806 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
1810 - Update our default RPM spec files to work with mock and rpmbuild
1811 on RHEL/Fedora. They have an updated set of dependencies and
1812 conflicts, a fix for an ancient typo when creating the "_tor"
1813 user, and better instructions. Thanks to Ondrej Mikle for the
1814 patch series. Fixes bug 6043.
1817 - Make it possible to set the TestingTorNetwork configuration
1818 option using AlternateDirAuthority and AlternateBridgeAuthority
1819 as an alternative to setting DirServer. Addresses ticket 6377.
1822 - Clarify the documentation for the Alternate*Authority options.
1824 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1826 o Code simplification and refactoring:
1827 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1828 10 lines. Also, don't nest them. Doing so in the past has
1829 led to hard-to-debug code. The new style is to use the
1830 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1833 Changes in version 0.2.3.19-rc - 2012-07-06
1834 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
1835 series. It fixes the compile on Windows, reverts to a GeoIP database
1836 that isn't as broken, and fixes a flow control bug that has been around
1837 since the beginning of Tor.
1840 - Fix a bug handling SENDME cells on nonexistent streams that could
1841 result in bizarre window values. Report and patch contributed
1842 pseudonymously. Fixes part of bug 6271. This bug was introduced
1843 before the first Tor release, in svn commit r152.
1844 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
1845 June 2012 database, Maxmind marked many Tor relays as country "A1",
1846 which will cause risky behavior for clients that set EntryNodes
1847 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
1848 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
1849 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
1852 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1853 bugfix on 0.2.1.10-alpha.
1856 Changes in version 0.2.3.18-rc - 2012-06-28
1857 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
1858 series. It fixes a few smaller bugs, but generally appears stable.
1859 Please test it and let us know whether it is!
1862 - Allow wildcarded mapaddress targets to be specified on the
1863 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
1864 - Make our linker option detection code more robust against linkers
1865 such as on FreeBSD 8, where a bad combination of options completes
1866 successfully but makes an unrunnable binary. Fixes bug 6173;
1867 bugfix on 0.2.3.17-beta.
1869 o Minor bugfixes (on 0.2.2.x and earlier):
1870 - Avoid a false positive in the util/threads unit test by increasing
1871 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1872 - Replace "Sending publish request" log messages with "Launching
1873 upload", so that they no longer confusingly imply that we're
1874 sending something to a directory we might not even be connected
1875 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1876 - Make sure to set *socket_error in all error cases in
1877 connection_connect(), so it can't produce a warning about
1878 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1879 0.2.1.1-alpha; resolves ticket 6028.
1880 - Downgrade "Got a certificate, but we already have it" log messages
1881 from warning to info, except when we're a dirauth. Fixes bug 5238;
1882 bugfix on 0.2.1.7-alpha.
1883 - When checking for requested signatures on the latest consensus
1884 before serving it to a client, make sure to check the right
1885 consensus flavor. Bugfix on 0.2.2.6-alpha.
1886 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1887 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1889 o Minor bugfixes (on 0.2.3.x):
1890 - Make format_helper_exit_status() avoid unnecessary space padding
1891 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
1893 - Downgrade a message about cleaning the microdescriptor cache to
1894 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
1895 - Log a BUG message at severity INFO if we have a networkstatus with
1896 a missing entry for some microdescriptor. Continues on a patch
1898 - Improve the log message when a managed proxy fails to launch. Fixes
1899 bug 5099; bugfix on 0.2.3.6-alpha.
1900 - Don't do DNS lookups when parsing corrupted managed proxy protocol
1901 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
1902 - When formatting wildcarded address mappings for the controller,
1903 be sure to include "*." as appropriate. Partially fixes bug 6244;
1904 bugfix on 0.2.3.9-alpha.
1905 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
1906 Bugfix on 0.2.3.13-alpha.
1907 - Stop logging messages about running with circuit timeout learning
1908 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
1909 - Disable a spurious warning about reading on a marked and flushing
1910 connection. We shouldn't be doing that, but apparently we
1911 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
1912 - Fix a bug that stopped AllowDotExit from working on addresses
1913 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
1916 o Code simplification, refactoring, unit tests:
1917 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
1918 Libevent's notion of cached time when possible.
1919 - Remove duplicate code for invoking getrlimit() from control.c.
1920 - Add a unit test for the environment_variable_names_equal function.
1923 - Document the --defaults-torrc option, and the new (in 0.2.3)
1924 semantics for overriding, extending, and clearing lists of
1925 options. Closes bug 4748.
1928 Changes in version 0.2.3.17-beta - 2012-06-15
1929 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
1930 gets our TLS handshake back on track for being able to blend in with
1931 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
1932 with Vidalia, and otherwise continues to get us closer to a release
1936 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1937 - Update TLS cipher list to match Firefox 8 and later. Resolves
1939 - Implement the client side of proposal 198: remove support for
1940 clients falsely claiming to support standard ciphersuites that
1941 they can actually provide. As of modern OpenSSL versions, it's not
1942 necessary to fake any standard ciphersuite, and doing so prevents
1943 us from using better ciphersuites in the future, since servers
1944 can't know whether an advertised ciphersuite is really supported or
1945 not. Some hosts -- notably, ones with very old versions of OpenSSL
1946 or where OpenSSL has been built with ECC disabled -- will stand
1947 out because of this change; TBB users should not be affected.
1950 - Change the default value for DynamicDHGroups (introduced in
1951 0.2.3.9-alpha) to 0. This feature can make Tor relays less
1952 identifiable by their use of the mod_ssl DH group, but at
1953 the cost of some usability (#4721) and bridge tracing (#6087)
1954 regressions. Resolves ticket 5598.
1955 - Send a CRLF at the end of each STATUS_* control protocol event. This
1956 bug tickled a bug in Vidalia which would make it freeze. Fixes
1957 bug 6094; bugfix on 0.2.3.16-alpha.
1960 - Disable writing on marked-for-close connections when they are
1961 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1962 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1963 case for flushing marked connections.
1964 - Detect SSL handshake even when the initial attempt to write the
1965 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
1966 - Change the AllowDotExit rules so they should actually work.
1967 We now enforce AllowDotExit only immediately after receiving an
1968 address via SOCKS or DNSPort: other sources are free to provide
1969 .exit addresses after the resolution occurs. Fixes bug 3940;
1970 bugfix on 0.2.2.1-alpha.
1971 - Fix a (harmless) integer overflow in cell statistics reported by
1972 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
1973 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
1974 right places and never depends on the consensus parameters or
1975 computes adaptive timeouts when it is disabled. Fixes bug 5049;
1976 bugfix on 0.2.2.14-alpha.
1977 - When building Tor on Windows with -DUNICODE (not default), ensure
1978 that error messages, filenames, and DNS server names are always
1979 NUL-terminated when we convert them to a single-byte encoding.
1980 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
1981 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
1982 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
1983 - Fix an edge case where TestingTorNetwork is set but the authorities
1984 and relays all have an uptime of zero, where the private Tor network
1985 could briefly lack support for hidden services. Fixes bug 3886;
1986 bugfix on 0.2.2.18-alpha.
1987 - Correct the manpage's descriptions for the default values of
1988 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
1990 - Fix the documentation for the --hush and --quiet command line
1991 options, which changed their behavior back in 0.2.3.3-alpha.
1992 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
1996 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
1997 more information to it, so that we can track it down in case it
1998 returns again. Mitigates bug 5235.
1999 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2000 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2001 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2002 - Warn the user when HTTPProxy, but no other proxy type, is
2003 configured. This can cause surprising behavior: it doesn't send
2004 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2005 directory traffic only. Resolves ticket 4663.
2006 - Issue a notice if a guard completes less than 40% of your circuits.
2007 Threshold is configurable by torrc option PathBiasNoticeRate and
2008 consensus parameter pb_noticepct. There is additional, off-by-
2009 default code to disable guards which fail too many circuits.
2010 Addresses ticket 5458.
2011 - Update to the June 6 2012 Maxmind GeoLite Country database.
2013 o Code simplifications and refactoring:
2014 - Remove validate_pluggable_transports_config(): its warning
2015 message is now handled by connection_or_connect().
2018 Changes in version 0.2.2.37 - 2012-06-06
2019 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2020 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2024 - Work around a bug in OpenSSL that broke renegotiation with TLS
2025 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2026 the v2 Tor connection protocol when both sides were using OpenSSL
2027 1.0.1 would fail. Resolves ticket 6033.
2028 - When waiting for a client to renegotiate, don't allow it to add
2029 any bytes to the input buffer. This fixes a potential DoS issue.
2030 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2031 - Fix an edge case where if we fetch or publish a hidden service
2032 descriptor, we might build a 4-hop circuit and then use that circuit
2033 for exiting afterwards -- even if the new last hop doesn't obey our
2034 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2037 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2038 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2041 - Tell GCC and Clang to check for any errors in format strings passed
2042 to the tor_v*(print|scan)f functions.
2045 Changes in version 0.2.3.16-alpha - 2012-06-05
2046 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2047 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2048 currently). It also fixes a variety of smaller bugs and other cleanups
2049 that get us closer to a release candidate.
2051 o Major bugfixes (general):
2052 - Work around a bug in OpenSSL that broke renegotiation with TLS
2053 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2054 the v2 Tor connection protocol when both sides were using OpenSSL
2055 1.0.1 would fail. Resolves ticket 6033.
2056 - When waiting for a client to renegotiate, don't allow it to add
2057 any bytes to the input buffer. This fixes a potential DoS issue.
2058 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2059 - Pass correct OR address to managed proxies (like obfsproxy),
2060 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2062 - The advertised platform of a router now includes only its operating
2063 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2064 service pack level (for Windows) or its CPU architecture (for Unix).
2065 We also no longer include the "git-XYZ" tag in the version. Resolves
2068 o Major bugfixes (clients):
2069 - If we are unable to find any exit that supports our predicted ports,
2070 stop calling them predicted, so that we don't loop and build
2071 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2072 which introduced predicted ports.
2073 - Fix an edge case where if we fetch or publish a hidden service
2074 descriptor, we might build a 4-hop circuit and then use that circuit
2075 for exiting afterwards -- even if the new last hop doesn't obey our
2076 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2077 - Check at each new consensus whether our entry guards were picked
2078 long enough ago that we should rotate them. Previously, we only
2079 did this check at startup, which could lead to us holding a guard
2080 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2081 - When fetching a bridge descriptor from a bridge authority,
2082 always do so anonymously, whether we have been able to open
2083 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2084 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2085 but we'll need to wait for bug 6010 before it's actually usable.
2087 o Major bugfixes (directory authorities):
2088 - When computing weight parameters, behave more robustly in the
2089 presence of a bad bwweightscale value. Previously, the authorities
2090 would crash if they agreed on a sufficiently broken weight_scale
2091 value: now, they use a reasonable default and carry on. Partial
2092 fix for 5786; bugfix on 0.2.2.17-alpha.
2093 - Check more thoroughly to prevent a rogue authority from
2094 double-voting on any consensus directory parameter. Previously,
2095 authorities would crash in this case if the total number of
2096 votes for any parameter exceeded the number of active voters,
2097 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2101 - Rate-limit log messages when asked to connect anonymously to
2102 a private address. When these hit, they tended to hit fast and
2103 often. Also, don't bother trying to connect to addresses that we
2104 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2105 reply makes us think we have been lied to, even when the address the
2106 client tried to connect to was "localhost." Resolves ticket 2822.
2107 - Allow packagers to insert an extra string in server descriptor
2108 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2109 Resolves the rest of ticket 2988.
2110 - Raise the threshold of server descriptors needed (75%) and exit
2111 server descriptors needed (50%) before we will declare ourselves
2112 bootstrapped. This will make clients start building circuits a
2113 little later, but makes the initially constructed circuits less
2114 skewed and less in conflict with further directory fetches. Fixes
2116 - Close any connection that sends unrecognized junk before the
2117 handshake. Solves an issue noted in bug 4369.
2118 - Improve log messages about managed transports. Resolves ticket 5070.
2119 - Tag a bridge's descriptor as "never to be sent unencrypted".
2120 This shouldn't matter, since bridges don't open non-anonymous
2121 connections to the bridge authority and don't allow unencrypted
2122 directory connections from clients, but we might as well make
2123 sure. Closes bug 5139.
2124 - Expose our view of whether we have gone dormant to the controller,
2125 via a new "GETINFO dormant" value. Torbutton and other controllers
2126 can use this to avoid doing periodic requests through Tor while
2127 it's dormant (bug 4718). Fixes bug 5954.
2128 - Tell GCC and Clang to check for any errors in format strings passed
2129 to the tor_v*(print|scan)f functions.
2130 - Update to the May 1 2012 Maxmind GeoLite Country database.
2132 o Minor bugfixes (already included in 0.2.2.36):
2133 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2134 Fixes bug 5346; bugfix on 0.0.8pre3.
2135 - Correct parsing of certain date types in parse_http_time().
2136 Without this patch, If-Modified-Since would behave
2137 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2138 Esteban Manchado Velázques.
2139 - Make our number-parsing functions always treat too-large values
2140 as an error, even when those values exceed the width of the
2141 underlying type. Previously, if the caller provided these
2142 functions with minima or maxima set to the extreme values of the
2143 underlying integer type, these functions would return those
2144 values on overflow rather than treating overflow as an error.
2145 Fixes part of bug 5786; bugfix on 0.0.9.
2146 - If we hit the error case where routerlist_insert() replaces an
2147 existing (old) server descriptor, make sure to remove that
2148 server descriptor from the old_routers list. Fix related to bug
2149 1776. Bugfix on 0.2.2.18-alpha.
2150 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2151 circuits. Fixes issue 5259.
2153 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2154 - Prevent a null-pointer dereference when receiving a data cell
2155 for a nonexistent stream when the circuit in question has an
2156 empty deliver window. We don't believe this is triggerable,
2157 since we don't currently allow deliver windows to become empty,
2158 but the logic is tricky enough that it's better to make the code
2159 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2160 - Fix a memory leak when trying to launch a DNS request when the
2161 network is disabled or the nameservers are unconfigurable. Fixes
2162 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2163 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2164 - Don't hold a Windows file handle open for every file mapping;
2165 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2167 - Avoid O(n^2) performance characteristics when parsing a large
2168 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2169 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2170 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2172 - Make our replacement implementation of strtok_r() compatible with
2173 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2174 bugfix on 0.2.2.1-alpha.
2175 - Fix a NULL-pointer dereference on a badly formed
2176 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2177 bugfix on 0.2.2.9-alpha.
2178 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2179 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2180 - Defensively refactor rend_mid_rendezvous() so that protocol
2181 violations and length checks happen in the beginning. Fixes
2183 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2184 that IPv6 stuff will compile on MSVC, and compilation issues
2185 will be easier to track down. Fixes bug 5861.
2187 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2188 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2189 resource exhaustion, so that clients can adjust their load to
2190 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2191 started using END_STREAM_REASON_RESOURCELIMIT.
2192 - Don't check for whether the address we're using for outbound
2193 connections has changed until after the outbound connection has
2194 completed. On Windows, getsockname() doesn't succeed until the
2195 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2196 - If the configuration tries to set MyFamily on a bridge, refuse to
2197 do so, and warn about the security implications. Fixes bug 4657;
2198 bugfix on 0.2.0.3-alpha.
2199 - If the client fails to set a reasonable set of ciphersuites
2200 during its v2 handshake renegotiation, allow the renegotiation to
2201 continue nevertheless (i.e. send all the required certificates).
2202 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2203 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2204 option is set to 0 (which Vidalia version 0.2.16 now does when
2205 a SAVECONF attempt fails), perform other actions that SIGHUP
2206 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2208 - If we fail to write a microdescriptor to the disk cache, do not
2209 continue replacing the old microdescriptor file. Fixes bug 2954;
2210 bugfix on 0.2.2.6-alpha.
2211 - Exit nodes don't need to fetch certificates for authorities that
2212 they don't recognize; only directory authorities, bridges,
2213 and caches need to do that. Fixes part of bug 2297; bugfix on
2215 - Correctly handle checking the permissions on the parent
2216 directory of a control socket in the root directory. Bug found
2217 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2219 - When told to add a bridge with the same digest as a preexisting
2220 bridge but a different addr:port, change the addr:port as
2221 requested. Previously we would not notice the change. Fixes half
2222 of bug 5603; fix on 0.2.2.26-beta.
2223 - End AUTHCHALLENGE error messages (in the control protocol) with
2224 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2226 o Minor bugfixes (on 0.2.3.x):
2227 - Turn an assertion (that the number of handshakes received as a
2228 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2230 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2231 we had reversed them when the answer was cached.) Fixes bug
2232 5723; bugfix on 0.2.3.1-alpha.
2233 - Work correctly on Linux systems with accept4 support advertised in
2234 their headers, but without accept4 support in the kernel. Fix
2235 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2236 - When told to add a bridge with the same addr:port as a preexisting
2237 bridge but a different transport, change the transport as
2238 requested. Previously we would not notice the change. Fixes half
2239 of bug 5603; fix on 0.2.3.2-alpha.
2240 - Avoid a "double-reply" warning when replying to a SOCKS request
2241 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2242 bugfix on 0.2.3.4-alpha.
2243 - Fix a bug where a bridge authority crashes if it has seen no
2244 directory requests when it's time to write statistics to disk.
2245 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2247 - Don't try to open non-control listeners when DisableNetwork is set.
2248 Previously, we'd open all listeners, then immediately close them.
2249 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2250 - Don't abort the managed proxy protocol if the managed proxy
2251 sends us an unrecognized line; ignore it instead. Fixes bug
2252 5910; bugfix on 0.2.3.9-alpha.
2253 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2254 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2255 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2256 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2257 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2258 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2259 - Resolve numerous small warnings and build issues with MSVC. Resolves
2262 o Documentation fixes:
2263 - Improve the manual's documentation for the NT Service command-line
2264 options. Addresses ticket 3964.
2265 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2266 - Document the changes to the ORPort and DirPort options, and the
2267 fact that {OR/Dir}ListenAddress is now unnecessary (and
2268 therefore deprecated). Resolves ticket 5597.
2271 - Remove the torrc.bridge file: we don't use it for anything, and
2272 it had become badly desynchronized from torrc.sample. Resolves
2276 Changes in version 0.2.2.36 - 2012-05-24
2277 Tor 0.2.2.36 updates the addresses for two of the eight directory
2278 authorities, fixes some potential anonymity and security issues,
2279 and fixes several crash bugs.
2281 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2282 known flaws, and nobody should be using them. You should upgrade. If
2283 you're using a Linux or BSD and its packages are obsolete, stop using
2284 those packages and upgrade anyway.
2286 o Directory authority changes:
2287 - Change IP address for maatuska (v3 directory authority).
2288 - Change IP address for ides (v3 directory authority), and rename
2292 - When building or running with any version of OpenSSL earlier
2293 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2294 versions have a bug (CVE-2011-4576) in which their block cipher
2295 padding includes uninitialized data, potentially leaking sensitive
2296 information to any peer with whom they make a SSLv3 connection. Tor
2297 does not use SSL v3 by default, but a hostile client or server
2298 could force an SSLv3 connection in order to gain information that
2299 they shouldn't have been able to get. The best solution here is to
2300 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2301 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2302 to make sure that the bug can't happen.
2303 - Never use a bridge or a controller-supplied node as an exit, even
2304 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2305 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2306 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2307 - Only build circuits if we have a sufficient threshold of the total
2308 descriptors that are marked in the consensus with the "Exit"
2309 flag. This mitigates an attack proposed by wanoskarnet, in which
2310 all of a client's bridges collude to restrict the exit nodes that
2311 the client knows about. Fixes bug 5343.
2312 - Provide controllers with a safer way to implement the cookie
2313 authentication mechanism. With the old method, if another locally
2314 running program could convince a controller that it was the Tor
2315 process, then that program could trick the controller into telling
2316 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2317 authentication method uses a challenge-response approach to prevent
2318 this attack. Fixes bug 5185; implements proposal 193.
2321 - Avoid logging uninitialized data when unable to decode a hidden
2322 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2323 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2324 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2326 - Fix builds when the path to sed, openssl, or sha1sum contains
2327 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2329 - Correct our replacements for the timeradd() and timersub() functions
2330 on platforms that lack them (for example, Windows). The timersub()
2331 function is used when expiring circuits, while timeradd() is
2332 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2333 bugfix on 0.2.2.24-alpha.
2334 - Fix the SOCKET_OK test that we use to tell when socket
2335 creation fails so that it works on Win64. Fixes part of bug 4533;
2336 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2339 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2340 Fixes bug 5346; bugfix on 0.0.8pre3.
2341 - Make our number-parsing functions always treat too-large values
2342 as an error, even when those values exceed the width of the
2343 underlying type. Previously, if the caller provided these
2344 functions with minima or maxima set to the extreme values of the
2345 underlying integer type, these functions would return those
2346 values on overflow rather than treating overflow as an error.
2347 Fixes part of bug 5786; bugfix on 0.0.9.
2348 - Older Linux kernels erroneously respond to strange nmap behavior
2349 by having accept() return successfully with a zero-length
2350 socket. When this happens, just close the connection. Previously,
2351 we would try harder to learn the remote address: but there was
2352 no such remote address to learn, and our method for trying to
2353 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2354 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2355 - Correct parsing of certain date types in parse_http_time().
2356 Without this patch, If-Modified-Since would behave
2357 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2358 Esteban Manchado Velázques.
2359 - Change the BridgePassword feature (part of the "bridge community"
2360 design, which is not yet implemented) to use a time-independent
2361 comparison. The old behavior might have allowed an adversary
2362 to use timing to guess the BridgePassword value. Fixes bug 5543;
2363 bugfix on 0.2.0.14-alpha.
2364 - Detect and reject certain misformed escape sequences in
2365 configuration values. Previously, these values would cause us
2366 to crash if received in a torrc file or over an authenticated
2367 control port. Bug found by Esteban Manchado Velázquez, and
2368 independently by Robert Connolly from Matta Consulting who further
2369 noted that it allows a post-authentication heap overflow. Patch
2370 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2371 bugfix on 0.2.0.16-alpha.
2372 - Fix a compile warning when using the --enable-openbsd-malloc
2373 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2374 - During configure, detect when we're building with clang version
2375 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2376 CFLAGS. clang doesn't support them yet.
2377 - When sending an HTTP/1.1 proxy request, include a Host header.
2378 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2379 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2380 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2381 - If we hit the error case where routerlist_insert() replaces an
2382 existing (old) server descriptor, make sure to remove that
2383 server descriptor from the old_routers list. Fix related to bug
2384 1776. Bugfix on 0.2.2.18-alpha.
2386 o Minor bugfixes (documentation and log messages):
2387 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2388 Fixes bug 4856; bugfix on Tor 0.0.6.
2389 - Update "ClientOnly" man page entry to explain that there isn't
2390 really any point to messing with it. Resolves ticket 5005.
2391 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2392 directory authority option (introduced in Tor 0.2.2.34).
2393 - Downgrade the "We're missing a certificate" message from notice
2394 to info: people kept mistaking it for a real problem, whereas it
2395 is seldom the problem even when we are failing to bootstrap. Fixes
2396 bug 5067; bugfix on 0.2.0.10-alpha.
2397 - Correctly spell "connect" in a log message on failure to create a
2398 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2399 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2400 circuits. Fixes issue 5259.
2403 - Directory authorities now reject versions of Tor older than
2404 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2405 inclusive. These versions accounted for only a small fraction of
2406 the Tor network, and have numerous known security issues. Resolves
2408 - Update to the May 1 2012 Maxmind GeoLite Country database.
2411 - When sending or relaying a RELAY_EARLY cell, we used to convert
2412 it to a RELAY cell if the connection was using the v1 link
2413 protocol. This was a workaround for older versions of Tor, which
2414 didn't handle RELAY_EARLY cells properly. Now that all supported
2415 versions can handle RELAY_EARLY cells, and now that we're enforcing
2416 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2417 remove this workaround. Addresses bug 4786.
2420 Changes in version 0.2.3.15-alpha - 2012-04-30
2421 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2422 the development branch build on Windows again.
2424 o Minor bugfixes (on 0.2.2.x and earlier):
2425 - Make sure that there are no unhandled pending TLS errors before
2426 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2427 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2428 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2429 - Fix an assert that directory authorities could trigger on sighup
2430 during some configuration state transitions. We now don't treat
2431 it as a fatal error when the new descriptor we just generated in
2432 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2433 - After we pick a directory mirror, we would refuse to use it if
2434 it's in our ExcludeExitNodes list, resulting in mysterious failures
2435 to bootstrap for people who just wanted to avoid exiting from
2436 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2437 - When building with --enable-static-tor on OpenBSD, do not
2438 erroneously attempt to link -lrt. Fixes bug 5103.
2440 o Minor bugfixes (on 0.2.3.x):
2441 - When Tor is built with kernel headers from a recent (last few
2442 years) Linux kernel, do not fail to run on older (pre-2.6.28
2443 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2444 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2446 - Fix compilation with miniupnpc version 1.6; patch from
2447 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2448 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2449 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2450 - Fix compilation on platforms without unistd.h, or where environ
2451 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2454 - Directory authorities are now a little more lenient at accepting
2455 older router descriptors, or newer router descriptors that don't
2456 make big changes. This should help ameliorate past and future
2457 issues where routers think they have uploaded valid descriptors,
2458 but the authorities don't think so. Fix for ticket 2479.
2459 - Make the code that clients use to detect an address change be
2460 IPv6-aware, so that it won't fill clients' logs with error
2461 messages when trying to get the IPv4 address of an IPv6
2462 connection. Implements ticket 5537.
2465 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2466 authorities needed to use it for a while to keep the network working
2467 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2468 that was six months ago. As of now, it should no longer be needed
2472 Changes in version 0.2.3.14-alpha - 2012-04-23
2473 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2474 candidate. It also dramatically speeds up AES: fast relays should
2475 consider switching to the newer OpenSSL library.
2477 o Directory authority changes:
2478 - Change IP address for ides (v3 directory authority), and rename
2482 - Avoid logging uninitialized data when unable to decode a hidden
2483 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2484 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2485 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2487 - If authorities are unable to get a v2 consensus document from other
2488 directory authorities, they no longer fall back to fetching
2489 them from regular directory caches. Fixes bug 5635; bugfix on
2490 0.2.2.26-beta, where routers stopped downloading v2 consensus
2492 - When we start a Tor client with a normal consensus already cached,
2493 be willing to download a microdescriptor consensus. Fixes bug 4011;
2494 fix on 0.2.3.1-alpha.
2496 o Major features (performance):
2497 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2498 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2499 vectorized AES implementations as appropriate. These can be much,
2500 much faster than other AES implementations.
2502 o Minor bugfixes (0.2.2.x and earlier):
2503 - Don't launch more than 10 service-side introduction-point circuits
2504 for a hidden service in five minutes. Previously, we would consider
2505 launching more introduction-point circuits if at least one second
2506 had passed without any introduction-point circuits failing. Fixes
2507 bug 4607; bugfix on 0.0.7pre1.
2508 - Change the BridgePassword feature (part of the "bridge community"
2509 design, which is not yet implemented) to use a time-independent
2510 comparison. The old behavior might have allowed an adversary
2511 to use timing to guess the BridgePassword value. Fixes bug 5543;
2512 bugfix on 0.2.0.14-alpha.
2513 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2514 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2515 - When sending an HTTP/1.1 proxy request, include a Host header.
2516 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2517 - Don't log that we have "decided to publish new relay descriptor"
2518 unless we are actually publishing a descriptor. Fixes bug 3942;
2519 bugfix on 0.2.2.28-beta.
2521 o Minor bugfixes (0.2.3.x):
2522 - Fix a bug where a bridge authority crashes (on a failed assert)
2523 if it has seen no directory requests when it's time to write
2524 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2525 - Fix bug stomping on ORPort option NoListen and ignoring option
2526 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2527 - In the testsuite, provide a large enough buffer in the tor_sscanf
2528 unit test. Otherwise we'd overrun that buffer and crash during
2529 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2531 - Make sure we create the keys directory if it doesn't exist and we're
2532 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2533 5572; bugfix on 0.2.3.13-alpha.
2534 - Fix a small memory leak when trying to decode incorrect base16
2535 authenticator during SAFECOOKIE authentication. Found by
2536 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2539 - Add more information to a log statement that might help track down
2540 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2541 non-IP address" messages (or any Bug messages, for that matter!),
2542 please let us know about it.
2543 - Relays now understand an IPv6 address when they get one from a
2544 directory server. Resolves ticket 4875.
2545 - Resolve IPv6 addresses in bridge and entry statistics to country
2546 code "??" which means we at least count them. Resolves ticket 5053;
2547 improves on 0.2.3.9-alpha.
2548 - Update to the April 3 2012 Maxmind GeoLite Country database.
2549 - Begin a doc/state-contents.txt file to explain the contents of
2550 the Tor state file. Fixes bug 2987.
2552 o Default torrc changes:
2553 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2554 port on 9050 by default anyway, so this should not change anything
2556 - Stop mentioning the deprecated *ListenAddress options in
2557 torrc.sample. Fixes bug 5438.
2558 - Document unit of bandwidth related options in sample torrc.
2562 - The "torify" script no longer supports the "tsocks" socksifier
2563 tool, since tsocks doesn't support DNS and UDP right for Tor.
2564 Everyone should be using torsocks instead. Fixes bugs 3530 and
2565 5180. Based on a patch by "ugh".
2568 - Change the symmetric cipher interface so that creating and
2569 initializing a stream cipher are no longer separate functions.
2570 - Remove all internal support for unpadded RSA. We never used it, and
2571 it would be a bad idea to start.
2574 Changes in version 0.2.3.13-alpha - 2012-03-26
2575 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2576 in managed pluggable transports, as well as providing other cleanups
2577 that get us closer to a release candidate.
2579 o Directory authority changes:
2580 - Change IP address for maatuska (v3 directory authority).
2583 - Provide controllers with a safer way to implement the cookie
2584 authentication mechanism. With the old method, if another locally
2585 running program could convince a controller that it was the Tor
2586 process, then that program could trick the controller into telling
2587 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2588 authentication method uses a challenge-response approach to prevent
2589 this attack. Fixes bug 5185, implements proposal 193.
2590 - Never use a bridge or a controller-supplied node as an exit, even
2591 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2592 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2593 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2594 - Only build circuits if we have a sufficient threshold of the total
2595 descriptors that are marked in the consensus with the "Exit"
2596 flag. This mitigates an attack proposed by wanoskarnet, in which
2597 all of a client's bridges collude to restrict the exit nodes that
2598 the client knows about. Fixes bug 5343.
2600 o Major bugfixes (on Tor 0.2.3.x):
2601 - Avoid an assert when managed proxies like obfsproxy are configured,
2602 and we receive HUP signals or setconf attempts too rapidly. This
2603 situation happens most commonly when Vidalia tries to attach to
2604 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2605 bugfix on 0.2.3.6-alpha.
2606 - Fix a relay-side pluggable transports bug where managed proxies were
2607 unreachable from the Internet, because Tor asked them to bind on
2608 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2609 - Stop discarding command-line arguments when TestingTorNetwork
2610 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2611 0.2.3.9-alpha, where task 4552 added support for two layers of
2613 - Resume allowing the unit tests to run in gdb. This was accidentally
2614 made impossible when the DisableDebuggerAttachment option was
2615 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2616 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2617 0.2.3.11-alpha. Reported by Anthony G. Basile.
2619 o Minor bugfixes (on 0.2.2.x and earlier):
2620 - Ensure we don't cannibalize circuits that are longer than three hops
2621 already, so we don't end up making circuits with 5 or more
2622 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2623 0.1.0.1-rc which introduced cannibalization.
2624 - Detect and reject certain misformed escape sequences in
2625 configuration values. Previously, these values would cause us
2626 to crash if received in a torrc file or over an authenticated
2627 control port. Bug found by Esteban Manchado Velázquez, and
2628 independently by Robert Connolly from Matta Consulting who further
2629 noted that it allows a post-authentication heap overflow. Patch
2630 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2631 bugfix on 0.2.0.16-alpha.
2632 - Fix a compile warning when using the --enable-openbsd-malloc
2633 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2634 - Directory caches no longer refuse to clean out descriptors because
2635 of missing v2 networkstatus documents, unless they're configured
2636 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2637 0.2.2.26-beta. Patch by Daniel Bryg.
2638 - Update to the latest version of the tinytest unit testing framework.
2639 This includes a couple of bugfixes that can be relevant for
2640 running forked unit tests on Windows, and removes all reserved
2643 o Minor bugfixes (on 0.2.3.x):
2644 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2645 4296; bugfix on 0.2.3.1-alpha.
2646 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2647 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2648 on 0.2.3.6-alpha. Patch by "frosty".
2649 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2650 option, so that the IP stack doesn't decide to use it for IPv4
2651 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2652 - Ensure that variables set in Tor's environment cannot override
2653 environment variables that Tor passes to a managed
2654 pluggable-transport proxy. Previously, Tor would pass every
2655 variable in its environment to managed proxies along with the new
2656 ones, in such a way that on many operating systems, the inherited
2657 environment variables would override those which Tor tried to
2658 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2659 bugfix on 0.2.3.9-alpha for Windows.
2662 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2663 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2664 - Update to the March 6 2012 Maxmind GeoLite Country database.
2667 Changes in version 0.2.3.12-alpha - 2012-02-13
2668 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2669 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2670 when Tor is configured to use a pluggable transport like obfsproxy.
2673 - Fix builds when the path to sed, openssl, or sha1sum contains
2674 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2676 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2677 connections. This change should allow busy exit relays to stop
2678 running out of available sockets as quickly. Fixes bug 4950;
2679 bugfix on 0.2.2.26-beta.
2680 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2681 would ask the bridge for microdescriptors, which are only supported
2682 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2683 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2684 - Properly set up obfsproxy's environment when in managed mode. The
2685 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2686 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2687 5076 and 5082; bugfix on 0.2.3.6-alpha.
2690 - Use the dead_strip option when building Tor on OS X. This reduces
2691 binary size by almost 19% when linking openssl and libevent
2692 statically, which we do for Tor Browser Bundle.
2693 - Fix broken URLs in the sample torrc file, and tell readers about
2694 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2695 PublishServerDescriptor options. Addresses bug 4652.
2696 - Update to the February 7 2012 Maxmind GeoLite Country database.
2699 - Downgrade the "We're missing a certificate" message from notice
2700 to info: people kept mistaking it for a real problem, whereas it
2701 is seldom the problem even when we are failing to bootstrap. Fixes
2702 bug 5067; bugfix on 0.2.0.10-alpha.
2703 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2704 managed pluggable transport server proxy's environment.
2705 Previously, we would put it there, even though Tor doesn't
2706 implement an 'extended server port' yet, and even though Tor
2707 almost certainly isn't listening at that address. For now, we set
2708 it to an empty string to avoid crashing older obfsproxies. Bugfix
2710 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2711 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2712 0.2.3.1-alpha. Bug reported by Scott Bennett.
2713 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2714 bugfix on 0.2.3.11-alpha.
2715 - Update "ClientOnly" man page entry to explain that there isn't
2716 really any point to messing with it. Resolves ticket 5005.
2717 - Use the correct CVE number for CVE-2011-4576 in our comments and
2718 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2721 o Code simplifications and refactoring:
2722 - Use the _WIN32 macro throughout our code to detect Windows.
2723 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2727 Changes in version 0.2.3.11-alpha - 2012-01-22
2728 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2729 the last step of the plan to limit maximum circuit length, includes
2730 a wide variety of hidden service performance and correctness fixes,
2731 works around an OpenSSL security flaw if your distro is too stubborn
2732 to upgrade, and fixes a bunch of smaller issues.
2735 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2736 part of "Proposal 110: Avoiding infinite length circuits" by
2737 refusing all circuit-extend requests that do not use a relay_early
2738 cell. This change helps Tor resist a class of denial-of-service
2739 attacks by limiting the maximum circuit length.
2740 - Adjust the number of introduction points that a hidden service
2741 will try to maintain based on how long its introduction points
2742 remain in use and how many introductions they handle. Fixes
2744 - Try to use system facilities for enumerating local interface
2745 addresses, before falling back to our old approach (which was
2746 binding a UDP socket, and calling getsockname() on it). That
2747 approach was scaring OS X users whose draconian firewall
2748 software warned about binding to UDP sockets, regardless of
2749 whether packets were sent. Now we try to use getifaddrs(),
2750 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2751 system supports. Resolves ticket 1827.
2753 o Major security workaround:
2754 - When building or running with any version of OpenSSL earlier
2755 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2756 versions have a bug (CVE-2011-4576) in which their block cipher
2757 padding includes uninitialized data, potentially leaking sensitive
2758 information to any peer with whom they make a SSLv3 connection. Tor
2759 does not use SSL v3 by default, but a hostile client or server
2760 could force an SSLv3 connection in order to gain information that
2761 they shouldn't have been able to get. The best solution here is to
2762 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2763 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2764 to make sure that the bug can't happen.
2767 - Fix the SOCKET_OK test that we use to tell when socket
2768 creation fails so that it works on Win64. Fixes part of bug 4533;
2769 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2770 - Correct our replacements for the timeradd() and timersub() functions
2771 on platforms that lack them (for example, Windows). The timersub()
2772 function is used when expiring circuits, while timeradd() is
2773 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2774 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2775 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2776 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2777 bug at runtime, not compile time, because some distributions hack
2778 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2779 on 0.2.3.9-alpha. Found by Pascal.
2781 o Minor features (controller):
2782 - Use absolute path names when reporting the torrc filename in the
2783 control protocol, so a controller can more easily find the torrc
2784 file. Resolves bug 1101.
2785 - Extend the control protocol to report flags that control a circuit's
2786 path selection in CIRC events and in replies to 'GETINFO
2787 circuit-status'. Implements part of ticket 2411.
2788 - Extend the control protocol to report the hidden service address
2789 and current state of a hidden-service-related circuit in CIRC
2790 events and in replies to 'GETINFO circuit-status'. Implements part
2792 - When reporting the path to the cookie file to the controller,
2793 give an absolute path. Resolves ticket 4881.
2794 - Allow controllers to request an event notification whenever a
2795 circuit is cannibalized or its purpose is changed. Implements
2796 part of ticket 3457.
2797 - Include the creation time of a circuit in CIRC and CIRC2
2798 control-port events and the list produced by the 'GETINFO
2799 circuit-status' control-port command.
2801 o Minor features (directory authorities):
2802 - Directory authorities now reject versions of Tor older than
2803 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2804 inclusive. These versions accounted for only a small fraction of
2805 the Tor network, and have numerous known security issues. Resolves
2807 - Authority operators can now vote for all relays in a given
2808 set of countries to be BadDir/BadExit/Invalid/Rejected.
2809 - Provide two consensus parameters (FastFlagMinThreshold and
2810 FastFlagMaxThreshold) to control the range of allowable bandwidths
2811 for the Fast directory flag. These allow authorities to run
2812 experiments on appropriate requirements for being a "Fast" node.
2813 The AuthDirFastGuarantee config value still applies. Implements
2815 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2816 directory authority option (introduced in Tor 0.2.2.34).
2818 o Minor features (other):
2819 - Don't disable the DirPort when we cannot exceed our AccountingMax
2820 limit during this interval because the effective bandwidthrate is
2821 low enough. This is useful in a situation where AccountMax is only
2822 used as an additional safeguard or to provide statistics.
2823 - Prepend an informative header to generated dynamic_dh_params files.
2824 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2825 EntryNodes will have no effect. Resolves issue 2571.
2826 - Log more useful messages when we fail to disable debugger
2828 - Log which authority we're missing votes from when we go to fetch
2829 them from the other auths.
2830 - Log (at debug level) whenever a circuit's purpose is changed.
2831 - Add missing documentation for the MaxClientCircuitsPending,
2832 UseMicrodescriptors, UserspaceIOCPBuffers, and
2833 _UseFilteringSSLBufferevents options, all introduced during
2835 - Update to the January 3 2012 Maxmind GeoLite Country database.
2837 o Minor bugfixes (hidden services):
2838 - Don't close hidden service client circuits which have almost
2839 finished connecting to their destination when they reach
2840 the normal circuit-build timeout. Previously, we would close
2841 introduction circuits which are waiting for an acknowledgement
2842 from the introduction point, and rendezvous circuits which have
2843 been specified in an INTRODUCE1 cell sent to a hidden service,
2844 after the normal CBT. Now, we mark them as 'timed out', and launch
2845 another rendezvous attempt in parallel. This behavior change can
2846 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2847 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2848 - Don't close hidden-service-side rendezvous circuits when they
2849 reach the normal circuit-build timeout. This behaviour change can
2850 be disabled using the new
2851 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2852 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2853 - Make sure we never mark the wrong rendezvous circuit as having
2854 had its introduction cell acknowleged by the introduction-point
2855 relay. Previously, when we received an INTRODUCE_ACK cell on a
2856 client-side hidden-service introduction circuit, we might have
2857 marked a rendezvous circuit other than the one we specified in
2858 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
2859 a warning message and interfered with the hidden service
2860 connection-establishment process. Fixes bug 4759; bugfix on
2861 0.2.3.3-alpha, when we added the stream-isolation feature which
2862 might cause Tor to open multiple rendezvous circuits for the same
2864 - Don't trigger an assertion failure when we mark a new client-side
2865 hidden-service introduction circuit for close during the process
2866 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
2869 o Minor bugfixes (log messages):
2870 - Correctly spell "connect" in a log message on failure to create a
2871 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
2873 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2874 Fixes bug 4856; bugfix on Tor 0.0.6.
2875 - Fix the log message describing how we work around discovering
2876 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2877 4837; bugfix on 0.2.2.9-alpha.
2878 - When logging about a disallowed .exit name, do not also call it
2879 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2881 o Minor bugfixes (build fixes):
2882 - During configure, detect when we're building with clang version
2883 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2884 CFLAGS. clang doesn't support them yet.
2885 - During configure, search for library containing cos function as
2886 libm lives in libcore on some platforms (BeOS/Haiku). Linking
2887 against libm was hard-coded before. Fixes the first part of bug
2888 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
2890 - Detect attempts to build Tor on (as yet hypothetical) versions
2891 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
2892 fix for bug 4533. Bugfix on 0.2.2.28-beta.
2893 - Preprocessor directives should not be put inside the arguments
2894 of a macro. This would break compilation with GCC releases prior
2895 to version 3.3. We would never recommend such an old GCC version,
2896 but it is apparently required for binary compatibility on some
2897 platforms (namely, certain builds of Haiku). Fixes the other part
2898 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
2901 o Minor bugfixes (other):
2902 - Older Linux kernels erroneously respond to strange nmap behavior
2903 by having accept() return successfully with a zero-length
2904 socket. When this happens, just close the connection. Previously,
2905 we would try harder to learn the remote address: but there was
2906 no such remote address to learn, and our method for trying to
2907 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2908 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2909 - Fix null-pointer access that could occur if TLS allocation failed.
2910 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
2911 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
2912 accidentally been reverted.
2913 - Fix our implementation of crypto_random_hostname() so it can't
2914 overflow on ridiculously large inputs. (No Tor version has ever
2915 provided this kind of bad inputs, but let's be correct in depth.)
2916 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2917 - Find more places in the code that should have been testing for
2918 invalid sockets using the SOCKET_OK macro. Required for a fix
2919 for bug 4533. Bugfix on 0.2.2.28-beta.
2920 - Fix an assertion failure when, while running with bufferevents, a
2921 connection finishes connecting after it is marked for close, but
2922 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
2923 - test_util_spawn_background_ok() hardcoded the expected value
2924 for ENOENT to 2. This isn't portable as error numbers are
2925 platform specific, and particularly the hurd has ENOENT at
2926 0x40000002. Construct expected string at runtime, using the correct
2927 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
2928 - Reject attempts to disable DisableDebuggerAttachment while Tor is
2929 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
2930 - Use an appropriate-width type for sockets in tor-fw-helper on
2931 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
2934 - When sending or relaying a RELAY_EARLY cell, we used to convert
2935 it to a RELAY cell if the connection was using the v1 link
2936 protocol. This was a workaround for older versions of Tor, which
2937 didn't handle RELAY_EARLY cells properly. Now that all supported
2938 versions can handle RELAY_EARLY cells, and now that we're enforcing
2939 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2940 remove this workaround. Addresses bug 4786.
2942 o Code simplifications and refactoring:
2943 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2944 own homebrewed ssl_state_to_string() replacement. Patch from
2945 Emile Snyder. Fixes bug 4653.
2946 - Use macros to indicate OpenSSL versions, so we don't need to worry
2947 about accidental hexadecimal bit shifts.
2948 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2950 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2951 - Use the smartlist_add_asprintf() alias more consistently.
2952 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2953 invalid value, rather than just -1.
2954 - Rename a handful of old identifiers, mostly related to crypto
2955 structures and crypto functions. By convention, our "create an
2956 object" functions are called "type_new()", our "free an object"
2957 functions are called "type_free()", and our types indicate that
2958 they are types only with a final "_t". But a handful of older
2959 types and functions broke these rules, with function names like
2960 "type_create" or "subsystem_op_type", or with type names like
2964 Changes in version 0.2.3.10-alpha - 2011-12-16
2965 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
2966 Tor's buffers code. Absolutely everybody should upgrade.
2968 The bug relied on an incorrect calculation when making data continuous
2969 in one of our IO buffers, if the first chunk of the buffer was
2970 misaligned by just the wrong amount. The miscalculation would allow an
2971 attacker to overflow a piece of heap-allocated memory. To mount this
2972 attack, the attacker would need to either open a SOCKS connection to
2973 Tor's SocksPort (usually restricted to localhost), or target a Tor
2974 instance configured to make its connections through a SOCKS proxy
2975 (which Tor does not do by default).
2977 Good security practice requires that all heap-overflow bugs should be
2978 presumed to be exploitable until proven otherwise, so we are treating
2979 this as a potential code execution attack. Please upgrade immediately!
2980 This bug does not affect bufferevents-based builds of Tor. Special
2981 thanks to "Vektor" for reporting this issue to us!
2983 This release also contains a few minor bugfixes for issues discovered
2987 - Fix a heap overflow bug that could occur when trying to pull
2988 data into the first chunk of a buffer, when that chunk had
2989 already had some data drained from it. Fixes CVE-2011-2778;
2990 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2993 - If we can't attach streams to a rendezvous circuit when we
2994 finish connecting to a hidden service, clear the rendezvous
2995 circuit's stream-isolation state and try to attach streams
2996 again. Previously, we cleared rendezvous circuits' isolation
2997 state either too early (if they were freshly built) or not at all
2998 (if they had been built earlier and were cannibalized). Bugfix on
2999 0.2.3.3-alpha; fixes bug 4655.
3000 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3001 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3002 - Fix an assertion failure when a relay with accounting enabled
3003 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3006 - Update to the December 6 2011 Maxmind GeoLite Country database.
3009 Changes in version 0.2.2.35 - 2011-12-16
3010 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3011 buffers code. Absolutely everybody should upgrade.
3013 The bug relied on an incorrect calculation when making data continuous
3014 in one of our IO buffers, if the first chunk of the buffer was
3015 misaligned by just the wrong amount. The miscalculation would allow an
3016 attacker to overflow a piece of heap-allocated memory. To mount this
3017 attack, the attacker would need to either open a SOCKS connection to
3018 Tor's SocksPort (usually restricted to localhost), or target a Tor
3019 instance configured to make its connections through a SOCKS proxy
3020 (which Tor does not do by default).
3022 Good security practice requires that all heap-overflow bugs should be
3023 presumed to be exploitable until proven otherwise, so we are treating
3024 this as a potential code execution attack. Please upgrade immediately!
3025 This bug does not affect bufferevents-based builds of Tor. Special
3026 thanks to "Vektor" for reporting this issue to us!
3028 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3029 crash bugs for unusual configurations, and a long-term bug that
3030 would prevent Tor from starting on Windows machines with draconian
3033 With this release, we remind everyone that 0.2.0.x has reached its
3034 formal end-of-life. Those Tor versions have many known flaws, and
3035 nobody should be using them. You should upgrade -- ideally to the
3036 0.2.2.x series. If you're using a Linux or BSD and its packages are
3037 obsolete, stop using those packages and upgrade anyway.
3039 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3040 longer receive support after some time in early 2012.
3043 - Fix a heap overflow bug that could occur when trying to pull
3044 data into the first chunk of a buffer, when that chunk had
3045 already had some data drained from it. Fixes CVE-2011-2778;
3046 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3047 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3048 that it doesn't attempt to allocate a socketpair. This could cause
3049 some problems on Windows systems with overzealous firewalls. Fix for
3050 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3052 - If we mark an OR connection for close based on a cell we process,
3053 don't process any further cells on it. We already avoid further
3054 reads on marked-for-close connections, but now we also discard the
3055 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3056 which was the first version where we might mark a connection for
3057 close based on processing a cell on it.
3058 - Correctly sanity-check that we don't underflow on a memory
3059 allocation (and then assert) for hidden service introduction
3060 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3061 bugfix on 0.2.1.5-alpha.
3062 - Fix a memory leak when we check whether a hidden service
3063 descriptor has any usable introduction points left. Fixes bug
3064 4424. Bugfix on 0.2.2.25-alpha.
3065 - Don't crash when we're running as a relay and don't have a GeoIP
3066 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3067 we've had in the 0.2.3.x branch already.
3068 - When running as a client, do not print a misleading (and plain
3069 wrong) log message that we're collecting "directory request"
3070 statistics: clients don't collect statistics. Also don't create a
3071 useless (because empty) stats file in the stats/ directory. Fixes
3072 bug 4353; bugfix on 0.2.2.34.
3075 - Detect failure to initialize Libevent. This fix provides better
3076 detection for future instances of bug 4457.
3077 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3078 function. This was eating up hideously large amounts of time on some
3079 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3080 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3081 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3083 - Don't warn about unused log_mutex in log.c when building with
3084 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3085 0.1.0.6-rc which introduced --disable-threads.
3086 - When configuring, starting, or stopping an NT service, stop
3087 immediately after the service configuration attempt has succeeded
3088 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3089 - When sending a NETINFO cell, include the original address
3090 received for the other side, not its canonical address. Found
3091 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3092 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3093 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3094 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3095 occurred when a client tried to fetch a descriptor for a bridge
3096 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3097 - Backport fixes for a pair of compilation warnings on Windows.
3098 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3099 - If we had ever tried to call tor_addr_to_str on an address of
3100 unknown type, we would have done a strdup on an uninitialized
3101 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3102 Reported by "troll_un".
3103 - Correctly detect and handle transient lookup failures from
3104 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3105 Reported by "troll_un".
3106 - Fix null-pointer access that could occur if TLS allocation failed.
3107 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3108 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3109 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3112 - Add two new config options for directory authorities:
3113 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3114 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3115 that is always sufficient to satisfy the bandwidth requirement for
3116 the Guard flag. Now it will be easier for researchers to simulate
3117 Tor networks with different values. Resolves ticket 4484.
3118 - When Tor ignores a hidden service specified in its configuration,
3119 include the hidden service's directory in the warning message.
3120 Previously, we would only tell the user that some hidden service
3121 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3122 - Update to the December 6 2011 Maxmind GeoLite Country database.
3124 o Packaging changes:
3125 - Make it easier to automate expert package builds on Windows,
3126 by removing an absolute path from makensis.exe command.
3129 Changes in version 0.2.1.32 - 2011-12-16
3130 Tor 0.2.1.32 backports important security and privacy fixes for
3131 oldstable. This release is intended only for package maintainers and
3132 others who cannot use the 0.2.2 stable series. All others should be
3133 using Tor 0.2.2.x or newer.
3135 The Tor 0.2.1.x series will reach formal end-of-life some time in
3136 early 2012; we will stop releasing patches for it then.
3138 o Major bugfixes (also included in 0.2.2.x):
3139 - Correctly sanity-check that we don't underflow on a memory
3140 allocation (and then assert) for hidden service introduction
3141 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3142 bugfix on 0.2.1.5-alpha.
3143 - Fix a heap overflow bug that could occur when trying to pull
3144 data into the first chunk of a buffer, when that chunk had
3145 already had some data drained from it. Fixes CVE-2011-2778;
3146 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3149 - Update to the December 6 2011 Maxmind GeoLite Country database.
3152 Changes in version 0.2.3.9-alpha - 2011-12-08
3153 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3154 a "DisableNetwork" security feature that bundles can use to avoid
3155 touching the network until bridges are configured, moves forward on
3156 the pluggable transport design, fixes a flaw in the hidden service
3157 design that unnecessarily prevented clients with wrong clocks from
3158 reaching hidden services, and fixes a wide variety of other issues.
3161 - Clients can now connect to private bridges over IPv6. Bridges
3162 still need at least one IPv4 address in order to connect to
3163 other relays. Note that we don't yet handle the case where the
3164 user has two bridge lines for the same bridge (one IPv4, one
3165 IPv6). Implements parts of proposal 186.
3166 - New "DisableNetwork" config option to prevent Tor from launching any
3167 connections or accepting any connections except on a control port.
3168 Bundles and controllers can set this option before letting Tor talk
3169 to the rest of the network, for example to prevent any connections
3170 to a non-bridge address. Packages like Orbot can also use this
3171 option to instruct Tor to save power when the network is off.
3172 - Clients and bridges can now be configured to use a separate
3173 "transport" proxy. This approach makes the censorship arms race
3174 easier by allowing bridges to use protocol obfuscation plugins. It
3175 implements the "managed proxy" part of proposal 180 (ticket 3472).
3176 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3177 implementation. It makes AES_CTR about 7% faster than our old one
3178 (which was about 10% faster than the one OpenSSL used to provide).
3179 Resolves ticket 4526.
3180 - Add a "tor2web mode" for clients that want to connect to hidden
3181 services non-anonymously (and possibly more quickly). As a safety
3182 measure to try to keep users from turning this on without knowing
3183 what they are doing, tor2web mode must be explicitly enabled at
3184 compile time, and a copy of Tor compiled to run in tor2web mode
3185 cannot be used as a normal Tor client. Implements feature 2553.
3186 - Add experimental support for running on Windows with IOCP and no
3187 kernel-space socket buffers. This feature is controlled by a new
3188 "UserspaceIOCPBuffers" config option (off by default), which has
3189 no effect unless Tor has been built with support for bufferevents,
3190 is running on Windows, and has enabled IOCP. This may, in the long
3191 run, help solve or mitigate bug 98.
3192 - Use a more secure consensus parameter voting algorithm. Now at
3193 least three directory authorities or a majority of them must
3194 vote on a given parameter before it will be included in the
3195 consensus. Implements proposal 178.
3198 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3199 They used to check that the timestamp was within 30 minutes
3200 of their system clock, so they could cap the size of their
3201 replay-detection cache, but that approach unnecessarily refused
3202 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3203 the v3 intro-point protocol (the first one which sent a timestamp
3204 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3205 - Only use the EVP interface when AES acceleration is enabled,
3206 to avoid a 5-7% performance regression. Resolves issue 4525;
3207 bugfix on 0.2.3.8-alpha.
3209 o Privacy/anonymity features (bridge detection):
3210 - Make bridge SSL certificates a bit more stealthy by using random
3211 serial numbers, in the same fashion as OpenSSL when generating
3212 self-signed certificates. Implements ticket 4584.
3213 - Introduce a new config option "DynamicDHGroups", enabled by
3214 default, which provides each bridge with a unique prime DH modulus
3215 to be used during SSL handshakes. This option attempts to help
3216 against censors who might use the Apache DH modulus as a static
3217 identifier for bridges. Addresses ticket 4548.
3219 o Minor features (new/different config options):
3220 - New configuration option "DisableDebuggerAttachment" (on by default)
3221 to prevent basic debugging attachment attempts by other processes.
3222 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3223 - Allow MapAddress directives to specify matches against super-domains,
3224 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3225 Implements issue 933.
3226 - Slightly change behavior of "list" options (that is, config
3227 options that can appear more than once) when they appear both in
3228 torrc and on the command line. Previously, the command-line options
3229 would be appended to the ones from torrc. Now, the command-line
3230 options override the torrc options entirely. This new behavior
3231 allows the user to override list options (like exit policies and
3232 ports to listen on) from the command line, rather than simply
3233 appending to the list.
3234 - You can get the old (appending) command-line behavior for "list"
3235 options by prefixing the option name with a "+".
3236 - You can remove all the values for a "list" option from the command
3237 line without adding any new ones by prefixing the option name
3239 - Add experimental support for a "defaults" torrc file to be parsed
3240 before the regular torrc. Torrc options override the defaults file's
3241 options in the same way that the command line overrides the torrc.
3242 The SAVECONF controller command saves only those options which
3243 differ between the current configuration and the defaults file. HUP
3244 reloads both files. (Note: This is an experimental feature; its
3245 behavior will probably be refined in future 0.2.3.x-alpha versions
3246 to better meet packagers' needs.) Implements task 4552.
3249 - Try to make the introductory warning message that Tor prints on
3250 startup more useful for actually finding help and information.
3251 Resolves ticket 2474.
3252 - Running "make version" now displays the version of Tor that
3253 we're about to build. Idea from katmagic; resolves issue 4400.
3254 - Expire old or over-used hidden service introduction points.
3255 Required by fix for bug 3460.
3256 - Move the replay-detection cache for the RSA-encrypted parts of
3257 INTRODUCE2 cells to the introduction point data structures.
3258 Previously, we would use one replay-detection cache per hidden
3259 service. Required by fix for bug 3460.
3260 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3261 public key replay-detection cache from 60 minutes to 5 minutes. This
3262 replay-detection cache is now used only to detect multiple
3263 INTRODUCE2 cells specifying the same rendezvous point, so we can
3264 avoid launching multiple simultaneous attempts to connect to it.
3266 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3267 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3268 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3270 - Fix a minor formatting issue in one of tor-gencert's error messages.
3272 - Prevent a false positive from the check-spaces script, by disabling
3273 the "whitespace between function name and (" check for functions
3275 - Fix a log message suggesting that people contact a non-existent
3276 email address. Fixes bug 3448.
3277 - Fix null-pointer access that could occur if TLS allocation failed.
3278 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3279 - Report a real bootstrap problem to the controller on router
3280 identity mismatch. Previously we just said "foo", which probably
3281 made a lot of sense at the time. Fixes bug 4169; bugfix on
3283 - If we had ever tried to call tor_addr_to_str() on an address of
3284 unknown type, we would have done a strdup() on an uninitialized
3285 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3286 Reported by "troll_un".
3287 - Correctly detect and handle transient lookup failures from
3288 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3289 Reported by "troll_un".
3290 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3291 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3292 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3293 bug 4532; found by "troll_un".
3295 o Minor bugfixes (on Tor 0.2.3.x):
3296 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3298 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3299 circuit for use as a hidden service client's rendezvous point.
3300 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3301 with help from wanoskarnet.
3302 - Restore behavior of overriding SocksPort, ORPort, and similar
3303 options from the command line. Bugfix on 0.2.3.3-alpha.
3306 - Properly handle the case where the build-tree is not the same
3307 as the source tree when generating src/common/common_sha1.i,
3308 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3309 bugfix on 0.2.0.1-alpha.
3311 o Code simplifications, cleanups, and refactorings:
3312 - Remove the pure attribute from all functions that used it
3313 previously. In many cases we assigned it incorrectly, because the
3314 functions might assert or call impure functions, and we don't have
3315 evidence that keeping the pure attribute is worthwhile. Implements
3316 changes suggested in ticket 4421.
3317 - Remove some dead code spotted by coverity. Fixes cid 432.
3318 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3321 Changes in version 0.2.3.8-alpha - 2011-11-22
3322 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3323 socketpair-related bug that has been bothering Windows users. It adds
3324 support to serve microdescriptors to controllers, so Vidalia's network
3325 map can resume listing relays (once Vidalia implements its side),
3326 and adds better support for hardware AES acceleration. Finally, it
3327 starts the process of adjusting the bandwidth cutoff for getting the
3328 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3329 that tiny relays harm performance more than they help network capacity.
3332 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3333 that it doesn't attempt to allocate a socketpair. This could cause
3334 some problems on Windows systems with overzealous firewalls. Fix for
3335 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3337 - Correctly sanity-check that we don't underflow on a memory
3338 allocation (and then assert) for hidden service introduction
3339 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3340 bugfix on 0.2.1.5-alpha.
3341 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3342 flag. In the past few years the average relay speed has picked
3343 up, and while the "top 7/8 of the network get the Fast flag" and
3344 "all relays with 20KB or more of capacity get the Fast flag" rules
3345 used to have the same result, now the top 7/8 of the network has
3346 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3347 - Fix a rare assertion failure when checking whether a v0 hidden
3348 service descriptor has any usable introduction points left, and
3349 we don't have enough information to build a circuit to the first
3350 intro point named in the descriptor. The HS client code in
3351 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3352 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3353 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3354 - Make bridge authorities not crash when they are asked for their own
3355 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3356 - When running as a client, do not print a misleading (and plain
3357 wrong) log message that we're collecting "directory request"
3358 statistics: clients don't collect statistics. Also don't create a
3359 useless (because empty) stats file in the stats/ directory. Fixes
3360 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3363 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3364 for a relay by identity digest or nickname. Previously,
3365 microdescriptors were only available by their own digests, so a
3366 controller would have to ask for and parse the whole microdescriptor
3367 consensus in order to look up a single relay's microdesc. Fixes
3368 bug 3832; bugfix on 0.2.3.1-alpha.
3369 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3370 operations can use hardware acceleration (if present). Resolves
3373 o Minor bugfixes (on 0.2.2.x and earlier):
3374 - Detect failure to initialize Libevent. This fix provides better
3375 detection for future instances of bug 4457.
3376 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3377 function. This was eating up hideously large amounts of time on some
3378 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3379 - Don't warn about unused log_mutex in log.c when building with
3380 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3381 0.1.0.6-rc which introduced --disable-threads.
3382 - Allow manual 'authenticate' commands to the controller interface
3383 from netcat (nc) as well as telnet. We were rejecting them because
3384 they didn't come with the expected whitespace at the end of the
3385 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3386 - Fix some (not actually triggerable) buffer size checks in usage of
3387 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3389 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3390 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3391 - When configuring, starting, or stopping an NT service, stop
3392 immediately after the service configuration attempt has succeeded
3393 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3394 - When sending a NETINFO cell, include the original address
3395 received for the other side, not its canonical address. Found
3396 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3397 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3398 can pick them up when the tests aren't disabled. Bugfix on
3399 0.2.2.4-alpha which introduced tinytest.
3400 - Fix a memory leak when we check whether a hidden service
3401 descriptor has any usable introduction points left. Fixes bug
3402 4424. Bugfix on 0.2.2.25-alpha.
3403 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3404 occurred when a client tried to fetch a descriptor for a bridge
3405 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3407 o Minor bugfixes (on 0.2.3.x):
3408 - Make util unit tests build correctly with MSVC. Bugfix on
3409 0.2.3.3-alpha. Patch by Gisle Vanem.
3410 - Successfully detect AUTH_CHALLENGE cells with no recognized
3411 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3413 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3414 it should still send a NETINFO cell to allow the connection to
3415 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3417 - Log less loudly when we get an invalid authentication certificate
3418 from a source other than a directory authority: it's not unusual
3419 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3421 - Tolerate servers with more clock skew in their authentication
3422 certificates than previously. Fixes bug 4371; bugfix on
3424 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3425 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3428 - Add two new config options for directory authorities:
3429 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3430 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3431 that is always sufficient to satisfy the bandwidth requirement for
3432 the Guard flag. Now it will be easier for researchers to simulate
3433 Tor networks with different values. Resolves ticket 4484.
3434 - When Tor ignores a hidden service specified in its configuration,
3435 include the hidden service's directory in the warning message.
3436 Previously, we would only tell the user that some hidden service
3437 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3438 - When we fail to initialize Libevent, retry with IOCP disabled so we
3439 don't need to turn on multi-threading support in Libevent, which in
3440 turn requires a working socketpair(). This is a workaround for bug
3441 4457, which affects Libevent versions from 2.0.1-alpha through
3443 - Detect when we try to build on a platform that doesn't define
3444 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3445 - Update to the November 1 2011 Maxmind GeoLite Country database.
3447 o Packaging changes:
3448 - Make it easier to automate expert package builds on Windows,
3449 by removing an absolute path from makensis.exe command.
3451 o Code simplifications and refactoring:
3452 - Remove some redundant #include directives throughout the code.
3453 Patch from Andrea Gelmini.
3454 - Unconditionally use OpenSSL's AES implementation instead of our
3455 old built-in one. OpenSSL's AES has been better for a while, and
3456 relatively few servers should still be on any version of OpenSSL
3457 that doesn't have good optimized assembly AES.
3458 - Use the name "CERTS" consistently to refer to the new cell type;
3459 we were calling it CERT in some places and CERTS in others.
3462 - Numerous new unit tests for functions in util.c and address.c by
3464 - The long-disabled benchmark tests are now split into their own
3465 ./src/test/bench binary.
3466 - The benchmark tests can now use more accurate timers than
3467 gettimeofday() when such timers are available.
3470 Changes in version 0.2.3.7-alpha - 2011-10-30
3471 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3472 the new v3 handshake. It also resolves yet another bridge address
3476 - If we mark an OR connection for close based on a cell we process,
3477 don't process any further cells on it. We already avoid further
3478 reads on marked-for-close connections, but now we also discard the
3479 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3480 which was the first version where we might mark a connection for
3481 close based on processing a cell on it.
3482 - Fix a double-free bug that would occur when we received an invalid
3483 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3484 bugfix on 0.2.3.6-alpha.
3485 - Bridges no longer include their address in NETINFO cells on outgoing
3486 OR connections, to allow them to blend in better with clients.
3487 Removes another avenue for enumerating bridges. Reported by
3488 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3489 cells were introduced.
3492 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3493 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3496 Changes in version 0.2.3.6-alpha - 2011-10-26
3497 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3498 anonymity vulnerability where an attacker can deanonymize Tor
3499 users. Everybody should upgrade.
3501 This release also features support for a new v3 connection handshake
3502 protocol, and fixes to make hidden service connections more robust.
3505 - Implement a new handshake protocol (v3) for authenticating Tors to
3506 each other over TLS. It should be more resistant to fingerprinting
3507 than previous protocols, and should require less TLS hacking for
3508 future Tor implementations. Implements proposal 176.
3509 - Allow variable-length padding cells to disguise the length of
3510 Tor's TLS records. Implements part of proposal 184.
3512 o Privacy/anonymity fixes (clients):
3513 - Clients and bridges no longer send TLS certificate chains on
3514 outgoing OR connections. Previously, each client or bridge would
3515 use the same cert chain for all outgoing OR connections until
3516 its IP address changes, which allowed any relay that the client
3517 or bridge contacted to determine which entry guards it is using.
3518 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3519 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3520 no longer considers that connection as suitable for satisfying a
3521 circuit EXTEND request. Now relays can protect clients from the
3522 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3523 - Directory authorities no longer assign the Guard flag to relays
3524 that haven't upgraded to the above "refuse EXTEND requests
3525 to client connections" fix. Now directory authorities can
3526 protect clients from the CVE-2011-2768 issue even if neither
3527 the clients nor the relays have upgraded yet. There's a new
3528 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3529 to let us transition smoothly, else tomorrow there would be no
3532 o Major bugfixes (hidden services):
3533 - Improve hidden service robustness: when an attempt to connect to
3534 a hidden service ends, be willing to refetch its hidden service
3535 descriptors from each of the HSDir relays responsible for them
3536 immediately. Previously, we would not consider refetching the
3537 service's descriptors from each HSDir for 15 minutes after the last
3538 fetch, which was inconvenient if the hidden service was not running
3539 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3540 - When one of a hidden service's introduction points appears to be
3541 unreachable, stop trying it. Previously, we would keep trying
3542 to build circuits to the introduction point until we lost the
3543 descriptor, usually because the user gave up and restarted Tor.
3544 Partly fixes bug 3825.
3545 - Don't launch a useless circuit after failing to use one of a
3546 hidden service's introduction points. Previously, we would
3547 launch a new introduction circuit, but not set the hidden service
3548 which that circuit was intended to connect to, so it would never
3549 actually be used. A different piece of code would then create a
3550 new introduction circuit correctly. Bug reported by katmagic and
3551 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3553 o Major bugfixes (other):
3554 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3555 that they initiated. Relays could distinguish incoming bridge
3556 connections from client connections, creating another avenue for
3557 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3558 Found by "frosty_un".
3559 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3560 tor gets started. This prevents a wrong average bandwidth
3561 estimate, which would cause relays to always start a new accounting
3562 interval at the earliest possible moment. Fixes bug 2003; bugfix
3563 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3564 immensely in tracking this bug down.
3565 - Fix a crash bug when changing node restrictions while a DNS lookup
3566 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3569 o Minor bugfixes (on 0.2.2.x and earlier):
3570 - When a hidden service turns an extra service-side introduction
3571 circuit into a general-purpose circuit, free the rend_data and
3572 intro_key fields first, so we won't leak memory if the circuit
3573 is cannibalized for use as another service-side introduction
3574 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3575 - Rephrase the log message emitted if the TestSocks check is
3576 successful. Patch from Fabian Keil; fixes bug 4094.
3577 - Bridges now skip DNS self-tests, to act a little more stealthily.
3578 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3579 bridges. Patch by "warms0x".
3580 - Remove a confusing dollar sign from the example fingerprint in the
3581 man page, and also make the example fingerprint a valid one. Fixes
3582 bug 4309; bugfix on 0.2.1.3-alpha.
3583 - Fix internal bug-checking logic that was supposed to catch
3584 failures in digest generation so that it will fail more robustly
3585 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3586 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3587 - Report any failure in init_keys() calls launched because our
3588 IP address has changed. Spotted by Coverity Scan. Bugfix on
3589 0.1.1.4-alpha; fixes CID 484.
3591 o Minor bugfixes (on 0.2.3.x):
3592 - Fix a bug in configure.in that kept it from building a configure
3593 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3594 bugfix on 0.2.3.1-alpha.
3595 - Don't warn users that they are exposing a client port to the
3596 Internet if they have specified an RFC1918 address. Previously,
3597 we would warn if the user had specified any non-loopback
3598 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3599 - Fix memory leaks in the failing cases of the new SocksPort and
3600 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3601 fixes coverity CIDs 485, 486, and 487.
3604 - When a hidden service's introduction point times out, consider
3605 trying it again during the next attempt to connect to the
3606 HS. Previously, we would not try it again unless a newly fetched
3607 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3608 - The next version of Windows will be called Windows 8, and it has
3609 a major version of 6, minor version of 2. Correctly identify that
3610 version instead of calling it "Very recent version". Resolves
3611 ticket 4153; reported by funkstar.
3612 - The Bridge Authority now writes statistics on how many bridge
3613 descriptors it gave out in total, and how many unique descriptors
3614 it gave out. It also lists how often the most and least commonly
3615 fetched descriptors were given out, as well as the median and
3616 25th/75th percentile. Implements tickets 4200 and 4294.
3617 - Update to the October 4 2011 Maxmind GeoLite Country database.
3619 o Code simplifications and refactoring:
3620 - Remove some old code to remember statistics about which descriptors
3621 we've served as a directory mirror. The feature wasn't used and
3622 is outdated now that microdescriptors are around.
3623 - Rename Tor functions that turn strings into addresses, so that
3624 "parse" indicates that no hostname resolution occurs, and
3625 "lookup" indicates that hostname resolution may occur. This
3626 should help prevent mistakes in the future. Fixes bug 3512.
3629 Changes in version 0.2.2.34 - 2011-10-26
3630 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3631 can deanonymize Tor users. Everybody should upgrade.
3633 The attack relies on four components: 1) Clients reuse their TLS cert
3634 when talking to different relays, so relays can recognize a user by
3635 the identity key in her cert. 2) An attacker who knows the client's
3636 identity key can probe each guard relay to see if that identity key
3637 is connected to that guard relay right now. 3) A variety of active
3638 attacks in the literature (starting from "Low-Cost Traffic Analysis
3639 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3640 discover the guard relays that a Tor user visiting the website is using.
3641 4) Clients typically pick three guards at random, so the set of guards
3642 for a given user could well be a unique fingerprint for her. This
3643 release fixes components #1 and #2, which is enough to block the attack;
3644 the other two remain as open research problems. Special thanks to
3645 "frosty_un" for reporting the issue to us!
3647 Clients should upgrade so they are no longer recognizable by the TLS
3648 certs they present. Relays should upgrade so they no longer allow a
3649 remote attacker to probe them to test whether unpatched clients are
3650 currently connected to them.
3652 This release also fixes several vulnerabilities that allow an attacker
3653 to enumerate bridge relays. Some bridge enumeration attacks still
3654 remain; see for example proposal 188.
3656 o Privacy/anonymity fixes (clients):
3657 - Clients and bridges no longer send TLS certificate chains on
3658 outgoing OR connections. Previously, each client or bridge would
3659 use the same cert chain for all outgoing OR connections until
3660 its IP address changes, which allowed any relay that the client
3661 or bridge contacted to determine which entry guards it is using.
3662 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3663 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3664 no longer considers that connection as suitable for satisfying a
3665 circuit EXTEND request. Now relays can protect clients from the
3666 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3667 - Directory authorities no longer assign the Guard flag to relays
3668 that haven't upgraded to the above "refuse EXTEND requests
3669 to client connections" fix. Now directory authorities can
3670 protect clients from the CVE-2011-2768 issue even if neither
3671 the clients nor the relays have upgraded yet. There's a new
3672 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3673 to let us transition smoothly, else tomorrow there would be no
3676 o Privacy/anonymity fixes (bridge enumeration):
3677 - Bridge relays now do their directory fetches inside Tor TLS
3678 connections, like all the other clients do, rather than connecting
3679 directly to the DirPort like public relays do. Removes another
3680 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3681 - Bridges relays now build circuits for themselves in a more similar
3682 way to how clients build them. Removes another avenue for
3683 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3684 when bridges were introduced.
3685 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3686 that they initiated. Relays could distinguish incoming bridge
3687 connections from client connections, creating another avenue for
3688 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3689 Found by "frosty_un".
3692 - Fix a crash bug when changing node restrictions while a DNS lookup
3693 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3695 - Don't launch a useless circuit after failing to use one of a
3696 hidden service's introduction points. Previously, we would
3697 launch a new introduction circuit, but not set the hidden service
3698 which that circuit was intended to connect to, so it would never
3699 actually be used. A different piece of code would then create a
3700 new introduction circuit correctly. Bug reported by katmagic and
3701 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3704 - Change an integer overflow check in the OpenBSD_Malloc code so
3705 that GCC is less likely to eliminate it as impossible. Patch
3706 from Mansour Moufid. Fixes bug 4059.
3707 - When a hidden service turns an extra service-side introduction
3708 circuit into a general-purpose circuit, free the rend_data and
3709 intro_key fields first, so we won't leak memory if the circuit
3710 is cannibalized for use as another service-side introduction
3711 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3712 - Bridges now skip DNS self-tests, to act a little more stealthily.
3713 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3714 bridges. Patch by "warms0x".
3715 - Fix internal bug-checking logic that was supposed to catch
3716 failures in digest generation so that it will fail more robustly
3717 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3718 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3719 - Report any failure in init_keys() calls launched because our
3720 IP address has changed. Spotted by Coverity Scan. Bugfix on
3721 0.1.1.4-alpha; fixes CID 484.
3723 o Minor bugfixes (log messages and documentation):
3724 - Remove a confusing dollar sign from the example fingerprint in the
3725 man page, and also make the example fingerprint a valid one. Fixes
3726 bug 4309; bugfix on 0.2.1.3-alpha.
3727 - The next version of Windows will be called Windows 8, and it has
3728 a major version of 6, minor version of 2. Correctly identify that
3729 version instead of calling it "Very recent version". Resolves
3730 ticket 4153; reported by funkstar.
3731 - Downgrade log messages about circuit timeout calibration from
3732 "notice" to "info": they don't require or suggest any human
3733 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3734 bugfix on 0.2.2.14-alpha.
3737 - Turn on directory request statistics by default and include them in
3738 extra-info descriptors. Don't break if we have no GeoIP database.
3739 Backported from 0.2.3.1-alpha; implements ticket 3951.
3740 - Update to the October 4 2011 Maxmind GeoLite Country database.
3743 Changes in version 0.2.1.31 - 2011-10-26
3744 Tor 0.2.1.31 backports important security and privacy fixes for
3745 oldstable. This release is intended only for package maintainers and
3746 others who cannot use the 0.2.2 stable series. All others should be
3747 using Tor 0.2.2.x or newer.
3749 o Security fixes (also included in 0.2.2.x):
3750 - Replace all potentially sensitive memory comparison operations
3751 with versions whose runtime does not depend on the data being
3752 compared. This will help resist a class of attacks where an
3753 adversary can use variations in timing information to learn
3754 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3755 implementation by Robert Ransom based partially on code by DJB.)
3756 - Fix an assert in parsing router descriptors containing IPv6
3757 addresses. This one took down the directory authorities when
3758 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3760 o Privacy/anonymity fixes (also included in 0.2.2.x):
3761 - Clients and bridges no longer send TLS certificate chains on
3762 outgoing OR connections. Previously, each client or bridge would
3763 use the same cert chain for all outgoing OR connections until
3764 its IP address changes, which allowed any relay that the client
3765 or bridge contacted to determine which entry guards it is using.
3766 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3767 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3768 no longer considers that connection as suitable for satisfying a
3769 circuit EXTEND request. Now relays can protect clients from the
3770 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3771 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3772 that they initiated. Relays could distinguish incoming bridge
3773 connections from client connections, creating another avenue for
3774 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3775 Found by "frosty_un".
3776 - When receiving a hidden service descriptor, check that it is for
3777 the hidden service we wanted. Previously, Tor would store any
3778 hidden service descriptors that a directory gave it, whether it
3779 wanted them or not. This wouldn't have let an attacker impersonate
3780 a hidden service, but it did let directories pre-seed a client
3781 with descriptors that it didn't want. Bugfix on 0.0.6.
3782 - Avoid linkability based on cached hidden service descriptors: forget
3783 all hidden service descriptors cached as a client when processing a
3784 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3785 - Make the bridge directory authority refuse to answer directory
3786 requests for "all" descriptors. It used to include bridge
3787 descriptors in its answer, which was a major information leak.
3788 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3789 - Don't attach new streams to old rendezvous circuits after SIGNAL
3790 NEWNYM. Previously, we would keep using an existing rendezvous
3791 circuit if it remained open (i.e. if it were kept open by a
3792 long-lived stream, or if a new stream were attached to it before
3793 Tor could notice that it was old and no longer in use). Bugfix on
3794 0.1.1.15-rc; fixes bug 3375.
3796 o Minor bugfixes (also included in 0.2.2.x):
3797 - When we restart our relay, we might get a successful connection
3798 from the outside before we've started our reachability tests,
3799 triggering a warning: "ORPort found reachable, but I have no
3800 routerinfo yet. Failing to inform controller of success." This
3801 bug was harmless unless Tor is running under a controller
3802 like Vidalia, in which case the controller would never get a
3803 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3805 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3806 enabled. Fixes bug 1526.
3807 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3808 anything since 0.2.1.16-rc.
3809 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3810 None of the cases where we did this before were wrong, but by making
3811 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3812 - Fix a rare crash bug that could occur when a client was configured
3813 with a large number of bridges. Fixes bug 2629; bugfix on
3814 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3815 - Correct the warning displayed when a rendezvous descriptor exceeds
3816 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3818 - Fix an uncommon assertion failure when running with DNSPort under
3819 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3820 - When warning about missing zlib development packages during compile,
3821 give the correct package names. Bugfix on 0.2.0.1-alpha.
3822 - Require that introduction point keys and onion keys have public
3823 exponent 65537. Bugfix on 0.2.0.10-alpha.
3824 - Do not crash when our configuration file becomes unreadable, for
3825 example due to a permissions change, between when we start up
3826 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3828 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3830 - Always NUL-terminate the sun_path field of a sockaddr_un before
3831 passing it to the kernel. (Not a security issue: kernels are
3832 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3833 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3834 - Don't stack-allocate the list of supplementary GIDs when we're
3835 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3836 could take up to 256K, which is way too much stack. Found by
3837 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3839 o Minor bugfixes (only in 0.2.1.x):
3840 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3841 rely on them. Bugfix on 0.2.1.30.
3842 - Use git revisions instead of svn revisions when generating our
3843 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3845 o Minor features (also included in 0.2.2.x):
3846 - Adjust the expiration time on our SSL session certificates to
3847 better match SSL certs seen in the wild. Resolves ticket 4014.
3848 - Allow nameservers with IPv6 address. Resolves bug 2574.
3849 - Update to the October 4 2011 Maxmind GeoLite Country database.
3852 Changes in version 0.2.3.5-alpha - 2011-09-28
3853 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
3854 bridge relays; fixes an assertion error that many users started hitting
3855 today; and adds the ability to refill token buckets more often than
3856 once per second, allowing significant performance improvements.
3859 - Bridge relays now do their directory fetches inside Tor TLS
3860 connections, like all the other clients do, rather than connecting
3861 directly to the DirPort like public relays do. Removes another
3862 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3863 - Bridges relays now build circuits for themselves in a more similar
3864 way to how clients build them. Removes another avenue for
3865 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3866 when bridges were introduced.
3869 - Fix an "Assertion md->held_by_node == 1 failed" error that could
3870 occur when the same microdescriptor was referenced by two node_t
3871 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
3873 o Major features (networking):
3874 - Add a new TokenBucketRefillInterval option to refill token buckets
3875 more frequently than once per second. This should improve network
3876 performance, alleviate queueing problems, and make traffic less
3877 bursty. Implements proposal 183; closes ticket 3630. Design by
3878 Florian Tschorsch and Björn Scheuermann; implementation by
3882 - Change an integer overflow check in the OpenBSD_Malloc code so
3883 that GCC is less likely to eliminate it as impossible. Patch
3884 from Mansour Moufid. Fixes bug 4059.
3886 o Minor bugfixes (usability):
3887 - Downgrade log messages about circuit timeout calibration from
3888 "notice" to "info": they don't require or suggest any human
3889 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3890 bugfix on 0.2.2.14-alpha.
3892 o Minor features (diagnostics):
3893 - When the system call to create a listener socket fails, log the
3894 error message explaining why. This may help diagnose bug 4027.
3897 Changes in version 0.2.3.4-alpha - 2011-09-13
3898 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
3899 tweak to Tor's TLS handshake that makes relays and bridges that run
3900 this new version reachable from Iran again. It also fixes a few new
3901 bugs in 0.2.3.x, and teaches relays to recognize when they're not
3902 listed in the network consensus and republish.
3904 o Major bugfixes (also part of 0.2.2.33):
3905 - Avoid an assertion failure when reloading a configuration with
3906 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3907 3923; bugfix on 0.2.2.25-alpha.
3909 o Minor features (security, also part of 0.2.2.33):
3910 - Check for replays of the public-key encrypted portion of an
3911 INTRODUCE1 cell, in addition to the current check for replays of
3912 the g^x value. This prevents a possible class of active attacks
3913 by an attacker who controls both an introduction point and a
3914 rendezvous point, and who uses the malleability of AES-CTR to
3915 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3916 that these attacks is infeasible (requiring the attacker to send
3917 on the order of zettabytes of altered cells in a short interval),
3918 but we'd rather block them off in case there are any classes of
3919 this attack that we missed. Reported by Willem Pinckaers.
3921 o Minor features (also part of 0.2.2.33):
3922 - Adjust the expiration time on our SSL session certificates to
3923 better match SSL certs seen in the wild. Resolves ticket 4014.
3924 - Change the default required uptime for a relay to be accepted as
3925 a HSDir (hidden service directory) from 24 hours to 25 hours.
3926 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3927 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3928 authorities to abstain from voting on assignment of the HSDir
3929 consensus flag. Related to bug 2649.
3930 - Update to the September 6 2011 Maxmind GeoLite Country database.
3932 o Minor bugfixes (also part of 0.2.2.33):
3933 - Demote the 'replay detected' log message emitted when a hidden
3934 service receives the same Diffie-Hellman public key in two different
3935 INTRODUCE2 cells to info level. A normal Tor client can cause that
3936 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3937 fixes part of bug 2442.
3938 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3939 level. There is nothing that a hidden service's operator can do
3940 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3942 - Clarify a log message specifying the characters permitted in
3943 HiddenServiceAuthorizeClient client names. Previously, the log
3944 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3945 given the impression that every ASCII character between "+" and "_"
3946 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3948 o Build fixes (also part of 0.2.2.33):
3949 - Clean up some code issues that prevented Tor from building on older
3950 BSDs. Fixes bug 3894; reported by "grarpamp".
3951 - Search for a platform-specific version of "ar" when cross-compiling.
3952 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3955 - Fix a bug where the SocksPort option (for example) would get
3956 ignored and replaced by the default if a SocksListenAddress
3957 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
3961 - Relays now try regenerating and uploading their descriptor more
3962 frequently if they are not listed in the consensus, or if the
3963 version of their descriptor listed in the consensus is too
3964 old. This fix should prevent situations where a server declines
3965 to re-publish itself because it has done so too recently, even
3966 though the authorities decided not to list its recent-enough
3967 descriptor. Fix for bug 3327.
3970 - Relays now include a reason for regenerating their descriptors
3971 in an HTTP header when uploading to the authorities. This will
3972 make it easier to debug descriptor-upload issues in the future.
3973 - When starting as root and then changing our UID via the User
3974 control option, and we have a ControlSocket configured, make sure
3975 that the ControlSocket is owned by the same account that Tor will
3976 run under. Implements ticket 3421; fix by Jérémy Bobbio.
3979 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
3980 utility function used in the control-port code). This shouldn't
3981 ever happen unless Tor is completely out of memory, but if it did
3982 happen and Tor somehow recovered from it, Tor could have sent a log
3983 message to a control port in the middle of a reply to a controller
3984 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
3985 - Make 'FetchUselessDescriptors' cause all descriptor types and
3986 all consensus types (including microdescriptors) to get fetched.
3987 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
3990 - Make a new "entry connection" struct as an internal subtype of "edge
3991 connection", to simplify the code and make exit connections smaller.
3994 Changes in version 0.2.2.33 - 2011-09-13
3995 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
3996 TLS handshake that makes relays and bridges that run this new version
3997 reachable from Iran again.
4000 - Avoid an assertion failure when reloading a configuration with
4001 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4002 3923; bugfix on 0.2.2.25-alpha.
4004 o Minor features (security):
4005 - Check for replays of the public-key encrypted portion of an
4006 INTRODUCE1 cell, in addition to the current check for replays of
4007 the g^x value. This prevents a possible class of active attacks
4008 by an attacker who controls both an introduction point and a
4009 rendezvous point, and who uses the malleability of AES-CTR to
4010 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4011 that these attacks are infeasible (requiring the attacker to send
4012 on the order of zettabytes of altered cells in a short interval),
4013 but we'd rather block them off in case there are any classes of
4014 this attack that we missed. Reported by Willem Pinckaers.
4017 - Adjust the expiration time on our SSL session certificates to
4018 better match SSL certs seen in the wild. Resolves ticket 4014.
4019 - Change the default required uptime for a relay to be accepted as
4020 a HSDir (hidden service directory) from 24 hours to 25 hours.
4021 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4022 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4023 authorities to abstain from voting on assignment of the HSDir
4024 consensus flag. Related to bug 2649.
4025 - Update to the September 6 2011 Maxmind GeoLite Country database.
4027 o Minor bugfixes (documentation and log messages):
4028 - Correct the man page to explain that HashedControlPassword and
4029 CookieAuthentication can both be set, in which case either method
4030 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4031 when we decided to allow these config options to both be set. Issue
4033 - Demote the 'replay detected' log message emitted when a hidden
4034 service receives the same Diffie-Hellman public key in two different
4035 INTRODUCE2 cells to info level. A normal Tor client can cause that
4036 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4037 fixes part of bug 2442.
4038 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4039 level. There is nothing that a hidden service's operator can do
4040 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4042 - Clarify a log message specifying the characters permitted in
4043 HiddenServiceAuthorizeClient client names. Previously, the log
4044 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4045 given the impression that every ASCII character between "+" and "_"
4046 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4049 - Provide a substitute implementation of lround() for MSVC, which
4050 apparently lacks it. Patch from Gisle Vanem.
4051 - Clean up some code issues that prevented Tor from building on older
4052 BSDs. Fixes bug 3894; reported by "grarpamp".
4053 - Search for a platform-specific version of "ar" when cross-compiling.
4054 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4057 Changes in version 0.2.3.3-alpha - 2011-09-01
4058 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4059 security, and provides client-side support for the microdescriptor
4060 and optimistic data features introduced earlier in the 0.2.3.x
4061 series. It also includes numerous critical bugfixes in the (optional)
4062 bufferevent-based networking backend.
4064 o Major features (stream isolation):
4065 - You can now configure Tor so that streams from different
4066 applications are isolated on different circuits, to prevent an
4067 attacker who sees your streams as they leave an exit node from
4068 linking your sessions to one another. To do this, choose some way
4069 to distinguish the applications: have them connect to different
4070 SocksPorts, or have one of them use SOCKS4 while the other uses
4071 SOCKS5, or have them pass different authentication strings to the
4072 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4073 degree of isolation you need. This implements Proposal 171.
4074 - There's a new syntax for specifying multiple client ports (such as
4075 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4076 multiple *Port entries with full addr:port syntax on each.
4077 The old *ListenAddress format is still supported, but you can't
4078 mix it with the new *Port syntax.
4080 o Major features (other):
4081 - Enable microdescriptor fetching by default for clients. This allows
4082 clients to download a much smaller amount of directory information.
4083 To disable it (and go back to the old-style consensus and
4084 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4085 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4086 "PortForwarding" config option), now supports Windows.
4087 - When using an exit relay running 0.2.3.x, clients can now
4088 "optimistically" send data before the exit relay reports that
4089 the stream has opened. This saves a round trip when starting
4090 connections where the client speaks first (such as web browsing).
4091 This behavior is controlled by a consensus parameter (currently
4092 disabled). To turn it on or off manually, use the "OptimisticData"
4093 torrc option. Implements proposal 181; code by Ian Goldberg.
4095 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4096 - When using IOCP on Windows, we need to enable Libevent windows
4098 - The IOCP backend now works even when the user has not specified
4099 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4100 Fixes part of bug 3752.
4101 - Correctly record the bytes we've read and written when using
4102 bufferevents, so that we can include them in our bandwidth history
4103 and advertised bandwidth. Fixes bug 3803.
4104 - Apply rate-limiting only at the bottom of a chain of filtering
4105 bufferevents. This prevents us from filling up internal read
4106 buffers and violating rate-limits when filtering bufferevents
4107 are enabled. Fixes part of bug 3804.
4108 - Add high-watermarks to the output buffers for filtered
4109 bufferevents. This prevents us from filling up internal write
4110 buffers and wasting CPU cycles when filtering bufferevents are
4111 enabled. Fixes part of bug 3804.
4112 - Correctly notice when data has been written from a bufferevent
4113 without flushing it completely. Fixes bug 3805.
4114 - Fix a bug where server-side tunneled bufferevent-based directory
4115 streams would get closed prematurely. Fixes bug 3814.
4116 - Fix a use-after-free error with per-connection rate-limiting
4117 buckets. Fixes bug 3888.
4119 o Major bugfixes (also part of 0.2.2.31-rc):
4120 - If we're configured to write our ControlPorts to disk, only write
4121 them after switching UID and creating the data directory. This way,
4122 we don't fail when starting up with a nonexistent DataDirectory
4123 and a ControlPortWriteToFile setting based on that directory. Fixes
4124 bug 3747; bugfix on Tor 0.2.2.26-beta.
4127 - Added a new CONF_CHANGED event so that controllers can be notified
4128 of any configuration changes made by other controllers, or by the
4129 user. Implements ticket 1692.
4130 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4131 leak when using bufferevents, and lets Libevent worry about how to
4132 best copy data out of a buffer.
4133 - Replace files in stats/ rather than appending to them. Now that we
4134 include statistics in extra-info descriptors, it makes no sense to
4135 keep old statistics forever. Implements ticket 2930.
4137 o Minor features (build compatibility):
4138 - Limited, experimental support for building with nmake and MSVC.
4139 - Provide a substitute implementation of lround() for MSVC, which
4140 apparently lacks it. Patch from Gisle Vanem.
4142 o Minor features (also part of 0.2.2.31-rc):
4143 - Update to the August 2 2011 Maxmind GeoLite Country database.
4145 o Minor bugfixes (on 0.2.3.x-alpha):
4146 - Fix a spurious warning when parsing SOCKS requests with
4147 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4148 - Get rid of a harmless warning that could happen on relays running
4149 with bufferevents. The warning was caused by someone doing an http
4150 request to a relay's orport. Also don't warn for a few related
4151 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4153 o Minor bugfixes (on 2.2.x and earlier):
4154 - Correct the man page to explain that HashedControlPassword and
4155 CookieAuthentication can both be set, in which case either method
4156 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4157 when we decided to allow these config options to both be set. Issue
4159 - The "--quiet" and "--hush" options now apply not only to Tor's
4160 behavior before logs are configured, but also to Tor's behavior in
4161 the absense of configured logs. Fixes bug 3550; bugfix on
4164 o Minor bugfixes (also part of 0.2.2.31-rc):
4165 - Write several files in text mode, on OSes that distinguish text
4166 mode from binary mode (namely, Windows). These files are:
4167 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4168 that collect those statistics; 'client_keys' and 'hostname' for
4169 hidden services that use authentication; and (in the tor-gencert
4170 utility) newly generated identity and signing keys. Previously,
4171 we wouldn't specify text mode or binary mode, leading to an
4172 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4173 the DirRecordUsageByCountry option which would have triggered
4174 the assertion failure was added), although this assertion failure
4175 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4176 - Selectively disable deprecation warnings on OS X because Lion
4177 started deprecating the shipped copy of openssl. Fixes bug 3643.
4178 - Remove an extra pair of quotation marks around the error
4179 message in control-port STATUS_GENERAL BUG events. Bugfix on
4180 0.1.2.6-alpha; fixes bug 3732.
4181 - When unable to format an address as a string, report its value
4182 as "???" rather than reusing the last formatted address. Bugfix
4185 o Code simplifications and refactoring:
4186 - Rewrite the listener-selection logic so that parsing which ports
4187 we want to listen on is now separate from binding to the ports
4191 - Building Tor with bufferevent support now requires Libevent
4192 2.0.13-stable or later. Previous versions of Libevent had bugs in
4193 SSL-related bufferevents and related issues that would make Tor
4194 work badly with bufferevents. Requiring 2.0.13-stable also allows
4195 Tor with bufferevents to take advantage of Libevent APIs
4196 introduced after 2.0.8-rc.
4199 Changes in version 0.2.2.32 - 2011-08-27
4200 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4201 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4202 a founder of the PETS community, a leader in our field, a mentor,
4203 and a friend. He left us with these words: "I had the possibility
4204 to contribute to this world that is not as it should be. I hope I
4205 could help in some areas to make the world a better place, and that
4206 I could also encourage other people to be engaged in improving the
4207 world. Please, stay engaged. This world needs you, your love, your
4208 initiative -- now I cannot be part of that anymore."
4210 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4211 ready. More than two years in the making, this release features improved
4212 client performance and hidden service reliability, better compatibility
4213 for Android, correct behavior for bridges that listen on more than
4214 one address, more extensible and flexible directory object handling,
4215 better reporting of network statistics, improved code security, and
4216 many many other features and bugfixes.
4219 Changes in version 0.2.2.31-rc - 2011-08-17
4220 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4221 for the Tor 0.2.2.x series.
4224 - Remove an extra pair of quotation marks around the error
4225 message in control-port STATUS_GENERAL BUG events. Bugfix on
4226 0.1.2.6-alpha; fixes bug 3732.
4227 - If we're configured to write our ControlPorts to disk, only write
4228 them after switching UID and creating the data directory. This way,
4229 we don't fail when starting up with a nonexistent DataDirectory
4230 and a ControlPortWriteToFile setting based on that directory. Fixes
4231 bug 3747; bugfix on Tor 0.2.2.26-beta.
4234 - Update to the August 2 2011 Maxmind GeoLite Country database.
4237 - Allow GETINFO fingerprint to return a fingerprint even when
4238 we have not yet built a router descriptor. Fixes bug 3577;
4239 bugfix on 0.2.0.1-alpha.
4240 - Write several files in text mode, on OSes that distinguish text
4241 mode from binary mode (namely, Windows). These files are:
4242 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4243 that collect those statistics; 'client_keys' and 'hostname' for
4244 hidden services that use authentication; and (in the tor-gencert
4245 utility) newly generated identity and signing keys. Previously,
4246 we wouldn't specify text mode or binary mode, leading to an
4247 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4248 the DirRecordUsageByCountry option which would have triggered
4249 the assertion failure was added), although this assertion failure
4250 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4251 - Selectively disable deprecation warnings on OS X because Lion
4252 started deprecating the shipped copy of openssl. Fixes bug 3643.
4253 - When unable to format an address as a string, report its value
4254 as "???" rather than reusing the last formatted address. Bugfix
4258 Changes in version 0.2.3.2-alpha - 2011-07-18
4259 Tor 0.2.3.2-alpha introduces two new experimental features:
4260 microdescriptors and pluggable transports. It also continues cleaning
4261 up a variety of recently introduced features.
4264 - Clients can now use microdescriptors instead of regular descriptors
4265 to build circuits. Microdescriptors are authority-generated
4266 summaries of regular descriptors' contents, designed to change
4267 very rarely (see proposal 158 for details). This feature is
4268 designed to save bandwidth, especially for clients on slow internet
4269 connections. It's off by default for now, since nearly no caches
4270 support it, but it will be on-by-default for clients in a future
4271 version. You can use the UseMicrodescriptors option to turn it on.
4272 - Tor clients using bridges can now be configured to use a separate
4273 'transport' proxy for each bridge. This approach helps to resist
4274 censorship by allowing bridges to use protocol obfuscation
4275 plugins. It implements part of proposal 180. Implements ticket 2841.
4276 - While we're trying to bootstrap, record how many TLS connections
4277 fail in each state, and report which states saw the most failures
4278 in response to any bootstrap failures. This feature may speed up
4279 diagnosis of censorship events. Implements ticket 3116.
4281 o Major bugfixes (on 0.2.3.1-alpha):
4282 - When configuring a large set of nodes in EntryNodes (as with
4283 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4284 random subset to be guards, and choose them in random
4285 order. Fixes bug 2798.
4286 - Tor could crash when remembering a consensus in a non-used consensus
4287 flavor without having a current consensus set. Fixes bug 3361.
4288 - Comparing an unknown address to a microdescriptor's shortened exit
4289 policy would always give a "rejected" result. Fixes bug 3599.
4290 - Using microdescriptors as a client no longer prevents Tor from
4291 uploading and downloading hidden service descriptors. Fixes
4295 - Allow nameservers with IPv6 address. Resolves bug 2574.
4296 - Accept attempts to include a password authenticator in the
4297 handshake, as supported by SOCKS5. This handles SOCKS clients that
4298 don't know how to omit a password when authenticating. Resolves
4300 - When configuring a large set of nodes in EntryNodes, and there are
4301 enough of them listed as Guard so that we don't need to consider
4302 the non-guard entries, prefer the ones listed with the Guard flag.
4303 - Check for and recover from inconsistency in the microdescriptor
4304 cache. This will make it harder for us to accidentally free a
4305 microdescriptor without removing it from the appropriate data
4306 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4307 - Log SSL state transitions at log level DEBUG, log domain
4308 HANDSHAKE. This can be useful for debugging censorship events.
4309 Implements ticket 3264.
4310 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4311 implements ticket 3439.
4313 o Minor bugfixes (on 0.2.3.1-alpha):
4314 - Do not free all general-purpose regular descriptors just
4315 because microdescriptor use is enabled. Fixes bug 3113.
4316 - Correctly link libevent_openssl when --enable-static-libevent
4317 is passed to configure. Fixes bug 3118.
4318 - Bridges should not complain during their heartbeat log messages that
4319 they are unlisted in the consensus: that's more or less the point
4320 of being a bridge. Fixes bug 3183.
4321 - Report a SIGNAL event to controllers when acting on a delayed
4322 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4323 event to the controller if we acted on a SIGNAL NEWNYM command
4324 immediately, and otherwise not report a SIGNAL event for the
4325 command at all. Fixes bug 3349.
4326 - Fix a crash when handling the SIGNAL controller command or
4327 reporting ERR-level status events with bufferevents enabled. Found
4328 by Robert Ransom. Fixes bug 3367.
4329 - Always ship the tor-fw-helper manpage in our release tarballs.
4330 Fixes bug 3389. Reported by Stephen Walker.
4331 - Fix a class of double-mark-for-close bugs when bufferevents
4332 are enabled. Fixes bug 3403.
4333 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4334 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4335 control-port command. Fixes part of bug 3465.
4336 - Prevent using negative indices during unit test runs when read_all()
4337 fails. Spotted by coverity.
4338 - Fix a rare memory leak when checking the nodelist without it being
4339 present. Found by coverity.
4340 - Only try to download a microdescriptor-flavored consensus from
4341 a directory cache that provides them.
4343 o Minor bugfixes (on 0.2.2.x and earlier):
4344 - Assert that hidden-service-related operations are not performed
4345 using single-hop circuits. Previously, Tor would assert that
4346 client-side streams are not attached to single-hop circuits,
4347 but not that other sensitive operations on the client and service
4348 side are not performed using single-hop circuits. Fixes bug 3332;
4350 - Don't publish a new relay descriptor when we reload our onion key,
4351 unless the onion key has actually changed. Fixes bug 3263 and
4352 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4353 - Allow GETINFO fingerprint to return a fingerprint even when
4354 we have not yet built a router descriptor. Fixes bug 3577;
4355 bugfix on 0.2.0.1-alpha.
4356 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4357 on 0.2.2.4-alpha; fixes bug 3427.
4359 o Code simplification and refactoring:
4360 - Use tor_sscanf() in place of scanf() in more places through the
4361 code. This makes us a little more locale-independent, and
4362 should help shut up code-analysis tools that can't tell
4363 a safe sscanf string from a dangerous one.
4364 - Use tt_assert(), not tor_assert(), for checking for test failures.
4365 This makes the unit tests more able to go on in the event that
4367 - Split connection_about_to_close() into separate functions for each
4371 - On Windows, we now define the _WIN32_WINNT macros only if they
4372 are not already defined. This lets the person building Tor decide,
4373 if they want, to require a later version of Windows.
4376 Changes in version 0.2.2.30-rc - 2011-07-07
4377 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4378 series. It fixes a few smaller bugs, but generally appears stable.
4379 Please test it and let us know whether it is!
4382 - Send a SUCCEEDED stream event to the controller when a reverse
4383 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4384 discovered by katmagic.
4385 - Always NUL-terminate the sun_path field of a sockaddr_un before
4386 passing it to the kernel. (Not a security issue: kernels are
4387 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4388 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4389 - Don't stack-allocate the list of supplementary GIDs when we're
4390 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4391 could take up to 256K, which is way too much stack. Found by
4392 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4393 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4394 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4395 fixes part of bug 3465.
4396 - Fix a memory leak when receiving a descriptor for a hidden
4397 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4401 - Update to the July 1 2011 Maxmind GeoLite Country database.
4404 Changes in version 0.2.2.29-beta - 2011-06-20
4405 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4406 have bridge lines in their torrc but don't want to use them; gets
4407 us closer to having the control socket feature working on Debian;
4408 and fixes a variety of smaller bugs.
4411 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4412 When we changed the default behavior to "use bridges if any
4413 are listed in the torrc", we surprised users who had bridges
4414 in their torrc files but who didn't actually want to use them.
4415 Partial resolution for bug 3354.
4418 - Don't attach new streams to old rendezvous circuits after SIGNAL
4419 NEWNYM. Previously, we would keep using an existing rendezvous
4420 circuit if it remained open (i.e. if it were kept open by a
4421 long-lived stream, or if a new stream were attached to it before
4422 Tor could notice that it was old and no longer in use). Bugfix on
4423 0.1.1.15-rc; fixes bug 3375.
4426 - Fix a bug when using ControlSocketsGroupWritable with User. The
4427 directory's group would be checked against the current group, not
4428 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4429 bugfix on 0.2.2.26-beta.
4430 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4431 expect it to emit a CRLF iff the format string ends with CRLF;
4432 it actually emitted a CRLF iff (a) the format string ended with
4433 CRLF or (b) the resulting string was over 1023 characters long or
4434 (c) the format string did not end with CRLF *and* the resulting
4435 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4436 fixes part of bug 3407.
4437 - Make send_control_event_impl()'s behaviour sane. Its callers
4438 expect it to always emit a CRLF at the end of the string; it
4439 might have emitted extra control characters as well. Bugfix on
4440 0.1.1.9-alpha; fixes another part of bug 3407.
4441 - Make crypto_rand_int() check the value of its input correctly.
4442 Previously, it accepted values up to UINT_MAX, but could return a
4443 negative number if given a value above INT_MAX+1. Found by George
4444 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4445 - Avoid a segfault when reading a malformed circuit build state
4446 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4448 - When asked about a DNS record type we don't support via a
4449 client DNSPort, reply with NOTIMPL rather than an empty
4450 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4451 - Fix a rare memory leak during stats writing. Found by coverity.
4454 - Update to the June 1 2011 Maxmind GeoLite Country database.
4456 o Code simplifications and refactoring:
4457 - Remove some dead code as indicated by coverity.
4458 - Remove a few dead assignments during router parsing. Found by
4460 - Add some forgotten return value checks during unit tests. Found
4462 - Don't use 1-bit wide signed bit fields. Found by coverity.
4465 Changes in version 0.2.2.28-beta - 2011-06-04
4466 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4467 fixed a big bug in whether relays stay in the consensus consistently,
4468 we moved closer to handling bridges and hidden services correctly,
4469 and we started the process of better handling the dreaded "my Vidalia
4470 died, and now my Tor demands a password when I try to reconnect to it"
4474 - Don't decide to make a new descriptor when receiving a HUP signal.
4475 This bug has caused a lot of 0.2.2.x relays to disappear from the
4476 consensus periodically. Fixes the most common case of triggering
4477 bug 1810; bugfix on 0.2.2.7-alpha.
4478 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4479 - Don't try to build descriptors if "ORPort auto" is set and we
4480 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4482 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4483 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4484 - Apply circuit timeouts to opened hidden-service-related circuits
4485 based on the correct start time. Previously, we would apply the
4486 circuit build timeout based on time since the circuit's creation;
4487 it was supposed to be applied based on time since the circuit
4488 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4489 - Use the same circuit timeout for client-side introduction
4490 circuits as for other four-hop circuits, rather than the timeout
4491 for single-hop directory-fetch circuits; the shorter timeout may
4492 have been appropriate with the static circuit build timeout in
4493 0.2.1.x and earlier, but caused many hidden service access attempts
4494 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4495 on 0.2.2.2-alpha; fixes another part of bug 1297.
4496 - In ticket 2511 we fixed a case where you could use an unconfigured
4497 bridge if you had configured it as a bridge the last time you ran
4498 Tor. Now fix another edge case: if you had configured it as a bridge
4499 but then switched to a different bridge via the controller, you
4500 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4504 - Add an __OwningControllerProcess configuration option and a
4505 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4506 that when it exits, Tor will shut down. Implements feature 3049.
4507 - If "UseBridges 1" is set and no bridges are configured, Tor will
4508 now refuse to build any circuits until some bridges are set.
4509 If "UseBridges auto" is set, Tor will use bridges if they are
4510 configured and we are not running as a server, but otherwise will
4511 make circuits as usual. The new default is "auto". Patch by anonym,
4512 so the Tails LiveCD can stop automatically revealing you as a Tor
4516 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4517 - Remove a trailing asterisk from "exit-policy/default" in the
4518 output of the control port command "GETINFO info/names". Bugfix
4520 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4522 - Warn when the user configures two HiddenServiceDir lines that point
4523 to the same directory. Bugfix on 0.0.6 (the version introducing
4524 HiddenServiceDir); fixes bug 3289.
4525 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4526 part of bug 2748; bugfix on 0.2.0.10-alpha.
4527 - Log malformed requests for rendezvous descriptors as protocol
4528 warnings, not warnings. Also, use a more informative log message
4529 in case someone sees it at log level warning without prior
4530 info-level messages. Fixes the other part of bug 2748; bugfix
4532 - Clear the table recording the time of the last request for each
4533 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4534 Previously, we would clear our HS descriptor cache on SIGNAL
4535 NEWNYM, but if we had previously retrieved a descriptor (or tried
4536 to) from every directory responsible for it, we would refuse to
4537 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4539 - Fix a log message that said "bits" while displaying a value in
4540 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4542 - When checking for 1024-bit keys, check for 1024 bits, not 128
4543 bytes. This allows Tor to correctly discard keys of length 1017
4544 through 1023. Bugfix on 0.0.9pre5.
4547 - Relays now log the reason for publishing a new relay descriptor,
4548 so we have a better chance of hunting down instances of bug 1810.
4549 Resolves ticket 3252.
4550 - Revise most log messages that refer to nodes by nickname to
4551 instead use the "$key=nickname at address" format. This should be
4552 more useful, especially since nicknames are less and less likely
4553 to be unique. Resolves ticket 3045.
4554 - Log (at info level) when purging pieces of hidden-service-client
4555 state because of SIGNAL NEWNYM.
4558 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4559 anything since 0.2.1.16-rc.
4562 Changes in version 0.2.2.27-beta - 2011-05-18
4563 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4564 release, and also adds a few more general bugfixes.
4567 - Fix a crash bug when changing bridges in a running Tor process.
4568 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4569 - When the controller configures a new bridge, don't wait 10 to 60
4570 seconds before trying to fetch its descriptor. Bugfix on
4571 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4574 - Require that onion keys have exponent 65537 in microdescriptors too.
4575 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4576 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4577 Changed the limit to 512 characters by removing base64 newlines.
4578 Fixes bug 2752. Fix by Michael Yakubovich.
4579 - When a client starts or stops using bridges, never use a circuit
4580 that was built before the configuration change. This behavior could
4581 put at risk a user who uses bridges to ensure that her traffic
4582 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4586 Changes in version 0.2.2.26-beta - 2011-05-17
4587 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4588 also introduces a new "socksport auto" approach that should make it
4589 easier to run multiple Tors on the same system, and does a lot of
4590 cleanup to get us closer to a release candidate.
4592 o Security/privacy fixes:
4593 - Replace all potentially sensitive memory comparison operations
4594 with versions whose runtime does not depend on the data being
4595 compared. This will help resist a class of attacks where an
4596 adversary can use variations in timing information to learn
4597 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4598 implementation by Robert Ransom based partially on code by DJB.)
4599 - When receiving a hidden service descriptor, check that it is for
4600 the hidden service we wanted. Previously, Tor would store any
4601 hidden service descriptors that a directory gave it, whether it
4602 wanted them or not. This wouldn't have let an attacker impersonate
4603 a hidden service, but it did let directories pre-seed a client
4604 with descriptors that it didn't want. Bugfix on 0.0.6.
4605 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4606 DNS cache entries, and virtual address mappings: that's what
4607 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4610 - The options SocksPort, ControlPort, and so on now all accept a
4611 value "auto" that opens a socket on an OS-selected port. A
4612 new ControlPortWriteToFile option tells Tor to write its
4613 actual control port or ports to a chosen file. If the option
4614 ControlPortFileGroupReadable is set, the file is created as
4615 group-readable. Now users can run two Tor clients on the same
4616 system without needing to manually mess with parameters. Resolves
4617 part of ticket 3076.
4618 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4619 help busy exit nodes avoid running out of useable ports just
4620 because all the ports have been used in the near past. Resolves
4624 - New "GETINFO net/listeners/(type)" controller command to return
4625 a list of addresses and ports that are bound for listeners for a
4626 given connection type. This is useful when the user has configured
4627 "SocksPort auto" and the controller needs to know which port got
4628 chosen. Resolves another part of ticket 3076.
4629 - Add a new ControlSocketsGroupWritable configuration option: when
4630 it is turned on, ControlSockets are group-writeable by the default
4631 group of the current user. Patch by Jérémy Bobbio; implements
4633 - Tor now refuses to create a ControlSocket in a directory that is
4634 world-readable (or group-readable if ControlSocketsGroupWritable
4635 is 0). This is necessary because some operating systems do not
4636 enforce permissions on an AF_UNIX sockets. Permissions on the
4637 directory holding the socket, however, seems to work everywhere.
4638 - Rate-limit a warning about failures to download v2 networkstatus
4639 documents. Resolves part of bug 1352.
4640 - Backport code from 0.2.3.x that allows directory authorities to
4641 clean their microdescriptor caches. Needed to resolve bug 2230.
4642 - When an HTTPS proxy reports "403 Forbidden", we now explain
4643 what it means rather than calling it an unexpected status code.
4644 Closes bug 2503. Patch from Michael Yakubovich.
4645 - Update to the May 1 2011 Maxmind GeoLite Country database.
4648 - Authorities now clean their microdesc cache periodically and when
4649 reading from disk initially, not only when adding new descriptors.
4650 This prevents a bug where we could lose microdescriptors. Bugfix
4651 on 0.2.2.6-alpha. Fixes bug 2230.
4652 - Do not crash when our configuration file becomes unreadable, for
4653 example due to a permissions change, between when we start up
4654 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4656 - Avoid a bug that would keep us from replacing a microdescriptor
4657 cache on Windows. (We would try to replace the file while still
4658 holding it open. That's fine on Unix, but Windows doesn't let us
4659 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4660 - Add missing explanations for the authority-related torrc options
4661 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4662 man page. Resolves issue 2379.
4663 - As an authority, do not upload our own vote or signature set to
4664 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4665 it would get flagged as a duplicate. Resolves bug 3026.
4666 - Accept hidden service descriptors if we think we might be a hidden
4667 service directory, regardless of what our consensus says. This
4668 helps robustness, since clients and hidden services can sometimes
4669 have a more up-to-date view of the network consensus than we do,
4670 and if they think that the directory authorities list us a HSDir,
4671 we might actually be one. Related to bug 2732; bugfix on
4673 - When a controller changes TrackHostExits, remove mappings for
4674 hosts that should no longer have their exits tracked. Bugfix on
4676 - When a controller changes VirtualAddrNetwork, remove any mappings
4677 for hosts that were automapped to the old network. Bugfix on
4679 - When a controller changes one of the AutomapHosts* options, remove
4680 any mappings for hosts that should no longer be automapped. Bugfix
4682 - Do not reset the bridge descriptor download status every time we
4683 re-parse our configuration or get a configuration change. Fixes
4684 bug 3019; bugfix on 0.2.0.3-alpha.
4686 o Minor bugfixes (code cleanup):
4687 - When loading the microdesc journal, remember its current size.
4688 In 0.2.2, this helps prevent the microdesc journal from growing
4689 without limit on authorities (who are the only ones to use it in
4690 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4691 Fix posted by "cypherpunks."
4692 - The microdesc journal is supposed to get rebuilt only if it is
4693 at least _half_ the length of the store, not _twice_ the length
4694 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4695 - Fix a potential null-pointer dereference while computing a
4696 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4698 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4699 cache without actually having any descriptors to cache. Bugfix on
4700 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4701 - If we fail to compute the identity digest of a v3 legacy keypair,
4702 warn, and don't use a buffer-full of junk instead. Bugfix on
4703 0.2.1.1-alpha; fixes bug 3106.
4704 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4705 where if the function had ever in the future been used to check
4706 for the presence of a too-large number, it would have given an
4707 incorrect result. (Fortunately, we only used it for 16-bit
4708 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4709 - Require that introduction point keys and onion handshake keys
4710 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4714 - Caches no longer download and serve v2 networkstatus documents
4715 unless FetchV2Networkstatus flag is set: these documents haven't
4716 haven't been used by clients or relays since 0.2.0.x. Resolves
4720 Changes in version 0.2.3.1-alpha - 2011-05-05
4721 Tor 0.2.3.1-alpha adds some new experimental features, including support
4722 for an improved network IO backend, IOCP networking on Windows,
4723 microdescriptor caching, "fast-start" support for streams, and automatic
4724 home router configuration. There are also numerous internal improvements
4725 to try to make the code easier for developers to work with.
4727 This is the first alpha release in a new series, so expect there to be
4728 bugs. Users who would rather test out a more stable branch should
4729 stay with 0.2.2.x for now.
4732 - Tor can now optionally build with the "bufferevents" buffered IO
4733 backend provided by Libevent 2. To use this feature, make sure you
4734 have the latest possible version of Libevent, and pass the
4735 --enable-bufferevents flag to configure when building Tor from
4736 source. This feature will make our networking code more flexible,
4737 let us stack layers on each other, and let us use more efficient
4738 zero-copy transports where available.
4739 - As an experimental feature, Tor can use IOCP for networking on Windows.
4740 Once this code is tuned and optimized, it promises much better
4741 performance than the select-based backend we've used in the past. To
4742 try this feature, you must build Tor with Libevent 2, configure Tor
4743 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4744 your torrc. There are known bugs here: only try this if you can help
4745 debug it as it breaks.
4746 - The EntryNodes option can now include country codes like {de} or IP
4747 addresses or network masks. Previously we had disallowed these options
4748 because we didn't have an efficient way to keep the list up to
4749 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4750 - Exit nodes now accept and queue data on not-yet-connected streams.
4751 Previously, the client wasn't allowed to send data until the stream was
4752 connected, which slowed down all connections. This change will enable
4753 clients to perform a "fast-start" on streams and send data without
4754 having to wait for a confirmation that the stream has opened. (Patch
4755 from Ian Goldberg; implements the server side of Proposal 174.)
4756 - Tor now has initial support for automatic port mapping on the many
4757 home routers that support NAT-PMP or UPnP. (Not yet supported on
4758 Windows). To build the support code, you'll need to have libnatpnp
4759 library and/or the libminiupnpc library, and you'll need to enable the
4760 feature specifically by passing "--enable-upnp" and/or
4761 "--enable-natpnp" to configure. To turn it on, use the new
4762 PortForwarding option.
4763 - Caches now download, cache, and serve multiple "flavors" of the
4764 consensus, including a flavor that describes microdescriptors.
4765 - Caches now download, cache, and serve microdescriptors -- small
4766 summaries of router descriptors that are authenticated by all of the
4767 directory authorities. Once enough caches are running this code,
4768 clients will be able to save significant amounts of directory bandwidth
4769 by downloading microdescriptors instead of router descriptors.
4772 - Make logging resolution configurable with a new LogTimeGranularity
4773 option, and change the default from 1 millisecond to 1 second.
4774 Implements enhancement 1668.
4775 - We log which torrc file we're using on startup. Implements ticket
4777 - Ordinarily, Tor does not count traffic from private addresses (like
4778 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4779 There is now a new option, CountPrivateBandwidth, to disable this
4780 behavior. Patch from Daniel Cagara.
4781 - New --enable-static-tor configure option for building Tor as
4782 statically as possible. Idea, general hackery and thoughts from
4783 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4785 - If you set the NumCPUs option to 0, Tor will now try to detect how
4786 many CPUs you have. This is the new default behavior.
4787 - Turn on directory request statistics by default and include them in
4788 extra-info descriptors. Don't break if we have no GeoIP database.
4789 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4790 bidirectional use of connections to disk every 24 hours.
4791 - Add a GeoIP file digest to the extra-info descriptor. Implements
4793 - The NodeFamily option -- which let you declare that you want to
4794 consider nodes to be part of a family whether they list themselves
4795 that way or not -- now allows IP address ranges and country codes.
4796 - Add a new 'Heartbeat' log message type to periodically log a message
4797 describing Tor's status at level Notice. This feature is meant for
4798 operators who log at notice, and want to make sure that their Tor
4799 server is still working. Implementation by George Kadianakis.
4801 o Minor bugfixes (on 0.2.2.25-alpha):
4802 - When loading the microdesc journal, remember its current size.
4803 In 0.2.2, this helps prevent the microdesc journal from growing
4804 without limit on authorities (who are the only ones to use it in
4805 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4806 Fix posted by "cypherpunks."
4807 - The microdesc journal is supposed to get rebuilt only if it is
4808 at least _half_ the length of the store, not _twice_ the length
4809 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4810 - If as an authority we fail to compute the identity digest of a v3
4811 legacy keypair, warn, and don't use a buffer-full of junk instead.
4812 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
4813 - Authorities now clean their microdesc cache periodically and when
4814 reading from disk initially, not only when adding new descriptors.
4815 This prevents a bug where we could lose microdescriptors. Bugfix
4818 o Minor features (controller):
4819 - Add a new SIGNAL event to the controller interface so that
4820 controllers can be notified when Tor handles a signal. Resolves
4821 issue 1955. Patch by John Brooks.
4822 - Add a new GETINFO option to get total bytes read and written. Patch
4823 from pipe, revised by atagar. Resolves ticket 2345.
4824 - Implement some GETINFO controller fields to provide information about
4825 the Tor process's pid, euid, username, and resource limits.
4828 - Our build system requires automake 1.6 or later to create the
4829 Makefile.in files. Previously, you could have used 1.4.
4830 This only affects developers and people building Tor from git;
4831 people who build Tor from the source distribution without changing
4832 the Makefile.am files should be fine.
4833 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
4834 so on. This is more robust against some of the failure modes
4835 associated with running the autotools pieces on their own.
4837 o Minor packaging issues:
4838 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
4839 already created. Patch from Andreas Stieger. Fixes bug 2573.
4841 o Code simplifications and refactoring:
4842 - A major revision to our internal node-selecting and listing logic.
4843 Tor already had at least two major ways to look at the question of
4844 "which Tor servers do we know about": a list of router descriptors,
4845 and a list of entries in the current consensus. With
4846 microdescriptors, we're adding a third. Having so many systems
4847 without an abstraction layer over them was hurting the codebase.
4848 Now, we have a new "node_t" abstraction that presents a consistent
4849 interface to a client's view of a Tor node, and holds (nearly) all
4850 of the mutable state formerly in routerinfo_t and routerstatus_t.
4851 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
4852 no longer link against Libevent: they never used it, but
4853 our library structure used to force them to link it.
4856 - Remove some old code to work around even older versions of Tor that
4857 used forked processes to handle DNS requests. Such versions of Tor
4858 are no longer in use as servers.
4860 o Documentation fixes:
4861 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
4862 - Add missing documentation for the authority-related torrc options
4863 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
4867 Changes in version 0.2.2.25-alpha - 2011-04-29
4868 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
4869 robust, routers no longer overreport their bandwidth, Win7 should crash
4870 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
4871 now prevents hidden service-related activity from being linkable. It
4872 provides more information to Vidalia so you can see if your bridge is
4873 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
4874 StrictNodes configuration options to make them more reliable, more
4875 understandable, and more regularly applied. If you use those options,
4876 please see the revised documentation for them in the manual page.
4879 - Relays were publishing grossly inflated bandwidth values because
4880 they were writing their state files wrong--now they write the
4881 correct value. Also, resume reading bandwidth history from the
4882 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
4883 - Improve hidden service robustness: When we find that we have
4884 extended a hidden service's introduction circuit to a relay not
4885 listed as an introduction point in the HS descriptor we currently
4886 have, retry with an introduction point from the current
4887 descriptor. Previously we would just give up. Fixes bugs 1024 and
4888 1930; bugfix on 0.2.0.10-alpha.
4889 - Clients now stop trying to use an exit node associated with a given
4890 destination by TrackHostExits if they fail to reach that exit node.
4891 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4892 - Fix crash bug on platforms where gmtime and localtime can return
4893 NULL. Windows 7 users were running into this one. Fixes part of bug
4894 2077. Bugfix on all versions of Tor. Found by boboper.
4896 o Security and stability fixes:
4897 - Don't double-free a parsable, but invalid, microdescriptor, even if
4898 it is followed in the blob we're parsing by an unparsable
4899 microdescriptor. Fixes an issue reported in a comment on bug 2954.
4900 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
4901 - If the Nickname configuration option isn't given, Tor would pick a
4902 nickname based on the local hostname as the nickname for a relay.
4903 Because nicknames are not very important in today's Tor and the
4904 "Unnamed" nickname has been implemented, this is now problematic
4905 behavior: It leaks information about the hostname without being
4906 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4907 introduced the Unnamed nickname. Reported by tagnaq.
4908 - Fix an uncommon assertion failure when running with DNSPort under
4909 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4910 - Avoid linkability based on cached hidden service descriptors: forget
4911 all hidden service descriptors cached as a client when processing a
4912 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4915 - Export GeoIP information on bridge usage to controllers even if we
4916 have not yet been running for 24 hours. Now Vidalia bridge operators
4917 can get more accurate and immediate feedback about their
4918 contributions to the network.
4920 o Major features and bugfixes (node selection):
4921 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4922 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
4923 options. Previously, we had been ambiguous in describing what
4924 counted as an "exit" node, and what operations exactly "StrictNodes
4925 0" would permit. This created confusion when people saw nodes built
4926 through unexpected circuits, and made it hard to tell real bugs from
4927 surprises. Now the intended behavior is:
4928 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4929 a node that delivers user traffic outside the Tor network.
4930 . "Entry", in the context of EntryNodes, means a node used as the
4931 first hop of a multihop circuit. It doesn't include direct
4932 connections to directory servers.
4933 . "ExcludeNodes" applies to all nodes.
4934 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4935 StrictNodes is set, Tor should avoid all nodes listed in
4936 ExcludeNodes, even when it will make user requests fail. When
4937 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4938 whenever it can, except when it must use an excluded node to
4939 perform self-tests, connect to a hidden service, provide a
4940 hidden service, fulfill a .exit request, upload directory
4941 information, or fetch directory information.
4942 Collectively, the changes to implement the behavior fix bug 1090.
4943 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4944 a node is listed in both, it's treated as excluded.
4945 - ExcludeNodes now applies to directory nodes -- as a preference if
4946 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4947 Don't exclude all the directory authorities and set StrictNodes to 1
4948 unless you really want your Tor to break.
4949 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4950 - ExcludeExitNodes now overrides .exit requests.
4951 - We don't use bridges listed in ExcludeNodes.
4952 - When StrictNodes is 1:
4953 . We now apply ExcludeNodes to hidden service introduction points
4954 and to rendezvous points selected by hidden service users. This
4955 can make your hidden service less reliable: use it with caution!
4956 . If we have used ExcludeNodes on ourself, do not try relay
4957 reachability self-tests.
4958 . If we have excluded all the directory authorities, we will not
4959 even try to upload our descriptor if we're a relay.
4960 . Do not honor .exit requests to an excluded node.
4961 - Remove a misfeature that caused us to ignore the Fast/Stable flags
4962 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
4963 - When the set of permitted nodes changes, we now remove any mappings
4964 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
4966 - We never cannibalize a circuit that had excluded nodes on it, even
4967 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
4968 - Revert a change where we would be laxer about attaching streams to
4969 circuits than when building the circuits. This was meant to prevent
4970 a set of bugs where streams were never attachable, but our improved
4971 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
4972 - Keep track of how many times we launch a new circuit to handle a
4973 given stream. Too many launches could indicate an inconsistency
4974 between our "launch a circuit to handle this stream" logic and our
4975 "attach this stream to one of the available circuits" logic.
4976 - Improve log messages related to excluded nodes.
4979 - Fix a spurious warning when moving from a short month to a long
4980 month on relays with month-based BandwidthAccounting. Bugfix on
4981 0.2.2.17-alpha; fixes bug 3020.
4982 - When a client finds that an origin circuit has run out of 16-bit
4983 stream IDs, we now mark it as unusable for new streams. Previously,
4984 we would try to close the entire circuit. Bugfix on 0.0.6.
4985 - Add a forgotten cast that caused a compile warning on OS X 10.6.
4986 Bugfix on 0.2.2.24-alpha.
4987 - Be more careful about reporting the correct error from a failed
4988 connect() system call. Under some circumstances, it was possible to
4989 look at an incorrect value for errno when sending the end reason.
4990 Bugfix on 0.1.0.1-rc.
4991 - Correctly handle an "impossible" overflow cases in connection byte
4992 counting, where we write or read more than 4GB on an edge connection
4993 in a single second. Bugfix on 0.1.2.8-beta.
4994 - Correct the warning displayed when a rendezvous descriptor exceeds
4995 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4997 - Clients and hidden services now use HSDir-flagged relays for hidden
4998 service descriptor downloads and uploads even if the relays have no
4999 DirPort set and the client has disabled TunnelDirConns. This will
5000 eventually allow us to give the HSDir flag to relays with no
5001 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5002 - Downgrade "no current certificates known for authority" message from
5003 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5004 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5005 2917. Bugfix on 0.1.1.1-alpha.
5006 - Only limit the lengths of single HS descriptors, even when multiple
5007 HS descriptors are published to an HSDir relay in a single POST
5008 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5009 - Write the current time into the LastWritten line in our state file,
5010 rather than the time from the previous write attempt. Also, stop
5011 trying to use a time of -1 in our log statements. Fixes bug 3039;
5012 bugfix on 0.2.2.14-alpha.
5013 - Be more consistent in our treatment of file system paths. "~" should
5014 get expanded to the user's home directory in the Log config option.
5015 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5016 feature for the -f and --DataDirectory options.
5019 - Make sure every relay writes a state file at least every 12 hours.
5020 Previously, a relay could go for weeks without writing its state
5021 file, and on a crash could lose its bandwidth history, capacity
5022 estimates, client country statistics, and so on. Addresses bug 3012.
5023 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5024 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5025 clients are already deprecated because of security bugs.
5026 - Don't allow v0 hidden service authorities to act as clients.
5027 Required by fix for bug 3000.
5028 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5029 by fix for bug 3000.
5030 - Ensure that no empty [dirreq-](read|write)-history lines are added
5031 to an extrainfo document. Implements ticket 2497.
5033 o Code simplification and refactoring:
5034 - Remove workaround code to handle directory responses from servers
5035 that had bug 539 (they would send HTTP status 503 responses _and_
5036 send a body too). Since only server versions before
5037 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5038 keep the workaround in place.
5039 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5040 handling calculations where we have a known amount of clock skew and
5041 an allowed amount of unknown skew. But we only used it in three
5042 places, and we never adjusted the known/unknown skew values. This is
5043 still something we might want to do someday, but if we do, we'll
5044 want to do it differently.
5045 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5046 None of the cases where we did this before were wrong, but by making
5047 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5048 - Use GetTempDir to find the proper temporary directory location on
5049 Windows when generating temporary files for the unit tests. Patch by
5053 Changes in version 0.2.2.24-alpha - 2011-04-08
5054 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5055 prevented Tor clients from effectively using "multihomed" bridges,
5056 that is, bridges that listen on multiple ports or IP addresses so users
5057 can continue to use some of their addresses even if others get blocked.
5060 - Fix a bug where bridge users who configure the non-canonical
5061 address of a bridge automatically switch to its canonical
5062 address. If a bridge listens at more than one address, it should be
5063 able to advertise those addresses independently and any non-blocked
5064 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5066 - If you configured Tor to use bridge A, and then quit and
5067 configured Tor to use bridge B instead, it would happily continue
5068 to use bridge A if it's still reachable. While this behavior is
5069 a feature if your goal is connectivity, in some scenarios it's a
5070 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5071 - Directory authorities now use data collected from their own
5072 uptime observations when choosing whether to assign the HSDir flag
5073 to relays, instead of trusting the uptime value the relay reports in
5074 its descriptor. This change helps prevent an attack where a small
5075 set of nodes with frequently-changing identity keys can blackhole
5076 a hidden service. (Only authorities need upgrade; others will be
5077 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5080 - When we restart our relay, we might get a successful connection
5081 from the outside before we've started our reachability tests,
5082 triggering a warning: "ORPort found reachable, but I have no
5083 routerinfo yet. Failing to inform controller of success." This
5084 bug was harmless unless Tor is running under a controller
5085 like Vidalia, in which case the controller would never get a
5086 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5088 - Make directory authorities more accurate at recording when
5089 relays that have failed several reachability tests became
5090 unreachable, so we can provide more accuracy at assigning Stable,
5091 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5092 - Fix an issue that prevented static linking of libevent on
5093 some platforms (notably Linux). Fixes bug 2698; bugfix on
5094 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5095 the --with-static-libevent configure option).
5096 - We now ask the other side of a stream (the client or the exit)
5097 for more data on that stream when the amount of queued data on
5098 that stream dips low enough. Previously, we wouldn't ask the
5099 other side for more data until either it sent us more data (which
5100 it wasn't supposed to do if it had exhausted its window!) or we
5101 had completely flushed all our queued data. This flow control fix
5102 should improve throughput. Fixes bug 2756; bugfix on the earliest
5103 released versions of Tor (svn commit r152).
5104 - Avoid a double-mark-for-free warning when failing to attach a
5105 transparent proxy connection. (We thought we had fixed this in
5106 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5107 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5108 bug) and 0.2.2.23-alpha (the incorrect fix).
5109 - When warning about missing zlib development packages during compile,
5110 give the correct package names. Bugfix on 0.2.0.1-alpha.
5113 - Directory authorities now log the source of a rejected POSTed v3
5115 - Make compilation with clang possible when using
5116 --enable-gcc-warnings by removing two warning options that clang
5117 hasn't implemented yet and by fixing a few warnings. Implements
5119 - When expiring circuits, use microsecond timers rather than
5120 one-second timers. This can avoid an unpleasant situation where a
5121 circuit is launched near the end of one second and expired right
5122 near the beginning of the next, and prevent fluctuations in circuit
5124 - Use computed circuit-build timeouts to decide when to launch
5125 parallel introduction circuits for hidden services. (Previously,
5126 we would retry after 15 seconds.)
5127 - Update to the April 1 2011 Maxmind GeoLite Country database.
5130 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5131 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5133 o Documentation changes:
5134 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5135 - Resolve all doxygen warnings except those for missing documentation.
5137 - Add doxygen documentation for more functions, fields, and types.
5140 Changes in version 0.2.2.23-alpha - 2011-03-08
5141 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5142 they restart they don't lose their bandwidth capacity estimate. This
5143 release also fixes a diverse set of user-facing bugs, ranging from
5144 relays overrunning their rate limiting to clients falsely warning about
5145 clock skew to bridge descriptor leaks by our bridge directory authority.
5148 - Stop sending a CLOCK_SKEW controller status event whenever
5149 we fetch directory information from a relay that has a wrong clock.
5150 Instead, only inform the controller when it's a trusted authority
5151 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5152 the rest of bug 1074.
5153 - Fix an assert in parsing router descriptors containing IPv6
5154 addresses. This one took down the directory authorities when
5155 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5156 - Make the bridge directory authority refuse to answer directory
5157 requests for "all" descriptors. It used to include bridge
5158 descriptors in its answer, which was a major information leak.
5159 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5160 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5161 Tor would ignore their RelayBandwidthBurst setting,
5162 potentially using more bandwidth than expected. Bugfix on
5163 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5164 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5165 hidserv" in her torrc. The 'hidserv' argument never controlled
5166 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5169 - Relays now save observed peak bandwidth throughput rates to their
5170 state file (along with total usage, which was already saved)
5171 so that they can determine their correct estimated bandwidth on
5172 restart. Resolves bug 1863, where Tor relays would reset their
5173 estimated bandwidth to 0 after restarting.
5174 - Directory authorities now take changes in router IP address and
5175 ORPort into account when determining router stability. Previously,
5176 if a router changed its IP or ORPort, the authorities would not
5177 treat it as having any downtime for the purposes of stability
5178 calculation, whereas clients would experience downtime since the
5179 change could take a while to propagate to them. Resolves issue 1035.
5180 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5181 Prevention (DEP) by default on Windows to make it harder for
5182 attackers to exploit vulnerabilities. Patch from John Brooks.
5184 o Minor bugfixes (on 0.2.1.x and earlier):
5185 - Fix a rare crash bug that could occur when a client was configured
5186 with a large number of bridges. Fixes bug 2629; bugfix on
5187 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5188 - Avoid a double mark-for-free warning when failing to attach a
5189 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5191 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5192 found by "cypherpunks". This bug was introduced before the first
5193 Tor release, in svn commit r110.
5194 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5195 don't mention them in the manpage. Fixes bug 2450; issue
5196 spotted by keb and G-Lo.
5197 - Fix a bug in bandwidth history state parsing that could have been
5198 triggered if a future version of Tor ever changed the timing
5199 granularity at which bandwidth history is measured. Bugfix on
5201 - When a relay decides that its DNS is too broken for it to serve
5202 as an exit server, it advertised itself as a non-exit, but
5203 continued to act as an exit. This could create accidental
5204 partitioning opportunities for users. Instead, if a relay is
5205 going to advertise reject *:* as its exit policy, it should
5206 really act with exit policy "reject *:*". Fixes bug 2366.
5207 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5208 - In the special case where you configure a public exit relay as your
5209 bridge, Tor would be willing to use that exit relay as the last
5210 hop in your circuit as well. Now we fail that circuit instead.
5211 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5212 - Fix a bug with our locking implementation on Windows that couldn't
5213 correctly detect when a file was already locked. Fixes bug 2504,
5214 bugfix on 0.2.1.6-alpha.
5215 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5216 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5218 - Set target port in get_interface_address6() correctly. Bugfix
5219 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5220 - Directory authorities are now more robust to hops back in time
5221 when calculating router stability. Previously, if a run of uptime
5222 or downtime appeared to be negative, the calculation could give
5223 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5225 - Fix an assert that got triggered when using the TestingTorNetwork
5226 configuration option and then issuing a GETINFO config-text control
5227 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5229 o Minor bugfixes (on 0.2.2.x):
5230 - Clients should not weight BadExit nodes as Exits in their node
5231 selection. Similarly, directory authorities should not count BadExit
5232 bandwidth as Exit bandwidth when computing bandwidth-weights.
5233 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5234 - Correctly clear our dir_read/dir_write history when there is an
5235 error parsing any bw history value from the state file. Bugfix on
5237 - Resolve a bug in verifying signatures of directory objects
5238 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5239 Fixes bug 2409. Found by "piebeer".
5240 - Bridge authorities no longer crash on SIGHUP when they try to
5241 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5245 - Log less aggressively about circuit timeout changes, and improve
5246 some other circuit timeout messages. Resolves bug 2004.
5247 - Log a little more clearly about the times at which we're no longer
5248 accepting new connections. Resolves bug 2181.
5249 - Reject attempts at the client side to open connections to private
5250 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5251 a randomly chosen exit node. Attempts to do so are always
5252 ill-defined, generally prevented by exit policies, and usually
5253 in error. This will also help to detect loops in transparent
5254 proxy configurations. You can disable this feature by setting
5255 "ClientRejectInternalAddresses 0" in your torrc.
5256 - Always treat failure to allocate an RSA key as an unrecoverable
5258 - Update to the March 1 2011 Maxmind GeoLite Country database.
5260 o Minor features (log subsystem):
5261 - Add documentation for configuring logging at different severities in
5262 different log domains. We've had this feature since 0.2.1.1-alpha,
5263 but for some reason it never made it into the manpage. Fixes
5265 - Make it simpler to specify "All log domains except for A and B".
5266 Previously you needed to say "[*,~A,~B]". Now you can just say
5268 - Add a "LogMessageDomains 1" option to include the domains of log
5269 messages along with the messages. Without this, there's no way
5270 to use log domains without reading the source or doing a lot
5273 o Packaging changes:
5274 - Stop shipping the Tor specs files and development proposal documents
5275 in the tarball. They are now in a separate git repository at
5276 git://git.torproject.org/torspec.git
5279 Changes in version 0.2.1.30 - 2011-02-23
5280 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5281 change is a slight tweak to Tor's TLS handshake that makes relays
5282 and bridges that run this new version reachable from Iran again.
5283 We don't expect this tweak will win the arms race long-term, but it
5284 buys us time until we roll out a better solution.
5287 - Stop sending a CLOCK_SKEW controller status event whenever
5288 we fetch directory information from a relay that has a wrong clock.
5289 Instead, only inform the controller when it's a trusted authority
5290 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5291 the rest of bug 1074.
5292 - Fix a bounds-checking error that could allow an attacker to
5293 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5295 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5296 Tor would ignore their RelayBandwidthBurst setting,
5297 potentially using more bandwidth than expected. Bugfix on
5298 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5299 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5300 hidserv" in her torrc. The 'hidserv' argument never controlled
5301 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5304 - Adjust our TLS Diffie-Hellman parameters to match those used by
5306 - Update to the February 1 2011 Maxmind GeoLite Country database.
5309 - Check for and reject overly long directory certificates and
5310 directory tokens before they have a chance to hit any assertions.
5311 Bugfix on 0.2.1.28. Found by "doorss".
5312 - Bring the logic that gathers routerinfos and assesses the
5313 acceptability of circuits into line. This prevents a Tor OP from
5314 getting locked in a cycle of choosing its local OR as an exit for a
5315 path (due to a .exit request) and then rejecting the circuit because
5316 its OR is not listed yet. It also prevents Tor clients from using an
5317 OR running in the same instance as an exit (due to a .exit request)
5318 if the OR does not meet the same requirements expected of an OR
5319 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5321 o Packaging changes:
5322 - Stop shipping the Tor specs files and development proposal documents
5323 in the tarball. They are now in a separate git repository at
5324 git://git.torproject.org/torspec.git
5325 - Do not include Git version tags as though they are SVN tags when
5326 generating a tarball from inside a repository that has switched
5327 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5330 Changes in version 0.2.2.22-alpha - 2011-01-25
5331 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5332 main other change is a slight tweak to Tor's TLS handshake that makes
5333 relays and bridges that run this new version reachable from Iran again.
5334 We don't expect this tweak will win the arms race long-term, but it
5335 will buy us a bit more time until we roll out a better solution.
5338 - Fix a bounds-checking error that could allow an attacker to
5339 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5341 - Don't assert when changing from bridge to relay or vice versa
5342 via the controller. The assert happened because we didn't properly
5343 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5344 bug 2433. Reported by bastik.
5347 - Adjust our TLS Diffie-Hellman parameters to match those used by
5349 - Provide a log message stating which geoip file we're parsing
5350 instead of just stating that we're parsing the geoip file.
5351 Implements ticket 2432.
5354 - Check for and reject overly long directory certificates and
5355 directory tokens before they have a chance to hit any assertions.
5356 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5359 Changes in version 0.2.2.21-alpha - 2011-01-15
5360 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5361 continues our recent code security audit work. The main fix resolves
5362 a remote heap overflow vulnerability that can allow remote code
5363 execution (CVE-2011-0427). Other fixes address a variety of assert
5364 and crash bugs, most of which we think are hard to exploit remotely.
5366 o Major bugfixes (security), also included in 0.2.1.29:
5367 - Fix a heap overflow bug where an adversary could cause heap
5368 corruption. This bug probably allows remote code execution
5369 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5371 - Prevent a denial-of-service attack by disallowing any
5372 zlib-compressed data whose compression factor is implausibly
5373 high. Fixes part of bug 2324; reported by "doorss".
5374 - Zero out a few more keys in memory before freeing them. Fixes
5375 bug 2384 and part of bug 2385. These key instances found by
5376 "cypherpunks", based on Andrew Case's report about being able
5377 to find sensitive data in Tor's memory space if you have enough
5378 permissions. Bugfix on 0.0.2pre9.
5380 o Major bugfixes (crashes), also included in 0.2.1.29:
5381 - Prevent calls to Libevent from inside Libevent log handlers.
5382 This had potential to cause a nasty set of crashes, especially
5383 if running Libevent with debug logging enabled, and running
5384 Tor with a controller watching for low-severity log messages.
5385 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5386 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5387 underflow errors there too. Fixes the other part of bug 2324.
5388 - Fix a bug where we would assert if we ever had a
5389 cached-descriptors.new file (or another file read directly into
5390 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5391 on 0.2.1.25. Found by doorss.
5392 - Fix some potential asserts and parsing issues with grossly
5393 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5396 o Minor bugfixes (other), also included in 0.2.1.29:
5397 - Fix a bug with handling misformed replies to reverse DNS lookup
5398 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5399 bug reported by doorss.
5400 - Fix compilation on mingw when a pthreads compatibility library
5401 has been installed. (We don't want to use it, so we shouldn't
5402 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5403 - Fix a bug where we would declare that we had run out of virtual
5404 addresses when the address space was only half-exhausted. Bugfix
5406 - Correctly handle the case where AutomapHostsOnResolve is set but
5407 no virtual addresses are available. Fixes bug 2328; bugfix on
5408 0.1.2.1-alpha. Bug found by doorss.
5409 - Correctly handle wrapping around when we run out of virtual
5410 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5412 o Minor features, also included in 0.2.1.29:
5413 - Update to the January 1 2011 Maxmind GeoLite Country database.
5414 - Introduce output size checks on all of our decryption functions.
5416 o Build changes, also included in 0.2.1.29:
5417 - Tor does not build packages correctly with Automake 1.6 and earlier;
5418 added a check to Makefile.am to make sure that we're building with
5419 Automake 1.7 or later.
5420 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5421 because we built it with a too-old version of automake. Thus that
5422 release broke ./configure --enable-openbsd-malloc, which is popular
5423 among really fast exit relays on Linux.
5425 o Major bugfixes, new in 0.2.2.21-alpha:
5426 - Prevent crash/heap corruption when the cbtnummodes consensus
5427 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5430 o Major features, new in 0.2.2.21-alpha:
5431 - Introduce minimum/maximum values that clients will believe
5432 from the consensus. Now we'll have a better chance to avoid crashes
5433 or worse when a consensus param has a weird value.
5435 o Minor features, new in 0.2.2.21-alpha:
5436 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5437 used on bridges, and it makes bridge scanning somewhat easier.
5438 - If writing the state file to disk fails, wait up to an hour before
5439 retrying again, rather than trying again each second. Fixes bug
5440 2346; bugfix on Tor 0.1.1.3-alpha.
5441 - Make Libevent log messages get delivered to controllers later,
5442 and not from inside the Libevent log handler. This prevents unsafe
5443 reentrant Libevent calls while still letting the log messages
5445 - Detect platforms that brokenly use a signed size_t, and refuse to
5446 build there. Found and analyzed by doorss and rransom.
5447 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5450 o Minor bugfixes, new in 0.2.2.21-alpha:
5451 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5452 than waiting forever for them to finish. Fixes bug 2330; bugfix
5453 on 0.2.0.16-alpha. Found by doorss.
5454 - Add assertions to check for overflow in arguments to
5455 base32_encode() and base32_decode(); fix a signed-unsigned
5456 comparison there too. These bugs are not actually reachable in Tor,
5457 but it's good to prevent future errors too. Found by doorss.
5458 - Correctly detect failures to create DNS requests when using Libevent
5459 versions before v2. (Before Libevent 2, we used our own evdns
5460 implementation. Its return values for Libevent's evdns_resolve_*()
5461 functions are not consistent with those from Libevent.) Fixes bug
5462 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5464 o Documentation, new in 0.2.2.21-alpha:
5465 - Document the default socks host and port (127.0.0.1:9050) for
5469 Changes in version 0.2.1.29 - 2011-01-15
5470 Tor 0.2.1.29 continues our recent code security audit work. The main
5471 fix resolves a remote heap overflow vulnerability that can allow remote
5472 code execution. Other fixes address a variety of assert and crash bugs,
5473 most of which we think are hard to exploit remotely.
5475 o Major bugfixes (security):
5476 - Fix a heap overflow bug where an adversary could cause heap
5477 corruption. This bug probably allows remote code execution
5478 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5480 - Prevent a denial-of-service attack by disallowing any
5481 zlib-compressed data whose compression factor is implausibly
5482 high. Fixes part of bug 2324; reported by "doorss".
5483 - Zero out a few more keys in memory before freeing them. Fixes
5484 bug 2384 and part of bug 2385. These key instances found by
5485 "cypherpunks", based on Andrew Case's report about being able
5486 to find sensitive data in Tor's memory space if you have enough
5487 permissions. Bugfix on 0.0.2pre9.
5489 o Major bugfixes (crashes):
5490 - Prevent calls to Libevent from inside Libevent log handlers.
5491 This had potential to cause a nasty set of crashes, especially
5492 if running Libevent with debug logging enabled, and running
5493 Tor with a controller watching for low-severity log messages.
5494 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5495 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5496 underflow errors there too. Fixes the other part of bug 2324.
5497 - Fix a bug where we would assert if we ever had a
5498 cached-descriptors.new file (or another file read directly into
5499 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5500 on 0.2.1.25. Found by doorss.
5501 - Fix some potential asserts and parsing issues with grossly
5502 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5505 o Minor bugfixes (other):
5506 - Fix a bug with handling misformed replies to reverse DNS lookup
5507 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5508 bug reported by doorss.
5509 - Fix compilation on mingw when a pthreads compatibility library
5510 has been installed. (We don't want to use it, so we shouldn't
5511 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5512 - Fix a bug where we would declare that we had run out of virtual
5513 addresses when the address space was only half-exhausted. Bugfix
5515 - Correctly handle the case where AutomapHostsOnResolve is set but
5516 no virtual addresses are available. Fixes bug 2328; bugfix on
5517 0.1.2.1-alpha. Bug found by doorss.
5518 - Correctly handle wrapping around to when we run out of virtual
5519 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5520 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5521 because we built it with a too-old version of automake. Thus that
5522 release broke ./configure --enable-openbsd-malloc, which is popular
5523 among really fast exit relays on Linux.
5526 - Update to the January 1 2011 Maxmind GeoLite Country database.
5527 - Introduce output size checks on all of our decryption functions.
5530 - Tor does not build packages correctly with Automake 1.6 and earlier;
5531 added a check to Makefile.am to make sure that we're building with
5532 Automake 1.7 or later.
5535 Changes in version 0.2.2.20-alpha - 2010-12-17
5536 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5537 exploitable bugs. We also fix a variety of other significant bugs,
5538 change the IP address for one of our directory authorities, and update
5539 the minimum version that Tor relays must run to join the network.
5542 - Fix a remotely exploitable bug that could be used to crash instances
5543 of Tor remotely by overflowing on the heap. Remote-code execution
5544 hasn't been confirmed, but can't be ruled out. Everyone should
5545 upgrade. Bugfix on the 0.1.1 series and later.
5546 - Fix a bug that could break accounting on 64-bit systems with large
5547 time_t values, making them hibernate for impossibly long intervals.
5548 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5549 - Fix a logic error in directory_fetches_from_authorities() that
5550 would cause all _non_-exits refusing single-hop-like circuits
5551 to fetch from authorities, when we wanted to have _exits_ fetch
5552 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5554 - Fix a stream fairness bug that would cause newer streams on a given
5555 circuit to get preference when reading bytes from the origin or
5556 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5557 introduced before the first Tor release, in svn revision r152.
5559 o Directory authority changes:
5560 - Change IP address and ports for gabelmoo (v3 directory authority).
5563 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5564 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5565 - Fix an off-by-one error in calculating some controller command
5566 argument lengths. Fortunately, this mistake is harmless since
5567 the controller code does redundant NUL termination too. Found by
5568 boboper. Bugfix on 0.1.1.1-alpha.
5569 - Do not dereference NULL if a bridge fails to build its
5570 extra-info descriptor. Found by an anonymous commenter on
5571 Trac. Bugfix on 0.2.2.19-alpha.
5574 - Update to the December 1 2010 Maxmind GeoLite Country database.
5575 - Directory authorities now reject relays running any versions of
5576 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5577 known bugs that keep RELAY_EARLY cells from working on rendezvous
5578 circuits. Followup to fix for bug 2081.
5579 - Directory authorities now reject relays running any version of Tor
5580 older than 0.2.0.26-rc. That version is the earliest that fetches
5581 current directory information correctly. Fixes bug 2156.
5582 - Report only the top 10 ports in exit-port stats in order not to
5583 exceed the maximum extra-info descriptor length of 50 KB. Implements
5587 Changes in version 0.2.1.28 - 2010-12-17
5588 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5589 exploitable bugs. We also took this opportunity to change the IP address
5590 for one of our directory authorities, and to update the geoip database
5594 - Fix a remotely exploitable bug that could be used to crash instances
5595 of Tor remotely by overflowing on the heap. Remote-code execution
5596 hasn't been confirmed, but can't be ruled out. Everyone should
5597 upgrade. Bugfix on the 0.1.1 series and later.
5599 o Directory authority changes:
5600 - Change IP address and ports for gabelmoo (v3 directory authority).
5603 - Update to the December 1 2010 Maxmind GeoLite Country database.
5606 Changes in version 0.2.1.27 - 2010-11-23
5607 Yet another OpenSSL security patch broke its compatibility with Tor:
5608 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5609 also took this opportunity to fix several crash bugs, integrate a new
5610 directory authority, and update the bundled GeoIP database.
5613 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5614 No longer set the tlsext_host_name extension on server SSL objects;
5615 but continue to set it on client SSL objects. Our goal in setting
5616 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5617 bugfix on 0.2.1.1-alpha.
5618 - Do not log messages to the controller while shrinking buffer
5619 freelists. Doing so would sometimes make the controller connection
5620 try to allocate a buffer chunk, which would mess up the internals
5621 of the freelist and cause an assertion failure. Fixes bug 1125;
5622 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5623 - Learn our external IP address when we're a relay or bridge, even if
5624 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5625 where we introduced bridge relays that don't need to publish to
5626 be useful. Fixes bug 2050.
5627 - Do even more to reject (and not just ignore) annotations on
5628 router descriptors received anywhere but from the cache. Previously
5629 we would ignore such annotations at first, but cache them to disk
5630 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5631 - When you're using bridges and your network goes away and your
5632 bridges get marked as down, recover when you attempt a new socks
5633 connection (if the network is back), rather than waiting up to an
5634 hour to try fetching new descriptors for your bridges. Bugfix on
5635 0.2.0.3-alpha; fixes bug 1981.
5638 - Move to the November 2010 Maxmind GeoLite country db (rather
5639 than the June 2009 ip-to-country GeoIP db) for our statistics that
5640 count how many users relays are seeing from each country. Now we'll
5641 have more accurate data, especially for many African countries.
5643 o New directory authorities:
5644 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5648 - Fix an assertion failure that could occur in directory caches or
5649 bridge users when using a very short voting interval on a testing
5650 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5652 - Enforce multiplicity rules when parsing annotations. Bugfix on
5653 0.2.0.8-alpha. Found by piebeer.
5654 - Allow handshaking OR connections to take a full KeepalivePeriod
5655 seconds to handshake. Previously, we would close them after
5656 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5657 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5659 - When building with --enable-gcc-warnings on OpenBSD, disable
5660 warnings in system headers. This makes --enable-gcc-warnings
5661 pass on OpenBSD 4.8.
5664 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5665 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5666 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5667 Servers can start sending this code when enough clients recognize
5668 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5669 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5670 Patch from mingw-san.
5673 - Remove the old debian/ directory from the main Tor distribution.
5674 The official Tor-for-debian git repository lives at the URL
5675 https://git.torproject.org/debian/tor.git
5676 - Stop shipping the old doc/website/ directory in the tarball. We
5677 changed the website format in late 2010, and what we shipped in
5678 0.2.1.26 really wasn't that useful anyway.
5681 Changes in version 0.2.2.19-alpha - 2010-11-22
5682 Yet another OpenSSL security patch broke its compatibility with Tor:
5683 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5686 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5687 No longer set the tlsext_host_name extension on server SSL objects;
5688 but continue to set it on client SSL objects. Our goal in setting
5689 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5690 bugfix on 0.2.1.1-alpha.
5693 - Try harder not to exceed the maximum length of 50 KB when writing
5694 statistics to extra-info descriptors. This bug was triggered by very
5695 fast relays reporting exit-port, entry, and dirreq statistics.
5696 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5697 - Publish a router descriptor even if generating an extra-info
5698 descriptor fails. Previously we would not publish a router
5699 descriptor without an extra-info descriptor; this can cause fast
5700 exit relays collecting exit-port statistics to drop from the
5701 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5704 Changes in version 0.2.2.18-alpha - 2010-11-16
5705 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5706 us lately, makes unpublished bridge relays able to detect their IP
5707 address, and fixes a wide variety of other bugs to get us much closer
5708 to a stable release.
5711 - Do even more to reject (and not just ignore) annotations on
5712 router descriptors received anywhere but from the cache. Previously
5713 we would ignore such annotations at first, but cache them to disk
5714 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5715 - Do not log messages to the controller while shrinking buffer
5716 freelists. Doing so would sometimes make the controller connection
5717 try to allocate a buffer chunk, which would mess up the internals
5718 of the freelist and cause an assertion failure. Fixes bug 1125;
5719 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5720 - Learn our external IP address when we're a relay or bridge, even if
5721 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5722 where we introduced bridge relays that don't need to publish to
5723 be useful. Fixes bug 2050.
5724 - Maintain separate TLS contexts and certificates for incoming and
5725 outgoing connections in bridge relays. Previously we would use the
5726 same TLS contexts and certs for incoming and outgoing connections.
5727 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5728 - Maintain separate identity keys for incoming and outgoing TLS
5729 contexts in bridge relays. Previously we would use the same
5730 identity keys for incoming and outgoing TLS contexts. Bugfix on
5731 0.2.0.3-alpha; addresses the other half of bug 988.
5732 - Avoid an assertion failure when we as an authority receive a
5733 duplicate upload of a router descriptor that we already have,
5734 but which we previously considered an obsolete descriptor.
5735 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5736 - Avoid a crash bug triggered by looking at a dangling pointer while
5737 setting the network status consensus. Found by Robert Ransom.
5738 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5739 - Fix a logic error where servers that _didn't_ act as exits would
5740 try to keep their server lists more aggressively up to date than
5741 exits, when it was supposed to be the other way around. Bugfix
5744 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5745 - When we're trying to guess whether we know our IP address as
5746 a relay, we would log various ways that we failed to guess
5747 our address, but never log that we ended up guessing it
5748 successfully. Now add a log line to help confused and anxious
5749 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5750 - Bring the logic that gathers routerinfos and assesses the
5751 acceptability of circuits into line. This prevents a Tor OP from
5752 getting locked in a cycle of choosing its local OR as an exit for a
5753 path (due to a .exit request) and then rejecting the circuit because
5754 its OR is not listed yet. It also prevents Tor clients from using an
5755 OR running in the same instance as an exit (due to a .exit request)
5756 if the OR does not meet the same requirements expected of an OR
5757 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5758 - Correctly describe errors that occur when generating a TLS object.
5759 Previously we would attribute them to a failure while generating a
5760 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5762 - Enforce multiplicity rules when parsing annotations. Bugfix on
5763 0.2.0.8-alpha. Found by piebeer.
5764 - Fix warnings that newer versions of autoconf produced during
5765 ./autogen.sh. These warnings appear to be harmless in our case,
5766 but they were extremely verbose. Fixes bug 2020.
5768 o Minor bugfixes (on Tor 0.2.2.x):
5769 - Enable protection of small arrays whenever we build with gcc
5770 hardening features, not only when also building with warnings
5771 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5774 - Make hidden services work better in private Tor networks by not
5775 requiring any uptime to join the hidden service descriptor
5776 DHT. Implements ticket 2088.
5777 - Rate-limit the "your application is giving Tor only an IP address"
5778 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5779 - When AllowSingleHopExits is set, print a warning to explain to the
5780 relay operator why most clients are avoiding her relay.
5781 - Update to the November 1 2010 Maxmind GeoLite Country database.
5783 o Code simplifications and refactoring:
5784 - When we fixed bug 1038 we had to put in a restriction not to send
5785 RELAY_EARLY cells on rend circuits. This was necessary as long
5786 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5787 active. Now remove this obsolete check. Resolves bug 2081.
5788 - Some options used different conventions for uppercasing of acronyms
5789 when comparing manpage and source. Fix those in favor of the
5790 manpage, as it makes sense to capitalize acronyms.
5791 - Remove the torrc.complete file. It hasn't been kept up to date
5792 and users will have better luck checking out the manpage.
5793 - Remove the obsolete "NoPublish" option; it has been flagged
5794 as obsolete and has produced a warning since 0.1.1.18-rc.
5795 - Remove everything related to building the expert bundle for OS X.
5796 It has confused many users, doesn't work right on OS X 10.6,
5797 and is hard to get rid of once installed. Resolves bug 1274.
5800 Changes in version 0.2.2.17-alpha - 2010-09-30
5801 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
5802 to use one-hop circuits (which can put the exit relays at higher risk,
5803 plus unbalance the network); fixes a big bug in bandwidth accounting
5804 for relays that want to limit their monthly bandwidth use; fixes a
5805 big pile of bugs in how clients tolerate temporary network failure;
5806 and makes our adaptive circuit build timeout feature (which improves
5807 client performance if your network is fast while not breaking things
5808 if your network is slow) better handle bad networks.
5811 - Exit relays now try harder to block exit attempts from unknown
5812 relays, to make it harder for people to use them as one-hop proxies
5813 a la tortunnel. Controlled by the refuseunknownexits consensus
5814 parameter (currently enabled), or you can override it on your
5815 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
5817 o Major bugfixes (0.2.1.x and earlier):
5818 - Fix a bug in bandwidth accounting that could make us use twice
5819 the intended bandwidth when our interval start changes due to
5820 daylight saving time. Now we tolerate skew in stored vs computed
5821 interval starts: if the start of the period changes by no more than
5822 50% of the period's duration, we remember bytes that we transferred
5823 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5824 - Always search the Windows system directory for system DLLs, and
5825 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5826 - When you're using bridges and your network goes away and your
5827 bridges get marked as down, recover when you attempt a new socks
5828 connection (if the network is back), rather than waiting up to an
5829 hour to try fetching new descriptors for your bridges. Bugfix on
5830 0.2.0.3-alpha; fixes bug 1981.
5832 o Major bugfixes (on 0.2.2.x):
5833 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
5835 - Fix a segfault that could happen when operating a bridge relay with
5836 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
5837 - The consensus bandwidth-weights (used by clients to choose fast
5838 relays) entered an unexpected edge case in September where
5839 Exits were much scarcer than Guards, resulting in bad weight
5840 recommendations. Now we compute them using new constraints that
5841 should succeed in all cases. Also alter directory authorities to
5842 not include the bandwidth-weights line if they fail to produce
5843 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
5844 - When weighting bridges during path selection, we used to trust
5845 the bandwidths they provided in their descriptor, only capping them
5846 at 10MB/s. This turned out to be problematic for two reasons:
5847 Bridges could claim to handle a lot more traffic then they
5848 actually would, thus making more clients pick them and have a
5849 pretty effective DoS attack. The other issue is that new bridges
5850 that might not have a good estimate for their bw capacity yet
5851 would not get used at all unless no other bridges are available
5852 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
5854 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
5855 - Ignore cannibalized circuits when recording circuit build times.
5856 This should provide for a minor performance improvement for hidden
5857 service users using 0.2.2.14-alpha, and should remove two spurious
5858 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
5859 - Simplify the logic that causes us to decide if the network is
5860 unavailable for purposes of recording circuit build times. If we
5861 receive no cells whatsoever for the entire duration of a circuit's
5862 full measured lifetime, the network is probably down. Also ignore
5863 one-hop directory fetching circuit timeouts when calculating our
5864 circuit build times. These changes should hopefully reduce the
5865 cases where we see ridiculous circuit build timeouts for people
5866 with spotty wireless connections. Fixes part of bug 1772; bugfix
5868 - Prevent the circuit build timeout from becoming larger than
5869 the maximum build time we have ever seen. Also, prevent the time
5870 period for measurement circuits from becoming larger than twice that
5871 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
5874 - When we run out of directory information such that we can't build
5875 circuits, but then get enough that we can build circuits, log when
5876 we actually construct a circuit, so the user has a better chance of
5877 knowing what's going on. Fixes bug 1362.
5878 - Be more generous with how much bandwidth we'd use up (with
5879 accounting enabled) before entering "soft hibernation". Previously,
5880 we'd refuse new connections and circuits once we'd used up 95% of
5881 our allotment. Now, we use up 95% of our allotment, AND make sure
5882 that we have no more than 500MB (or 3 hours of expected traffic,
5883 whichever is lower) remaining before we enter soft hibernation.
5884 - If we've configured EntryNodes and our network goes away and/or all
5885 our entrynodes get marked down, optimistically retry them all when
5886 a new socks application request appears. Fixes bug 1882.
5887 - Add some more defensive programming for architectures that can't
5888 handle unaligned integer accesses. We don't know of any actual bugs
5889 right now, but that's the best time to fix them. Fixes bug 1943.
5890 - Support line continuations in the torrc config file. If a line
5891 ends with a single backslash character, the newline is ignored, and
5892 the configuration value is treated as continuing on the next line.
5895 o Minor bugfixes (on 0.2.1.x and earlier):
5896 - For bandwidth accounting, calculate our expected bandwidth rate
5897 based on the time during which we were active and not in
5898 soft-hibernation during the last interval. Previously, we were
5899 also considering the time spent in soft-hibernation. If this
5900 was a long time, we would wind up underestimating our bandwidth
5901 by a lot, and skewing our wakeup time towards the start of the
5902 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
5904 o Minor bugfixes (on 0.2.2.x):
5905 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
5906 which were disabled by the circuit build timeout changes in
5907 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
5908 - Make sure we don't warn about missing bandwidth weights when
5909 choosing bridges or other relays not in the consensus. Bugfix on
5910 0.2.2.10-alpha; fixes bug 1805.
5911 - In our logs, do not double-report signatures from unrecognized
5912 authorities both as "from unknown authority" and "not
5913 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
5916 Changes in version 0.2.2.16-alpha - 2010-09-17
5917 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
5918 evident at exit relays), and also continues to resolve all the little
5919 bugs that have been filling up trac lately.
5921 o Major bugfixes (stream-level fairness):
5922 - When receiving a circuit-level SENDME for a blocked circuit, try
5923 to package cells fairly from all the streams that had previously
5924 been blocked on that circuit. Previously, we had started with the
5925 oldest stream, and allowed each stream to potentially exhaust
5926 the circuit's package window. This gave older streams on any
5927 given circuit priority over newer ones. Fixes bug 1937. Detected
5928 originally by Camilo Viecco. This bug was introduced before the
5929 first Tor release, in svn commit r152: it is the new winner of
5930 the longest-lived bug prize.
5931 - When the exit relay got a circuit-level sendme cell, it started
5932 reading on the exit streams, even if had 500 cells queued in the
5933 circuit queue already, so the circuit queue just grew and grew in
5934 some cases. We fix this by not re-enabling reading on receipt of a
5935 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
5936 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
5938 - Newly created streams were allowed to read cells onto circuits,
5939 even if the circuit's cell queue was blocked and waiting to drain.
5940 This created potential unfairness, as older streams would be
5941 blocked, but newer streams would gladly fill the queue completely.
5942 We add code to detect this situation and prevent any stream from
5943 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
5947 - Update to the September 1 2010 Maxmind GeoLite Country database.
5948 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
5949 not. This would lead to a cookie that is still not group readable.
5950 Closes bug 1843. Suggested by katmagic.
5951 - When logging a rate-limited warning, we now mention how many messages
5952 got suppressed since the last warning.
5953 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
5954 do individual connection-level rate limiting of clients. The torrc
5955 config options with the same names trump the consensus params, if
5956 both are present. Replaces the old "bwconnrate" and "bwconnburst"
5957 consensus params which were broken from 0.2.2.7-alpha through
5958 0.2.2.14-alpha. Closes bug 1947.
5959 - When a router changes IP address or port, authorities now launch
5960 a new reachability test for it. Implements ticket 1899.
5961 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
5962 2 no signature, 4 required" messages about consensus signatures
5963 easier to read, and make sure they get logged at the same severity
5964 as the messages explaining which keys are which. Fixes bug 1290.
5965 - Don't warn when we have a consensus that we can't verify because
5966 of missing certificates, unless those certificates are ones
5967 that we have been trying and failing to download. Fixes bug 1145.
5968 - If you configure your bridge with a known identity fingerprint,
5969 and the bridge authority is unreachable (as it is in at least
5970 one country now), fall back to directly requesting the descriptor
5971 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
5973 - When building with --enable-gcc-warnings on OpenBSD, disable
5974 warnings in system headers. This makes --enable-gcc-warnings
5975 pass on OpenBSD 4.8.
5977 o Minor bugfixes (on 0.2.1.x and earlier):
5978 - Authorities will now attempt to download consensuses if their
5979 own efforts to make a live consensus have failed. This change
5980 means authorities that restart will fetch a valid consensus, and
5981 it means authorities that didn't agree with the current consensus
5982 will still fetch and serve it if it has enough signatures. Bugfix
5983 on 0.2.0.9-alpha; fixes bug 1300.
5984 - Ensure DNS requests launched by "RESOLVE" commands from the
5985 controller respect the __LeaveStreamsUnattached setconf options. The
5986 same goes for requests launched via DNSPort or transparent
5987 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
5988 - Allow handshaking OR connections to take a full KeepalivePeriod
5989 seconds to handshake. Previously, we would close them after
5990 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5991 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5993 - Rate-limit "Failed to hand off onionskin" warnings.
5994 - Never relay a cell for a circuit we have already destroyed.
5995 Between marking a circuit as closeable and finally closing it,
5996 it may have been possible for a few queued cells to get relayed,
5997 even though they would have been immediately dropped by the next
5998 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
5999 - Never queue a cell for a circuit that's already been marked
6001 - Never vote for a server as "Running" if we have a descriptor for
6002 it claiming to be hibernating, and that descriptor was published
6003 more recently than our last contact with the server. Bugfix on
6004 0.2.0.3-alpha; fixes bug 911.
6005 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6008 o Minor bugfixes (on 0.2.2.x):
6009 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6010 down if a directory fetch fails and you've configured either
6011 bridges or EntryNodes. The intent was to mark the relay as down
6012 _unless_ you're using bridges or EntryNodes, since if you are
6013 then you could quickly run out of entry points.
6014 - Fix the Windows directory-listing code. A bug introduced in
6015 0.2.2.14-alpha could make Windows directory servers forget to load
6016 some of their cached v2 networkstatus files.
6017 - Really allow clients to use relays as bridges. Fixes bug 1776;
6018 bugfix on 0.2.2.15-alpha.
6019 - Demote a warn to info that happens when the CellStatistics option
6020 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6021 Reported by Moritz Bartl.
6022 - On Windows, build correctly either with or without Unicode support.
6023 This is necessary so that Tor can support fringe platforms like
6024 Windows 98 (which has no Unicode), or Windows CE (which has no
6025 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6028 - Add a unit test for cross-platform directory-listing code.
6031 Changes in version 0.2.2.15-alpha - 2010-08-18
6032 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6033 fixes a variety of other bugs that were preventing performance
6034 experiments from moving forward, fixes several bothersome memory leaks,
6035 and generally closes a lot of smaller bugs that have been filling up
6039 - Stop assigning the HSDir flag to relays that disable their
6040 DirPort (and thus will refuse to answer directory requests). This
6041 fix should dramatically improve the reachability of hidden services:
6042 hidden services and hidden service clients pick six HSDir relays
6043 to store and retrieve the hidden service descriptor, and currently
6044 about half of the HSDir relays will refuse to work. Bugfix on
6045 0.2.0.10-alpha; fixes part of bug 1693.
6046 - The PerConnBWRate and Burst config options, along with the
6047 bwconnrate and bwconnburst consensus params, initialized each conn's
6048 token bucket values only when the connection is established. Now we
6049 update them if the config options change, and update them every time
6050 we get a new consensus. Otherwise we can encounter an ugly edge
6051 case where we initialize an OR conn to client-level bandwidth,
6052 but then later the relay joins the consensus and we leave it
6053 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6054 - Fix a regression that caused Tor to rebind its ports if it receives
6055 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6058 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6059 should give us approximately 40-50% more Guard-flagged nodes,
6060 improving the anonymity the Tor network can provide and also
6061 decreasing the dropoff in throughput that relays experience when
6062 they first get the Guard flag.
6063 - Allow enabling or disabling the *Statistics config options while
6067 - Update to the August 1 2010 Maxmind GeoLite Country database.
6068 - Have the controller interface give a more useful message than
6069 "Internal Error" in response to failed GETINFO requests.
6070 - Warn when the same option is provided more than once in a torrc
6071 file, on the command line, or in a single SETCONF statement, and
6072 the option is one that only accepts a single line. Closes bug 1384.
6073 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6074 Patch from mingw-san.
6075 - Add support for the country code "{??}" in torrc options like
6076 ExcludeNodes, to indicate all routers of unknown country. Closes
6078 - Relays report the number of bytes spent on answering directory
6079 requests in extra-info descriptors similar to {read,write}-history.
6080 Implements enhancement 1790.
6082 o Minor bugfixes (on 0.2.1.x and earlier):
6083 - Complain if PublishServerDescriptor is given multiple arguments that
6084 include 0 or 1. This configuration will be rejected in the future.
6085 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6086 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6087 Bugfix on 0.2.0.13-alpha; closes bug 928.
6088 - Change "Application request when we're believed to be offline."
6089 notice to "Application request when we haven't used client
6090 functionality lately.", to clarify that it's not an error. Bugfix
6091 on 0.0.9.3; fixes bug 1222.
6092 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6093 would return "551 Internal error" rather than "552 Unrecognized key
6094 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6095 - Users can't configure a regular relay to be their bridge. It didn't
6096 work because when Tor fetched the bridge descriptor, it found
6097 that it already had it, and didn't realize that the purpose of the
6098 descriptor had changed. Now we replace routers with a purpose other
6099 than bridge with bridge descriptors when fetching them. Bugfix on
6100 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6101 refetch the descriptor with router purpose 'general', disabling
6103 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6104 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6105 on 0.2.0.10-alpha; fixes bug 1808.
6106 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6107 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6108 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6109 Servers can start sending this code when enough clients recognize
6110 it. Also update the spec to reflect this new reason. Bugfix on
6111 0.1.0.1-rc; fixes part of bug 1793.
6112 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6113 when we switch from being a public relay to a bridge. Otherwise
6114 there will still be clients that see the relay in their consensus,
6115 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6117 - Instead of giving an assertion failure on an internal mismatch
6118 on estimated freelist size, just log a BUG warning and try later.
6119 Mitigates but does not fix bug 1125.
6120 - Fix an assertion failure that could occur in caches or bridge users
6121 when using a very short voting interval on a testing network.
6122 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6124 o Minor bugfixes (on 0.2.2.x):
6125 - Alter directory authorities to always consider Exit-flagged nodes
6126 as potential Guard nodes in their votes. The actual decision to
6127 use Exits as Guards is done in the consensus bandwidth weights.
6128 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6129 - When the controller is reporting the purpose of circuits that
6130 didn't finish building before the circuit build timeout, it was
6131 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6132 - Our libevent version parsing code couldn't handle versions like
6133 1.4.14b-stable and incorrectly warned the user about using an
6134 old and broken version of libevent. Treat 1.4.14b-stable like
6135 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6137 - Don't use substitution references like $(VAR:MOD) when
6138 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6139 '$(:x)' to 'x' rather than the empty string. This bites us in
6140 doc/ when configured with --disable-asciidoc. Bugfix on
6141 0.2.2.9-alpha; fixes bug 1773.
6142 - Remove a spurious hidden service server-side log notice about
6143 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6145 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6147 - Correctly report written bytes on linked connections. Found while
6148 implementing 1790. Bugfix on 0.2.2.4-alpha.
6149 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6150 one in dirvote_add_signatures_to_pending_consensus(), and one every
6151 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6152 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6154 o Code simplifications and refactoring:
6155 - Take a first step towards making or.h smaller by splitting out
6156 function definitions for all source files in src/or/. Leave
6157 structures and defines in or.h for now.
6158 - Remove a bunch of unused function declarations as well as a block of
6159 #if 0'd code from the unit tests. Closes bug 1824.
6160 - New unit tests for exit-port history statistics; refactored exit
6161 statistics code to be more easily tested.
6162 - Remove the old debian/ directory from the main Tor distribution.
6163 The official Tor-for-debian git repository lives at the URL
6164 https://git.torproject.org/debian/tor.git
6167 Changes in version 0.2.2.14-alpha - 2010-07-12
6168 Tor 0.2.2.14-alpha greatly improves client-side handling of
6169 circuit build timeouts, which are used to estimate speed and improve
6170 performance. We also move to a much better GeoIP database, port Tor to
6171 Windows CE, introduce new compile flags that improve code security,
6172 add an eighth v3 directory authority, and address a lot of more
6176 - Tor directory authorities no longer crash when started with a
6177 cached-microdesc-consensus file in their data directory. Bugfix
6178 on 0.2.2.6-alpha; fixes bug 1532.
6179 - Treat an unset $HOME like an empty $HOME rather than triggering an
6180 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6181 - Ignore negative and large circuit build timeout values that can
6182 happen during a suspend or hibernate. These values caused various
6183 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6184 - Alter calculation of Pareto distribution parameter 'Xm' for
6185 Circuit Build Timeout learning to use the weighted average of the
6186 top N=3 modes (because we have three entry guards). Considering
6187 multiple modes should improve the timeout calculation in some cases,
6188 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6190 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6191 right censored distribution model. This approach improves over the
6192 synthetic timeout generation approach that was producing insanely
6193 high timeout values. Now we calculate build timeouts using truncated
6194 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6195 - Do not close circuits that are under construction when they reach
6196 the circuit build timeout. Instead, leave them building (but do not
6197 use them) for up until the time corresponding to the 95th percentile
6198 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6199 to provide better data for the new Pareto model. This percentile
6200 can be controlled by the consensus.
6203 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6204 June 2009 ip-to-country GeoIP db) for our statistics that count
6205 how many users relays are seeing from each country. Now we have
6206 more accurate data for many African countries.
6207 - Port Tor to build and run correctly on Windows CE systems, using
6208 the wcecompat library. Contributed by Valerio Lupi.
6209 - New "--enable-gcc-hardening" ./configure flag (off by default)
6210 to turn on gcc compile time hardening options. It ensures
6211 that signed ints have defined behavior (-fwrapv), enables
6212 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6213 with canaries (-fstack-protector-all), turns on ASLR protection if
6214 supported by the kernel (-fPIE, -pie), and adds additional security
6215 related warnings. Verified to work on Mac OS X and Debian Lenny.
6216 - New "--enable-linker-hardening" ./configure flag (off by default)
6217 to turn on ELF specific hardening features (relro, now). This does
6218 not work with Mac OS X or any other non-ELF binary format.
6220 o New directory authorities:
6221 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6225 - New config option "WarnUnsafeSocks 0" disables the warning that
6226 occurs whenever Tor receives a socks handshake using a version of
6227 the socks protocol that can only provide an IP address (rather
6228 than a hostname). Setups that do DNS locally over Tor are fine,
6229 and we shouldn't spam the logs in that case.
6230 - Convert the HACKING file to asciidoc, and add a few new sections
6231 to it, explaining how we use Git, how we make changelogs, and
6232 what should go in a patch.
6233 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6234 event, to give information on the current rate of circuit timeouts
6235 over our stored history.
6236 - Add ability to disable circuit build time learning via consensus
6237 parameter and via a LearnCircuitBuildTimeout config option. Also
6238 automatically disable circuit build time calculation if we are
6239 either a AuthoritativeDirectory, or if we fail to write our state
6240 file. Fixes bug 1296.
6241 - More gracefully handle corrupt state files, removing asserts
6242 in favor of saving a backup and resetting state.
6243 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6247 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6249 - When a2x fails, mention that the user could disable manpages instead
6250 of trying to fix their asciidoc installation.
6251 - Where available, use Libevent 2.0's periodic timers so that our
6252 once-per-second cleanup code gets called even more closely to
6253 once per second than it would otherwise. Fixes bug 943.
6254 - If you run a bridge that listens on multiple IP addresses, and
6255 some user configures a bridge address that uses a different IP
6256 address than your bridge writes in its router descriptor, and the
6257 user doesn't specify an identity key, their Tor would discard the
6258 descriptor because "it isn't one of our configured bridges", and
6259 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6260 Bugfix on 0.2.0.3-alpha.
6261 - If OpenSSL fails to make a duplicate of a private or public key, log
6262 an error message and try to exit cleanly. May help with debugging
6263 if bug 1209 ever remanifests.
6264 - Save a couple bytes in memory allocation every time we escape
6265 certain characters in a string. Patch from Florian Zumbiehl.
6266 - Make it explicit that we don't cannibalize one-hop circuits. This
6267 happens in the wild, but doesn't turn out to be a problem because
6268 we fortunately don't use those circuits. Many thanks to outofwords
6269 for the initial analysis and to swissknife who confirmed that
6270 two-hop circuits are actually created.
6271 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6272 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6273 - Eliminate a case where a circuit build time warning was displayed
6274 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6277 Changes in version 0.2.1.26 - 2010-05-02
6278 Tor 0.2.1.26 addresses the recent connection and memory overload
6279 problems we've been seeing on relays, especially relays with their
6280 DirPort open. If your relay has been crashing, or you turned it off
6281 because it used too many resources, give this release a try.
6283 This release also fixes yet another instance of broken OpenSSL libraries
6284 that was causing some relays to drop out of the consensus.
6287 - Teach relays to defend themselves from connection overload. Relays
6288 now close idle circuits early if it looks like they were intended
6289 for directory fetches. Relays are also more aggressive about closing
6290 TLS connections that have no circuits on them. Such circuits are
6291 unlikely to be re-used, and tens of thousands of them were piling
6292 up at the fast relays, causing the relays to run out of sockets
6293 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6294 their directory fetches over TLS).
6295 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6296 that claim to be earlier than 0.9.8m, but which have in reality
6297 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6298 behavior. Possible fix for some cases of bug 1346.
6299 - Directory mirrors were fetching relay descriptors only from v2
6300 directory authorities, rather than v3 authorities like they should.
6301 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6302 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6305 - Finally get rid of the deprecated and now harmful notion of "clique
6306 mode", where directory authorities maintain TLS connections to
6310 - In the util/threads test, no longer free the test_mutex before all
6311 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6312 - The master thread could starve the worker threads quite badly on
6313 certain systems, causing them to run only partially in the allowed
6314 window. This resulted in test failures. Now the master thread sleeps
6315 occasionally for a few microseconds while the two worker-threads
6316 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6319 Changes in version 0.2.2.13-alpha - 2010-04-24
6320 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6321 problems we've been seeing on relays, especially relays with their
6322 DirPort open. If your relay has been crashing, or you turned it off
6323 because it used too many resources, give this release a try.
6326 - Teach relays to defend themselves from connection overload. Relays
6327 now close idle circuits early if it looks like they were intended
6328 for directory fetches. Relays are also more aggressive about closing
6329 TLS connections that have no circuits on them. Such circuits are
6330 unlikely to be re-used, and tens of thousands of them were piling
6331 up at the fast relays, causing the relays to run out of sockets
6332 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6333 their directory fetches over TLS).
6336 - Finally get rid of the deprecated and now harmful notion of "clique
6337 mode", where directory authorities maintain TLS connections to
6339 - Directory authorities now do an immediate reachability check as soon
6340 as they hear about a new relay. This change should slightly reduce
6341 the time between setting up a relay and getting listed as running
6342 in the consensus. It should also improve the time between setting
6343 up a bridge and seeing use by bridge users.
6344 - Directory authorities no longer launch a TLS connection to every
6345 relay as they startup. Now that we have 2k+ descriptors cached,
6346 the resulting network hiccup is becoming a burden. Besides,
6347 authorities already avoid voting about Running for the first half
6348 hour of their uptime.
6351 Changes in version 0.2.2.12-alpha - 2010-04-20
6352 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6353 handle and vote on descriptors. It was causing relays to drop out of
6357 - Many relays have been falling out of the consensus lately because
6358 not enough authorities know about their descriptor for them to get
6359 a majority of votes. When we deprecated the v2 directory protocol,
6360 we got rid of the only way that v3 authorities can hear from each
6361 other about other descriptors. Now authorities examine every v3
6362 vote for new descriptors, and fetch them from that authority. Bugfix
6364 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6365 and a warning in or.h related to bandwidth_weight_rule_t that
6366 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6368 - Fix a segfault on relays when DirReqStatistics is enabled
6369 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6373 - Demote a confusing TLS warning that relay operators might get when
6374 someone tries to talk to their OrPort. It is neither the operator's
6375 fault nor can they do anything about it. Fixes bug 1364; bugfix
6379 Changes in version 0.2.2.11-alpha - 2010-04-15
6380 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6381 libraries that was causing some relays to drop out of the consensus.
6384 - Directory mirrors were fetching relay descriptors only from v2
6385 directory authorities, rather than v3 authorities like they should.
6386 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6387 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6388 - Fix a parsing error that made every possible value of
6389 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6390 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6391 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6392 about the option without breaking older ones.
6393 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6394 that claim to be earlier than 0.9.8m, but which have in reality
6395 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6396 behavior. Possible fix for some cases of bug 1346.
6399 - Experiment with a more aggressive approach to preventing clients
6400 from making one-hop exit streams. Exit relays who want to try it
6401 out can set "RefuseUnknownExits 1" in their torrc, and then look
6402 for "Attempt by %s to open a stream" log messages. Let us know
6404 - Add support for statically linking zlib by specifying
6405 --enable-static-zlib, to go with our support for statically linking
6406 openssl and libevent. Resolves bug 1358.
6409 - Fix a segfault that happens whenever a Tor client that is using
6410 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6412 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6413 out the first line. Fixes bug 1295.
6414 - When building the manpage from a tarball, we required asciidoc, but
6415 the asciidoc -> roff/html conversion was already done for the
6416 tarball. Make 'make' complain only when we need asciidoc (either
6417 because we're compiling directly from git, or because we altered
6418 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6419 - When none of the directory authorities vote on any params, Tor
6420 segfaulted when trying to make the consensus from the votes. We
6421 didn't trigger the bug in practice, because authorities do include
6422 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6425 - In the util/threads test, no longer free the test_mutex before all
6426 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6427 - The master thread could starve the worker threads quite badly on
6428 certain systems, causing them to run only partially in the allowed
6429 window. This resulted in test failures. Now the master thread sleeps
6430 occasionally for a few microseconds while the two worker-threads
6431 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6434 Changes in version 0.2.2.10-alpha - 2010-03-07
6435 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6436 could prevent relays from guessing their IP address correctly. It also
6437 starts the groundwork for another client-side performance boost, since
6438 currently we're not making efficient use of relays that have both the
6439 Guard flag and the Exit flag.
6442 - Fix a regression from our patch for bug 1244 that caused relays
6443 to guess their IP address incorrectly if they didn't set Address
6444 in their torrc and/or their address fails to resolve. Bugfix on
6445 0.2.2.9-alpha; fixes bug 1269.
6447 o Major features (performance):
6448 - Directory authorities now compute consensus weightings that instruct
6449 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6450 and no flag. Clients that use these weightings will distribute
6451 network load more evenly across these different relay types. The
6452 weightings are in the consensus so we can change them globally in
6453 the future. Extra thanks to "outofwords" for finding some nasty
6454 security bugs in the first implementation of this feature.
6456 o Minor features (performance):
6457 - Always perform router selections using weighted relay bandwidth,
6458 even if we don't need a high capacity circuit at the time. Non-fast
6459 circuits now only differ from fast ones in that they can use relays
6460 not marked with the Fast flag. This "feature" could turn out to
6461 be a horrible bug; we should investigate more before it goes into
6465 - Allow disabling building of the manpages. Skipping the manpage
6466 speeds up the build considerably.
6468 o Minor bugfixes (on 0.2.2.x):
6469 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6470 Bugfix on 0.2.2.9-alpha.
6471 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6472 config option. Bugfix on 0.2.2.7-alpha.
6473 - Ship the asciidoc-helper file in the tarball, so that people can
6474 build from source if they want to, and touching the .1.txt files
6475 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6477 o Minor bugfixes (on 0.2.1.x or earlier):
6478 - Fix a dereference-then-NULL-check sequence when publishing
6479 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6481 - Fix another dereference-then-NULL-check sequence. Bugfix on
6482 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6483 - Make sure we treat potentially not NUL-terminated strings correctly.
6484 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6486 o Code simplifications and refactoring:
6487 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6488 compliant. Based on a patch from Christian Kujau.
6489 - Don't use sed in asciidoc-helper anymore.
6490 - Make the build process fail if asciidoc cannot be found and
6491 building with asciidoc isn't disabled.
6494 Changes in version 0.2.2.9-alpha - 2010-02-22
6495 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6496 location of a directory authority, and cleans up a bunch of small bugs.
6498 o Directory authority changes:
6499 - Change IP address for dannenberg (v3 directory authority), and
6500 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6501 service directory authority) from the list.
6504 - Make Tor work again on the latest OS X: when deciding whether to
6505 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6506 version at run-time, not compile time. We need to do this because
6507 Apple doesn't update its dev-tools headers when it updates its
6508 libraries in a security patch.
6509 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6510 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6511 a memory leak when requesting a hidden service descriptor we've
6512 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6514 - Authorities could be tricked into giving out the Exit flag to relays
6515 that didn't allow exiting to any ports. This bug could screw
6516 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6517 1238. Bug discovered by Martin Kowalczyk.
6518 - When freeing a session key, zero it out completely. We only zeroed
6519 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6520 patched by ekir. Fixes bug 1254.
6523 - Fix static compilation by listing the openssl libraries in the right
6524 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6525 - Resume handling .exit hostnames in a special way: originally we
6526 stripped the .exit part and used the requested exit relay. In
6527 0.2.2.1-alpha we stopped treating them in any special way, meaning
6528 if you use a .exit address then Tor will pass it on to the exit
6529 relay. Now we reject the .exit stream outright, since that behavior
6530 might be more expected by the user. Found and diagnosed by Scott
6531 Bennett and Downie on or-talk.
6532 - Don't spam the controller with events when we have no file
6533 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6534 for log messages was already solved from bug 748.)
6535 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6537 - Make the DNSPort option work with libevent 2.x. Don't alter the
6538 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6539 - Emit a GUARD DROPPED controller event for a case we missed.
6540 - Make more fields in the controller protocol case-insensitive, since
6541 control-spec.txt said they were.
6542 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6543 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6544 - Fix a spec conformance issue: the network-status-version token
6545 must be the first token in a v3 consensus or vote. Discovered by
6546 parakeep. Bugfix on 0.2.0.3-alpha.
6548 o Code simplifications and refactoring:
6549 - Generate our manpage and HTML documentation using Asciidoc. This
6550 change should make it easier to maintain the documentation, and
6552 - Remove the --enable-iphone option. According to reports from Marco
6553 Bonetti, Tor builds fine without any special tweaking on recent
6554 iPhone SDK versions.
6555 - Removed some unnecessary files from the source distribution. The
6556 AUTHORS file has now been merged into the people page on the
6557 website. The roadmaps and design doc can now be found in the
6558 projects directory in svn.
6559 - Enabled various circuit build timeout constants to be controlled
6560 by consensus parameters. Also set better defaults for these
6561 parameters based on experimentation on broadband and simulated
6565 - The 'EXTENDCIRCUIT' control port command can now be used with
6566 a circ id of 0 and no path. This feature will cause Tor to build
6567 a new 'fast' general purpose circuit using its own path selection
6569 - Added a BUILDTIMEOUT_SET controller event to describe changes
6570 to the circuit build timeout.
6571 - Future-proof the controller protocol a bit by ignoring keyword
6572 arguments we do not recognize.
6573 - Expand homedirs passed to tor-checkkey. This should silence a
6574 coverity complaint about passing a user-supplied string into
6575 open() without checking it.
6578 Changes in version 0.2.1.25 - 2010-03-16
6579 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6580 prevent relays from guessing their IP address correctly. It also fixes
6581 several minor potential security bugs.
6584 - Fix a regression from our patch for bug 1244 that caused relays
6585 to guess their IP address incorrectly if they didn't set Address
6586 in their torrc and/or their address fails to resolve. Bugfix on
6587 0.2.1.23; fixes bug 1269.
6588 - When freeing a session key, zero it out completely. We only zeroed
6589 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6590 patched by ekir. Fixes bug 1254.
6593 - Fix a dereference-then-NULL-check sequence when publishing
6594 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6596 - Fix another dereference-then-NULL-check sequence. Bugfix on
6597 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6598 - Make sure we treat potentially not NUL-terminated strings correctly.
6599 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6603 Changes in version 0.2.1.24 - 2010-02-21
6604 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6608 - Work correctly out-of-the-box with even more vendor-patched versions
6609 of OpenSSL. In particular, make it so Debian and OS X don't need
6610 customized patches to run/build.
6613 Changes in version 0.2.1.23 - 2010-02-13
6614 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6615 again on the latest OS X, and updates the location of a directory
6618 o Major bugfixes (performance):
6619 - We were selecting our guards uniformly at random, and then weighting
6620 which of our guards we'd use uniformly at random. This imbalance
6621 meant that Tor clients were severely limited on throughput (and
6622 probably latency too) by the first hop in their circuit. Now we
6623 select guards weighted by currently advertised bandwidth. We also
6624 automatically discard guards picked using the old algorithm. Fixes
6625 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6628 - Make Tor work again on the latest OS X: when deciding whether to
6629 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6630 version at run-time, not compile time. We need to do this because
6631 Apple doesn't update its dev-tools headers when it updates its
6632 libraries in a security patch.
6633 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6634 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6635 a memory leak when requesting a hidden service descriptor we've
6636 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6639 o Directory authority changes:
6640 - Change IP address for dannenberg (v3 directory authority), and
6641 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6642 service directory authority) from the list.
6645 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6646 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6649 - Avoid a mad rush at the beginning of each month when each client
6650 rotates half of its guards. Instead we spread the rotation out
6651 throughout the month, but we still avoid leaving a precise timestamp
6652 in the state file about when we first picked the guard. Improves
6653 over the behavior introduced in 0.1.2.17.
6656 Changes in version 0.2.2.8-alpha - 2010-01-26
6657 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6658 causing bridge relays to disappear. If you're running a bridge,
6662 - Fix a memory corruption bug on bridges that occured during the
6663 inclusion of stats data in extra-info descriptors. Also fix the
6664 interface for geoip_get_bridge_stats* to prevent similar bugs in
6665 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6666 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6669 - Ignore OutboundBindAddress when connecting to localhost.
6670 Connections to localhost need to come _from_ localhost, or else
6671 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6675 Changes in version 0.2.2.7-alpha - 2010-01-19
6676 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6677 as laying the groundwork for further relay-side performance fixes. It
6678 also starts cleaning up client behavior with respect to the EntryNodes,
6679 ExitNodes, and StrictNodes config options.
6681 This release also rotates two directory authority keys, due to a
6682 security breach of some of the Torproject servers.
6684 o Directory authority changes:
6685 - Rotate keys (both v3 identity and relay identity) for moria1
6688 o Major features (performance):
6689 - We were selecting our guards uniformly at random, and then weighting
6690 which of our guards we'd use uniformly at random. This imbalance
6691 meant that Tor clients were severely limited on throughput (and
6692 probably latency too) by the first hop in their circuit. Now we
6693 select guards weighted by currently advertised bandwidth. We also
6694 automatically discard guards picked using the old algorithm. Fixes
6695 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6696 - When choosing which cells to relay first, relays can now favor
6697 circuits that have been quiet recently, to provide lower latency
6698 for low-volume circuits. By default, relays enable or disable this
6699 feature based on a setting in the consensus. You can override
6700 this default by using the new "CircuitPriorityHalflife" config
6701 option. Design and code by Ian Goldberg, Can Tang, and Chris
6703 - Add separate per-conn write limiting to go with the per-conn read
6704 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6705 but never per-conn write limits.
6706 - New consensus params "bwconnrate" and "bwconnburst" to let us
6707 rate-limit client connections as they enter the network. It's
6708 controlled in the consensus so we can turn it on and off for
6709 experiments. It's starting out off. Based on proposal 163.
6711 o Major features (relay selection options):
6712 - Switch to a StrictNodes config option, rather than the previous
6713 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6714 "StrictExcludeNodes" option.
6715 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6716 change during a config reload, mark and discard all our origin
6717 circuits. This fix should address edge cases where we change the
6718 config options and but then choose a circuit that we created before
6720 - If EntryNodes or ExitNodes are set, be more willing to use an
6721 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6723 - Make EntryNodes config option much more aggressive even when
6724 StrictNodes is not set. Before it would prepend your requested
6725 entrynodes to your list of guard nodes, but feel free to use others
6726 after that. Now it chooses only from your EntryNodes if any of
6727 those are available, and only falls back to others if a) they're
6728 all down and b) StrictNodes is not set.
6729 - Now we refresh your entry guards from EntryNodes at each consensus
6730 fetch -- rather than just at startup and then they slowly rot as
6731 the network changes.
6734 - Stop bridge directory authorities from answering dbg-stability.txt
6735 directory queries, which would let people fetch a list of all
6736 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6739 - Log a notice when we get a new control connection. Now it's easier
6740 for security-conscious users to recognize when a local application
6741 is knocking on their controller door. Suggested by bug 1196.
6742 - New config option "CircuitStreamTimeout" to override our internal
6743 timeout schedule for how many seconds until we detach a stream from
6744 a circuit and try a new circuit. If your network is particularly
6745 slow, you might want to set this to a number like 60.
6746 - New controller command "getinfo config-text". It returns the
6747 contents that Tor would write if you send it a SAVECONF command,
6748 so the controller can write the file to disk itself.
6749 - New options for SafeLogging to allow scrubbing only log messages
6750 generated while acting as a relay.
6751 - Ship the bridges spec file in the tarball too.
6752 - Avoid a mad rush at the beginning of each month when each client
6753 rotates half of its guards. Instead we spread the rotation out
6754 throughout the month, but we still avoid leaving a precise timestamp
6755 in the state file about when we first picked the guard. Improves
6756 over the behavior introduced in 0.1.2.17.
6758 o Minor bugfixes (compiling):
6759 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6760 hides it. Bugfix on 0.2.2.6-alpha.
6761 - Fix compilation on Solaris by removing support for the
6762 DisableAllSwap config option. Solaris doesn't have an rlimit for
6763 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6766 o Minor bugfixes (crashes):
6767 - Do not segfault when writing buffer stats when we haven't observed
6768 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6770 - If we're in the pathological case where there's no exit bandwidth
6771 but there is non-exit bandwidth, or no guard bandwidth but there
6772 is non-guard bandwidth, don't crash during path selection. Bugfix
6774 - Fix an impossible-to-actually-trigger buffer overflow in relay
6775 descriptor generation. Bugfix on 0.1.0.15.
6777 o Minor bugfixes (privacy):
6778 - Fix an instance where a Tor directory mirror might accidentally
6779 log the IP address of a misbehaving Tor client. Bugfix on
6781 - Don't list Windows capabilities in relay descriptors. We never made
6782 use of them, and maybe it's a bad idea to publish them. Bugfix
6785 o Minor bugfixes (other):
6786 - Resolve an edge case in path weighting that could make us misweight
6787 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6788 - Fix statistics on client numbers by country as seen by bridges that
6789 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
6790 intervals instead of variable 12-to-48-hour intervals.
6791 - After we free an internal connection structure, overwrite it
6792 with a different memory value than we use for overwriting a freed
6793 internal circuit structure. Should help with debugging. Suggested
6795 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6799 - Remove the HSAuthorityRecordStats option that version 0 hidden
6800 service authorities could have used to track statistics of overall
6801 hidden service usage.
6804 Changes in version 0.2.1.22 - 2010-01-19
6805 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6806 authorities -- it would tell you its whole history of bridge descriptors
6807 if you make the right directory request. This stable update also
6808 rotates two of the seven v3 directory authority keys and locations.
6810 o Directory authority changes:
6811 - Rotate keys (both v3 identity and relay identity) for moria1
6815 - Stop bridge directory authorities from answering dbg-stability.txt
6816 directory queries, which would let people fetch a list of all
6817 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6820 Changes in version 0.2.1.21 - 2009-12-21
6821 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6822 library. If you use Tor on Linux / Unix and you're getting SSL
6823 renegotiation errors, upgrading should help. We also recommend an
6824 upgrade if you're an exit relay.
6827 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6828 handshake from working unless we explicitly tell OpenSSL that we
6829 are using SSL renegotiation safely. We are, of course, but OpenSSL
6830 0.9.8l won't work unless we say we are.
6831 - Avoid crashing if the client is trying to upload many bytes and the
6832 circuit gets torn down at the same time, or if the flip side
6833 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6836 - Do not refuse to learn about authority certs and v2 networkstatus
6837 documents that are older than the latest consensus. This bug might
6838 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6839 Spotted and fixed by xmux.
6840 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
6841 trigger platform-specific option misparsing case found by Coverity
6843 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
6844 trigger assert. Fixes bug 1173.
6847 Changes in version 0.2.2.6-alpha - 2009-11-19
6848 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
6849 support for the new lower-footprint "microdescriptor" directory design,
6850 future-proofing our consensus format against new hash functions or
6851 other changes, and an Android port. It also makes Tor compatible with
6852 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
6855 - Directory authorities can now create, vote on, and serve multiple
6856 parallel formats of directory data as part of their voting process.
6857 Partially implements Proposal 162: "Publish the consensus in
6859 - Directory authorities can now agree on and publish small summaries
6860 of router information that clients can use in place of regular
6861 server descriptors. This transition will eventually allow clients
6862 to use far less bandwidth for downloading information about the
6863 network. Begins the implementation of Proposal 158: "Clients
6864 download consensus + microdescriptors".
6865 - The directory voting system is now extensible to use multiple hash
6866 algorithms for signatures and resource selection. Newer formats
6867 are signed with SHA256, with a possibility for moving to a better
6868 hash algorithm in the future.
6869 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
6870 current and future memory pages via mlockall(). On supported
6871 platforms (modern Linux and probably BSD but not Windows or OS X),
6872 this should effectively disable any and all attempts to page out
6873 memory. This option requires that you start your Tor as root --
6874 if you use DisableAllSwap, please consider using the User option
6875 to properly reduce the privileges of your Tor.
6876 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
6877 to help Tor build correctly for Android phones.
6880 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6881 handshake from working unless we explicitly tell OpenSSL that we
6882 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
6883 won't work unless we say we are.
6886 - Fix a crash bug when trying to initialize the evdns module in
6887 Libevent 2. Bugfix on 0.2.1.16-rc.
6888 - Stop logging at severity 'warn' when some other Tor client tries
6889 to establish a circuit with us using weak DH keys. It's a protocol
6890 violation, but that doesn't mean ordinary users need to hear about
6891 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6892 - Do not refuse to learn about authority certs and v2 networkstatus
6893 documents that are older than the latest consensus. This bug might
6894 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6895 Spotted and fixed by xmux.
6896 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
6897 - If all authorities restart at once right before a consensus vote,
6898 nobody will vote about "Running", and clients will get a consensus
6899 with no usable relays. Instead, authorities refuse to build a
6900 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
6901 - If your relay can't keep up with the number of incoming create
6902 cells, it would log one warning per failure into your logs. Limit
6903 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6904 - Bridges now use "reject *:*" as their default exit policy. Bugfix
6905 on 0.2.0.3-alpha; fixes bug 1113.
6906 - Fix a memory leak on directory authorities during voting that was
6907 introduced in 0.2.2.1-alpha. Found via valgrind.
6910 Changes in version 0.2.1.20 - 2009-10-15
6911 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
6912 services at once, prepares for more performance improvements, and
6913 fixes a bunch of smaller bugs.
6915 The Windows and OS X bundles also include a more recent Vidalia,
6916 and switch from Privoxy to Polipo.
6918 The OS X installers are now drag and drop. It's best to un-install
6919 Tor/Vidalia and then install this new bundle, rather than upgrade. If
6920 you want to upgrade, you'll need to update the paths for Tor and Polipo
6921 in the Vidalia Settings window.
6924 - Send circuit or stream sendme cells when our window has decreased
6925 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6926 by Karsten when testing the "reduce circuit window" performance
6927 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6928 before the release of Tor 0.0.0. This is the new winner of the
6930 - Fix a remotely triggerable memory leak when a consensus document
6931 contains more than one signature from the same voter. Bugfix on
6933 - Avoid segfault in rare cases when finishing an introduction circuit
6934 as a client and finding out that we don't have an introduction key
6935 for it. Fixes bug 1073. Reported by Aaron Swartz.
6938 - Tor now reads the "circwindow" parameter out of the consensus,
6939 and uses that value for its circuit package window rather than the
6940 default of 1000 cells. Begins the implementation of proposal 168.
6942 o New directory authorities:
6943 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6945 - Move moria1 and tonga to alternate IP addresses.
6948 - Fix a signed/unsigned compile warning in 0.2.1.19.
6949 - Fix possible segmentation fault on directory authorities. Bugfix on
6951 - Fix an extremely rare infinite recursion bug that could occur if
6952 we tried to log a message after shutting down the log subsystem.
6953 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6954 - Fix an obscure bug where hidden services on 64-bit big-endian
6955 systems might mis-read the timestamp in v3 introduce cells, and
6956 refuse to connect back to the client. Discovered by "rotor".
6957 Bugfix on 0.2.1.6-alpha.
6958 - We were triggering a CLOCK_SKEW controller status event whenever
6959 we connect via the v2 connection protocol to any relay that has
6960 a wrong clock. Instead, we should only inform the controller when
6961 it's a trusted authority that claims our clock is wrong. Bugfix
6962 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6963 - We were telling the controller about CHECKING_REACHABILITY and
6964 REACHABILITY_FAILED status events whenever we launch a testing
6965 circuit or notice that one has failed. Instead, only tell the
6966 controller when we want to inform the user of overall success or
6967 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6969 - Don't warn when we're using a circuit that ends with a node
6970 excluded in ExcludeExitNodes, but the circuit is not used to access
6971 the outside world. This should help fix bug 1090. Bugfix on
6973 - Work around a small memory leak in some versions of OpenSSL that
6974 stopped the memory used by the hostname TLS extension from being
6978 - Add a "getinfo status/accepted-server-descriptor" controller
6979 command, which is the recommended way for controllers to learn
6980 whether our server descriptor has been successfully received by at
6981 least on directory authority. Un-recommend good-server-descriptor
6982 getinfo and status events until we have a better design for them.
6985 Changes in version 0.2.2.5-alpha - 2009-10-11
6986 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
6989 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
6991 o Directory authorities:
6992 - Temporarily (just for this release) move dizum to an alternate
6996 Changes in version 0.2.2.4-alpha - 2009-10-10
6997 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
6998 introduces a new unit test framework, shifts directry authority
6999 addresses around to reduce the impact from recent blocking events,
7000 and fixes a few smaller bugs.
7003 - Fix several more asserts in the circuit_build_times code, for
7004 example one that causes Tor to fail to start once we have
7005 accumulated 5000 build times in the state file. Bugfixes on
7006 0.2.2.2-alpha; fixes bug 1108.
7008 o New directory authorities:
7009 - Move moria1 and Tonga to alternate IP addresses.
7012 - Log SSL state transitions at debug level during handshake, and
7013 include SSL states in error messages. This may help debug future
7014 SSL handshake issues.
7015 - Add a new "Handshake" log domain for activities that happen
7016 during the TLS handshake.
7017 - Revert to the "June 3 2009" ip-to-country file. The September one
7018 seems to have removed most US IP addresses.
7019 - Directory authorities now reject Tor relays with versions less than
7020 0.1.2.14. This step cuts out four relays from the current network,
7021 none of which are very big.
7024 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7026 - Fix two memory leaks in the error case of
7027 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7028 - Don't count one-hop circuits when we're estimating how long it
7029 takes circuits to build on average. Otherwise we'll set our circuit
7030 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7031 - Directory authorities no longer change their opinion of, or vote on,
7032 whether a router is Running, unless they have themselves been
7033 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7036 o Code simplifications and refactoring:
7037 - Revise our unit tests to use the "tinytest" framework, so we
7038 can run tests in their own processes, have smarter setup/teardown
7039 code, and so on. The unit test code has moved to its own
7040 subdirectory, and has been split into multiple modules.
7043 Changes in version 0.2.2.3-alpha - 2009-09-23
7044 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7047 - Fix an overzealous assert in our new circuit build timeout code.
7048 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7051 - If the networkstatus consensus tells us that we should use a
7052 negative circuit package window, ignore it. Otherwise we'll
7053 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7056 Changes in version 0.2.2.2-alpha - 2009-09-21
7057 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7058 clients: Tor tracks the average time it takes to build a circuit, and
7059 avoids using circuits that take too long to build. For fast connections,
7060 this feature can cut your expected latency in half. For slow or flaky
7061 connections, it could ruin your Tor experience. Let us know if it does!
7064 - Tor now tracks how long it takes to build client-side circuits
7065 over time, and adapts its timeout to local network performance.
7066 Since a circuit that takes a long time to build will also provide
7067 bad performance, we get significant latency improvements by
7068 discarding the slowest 20% of circuits. Specifically, Tor creates
7069 circuits more aggressively than usual until it has enough data
7070 points for a good timeout estimate. Implements proposal 151.
7071 We are especially looking for reports (good and bad) from users with
7072 both EDGE and broadband connections that can move from broadband
7073 to EDGE and find out if the build-time data in the .tor/state gets
7074 reset without loss of Tor usability. You should also see a notice
7075 log message telling you that Tor has reset its timeout.
7076 - Directory authorities can now vote on arbitary integer values as
7077 part of the consensus process. This is designed to help set
7078 network-wide parameters. Implements proposal 167.
7079 - Tor now reads the "circwindow" parameter out of the consensus,
7080 and uses that value for its circuit package window rather than the
7081 default of 1000 cells. Begins the implementation of proposal 168.
7084 - Fix a remotely triggerable memory leak when a consensus document
7085 contains more than one signature from the same voter. Bugfix on
7089 - Fix an extremely rare infinite recursion bug that could occur if
7090 we tried to log a message after shutting down the log subsystem.
7091 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7092 - Fix parsing for memory or time units given without a space between
7093 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7094 - A networkstatus vote must contain exactly one signature. Spec
7095 conformance issue. Bugfix on 0.2.0.3-alpha.
7096 - Fix an obscure bug where hidden services on 64-bit big-endian
7097 systems might mis-read the timestamp in v3 introduce cells, and
7098 refuse to connect back to the client. Discovered by "rotor".
7099 Bugfix on 0.2.1.6-alpha.
7100 - We were triggering a CLOCK_SKEW controller status event whenever
7101 we connect via the v2 connection protocol to any relay that has
7102 a wrong clock. Instead, we should only inform the controller when
7103 it's a trusted authority that claims our clock is wrong. Bugfix
7104 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7105 - We were telling the controller about CHECKING_REACHABILITY and
7106 REACHABILITY_FAILED status events whenever we launch a testing
7107 circuit or notice that one has failed. Instead, only tell the
7108 controller when we want to inform the user of overall success or
7109 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7111 - Don't warn when we're using a circuit that ends with a node
7112 excluded in ExcludeExitNodes, but the circuit is not used to access
7113 the outside world. This should help fix bug 1090, but more problems
7114 remain. Bugfix on 0.2.1.6-alpha.
7115 - Work around a small memory leak in some versions of OpenSSL that
7116 stopped the memory used by the hostname TLS extension from being
7118 - Make our 'torify' script more portable; if we have only one of
7119 'torsocks' or 'tsocks' installed, don't complain to the user;
7120 and explain our warning about tsocks better.
7123 - Add a "getinfo status/accepted-server-descriptor" controller
7124 command, which is the recommended way for controllers to learn
7125 whether our server descriptor has been successfully received by at
7126 least on directory authority. Un-recommend good-server-descriptor
7127 getinfo and status events until we have a better design for them.
7128 - Update to the "September 4 2009" ip-to-country file.
7131 Changes in version 0.2.2.1-alpha - 2009-08-26
7132 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7133 Tor clients to bootstrap on networks where only port 80 is reachable,
7134 makes it more straightforward to support hardware crypto accelerators,
7135 and starts the groundwork for gathering stats safely at relays.
7138 - Start the process of disabling ".exit" address notation, since it
7139 can be used for a variety of esoteric application-level attacks
7140 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7143 o New directory authorities:
7144 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7148 - New AccelName and AccelDir options add support for dynamic OpenSSL
7149 hardware crypto acceleration engines.
7150 - Tor now supports tunneling all of its outgoing connections over
7151 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7152 configuration options. Code by Christopher Davis.
7155 - Send circuit or stream sendme cells when our window has decreased
7156 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7157 by Karsten when testing the "reduce circuit window" performance
7158 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7159 before the release of Tor 0.0.0. This is the new winner of the
7162 o New options for gathering stats safely:
7163 - Directory mirrors that set "DirReqStatistics 1" write statistics
7164 about directory requests to disk every 24 hours. As compared to the
7165 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7166 1) stats are written to disk exactly every 24 hours; 2) estimated
7167 shares of v2 and v3 requests are determined as mean values, not at
7168 the end of a measurement period; 3) unresolved requests are listed
7169 with country code '??'; 4) directories also measure download times.
7170 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7171 number of exit streams and transferred bytes per port to disk every
7173 - Relays that set "CellStatistics 1" write statistics on how long
7174 cells spend in their circuit queues to disk every 24 hours.
7175 - Entry nodes that set "EntryStatistics 1" write statistics on the
7176 rough number and origins of connecting clients to disk every 24
7178 - Relays that write any of the above statistics to disk and set
7179 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7180 their extra-info documents.
7183 - New --digests command-line switch to output the digests of the
7184 source files Tor was built with.
7185 - The "torify" script now uses torsocks where available.
7186 - The memarea code now uses a sentinel value at the end of each area
7187 to make sure nothing writes beyond the end of an area. This might
7188 help debug some conceivable causes of bug 930.
7189 - Time and memory units in the configuration file can now be set to
7190 fractional units. For example, "2.5 GB" is now a valid value for
7192 - Certain Tor clients (such as those behind check.torproject.org) may
7193 want to fetch the consensus in an extra early manner. To enable this
7194 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7195 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7196 as only certain clients who must have this information sooner should
7198 - Instead of adding the svn revision to the Tor version string, report
7199 the git commit (when we're building from a git checkout).
7202 - If any of the v3 certs we download are unparseable, we should
7203 actually notice the failure so we don't retry indefinitely. Bugfix
7204 on 0.2.0.x; reported by "rotator".
7205 - If the cached cert file is unparseable, warn but don't exit.
7206 - Fix possible segmentation fault on directory authorities. Bugfix on
7208 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7209 Might help diagnosing bug 1051.
7211 o Deprecated and removed features:
7212 - The controller no longer accepts the old obsolete "addr-mappings/"
7213 or "unregistered-servers-" GETINFO values.
7214 - Hidden services no longer publish version 0 descriptors, and clients
7215 do not request or use version 0 descriptors. However, the old hidden
7216 service authorities still accept and serve version 0 descriptors
7217 when contacted by older hidden services/clients.
7218 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7219 always on; using them is necessary for correct forward-compatible
7221 - Remove support for .noconnect style addresses. Nobody was using
7222 them, and they provided another avenue for detecting Tor users
7223 via application-level web tricks.
7225 o Packaging changes:
7226 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7227 installer bundles. See
7228 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7229 for details of what's new in Vidalia 0.2.3.
7230 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7231 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7232 configuration file, rather than the old Privoxy.
7233 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7234 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7235 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7236 better compatibility with OS X 10.6, aka Snow Leopard.
7237 - OS X Vidalia Bundle: The multi-package installer is now replaced
7238 by a simple drag and drop to the /Applications folder. This change
7239 occurred with the upgrade to Vidalia 0.2.3.
7242 Changes in version 0.2.1.19 - 2009-07-28
7243 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7244 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7247 - Make accessing hidden services on 0.2.1.x work right again.
7248 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7249 part of patch provided by "optimist".
7252 - When a relay/bridge is writing out its identity key fingerprint to
7253 the "fingerprint" file and to its logs, write it without spaces. Now
7254 it will look like the fingerprints in our bridges documentation,
7255 and confuse fewer users.
7258 - Relays no longer publish a new server descriptor if they change
7259 their MaxAdvertisedBandwidth config option but it doesn't end up
7260 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7261 fixes bug 1026. Patch from Sebastian.
7262 - Avoid leaking memory every time we get a create cell but we have
7263 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7264 fixes bug 1034. Reported by BarkerJr.
7267 Changes in version 0.2.1.18 - 2009-07-24
7268 Tor 0.2.1.18 lays the foundations for performance improvements,
7269 adds status events to help users diagnose bootstrap problems, adds
7270 optional authentication/authorization for hidden services, fixes a
7271 variety of potential anonymity problems, and includes a huge pile of
7272 other features and bug fixes.
7275 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7278 Changes in version 0.2.1.17-rc - 2009-07-07
7279 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7280 candidate for the 0.2.1.x series. It lays the groundwork for further
7281 client performance improvements, and also fixes a big bug with directory
7282 authorities that were causing them to assign Guard and Stable flags
7285 The Windows bundles also finally include the geoip database that we
7286 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7287 should actually install Torbutton rather than giving you a cryptic
7288 failure message (oops).
7291 - Clients now use the bandwidth values in the consensus, rather than
7292 the bandwidth values in each relay descriptor. This approach opens
7293 the door to more accurate bandwidth estimates once the directory
7294 authorities start doing active measurements. Implements more of
7298 - When Tor clients restart after 1-5 days, they discard all their
7299 cached descriptors as too old, but they still use the cached
7300 consensus document. This approach is good for robustness, but
7301 bad for performance: since they don't know any bandwidths, they
7302 end up choosing at random rather than weighting their choice by
7303 speed. Fixed by the above feature of putting bandwidths in the
7304 consensus. Bugfix on 0.2.0.x.
7305 - Directory authorities were neglecting to mark relays down in their
7306 internal histories if the relays fall off the routerlist without
7307 ever being found unreachable. So there were relays in the histories
7308 that haven't been seen for eight months, and are listed as being
7309 up for eight months. This wreaked havoc on the "median wfu"
7310 and "median mtbf" calculations, in turn making Guard and Stable
7311 flags very wrong, hurting network performance. Fixes bugs 696 and
7312 969. Bugfix on 0.2.0.6-alpha.
7315 - Serve the DirPortFrontPage page even when we have been approaching
7316 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7317 - The control port would close the connection before flushing long
7318 replies, such as the network consensus, if a QUIT command was issued
7319 before the reply had completed. Now, the control port flushes all
7320 pending replies before closing the connection. Also fixed a spurious
7321 warning when a QUIT command is issued after a malformed or rejected
7322 AUTHENTICATE command, but before the connection was closed. Patch
7323 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7324 - When we can't find an intro key for a v2 hidden service descriptor,
7325 fall back to the v0 hidden service descriptor and log a bug message.
7326 Workaround for bug 1024.
7327 - Fix a log message that did not respect the SafeLogging option.
7331 - If we're a relay and we change our IP address, be more verbose
7332 about the reason that made us change. Should help track down
7333 further bugs for relays on dynamic IP addresses.
7336 Changes in version 0.2.0.35 - 2009-06-24
7338 - Avoid crashing in the presence of certain malformed descriptors.
7339 Found by lark, and by automated fuzzing.
7340 - Fix an edge case where a malicious exit relay could convince a
7341 controller that the client's DNS question resolves to an internal IP
7342 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7345 - Finally fix the bug where dynamic-IP relays disappear when their
7346 IP address changes: directory mirrors were mistakenly telling
7347 them their old address if they asked via begin_dir, so they
7348 never got an accurate answer about their new address, so they
7349 just vanished after a day. For belt-and-suspenders, relays that
7350 don't set Address in their config now avoid using begin_dir for
7351 all direct connections. Should fix bugs 827, 883, and 900.
7352 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7353 that would occur on some exit nodes when DNS failures and timeouts
7354 occurred in certain patterns. Fix for bug 957.
7357 - When starting with a cache over a few days old, do not leak
7358 memory for the obsolete router descriptors in it. Bugfix on
7359 0.2.0.33; fixes bug 672.
7360 - Hidden service clients didn't use a cached service descriptor that
7361 was older than 15 minutes, but wouldn't fetch a new one either,
7362 because there was already one in the cache. Now, fetch a v2
7363 descriptor unless the same descriptor was added to the cache within
7364 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7367 Changes in version 0.2.1.16-rc - 2009-06-20
7368 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7369 a bunch of minor bugs.
7372 - Fix an edge case where a malicious exit relay could convince a
7373 controller that the client's DNS question resolves to an internal IP
7374 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7376 o Major performance improvements (on 0.2.0.x):
7377 - Disable and refactor some debugging checks that forced a linear scan
7378 over the whole server-side DNS cache. These accounted for over 50%
7379 of CPU time on a relatively busy exit node's gprof profile. Found
7381 - Disable some debugging checks that appeared in exit node profile
7385 - Update to the "June 3 2009" ip-to-country file.
7386 - Do not have tor-resolve automatically refuse all .onion addresses;
7387 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7389 o Minor bugfixes (on 0.2.0.x):
7390 - Log correct error messages for DNS-related network errors on
7392 - Fix a race condition that could cause crashes or memory corruption
7393 when running as a server with a controller listening for log
7395 - Avoid crashing when we have a policy specified in a DirPolicy or
7396 SocksPolicy or ReachableAddresses option with ports set on it,
7397 and we re-load the policy. May fix bug 996.
7398 - Hidden service clients didn't use a cached service descriptor that
7399 was older than 15 minutes, but wouldn't fetch a new one either,
7400 because there was already one in the cache. Now, fetch a v2
7401 descriptor unless the same descriptor was added to the cache within
7402 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7404 o Minor bugfixes (on 0.2.1.x):
7405 - Don't warn users about low port and hibernation mix when they
7406 provide a *ListenAddress directive to fix that. Bugfix on
7408 - When switching back and forth between bridge mode, do not start
7409 gathering GeoIP data until two hours have passed.
7410 - Do not complain that the user has requested an excluded node as
7411 an exit when the node is not really an exit. This could happen
7412 because the circuit was for testing, or an introduction point.
7416 Changes in version 0.2.1.15-rc - 2009-05-25
7417 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7418 series. It fixes a major bug on fast exit relays, as well as a variety
7421 o Major bugfixes (on 0.2.0.x):
7422 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7423 that would occur on some exit nodes when DNS failures and timeouts
7424 occurred in certain patterns. Fix for bug 957.
7426 o Minor bugfixes (on 0.2.0.x):
7427 - Actually return -1 in the error case for read_bandwidth_usage().
7428 Harmless bug, since we currently don't care about the return value
7429 anywhere. Bugfix on 0.2.0.9-alpha.
7430 - Provide a more useful log message if bug 977 (related to buffer
7431 freelists) ever reappears, and do not crash right away.
7432 - Fix an assertion failure on 64-bit platforms when we allocated
7433 memory right up to the end of a memarea, then realigned the memory
7434 one step beyond the end. Fixes a possible cause of bug 930.
7435 - Protect the count of open sockets with a mutex, so we can't
7436 corrupt it when two threads are closing or opening sockets at once.
7437 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7438 - Don't allow a bridge to publish its router descriptor to a
7439 non-bridge directory authority. Fixes part of bug 932.
7440 - When we change to or from being a bridge, reset our counts of
7441 client usage by country. Fixes bug 932.
7442 - Fix a bug that made stream bandwidth get misreported to the
7444 - Stop using malloc_usable_size() to use more area than we had
7445 actually allocated: it was safe, but made valgrind really unhappy.
7446 - Fix a memory leak when v3 directory authorities load their keys
7447 and cert from disk. Bugfix on 0.2.0.1-alpha.
7449 o Minor bugfixes (on 0.2.1.x):
7450 - Fix use of freed memory when deciding to mark a non-addable
7451 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7454 Changes in version 0.2.1.14-rc - 2009-04-12
7455 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7456 series. It begins fixing some major performance problems, and also
7457 finally addresses the bug that was causing relays on dynamic IP
7458 addresses to fall out of the directory.
7461 - Clients replace entry guards that were chosen more than a few months
7462 ago. This change should significantly improve client performance,
7463 especially once more people upgrade, since relays that have been
7464 a guard for a long time are currently overloaded.
7466 o Major bugfixes (on 0.2.0):
7467 - Finally fix the bug where dynamic-IP relays disappear when their
7468 IP address changes: directory mirrors were mistakenly telling
7469 them their old address if they asked via begin_dir, so they
7470 never got an accurate answer about their new address, so they
7471 just vanished after a day. For belt-and-suspenders, relays that
7472 don't set Address in their config now avoid using begin_dir for
7473 all direct connections. Should fix bugs 827, 883, and 900.
7474 - Relays were falling out of the networkstatus consensus for
7475 part of a day if they changed their local config but the
7476 authorities discarded their new descriptor as "not sufficiently
7477 different". Now directory authorities accept a descriptor as changed
7478 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7480 - Avoid crashing in the presence of certain malformed descriptors.
7481 Found by lark, and by automated fuzzing.
7484 - When generating circuit events with verbose nicknames for
7485 controllers, try harder to look up nicknames for routers on a
7486 circuit. (Previously, we would look in the router descriptors we had
7487 for nicknames, but not in the consensus.) Partial fix for bug 941.
7488 - If the bridge config line doesn't specify a port, assume 443.
7489 This makes bridge lines a bit smaller and easier for users to
7491 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7492 bytes (aka 20KB/s), to match our documentation. Also update
7493 directory authorities so they always assign the Fast flag to relays
7494 with 20KB/s of capacity. Now people running relays won't suddenly
7495 find themselves not seeing any use, if the network gets faster
7497 - Update to the "April 3 2009" ip-to-country file.
7500 - Avoid trying to print raw memory to the logs when we decide to
7501 give up on downloading a given relay descriptor. Bugfix on
7503 - In tor-resolve, when the Tor client to use is specified by
7504 <hostname>:<port>, actually use the specified port rather than
7505 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7506 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7507 - When starting with a cache over a few days old, do not leak
7508 memory for the obsolete router descriptors in it. Bugfix on
7510 - Avoid double-free on list of successfully uploaded hidden
7511 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7512 - Change memarea_strndup() implementation to work even when
7513 duplicating a string at the end of a page. This bug was
7514 harmless for now, but could have meant crashes later. Fix by
7515 lark. Bugfix on 0.2.1.1-alpha.
7516 - Limit uploaded directory documents to be 16M rather than 500K.
7517 The directory authorities were refusing v3 consensus votes from
7518 other authorities, since the votes are now 504K. Fixes bug 959;
7519 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7520 - Directory authorities should never send a 503 "busy" response to
7521 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7525 Changes in version 0.2.1.13-alpha - 2009-03-09
7526 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7527 cleanups. We're finally getting close to a release candidate.
7530 - Correctly update the list of which countries we exclude as
7531 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7532 lark. Bugfix on 0.2.1.6-alpha.
7534 o Minor bugfixes (on 0.2.0.x and earlier):
7535 - Automatically detect MacOSX versions earlier than 10.4.0, and
7536 disable kqueue from inside Tor when running with these versions.
7537 We previously did this from the startup script, but that was no
7538 help to people who didn't use the startup script. Resolves bug 863.
7539 - When we had picked an exit node for a connection, but marked it as
7540 "optional", and it turned out we had no onion key for the exit,
7541 stop wanting that exit and try again. This situation may not
7542 be possible now, but will probably become feasible with proposal
7543 158. Spotted by rovv. Fixes another case of bug 752.
7544 - Clients no longer cache certificates for authorities they do not
7545 recognize. Bugfix on 0.2.0.9-alpha.
7546 - When we can't transmit a DNS request due to a network error, retry
7547 it after a while, and eventually transmit a failing response to
7548 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7549 - If the controller claimed responsibility for a stream, but that
7550 stream never finished making its connection, it would live
7551 forever in circuit_wait state. Now we close it after SocksTimeout
7552 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7553 - Drop begin cells to a hidden service if they come from the middle
7554 of a circuit. Patch from lark.
7555 - When we erroneously receive two EXTEND cells for the same circuit
7556 ID on the same connection, drop the second. Patch from lark.
7557 - Fix a crash that occurs on exit nodes when a nameserver request
7558 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7559 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7561 - Do not assume that a stack-allocated character array will be
7562 64-bit aligned on platforms that demand that uint64_t access is
7563 aligned. Possible fix for bug 604.
7564 - Parse dates and IPv4 addresses in a locale- and libc-independent
7565 manner, to avoid platform-dependent behavior on malformed input.
7566 - Build correctly when configured to build outside the main source
7567 path. Patch from Michael Gold.
7568 - We were already rejecting relay begin cells with destination port
7569 of 0. Now also reject extend cells with destination port or address
7570 of 0. Suggested by lark.
7572 o Minor bugfixes (on 0.2.1.x):
7573 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7574 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7575 - If we're an exit node, scrub the IP address to which we are exiting
7576 in the logs. Bugfix on 0.2.1.8-alpha.
7579 - On Linux, use the prctl call to re-enable core dumps when the user
7581 - New controller event NEWCONSENSUS that lists the networkstatus
7582 lines for every recommended relay. Now controllers like Torflow
7583 can keep up-to-date on which relays they should be using.
7584 - Update to the "February 26 2009" ip-to-country file.
7587 Changes in version 0.2.0.34 - 2009-02-08
7588 Tor 0.2.0.34 features several more security-related fixes. You should
7589 upgrade, especially if you run an exit relay (remote crash) or a
7590 directory authority (remote infinite loop), or you're on an older
7591 (pre-XP) or not-recently-patched Windows (remote exploit).
7593 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7594 have many known flaws, and nobody should be using them. You should
7595 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7596 stop using those packages and upgrade anyway.
7599 - Fix an infinite-loop bug on handling corrupt votes under certain
7600 circumstances. Bugfix on 0.2.0.8-alpha.
7601 - Fix a temporary DoS vulnerability that could be performed by
7602 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7603 - Avoid a potential crash on exit nodes when processing malformed
7604 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7605 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7606 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7609 - Fix compilation on systems where time_t is a 64-bit integer.
7610 Patch from Matthias Drochner.
7611 - Don't consider expiring already-closed client connections. Fixes
7612 bug 893. Bugfix on 0.0.2pre20.
7615 Changes in version 0.2.1.12-alpha - 2009-02-08
7616 Tor 0.2.1.12-alpha features several more security-related fixes. You
7617 should upgrade, especially if you run an exit relay (remote crash) or
7618 a directory authority (remote infinite loop), or you're on an older
7619 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7620 includes a big pile of minor bugfixes and cleanups.
7623 - Fix an infinite-loop bug on handling corrupt votes under certain
7624 circumstances. Bugfix on 0.2.0.8-alpha.
7625 - Fix a temporary DoS vulnerability that could be performed by
7626 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7627 - Avoid a potential crash on exit nodes when processing malformed
7628 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7631 - Let controllers actually ask for the "clients_seen" event for
7632 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7633 reported by Matt Edman.
7634 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7636 - Fix a bug in address parsing that was preventing bridges or hidden
7637 service targets from being at IPv6 addresses.
7638 - Solve a bug that kept hardware crypto acceleration from getting
7639 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7641 - Remove a bash-ism from configure.in to build properly on non-Linux
7642 platforms. Bugfix on 0.2.1.1-alpha.
7643 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7644 headers. Bugfix on 0.2.0.10-alpha.
7645 - Don't consider expiring already-closed client connections. Fixes
7646 bug 893. Bugfix on 0.0.2pre20.
7647 - Fix another interesting corner-case of bug 891 spotted by rovv:
7648 Previously, if two hosts had different amounts of clock drift, and
7649 one of them created a new connection with just the wrong timing,
7650 the other might decide to deprecate the new connection erroneously.
7651 Bugfix on 0.1.1.13-alpha.
7652 - Resolve a very rare crash bug that could occur when the user forced
7653 a nameserver reconfiguration during the middle of a nameserver
7654 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7655 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7656 Bugfix on 0.2.1.7-alpha.
7657 - If we're using bridges and our network goes away, be more willing
7658 to forgive our bridges and try again when we get an application
7659 request. Bugfix on 0.2.0.x.
7662 - Support platforms where time_t is 64 bits long. (Congratulations,
7663 NetBSD!) Patch from Matthias Drochner.
7664 - Add a 'getinfo status/clients-seen' controller command, in case
7665 controllers want to hear clients_seen events but connect late.
7668 - Disable GCC's strict alias optimization by default, to avoid the
7669 likelihood of its introducing subtle bugs whenever our code violates
7670 the letter of C99's alias rules.
7673 Changes in version 0.2.0.33 - 2009-01-21
7674 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7675 useful to users. It also finally fixes a bug where a relay or client
7676 that's been off for many days would take a long time to bootstrap.
7678 This update also fixes an important security-related bug reported by
7679 Ilja van Sprundel. You should upgrade. (We'll send out more details
7680 about the bug once people have had some time to upgrade.)
7683 - Fix a heap-corruption bug that may be remotely triggerable on
7684 some platforms. Reported by Ilja van Sprundel.
7687 - When a stream at an exit relay is in state "resolving" or
7688 "connecting" and it receives an "end" relay cell, the exit relay
7689 would silently ignore the end cell and not close the stream. If
7690 the client never closes the circuit, then the exit relay never
7691 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7693 - When sending CREATED cells back for a given circuit, use a 64-bit
7694 connection ID to find the right connection, rather than an addr:port
7695 combination. Now that we can have multiple OR connections between
7696 the same ORs, it is no longer possible to use addr:port to uniquely
7697 identify a connection.
7698 - Bridge relays that had DirPort set to 0 would stop fetching
7699 descriptors shortly after startup, and then briefly resume
7700 after a new bandwidth test and/or after publishing a new bridge
7701 descriptor. Bridge users that try to bootstrap from them would
7702 get a recent networkstatus but would get descriptors from up to
7703 18 hours earlier, meaning most of the descriptors were obsolete
7704 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7705 - Prevent bridge relays from serving their 'extrainfo' document
7706 to anybody who asks, now that extrainfo docs include potentially
7707 sensitive aggregated client geoip summaries. Bugfix on
7709 - If the cached networkstatus consensus is more than five days old,
7710 discard it rather than trying to use it. In theory it could be
7711 useful because it lists alternate directory mirrors, but in practice
7712 it just means we spend many minutes trying directory mirrors that
7713 are long gone from the network. Also discard router descriptors as
7714 we load them if they are more than five days old, since the onion
7715 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7718 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7719 could make gcc generate non-functional binary search code. Bugfix
7721 - Build correctly on platforms without socklen_t.
7722 - Compile without warnings on solaris.
7723 - Avoid potential crash on internal error during signature collection.
7724 Fixes bug 864. Patch from rovv.
7725 - Correct handling of possible malformed authority signing key
7726 certificates with internal signature types. Fixes bug 880.
7727 Bugfix on 0.2.0.3-alpha.
7728 - Fix a hard-to-trigger resource leak when logging credential status.
7730 - When we can't initialize DNS because the network is down, do not
7731 automatically stop Tor from starting. Instead, we retry failed
7732 dns_init() every 10 minutes, and change the exit policy to reject
7733 *:* until one succeeds. Fixes bug 691.
7734 - Use 64 bits instead of 32 bits for connection identifiers used with
7735 the controller protocol, to greatly reduce risk of identifier reuse.
7736 - When we're choosing an exit node for a circuit, and we have
7737 no pending streams, choose a good general exit rather than one that
7738 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7739 - Fix another case of assuming, when a specific exit is requested,
7740 that we know more than the user about what hosts it allows.
7741 Fixes one case of bug 752. Patch from rovv.
7742 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7743 seconds. Warn the user if lower values are given in the
7744 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7745 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7746 user if lower values are given in the configuration. Bugfix on
7747 0.1.1.17-rc. Patch by Sebastian.
7748 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7749 the cache because we already had a v0 descriptor with the same ID.
7750 Bugfix on 0.2.0.18-alpha.
7751 - Fix a race condition when freeing keys shared between main thread
7752 and CPU workers that could result in a memory leak. Bugfix on
7753 0.1.0.1-rc. Fixes bug 889.
7754 - Send a valid END cell back when a client tries to connect to a
7755 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7756 840. Patch from rovv.
7757 - Check which hops rendezvous stream cells are associated with to
7758 prevent possible guess-the-streamid injection attacks from
7759 intermediate hops. Fixes another case of bug 446. Based on patch
7761 - If a broken client asks a non-exit router to connect somewhere,
7762 do not even do the DNS lookup before rejecting the connection.
7763 Fixes another case of bug 619. Patch from rovv.
7764 - When a relay gets a create cell it can't decrypt (e.g. because it's
7765 using the wrong onion key), we were dropping it and letting the
7766 client time out. Now actually answer with a destroy cell. Fixes
7767 bug 904. Bugfix on 0.0.2pre8.
7769 o Minor bugfixes (hidden services):
7770 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7771 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7774 - Report the case where all signatures in a detached set are rejected
7775 differently than the case where there is an error handling the
7777 - When we realize that another process has modified our cached
7778 descriptors, print out a more useful error message rather than
7779 triggering an assertion. Fixes bug 885. Patch from Karsten.
7780 - Implement the 0x20 hack to better resist DNS poisoning: set the
7781 case on outgoing DNS requests randomly, and reject responses that do
7782 not match the case correctly. This logic can be disabled with the
7783 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7784 of servers that do not reliably preserve case in replies. See
7785 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7787 - Check DNS replies for more matching fields to better resist DNS
7789 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7790 compress cells, which are basically all encrypted, compressed, or
7794 Changes in version 0.2.1.11-alpha - 2009-01-20
7795 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
7796 week it will take a long time to bootstrap again" bug. It also fixes
7797 an important security-related bug reported by Ilja van Sprundel. You
7798 should upgrade. (We'll send out more details about the bug once people
7799 have had some time to upgrade.)
7802 - Fix a heap-corruption bug that may be remotely triggerable on
7803 some platforms. Reported by Ilja van Sprundel.
7806 - Discard router descriptors as we load them if they are more than
7807 five days old. Otherwise if Tor is off for a long time and then
7808 starts with cached descriptors, it will try to use the onion
7809 keys in those obsolete descriptors when building circuits. Bugfix
7810 on 0.2.0.x. Fixes bug 887.
7813 - Try to make sure that the version of Libevent we're running with
7814 is binary-compatible with the one we built with. May address bug
7816 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
7817 for bug 905. Bugfix on 0.2.1.7-alpha.
7818 - Add a new --enable-local-appdata configuration switch to change
7819 the default location of the datadir on win32 from APPDATA to
7820 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7821 entirely. Patch from coderman.
7824 - Make outbound DNS packets respect the OutboundBindAddress setting.
7825 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7826 - When our circuit fails at the first hop (e.g. we get a destroy
7827 cell back), avoid using that OR connection anymore, and also
7828 tell all the one-hop directory requests waiting for it that they
7829 should fail. Bugfix on 0.2.1.3-alpha.
7830 - In the torify(1) manpage, mention that tsocks will leak your
7834 Changes in version 0.2.1.10-alpha - 2009-01-06
7835 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
7836 would make the bridge relay not so useful if it had DirPort set to 0,
7837 and one that could let an attacker learn a little bit of information
7838 about the bridge's users), and a bug that would cause your Tor relay
7839 to ignore a circuit create request it can't decrypt (rather than reply
7840 with an error). It also fixes a wide variety of other bugs.
7843 - If the cached networkstatus consensus is more than five days old,
7844 discard it rather than trying to use it. In theory it could
7845 be useful because it lists alternate directory mirrors, but in
7846 practice it just means we spend many minutes trying directory
7847 mirrors that are long gone from the network. Helps bug 887 a bit;
7849 - Bridge relays that had DirPort set to 0 would stop fetching
7850 descriptors shortly after startup, and then briefly resume
7851 after a new bandwidth test and/or after publishing a new bridge
7852 descriptor. Bridge users that try to bootstrap from them would
7853 get a recent networkstatus but would get descriptors from up to
7854 18 hours earlier, meaning most of the descriptors were obsolete
7855 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7856 - Prevent bridge relays from serving their 'extrainfo' document
7857 to anybody who asks, now that extrainfo docs include potentially
7858 sensitive aggregated client geoip summaries. Bugfix on
7862 - New controller event "clients_seen" to report a geoip-based summary
7863 of which countries we've seen clients from recently. Now controllers
7864 like Vidalia can show bridge operators that they're actually making
7866 - Build correctly against versions of OpenSSL 0.9.8 or later built
7867 without support for deprecated functions.
7868 - Update to the "December 19 2008" ip-to-country file.
7870 o Minor bugfixes (on 0.2.0.x):
7871 - Authorities now vote for the Stable flag for any router whose
7872 weighted MTBF is at least 5 days, regardless of the mean MTBF.
7873 - Do not remove routers as too old if we do not have any consensus
7874 document. Bugfix on 0.2.0.7-alpha.
7875 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7876 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7877 - When an exit relay resolves a stream address to a local IP address,
7878 do not just keep retrying that same exit relay over and
7879 over. Instead, just close the stream. Addresses bug 872. Bugfix
7880 on 0.2.0.32. Patch from rovv.
7881 - If a hidden service sends us an END cell, do not consider
7882 retrying the connection; just close it. Patch from rovv.
7883 - When we made bridge authorities stop serving bridge descriptors over
7884 unencrypted links, we also broke DirPort reachability testing for
7885 bridges. So bridges with a non-zero DirPort were printing spurious
7886 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
7887 - When a relay gets a create cell it can't decrypt (e.g. because it's
7888 using the wrong onion key), we were dropping it and letting the
7889 client time out. Now actually answer with a destroy cell. Fixes
7890 bug 904. Bugfix on 0.0.2pre8.
7891 - Squeeze 2-5% out of client performance (according to oprofile) by
7892 improving the implementation of some policy-manipulation functions.
7894 o Minor bugfixes (on 0.2.1.x):
7895 - Make get_interface_address() function work properly again; stop
7896 guessing the wrong parts of our address as our address.
7897 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
7898 send on that circuit. Otherwise we might violate the proposal-110
7899 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
7901 - When we're sending non-EXTEND cells to the first hop in a circuit,
7902 for example to use an encrypted directory connection, we don't need
7903 to use RELAY_EARLY cells: the first hop knows what kind of cell
7904 it is, and nobody else can even see the cell type. Conserving
7905 RELAY_EARLY cells makes it easier to cannibalize circuits like
7907 - Stop logging nameserver addresses in reverse order.
7908 - If we are retrying a directory download slowly over and over, do
7909 not automatically give up after the 254th failure. Bugfix on
7911 - Resume reporting accurate "stream end" reasons to the local control
7912 port. They were lost in the changes for Proposal 148. Bugfix on
7915 o Deprecated and removed features:
7916 - The old "tor --version --version" command, which would print out
7917 the subversion "Id" of most of the source files, is now removed. It
7918 turned out to be less useful than we'd expected, and harder to
7921 o Code simplifications and refactoring:
7922 - Change our header file guard macros to be less likely to conflict
7923 with system headers. Adam Langley noticed that we were conflicting
7924 with log.h on Android.
7925 - Tool-assisted documentation cleanup. Nearly every function or
7926 static variable in Tor should have its own documentation now.
7929 Changes in version 0.2.1.9-alpha - 2008-12-25
7930 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
7932 o New directory authorities:
7933 - gabelmoo (the authority run by Karsten Loesing) now has a new
7937 - Never use a connection with a mismatched address to extend a
7938 circuit, unless that connection is canonical. A canonical
7939 connection is one whose address is authenticated by the router's
7940 identity key, either in a NETINFO cell or in a router descriptor.
7941 - Avoid a possible memory corruption bug when receiving hidden service
7942 descriptors. Bugfix on 0.2.1.6-alpha.
7945 - Fix a logic error that would automatically reject all but the first
7946 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
7947 part of bug 813/868. Bug spotted by coderman.
7948 - When a stream at an exit relay is in state "resolving" or
7949 "connecting" and it receives an "end" relay cell, the exit relay
7950 would silently ignore the end cell and not close the stream. If
7951 the client never closes the circuit, then the exit relay never
7952 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
7954 - When we can't initialize DNS because the network is down, do not
7955 automatically stop Tor from starting. Instead, retry failed
7956 dns_init() every 10 minutes, and change the exit policy to reject
7957 *:* until one succeeds. Fixes bug 691.
7960 - Give a better error message when an overzealous init script says
7961 "sudo -u username tor --user username". Makes Bug 882 easier for
7963 - When a directory authority gives us a new guess for our IP address,
7964 log which authority we used. Hopefully this will help us debug
7965 the recent complaints about bad IP address guesses.
7966 - Detect svn revision properly when we're using git-svn.
7967 - Try not to open more than one descriptor-downloading connection
7968 to an authority at once. This should reduce load on directory
7969 authorities. Fixes bug 366.
7970 - Add cross-certification to newly generated certificates, so that
7971 a signing key is enough information to look up a certificate.
7972 Partial implementation of proposal 157.
7973 - Start serving certificates by <identity digest, signing key digest>
7974 pairs. Partial implementation of proposal 157.
7975 - Clients now never report any stream end reason except 'MISC'.
7976 Implements proposal 148.
7977 - On platforms with a maximum syslog string length, truncate syslog
7978 messages to that length ourselves, rather than relying on the
7979 system to do it for us.
7980 - Optimize out calls to time(NULL) that occur for every IO operation,
7981 or for every cell. On systems where time() is a slow syscall,
7982 this fix will be slightly helpful.
7983 - Exit servers can now answer resolve requests for ip6.arpa addresses.
7984 - When we download a descriptor that we then immediately (as
7985 a directory authority) reject, do not retry downloading it right
7986 away. Should save some bandwidth on authorities. Fix for bug
7987 888. Patch by Sebastian Hahn.
7988 - When a download gets us zero good descriptors, do not notify
7989 Tor that new directory information has arrived.
7990 - Avoid some nasty corner cases in the logic for marking connections
7991 as too old or obsolete or noncanonical for circuits. Partial
7994 o Minor features (controller):
7995 - New CONSENSUS_ARRIVED event to note when a new consensus has
7996 been fetched and validated.
7997 - When we realize that another process has modified our cached
7998 descriptors file, print out a more useful error message rather
7999 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8000 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8001 controllers to prevent SIGHUP from reloading the
8002 configuration. Fixes bug 856.
8005 - Resume using the correct "REASON=" stream when telling the
8006 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8007 - When a canonical connection appears later in our internal list
8008 than a noncanonical one for a given OR ID, always use the
8009 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8011 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8012 seconds. Warn the user if lower values are given in the
8013 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8014 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8015 user if lower values are given in the configuration. Bugfix on
8016 0.1.1.17-rc. Patch by Sebastian.
8017 - Fix a race condition when freeing keys shared between main thread
8018 and CPU workers that could result in a memory leak. Bugfix on
8019 0.1.0.1-rc. Fixes bug 889.
8021 o Minor bugfixes (hidden services):
8022 - Do not throw away existing introduction points on SIGHUP (bugfix on
8023 0.0.6pre1); also, do not stall hidden services because we're
8024 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8025 by John Brooks. Patch by Karsten. Fixes bug 874.
8026 - Fix a memory leak when we decline to add a v2 rendezvous
8027 descriptor to the cache because we already had a v0 descriptor
8028 with the same ID. Bugfix on 0.2.0.18-alpha.
8030 o Deprecated and removed features:
8031 - RedirectExits has been removed. It was deprecated since
8033 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8034 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8035 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8037 o Code simplifications and refactoring:
8038 - Rename the confusing or_is_obsolete field to the more appropriate
8039 is_bad_for_new_circs, and move it to or_connection_t where it
8041 - Move edge-only flags from connection_t to edge_connection_t: not
8042 only is this better coding, but on machines of plausible alignment,
8043 it should save 4-8 bytes per connection_t. "Every little bit helps."
8044 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8045 for consistency; keep old option working for backward compatibility.
8046 - Simplify the code for finding connections to use for a circuit.
8049 Changes in version 0.2.1.8-alpha - 2008-12-08
8050 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8051 builds better on unusual platforms like Solaris and old OS X, and
8052 fixes a variety of other issues.
8055 - New DirPortFrontPage option that takes an html file and publishes
8056 it as "/" on the DirPort. Now relay operators can provide a
8057 disclaimer without needing to set up a separate webserver. There's
8058 a sample disclaimer in contrib/tor-exit-notice.html.
8061 - When the client is choosing entry guards, now it selects at most
8062 one guard from a given relay family. Otherwise we could end up with
8063 all of our entry points into the network run by the same operator.
8064 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8067 - Fix a DOS opportunity during the voting signature collection process
8068 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8069 - Fix a possible segfault when establishing an exit connection. Bugfix
8073 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8075 - Made Tor a little less aggressive about deleting expired
8076 certificates. Partial fix for bug 854.
8077 - Stop doing unaligned memory access that generated bus errors on
8078 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8079 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8080 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8081 - Make USR2 log-level switch take effect immediately. Bugfix on
8083 - If one win32 nameserver fails to get added, continue adding the
8084 rest, and don't automatically fail.
8085 - Use fcntl() for locking when flock() is not available. Should fix
8086 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8087 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8088 could make gcc generate non-functional binary search code. Bugfix
8090 - Build correctly on platforms without socklen_t.
8091 - Avoid potential crash on internal error during signature collection.
8092 Fixes bug 864. Patch from rovv.
8093 - Do not use C's stdio library for writing to log files. This will
8094 improve logging performance by a minute amount, and will stop
8095 leaking fds when our disk is full. Fixes bug 861.
8096 - Stop erroneous use of O_APPEND in cases where we did not in fact
8097 want to re-seek to the end of a file before every last write().
8098 - Correct handling of possible malformed authority signing key
8099 certificates with internal signature types. Fixes bug 880. Bugfix
8101 - Fix a hard-to-trigger resource leak when logging credential status.
8105 - Directory mirrors no longer fetch the v1 directory or
8106 running-routers files. They are obsolete, and nobody asks for them
8107 anymore. This is the first step to making v1 authorities obsolete.
8109 o Minor features (controller):
8110 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8114 Changes in version 0.2.0.32 - 2008-11-20
8115 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8116 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8117 a smaller security flaw that might allow an attacker to access local
8118 services, further improves hidden service performance, and fixes a
8119 variety of other issues.
8122 - The "User" and "Group" config options did not clear the
8123 supplementary group entries for the Tor process. The "User" option
8124 is now more robust, and we now set the groups to the specified
8125 user's primary group. The "Group" option is now ignored. For more
8126 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8127 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8128 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8129 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8130 consistently obeyed: if an exit relay refuses a stream because its
8131 exit policy doesn't allow it, we would remember what IP address
8132 the relay said the destination address resolves to, even if it's
8133 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8136 - Fix a DOS opportunity during the voting signature collection process
8137 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8139 o Major bugfixes (hidden services):
8140 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8141 we were failing the whole hidden service request when the v0
8142 descriptor fetch fails, even if the v2 fetch is still pending and
8143 might succeed. Similarly, if the last v2 fetch fails, we were
8144 failing the whole hidden service request even if a v0 fetch is
8145 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8146 - When extending a circuit to a hidden service directory to upload a
8147 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8148 requests failed, because the router descriptor has not been
8149 downloaded yet. In these cases, do not attempt to upload the
8150 rendezvous descriptor, but wait until the router descriptor is
8151 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8152 descriptor from a hidden service directory for which the router
8153 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8157 - Fix several infrequent memory leaks spotted by Coverity.
8158 - When testing for libevent functions, set the LDFLAGS variable
8159 correctly. Found by Riastradh.
8160 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8161 bootstrapping with tunneled directory connections. Bugfix on
8162 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8163 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8164 and we know that server B rejects most-but-not all connections to
8165 port 80, we would previously reject the connection. Now, we assume
8166 the user knows what they were asking for. Fixes bug 752. Bugfix
8167 on 0.0.9rc5. Diagnosed by BarkerJr.
8168 - If we overrun our per-second write limits a little, count this as
8169 having used up our write allocation for the second, and choke
8170 outgoing directory writes. Previously, we had only counted this when
8171 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8172 Bugfix on 0.2.0.x (??).
8173 - Remove the old v2 directory authority 'lefkada' from the default
8174 list. It has been gone for many months.
8175 - Stop doing unaligned memory access that generated bus errors on
8176 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8177 - Make USR2 log-level switch take effect immediately. Bugfix on
8180 o Minor bugfixes (controller):
8181 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8182 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8185 Changes in version 0.2.1.7-alpha - 2008-11-08
8186 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8187 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8188 a smaller security flaw that might allow an attacker to access local
8189 services, adds better defense against DNS poisoning attacks on exit
8190 relays, further improves hidden service performance, and fixes a
8191 variety of other issues.
8194 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8195 consistently obeyed: if an exit relay refuses a stream because its
8196 exit policy doesn't allow it, we would remember what IP address
8197 the relay said the destination address resolves to, even if it's
8198 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8199 - The "User" and "Group" config options did not clear the
8200 supplementary group entries for the Tor process. The "User" option
8201 is now more robust, and we now set the groups to the specified
8202 user's primary group. The "Group" option is now ignored. For more
8203 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8204 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8205 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8206 - Do not use or believe expired v3 authority certificates. Patch
8207 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8210 - Now NodeFamily and MyFamily config options allow spaces in
8211 identity fingerprints, so it's easier to paste them in.
8212 Suggested by Lucky Green.
8213 - Implement the 0x20 hack to better resist DNS poisoning: set the
8214 case on outgoing DNS requests randomly, and reject responses that do
8215 not match the case correctly. This logic can be disabled with the
8216 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8217 of servers that do not reliably preserve case in replies. See
8218 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8220 - Preserve case in replies to DNSPort requests in order to support
8221 the 0x20 hack for resisting DNS poisoning attacks.
8223 o Hidden service performance improvements:
8224 - When the client launches an introduction circuit, retry with a
8225 new circuit after 30 seconds rather than 60 seconds.
8226 - Launch a second client-side introduction circuit in parallel
8227 after a delay of 15 seconds (based on work by Christian Wilms).
8228 - Hidden services start out building five intro circuits rather
8229 than three, and when the first three finish they publish a service
8230 descriptor using those. Now we publish our service descriptor much
8231 faster after restart.
8234 - Minor fix in the warning messages when you're having problems
8235 bootstrapping; also, be more forgiving of bootstrap problems when
8236 we're still making incremental progress on a given bootstrap phase.
8237 - When we're choosing an exit node for a circuit, and we have
8238 no pending streams, choose a good general exit rather than one that
8239 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8240 - Send a valid END cell back when a client tries to connect to a
8241 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8242 840. Patch from rovv.
8243 - If a broken client asks a non-exit router to connect somewhere,
8244 do not even do the DNS lookup before rejecting the connection.
8245 Fixes another case of bug 619. Patch from rovv.
8246 - Fix another case of assuming, when a specific exit is requested,
8247 that we know more than the user about what hosts it allows.
8248 Fixes another case of bug 752. Patch from rovv.
8249 - Check which hops rendezvous stream cells are associated with to
8250 prevent possible guess-the-streamid injection attacks from
8251 intermediate hops. Fixes another case of bug 446. Based on patch
8253 - Avoid using a negative right-shift when comparing 32-bit
8254 addresses. Possible fix for bug 845 and bug 811.
8255 - Make the assert_circuit_ok() function work correctly on circuits that
8256 have already been marked for close.
8257 - Fix read-off-the-end-of-string error in unit tests when decoding
8258 introduction points.
8259 - Fix uninitialized size field for memory area allocation: may improve
8260 memory performance during directory parsing.
8261 - Treat duplicate certificate fetches as failures, so that we do
8262 not try to re-fetch an expired certificate over and over and over.
8263 - Do not say we're fetching a certificate when we'll in fact skip it
8264 because of a pending download.
8267 Changes in version 0.2.1.6-alpha - 2008-09-30
8268 Tor 0.2.1.6-alpha further improves performance and robustness of
8269 hidden services, starts work on supporting per-country relay selection,
8270 and fixes a variety of smaller issues.
8273 - Implement proposal 121: make it possible to build hidden services
8274 that only certain clients are allowed to connect to. This is
8275 enforced at several points, so that unauthorized clients are unable
8276 to send INTRODUCE cells to the service, or even (depending on the
8277 type of authentication) to learn introduction points. This feature
8278 raises the bar for certain kinds of active attacks against hidden
8279 services. Code by Karsten Loesing.
8280 - Relays now store and serve v2 hidden service descriptors by default,
8281 i.e., the new default value for HidServDirectoryV2 is 1. This is
8282 the last step in proposal 114, which aims to make hidden service
8283 lookups more reliable.
8284 - Start work to allow node restrictions to include country codes. The
8285 syntax to exclude nodes in a country with country code XX is
8286 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8287 refinement to decide what config options should take priority if
8288 you ask to both use a particular node and exclude it.
8289 - Allow ExitNodes list to include IP ranges and country codes, just
8290 like the Exclude*Nodes lists. Patch from Robert Hogan.
8293 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8294 Tor to fail to start if you had it configured to use a bridge
8295 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8296 - When extending a circuit to a hidden service directory to upload a
8297 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8298 requests failed, because the router descriptor had not been
8299 downloaded yet. In these cases, we now wait until the router
8300 descriptor is downloaded, and then retry. Likewise, clients
8301 now skip over a hidden service directory if they don't yet have
8302 its router descriptor, rather than futilely requesting it and
8303 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8305 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8306 we were failing the whole hidden service request when the v0
8307 descriptor fetch fails, even if the v2 fetch is still pending and
8308 might succeed. Similarly, if the last v2 fetch fails, we were
8309 failing the whole hidden service request even if a v0 fetch is
8310 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8311 - DNS replies need to have names matching their requests, but
8312 these names should be in the questions section, not necessarily
8313 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8316 - Update to the "September 1 2008" ip-to-country file.
8317 - Allow ports 465 and 587 in the default exit policy again. We had
8318 rejected them in 0.1.0.15, because back in 2005 they were commonly
8319 misconfigured and ended up as spam targets. We hear they are better
8320 locked down these days.
8321 - Use a lockfile to make sure that two Tor processes are not
8322 simultaneously running with the same datadir.
8323 - Serve the latest v3 networkstatus consensus via the control
8324 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8325 - Better logging about stability/reliability calculations on directory
8327 - Drop the requirement to have an open dir port for storing and
8328 serving v2 hidden service descriptors.
8329 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8330 help debug WFU and MTBF calculations.
8331 - Implement most of Proposal 152: allow specialized servers to permit
8332 single-hop circuits, and clients to use those servers to build
8333 single-hop circuits when using a specialized controller. Patch
8334 from Josh Albrecht. Resolves feature request 768.
8335 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8336 people find host:port too confusing.
8337 - Make TrackHostExit mappings expire a while after their last use, not
8338 after their creation. Patch from Robert Hogan.
8339 - Provide circuit purposes along with circuit events to the controller.
8342 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8344 - Fixed some memory leaks -- some quite frequent, some almost
8345 impossible to trigger -- based on results from Coverity.
8346 - When testing for libevent functions, set the LDFLAGS variable
8347 correctly. Found by Riastradh.
8348 - Fix an assertion bug in parsing policy-related options; possible fix
8350 - Catch and report a few more bootstrapping failure cases when Tor
8351 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8352 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8353 bootstrapping with tunneled directory connections. Bugfix on
8354 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8355 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8356 and we know that server B rejects most-but-not all connections to
8357 port 80, we would previously reject the connection. Now, we assume
8358 the user knows what they were asking for. Fixes bug 752. Bugfix
8359 on 0.0.9rc5. Diagnosed by BarkerJr.
8360 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8361 service directories if they have no advertised dir port. Bugfix
8363 - If we overrun our per-second write limits a little, count this as
8364 having used up our write allocation for the second, and choke
8365 outgoing directory writes. Previously, we had only counted this when
8366 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8367 Bugfix on 0.2.0.x (??).
8368 - Avoid a "0 divided by 0" calculation when calculating router uptime
8369 at directory authorities. Bugfix on 0.2.0.8-alpha.
8370 - Make DNS resolved controller events into "CLOSED", not
8371 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8373 - Fix a bug where an unreachable relay would establish enough
8374 reachability testing circuits to do a bandwidth test -- if
8375 we already have a connection to the middle hop of the testing
8376 circuit, then it could establish the last hop by using the existing
8377 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8378 circuits no longer use entry guards in 0.2.1.3-alpha.
8379 - If we have correct permissions on $datadir, we complain to stdout
8380 and fail to start. But dangerous permissions on
8381 $datadir/cached-status/ would cause us to open a log and complain
8382 there. Now complain to stdout and fail to start in both cases. Fixes
8383 bug 820, reported by seeess.
8384 - Remove the old v2 directory authority 'lefkada' from the default
8385 list. It has been gone for many months.
8387 o Code simplifications and refactoring:
8388 - Revise the connection_new functions so that a more typesafe variant
8389 exists. This will work better with Coverity, and let us find any
8390 actual mistakes we're making here.
8391 - Refactor unit testing logic so that dmalloc can be used sensibly
8392 with unit tests to check for memory leaks.
8393 - Move all hidden-service related fields from connection and circuit
8394 structure to substructures: this way they won't eat so much memory.
8397 Changes in version 0.2.0.31 - 2008-09-03
8398 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8399 a big bug we're seeing where in rare cases traffic from one Tor stream
8400 gets mixed into another stream, and fixes a variety of smaller issues.
8403 - Make sure that two circuits can never exist on the same connection
8404 with the same circuit ID, even if one is marked for close. This
8405 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8406 - Relays now reject risky extend cells: if the extend cell includes
8407 a digest of all zeroes, or asks to extend back to the relay that
8408 sent the extend cell, tear down the circuit. Ideas suggested
8410 - If not enough of our entry guards are available so we add a new
8411 one, we might use the new one even if it overlapped with the
8412 current circuit's exit relay (or its family). Anonymity bugfix
8413 pointed out by rovv.
8416 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8417 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8418 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8419 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8420 - Pick size of default geoip filename string correctly on windows.
8421 Fixes bug 806. Bugfix on 0.2.0.30.
8422 - Make the autoconf script accept the obsolete --with-ssl-dir
8423 option as an alias for the actually-working --with-openssl-dir
8424 option. Fix the help documentation to recommend --with-openssl-dir.
8425 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8426 - When using the TransPort option on OpenBSD, and using the User
8427 option to change UID and drop privileges, make sure to open
8428 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8429 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8430 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8431 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8432 on the client side when connecting to a hidden service. Bugfix
8433 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8434 - When closing an application-side connection because its circuit is
8435 getting torn down, generate the stream event correctly. Bugfix on
8436 0.1.2.x. Anonymous patch.
8439 Changes in version 0.2.1.5-alpha - 2008-08-31
8440 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8441 in a lot of the infrastructure for adding authorization to hidden
8442 services, lays the groundwork for having clients read their load
8443 balancing information out of the networkstatus consensus rather than
8444 the individual router descriptors, addresses two potential anonymity
8445 issues, and fixes a variety of smaller issues.
8448 - Convert many internal address representations to optionally hold
8450 - Generate and accept IPv6 addresses in many protocol elements.
8451 - Make resolver code handle nameservers located at ipv6 addresses.
8452 - Begin implementation of proposal 121 ("Client authorization for
8453 hidden services"): configure hidden services with client
8454 authorization, publish descriptors for them, and configure
8455 authorization data for hidden services at clients. The next
8456 step is to actually access hidden services that perform client
8458 - More progress toward proposal 141: Network status consensus
8459 documents and votes now contain bandwidth information for each
8460 router and a summary of that router's exit policy. Eventually this
8461 will be used by clients so that they do not have to download every
8462 known descriptor before building circuits.
8464 o Major bugfixes (on 0.2.0.x and before):
8465 - When sending CREATED cells back for a given circuit, use a 64-bit
8466 connection ID to find the right connection, rather than an addr:port
8467 combination. Now that we can have multiple OR connections between
8468 the same ORs, it is no longer possible to use addr:port to uniquely
8469 identify a connection.
8470 - Relays now reject risky extend cells: if the extend cell includes
8471 a digest of all zeroes, or asks to extend back to the relay that
8472 sent the extend cell, tear down the circuit. Ideas suggested
8474 - If not enough of our entry guards are available so we add a new
8475 one, we might use the new one even if it overlapped with the
8476 current circuit's exit relay (or its family). Anonymity bugfix
8477 pointed out by rovv.
8480 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8481 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8482 - When using the TransPort option on OpenBSD, and using the User
8483 option to change UID and drop privileges, make sure to open /dev/pf
8484 before dropping privileges. Fixes bug 782. Patch from Christopher
8485 Davis. Bugfix on 0.1.2.1-alpha.
8486 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8487 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8488 - Add a missing safe_str() call for a debug log message.
8489 - Use 64 bits instead of 32 bits for connection identifiers used with
8490 the controller protocol, to greatly reduce risk of identifier reuse.
8491 - Make the autoconf script accept the obsolete --with-ssl-dir
8492 option as an alias for the actually-working --with-openssl-dir
8493 option. Fix the help documentation to recommend --with-openssl-dir.
8494 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8497 - Rate-limit too-many-sockets messages: when they happen, they happen
8498 a lot. Resolves bug 748.
8499 - Resist DNS poisoning a little better by making sure that names in
8500 answer sections match.
8501 - Print the SOCKS5 error message string as well as the error code
8502 when a tor-resolve request fails. Patch from Jacob.
8505 Changes in version 0.2.1.4-alpha - 2008-08-04
8506 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8509 - The address part of exit policies was not correctly written
8510 to router descriptors. This generated router descriptors that failed
8511 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8513 - Tor triggered a false assert when extending a circuit to a relay
8514 but we already have a connection open to that relay. Noticed by
8515 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8518 - Fix a hidden service logging bug: in some edge cases, the router
8519 descriptor of a previously picked introduction point becomes
8520 obsolete and we need to give up on it rather than continually
8521 complaining that it has become obsolete. Observed by xiando. Bugfix
8525 - Take out the TestVia config option, since it was a workaround for
8526 a bug that was fixed in Tor 0.1.1.21.
8529 Changes in version 0.2.1.3-alpha - 2008-08-03
8530 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8531 infinite-length circuit attacks (see proposal 110); fixes a bug that
8532 might cause exit relays to corrupt streams they send back; allows
8533 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8534 ExcludeExitNodes config options; and fixes a big pile of bugs.
8536 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8537 - Send a bootstrap problem "warn" event on the first problem if the
8538 reason is NO_ROUTE (that is, our network is down).
8541 - Implement most of proposal 110: The first K cells to be sent
8542 along a circuit are marked as special "early" cells; only K "early"
8543 cells will be allowed. Once this code is universal, we can block
8544 certain kinds of DOS attack by requiring that EXTEND commands must
8545 be sent using an "early" cell.
8548 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8549 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8550 on the client side when connecting to a hidden service. Bugfix
8551 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8552 - Ensure that two circuits can never exist on the same connection
8553 with the same circuit ID, even if one is marked for close. This
8554 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8557 - When relays do their initial bandwidth measurement, don't limit
8558 to just our entry guards for the test circuits. Otherwise we tend
8559 to have multiple test circuits going through a single entry guard,
8560 which makes our bandwidth test less accurate. Fixes part of bug 654;
8561 patch contributed by Josh Albrecht.
8562 - Add an ExcludeExitNodes option so users can list a set of nodes
8563 that should be be excluded from the exit node position, but
8564 allowed elsewhere. Implements proposal 151.
8565 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8566 ExcludeNodes and ExcludeExitNodes lists.
8567 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8568 be more efficient. Formerly it was quadratic in the number of
8569 servers; now it should be linear. Fixes bug 509.
8570 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8571 and n_conn_id_digest fields into a separate structure that's
8572 only needed when the circuit has not yet attached to an n_conn.
8575 - Change the contrib/tor.logrotate script so it makes the new
8576 logs as "_tor:_tor" rather than the default, which is generally
8577 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8578 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8579 warnings (occasionally), but it can also cause the compiler to
8580 eliminate error-checking code. Suggested by Peter Gutmann.
8581 - When a hidden service is giving up on an introduction point candidate
8582 that was not included in the last published rendezvous descriptor,
8583 don't reschedule publication of the next descriptor. Fixes bug 763.
8585 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8586 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8587 and nobody claims to be using them. Fixes bug 754. Bugfix on
8588 0.1.0.1-rc. Patch from Christian Wilms.
8589 - Fix a small alignment and memory-wasting bug on buffer chunks.
8592 o Minor bugfixes (controller):
8593 - When closing an application-side connection because its circuit
8594 is getting torn down, generate the stream event correctly.
8595 Bugfix on 0.1.2.x. Anonymous patch.
8598 - Remove all backward-compatibility code to support relays running
8599 versions of Tor so old that they no longer work at all on the
8603 Changes in version 0.2.0.30 - 2008-07-15
8605 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8606 warnings (occasionally), but it can also cause the compiler to
8607 eliminate error-checking code. Suggested by Peter Gutmann.
8610 Changes in version 0.2.0.29-rc - 2008-07-08
8611 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8612 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8615 - If you have more than one bridge but don't know their keys,
8616 you would only launch a request for the descriptor of the first one
8617 on your list. (Tor considered launching requests for the others, but
8618 found that it already had a connection on the way for $0000...0000
8619 so it didn't open another.) Bugfix on 0.2.0.x.
8620 - If you have more than one bridge but don't know their keys, and the
8621 connection to one of the bridges failed, you would cancel all
8622 pending bridge connections. (After all, they all have the same
8623 digest.) Bugfix on 0.2.0.x.
8624 - When a hidden service was trying to establish an introduction point,
8625 and Tor had built circuits preemptively for such purposes, we
8626 were ignoring all the preemptive circuits and launching a new one
8627 instead. Bugfix on 0.2.0.14-alpha.
8628 - When a hidden service was trying to establish an introduction point,
8629 and Tor *did* manage to reuse one of the preemptively built
8630 circuits, it didn't correctly remember which one it used,
8631 so it asked for another one soon after, until there were no
8632 more preemptive circuits, at which point it launched one from
8633 scratch. Bugfix on 0.0.9.x.
8634 - Make directory servers include the X-Your-Address-Is: http header in
8635 their responses even for begin_dir conns. Now clients who only
8636 ever use begin_dir connections still have a way to learn their IP
8637 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8640 - Fix a macro/CPP interaction that was confusing some compilers:
8641 some GCCs don't like #if/#endif pairs inside macro arguments.
8643 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8644 Fixes bug 704; fix from Steven Murdoch.
8645 - When opening /dev/null in finish_daemonize(), do not pass the
8646 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8647 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8648 - Correctly detect transparent proxy support on Linux hosts that
8649 require in.h to be included before netfilter_ipv4.h. Patch
8651 - Disallow session resumption attempts during the renegotiation
8652 stage of the v2 handshake protocol. Clients should never be trying
8653 session resumption at this point, but apparently some did, in
8654 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8655 found by Geoff Goodell.
8658 Changes in version 0.2.1.2-alpha - 2008-06-20
8659 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8660 make it easier to set up your own private Tor network; fixes several
8661 big bugs with using more than one bridge relay; fixes a big bug with
8662 offering hidden services quickly after Tor starts; and uses a better
8663 API for reporting potential bootstrapping problems to the controller.
8666 - New TestingTorNetwork config option to allow adjustment of
8667 previously constant values that, while reasonable, could slow
8668 bootstrapping. Implements proposal 135. Patch from Karsten.
8671 - If you have more than one bridge but don't know their digests,
8672 you would only learn a request for the descriptor of the first one
8673 on your list. (Tor considered launching requests for the others, but
8674 found that it already had a connection on the way for $0000...0000
8675 so it didn't open another.) Bugfix on 0.2.0.x.
8676 - If you have more than one bridge but don't know their digests,
8677 and the connection to one of the bridges failed, you would cancel
8678 all pending bridge connections. (After all, they all have the
8679 same digest.) Bugfix on 0.2.0.x.
8680 - When establishing a hidden service, introduction points that
8681 originate from cannibalized circuits are completely ignored and not
8682 included in rendezvous service descriptors. This might be another
8683 reason for delay in making a hidden service available. Bugfix
8684 from long ago (0.0.9.x?)
8687 - Allow OpenSSL to use dynamic locks if it wants.
8688 - When building a consensus, do not include routers that are down.
8689 This will cut down 30% to 40% on consensus size. Implements
8691 - In directory authorities' approved-routers files, allow
8692 fingerprints with or without space.
8693 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8694 controller can query our current bootstrap state in case it attaches
8695 partway through and wants to catch up.
8696 - Send an initial "Starting" bootstrap status event, so we have a
8697 state to start out in.
8700 - Asking for a conditional consensus at .../consensus/<fingerprints>
8701 would crash a dirserver if it did not already have a
8702 consensus. Bugfix on 0.2.1.1-alpha.
8703 - Clean up some macro/CPP interactions: some GCC versions don't like
8704 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8707 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8708 - Directory authorities shouldn't complain about bootstrapping
8709 problems just because they do a lot of reachability testing and
8710 some of the connection attempts fail.
8711 - Start sending "count" and "recommendation" key/value pairs in
8712 bootstrap problem status events, so the controller can hear about
8713 problems even before Tor decides they're worth reporting for sure.
8714 - If you're using bridges, generate "bootstrap problem" warnings
8715 as soon as you run out of working bridges, rather than waiting
8716 for ten failures -- which will never happen if you have less than
8718 - If we close our OR connection because there's been a circuit
8719 pending on it for too long, we were telling our bootstrap status
8720 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8723 Changes in version 0.2.1.1-alpha - 2008-06-13
8724 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8725 were making the Tor process bloat especially on Linux; makes our TLS
8726 handshake blend in better; sends "bootstrap phase" status events to
8727 the controller, so it can keep the user informed of progress (and
8728 problems) fetching directory information and establishing circuits;
8729 and adds a variety of smaller features.
8732 - More work on making our TLS handshake blend in: modify the list
8733 of ciphers advertised by OpenSSL in client mode to even more
8734 closely resemble a common web browser. We cheat a little so that
8735 we can advertise ciphers that the locally installed OpenSSL doesn't
8737 - Start sending "bootstrap phase" status events to the controller,
8738 so it can keep the user informed of progress fetching directory
8739 information and establishing circuits. Also inform the controller
8740 if we think we're stuck at a particular bootstrap phase. Implements
8742 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8743 cross-platform entropy collection again. We used to use it, then
8744 stopped using it because of a bug that could crash systems that
8745 called RAND_poll when they had a lot of fds open. It looks like the
8746 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8747 at startup, and to call RAND_poll() when we reseed later only if
8748 we have a non-buggy OpenSSL version.
8751 - When we choose to abandon a new entry guard because we think our
8752 older ones might be better, close any circuits pending on that
8753 new entry guard connection. This fix should make us recover much
8754 faster when our network is down and then comes back. Bugfix on
8755 0.1.2.8-beta; found by lodger.
8757 o Memory fixes and improvements:
8758 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8759 to avoid unused RAM in buffer chunks and memory pools.
8760 - Speed up parsing and cut down on memory fragmentation by using
8761 stack-style allocations for parsing directory objects. Previously,
8762 this accounted for over 40% of allocations from within Tor's code
8763 on a typical directory cache.
8764 - Use a Bloom filter rather than a digest-based set to track which
8765 descriptors we need to keep around when we're cleaning out old
8766 router descriptors. This speeds up the computation significantly,
8767 and may reduce fragmentation.
8768 - Reduce the default smartlist size from 32 to 16; it turns out that
8769 most smartlists hold around 8-12 elements tops.
8770 - Make dumpstats() log the fullness and size of openssl-internal
8772 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8773 patch to their OpenSSL, turn it on to save memory on servers. This
8774 patch will (with any luck) get included in a mainline distribution
8776 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8777 compress cells, which are basically all encrypted, compressed,
8781 - Stop reloading the router list from disk for no reason when we
8782 run out of reachable directory mirrors. Once upon a time reloading
8783 it would set the 'is_running' flag back to 1 for them. It hasn't
8784 done that for a long time.
8785 - In very rare situations new hidden service descriptors were
8786 published earlier than 30 seconds after the last change to the
8787 service. (We currently think that a hidden service descriptor
8788 that's been stable for 30 seconds is worth publishing.)
8791 - Allow separate log levels to be configured for different logging
8792 domains. For example, this allows one to log all notices, warnings,
8793 or errors, plus all memory management messages of level debug or
8794 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
8795 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8796 and stop using a warning that had become unfixably verbose under
8798 - New --hush command-line option similar to --quiet. While --quiet
8799 disables all logging to the console on startup, --hush limits the
8800 output to messages of warning and error severity.
8801 - Servers support a new URL scheme for consensus downloads that
8802 allows the client to specify which authorities are trusted.
8803 The server then only sends the consensus if the client will trust
8804 it. Otherwise a 404 error is sent back. Clients use this
8805 new scheme when the server supports it (meaning it's running
8806 0.2.1.1-alpha or later). Implements proposal 134.
8807 - New configure/torrc options (--enable-geoip-stats,
8808 DirRecordUsageByCountry) to record how many IPs we've served
8809 directory info to in each country code, how many status documents
8810 total we've sent to each country code, and what share of the total
8811 directory requests we should expect to see.
8812 - Use the TLS1 hostname extension to more closely resemble browser
8814 - Lots of new unit tests.
8815 - Add a macro to implement the common pattern of iterating through
8816 two parallel lists in lockstep.
8819 Changes in version 0.2.0.28-rc - 2008-06-13
8820 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
8821 performance bug, and fixes a bunch of smaller bugs.
8824 - Fix a bug where, when we were choosing the 'end stream reason' to
8825 put in our relay end cell that we send to the exit relay, Tor
8826 clients on Windows were sometimes sending the wrong 'reason'. The
8827 anonymity problem is that exit relays may be able to guess whether
8828 the client is running Windows, thus helping partition the anonymity
8829 set. Down the road we should stop sending reasons to exit relays,
8830 or otherwise prevent future versions of this bug.
8833 - While setting up a hidden service, some valid introduction circuits
8834 were overlooked and abandoned. This might be the reason for
8835 the long delay in making a hidden service available. Bugfix on
8839 - Update to the "June 9 2008" ip-to-country file.
8840 - Run 'make test' as part of 'make dist', so we stop releasing so
8841 many development snapshots that fail their unit tests.
8844 - When we're checking if we have enough dir info for each relay
8845 to begin establishing circuits, make sure that we actually have
8846 the descriptor listed in the consensus, not just any descriptor.
8848 - Bridge relays no longer print "xx=0" in their extrainfo document
8849 for every single country code in the geoip db. Bugfix on
8851 - Only warn when we fail to load the geoip file if we were planning to
8852 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
8853 - If we change our MaxAdvertisedBandwidth and then reload torrc,
8854 Tor won't realize it should publish a new relay descriptor. Fixes
8855 bug 688, reported by mfr. Bugfix on 0.1.2.x.
8856 - When we haven't had any application requests lately, don't bother
8857 logging that we have expired a bunch of descriptors. Bugfix
8859 - Make relay cells written on a connection count as non-padding when
8860 tracking how long a connection has been in use. Bugfix on
8861 0.2.0.1-alpha. Spotted by lodger.
8862 - Fix unit tests in 0.2.0.27-rc.
8863 - Fix compile on Windows.
8866 Changes in version 0.2.0.27-rc - 2008-06-03
8867 Tor 0.2.0.27-rc adds a few features we left out of the earlier
8868 release candidates. In particular, we now include an IP-to-country
8869 GeoIP database, so controllers can easily look up what country a
8870 given relay is in, and so bridge relays can give us some sanitized
8871 summaries about which countries are making use of bridges. (See proposal
8872 126-geoip-fetching.txt for details.)
8875 - Include an IP-to-country GeoIP file in the tarball, so bridge
8876 relays can report sanitized summaries of the usage they're seeing.
8879 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
8880 Robert Hogan. Fixes the first part of bug 681.
8881 - Make bridge authorities never serve extrainfo docs.
8882 - Add support to detect Libevent versions in the 1.4.x series
8884 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
8885 - Include a new contrib/tor-exit-notice.html file that exit relay
8886 operators can put on their website to help reduce abuse queries.
8889 - When tunneling an encrypted directory connection, and its first
8890 circuit fails, do not leave it unattached and ask the controller
8891 to deal. Fixes the second part of bug 681.
8892 - Make bridge authorities correctly expire old extrainfo documents
8896 Changes in version 0.2.0.26-rc - 2008-05-13
8897 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
8898 in Debian's OpenSSL packages. All users running any 0.2.0.x version
8899 should upgrade, whether they're running Debian or not.
8901 o Major security fixes:
8902 - Use new V3 directory authority keys on the tor26, gabelmoo, and
8903 moria1 V3 directory authorities. The old keys were generated with
8904 a vulnerable version of Debian's OpenSSL package, and must be
8905 considered compromised. Other authorities' keys were not generated
8906 with an affected version of OpenSSL.
8909 - List authority signatures as "unrecognized" based on DirServer
8910 lines, not on cert cache. Bugfix on 0.2.0.x.
8913 - Add a new V3AuthUseLegacyKey option to make it easier for
8914 authorities to change their identity keys if they have to.
8917 Changes in version 0.2.0.25-rc - 2008-04-23
8918 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
8921 - Remember to initialize threading before initializing logging.
8922 Otherwise, many BSD-family implementations will crash hard on
8923 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
8926 - Authorities correctly free policies on bad servers on
8927 exit. Fixes bug 672. Bugfix on 0.2.0.x.
8930 Changes in version 0.2.0.24-rc - 2008-04-22
8931 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
8932 v3 directory authority, makes relays with dynamic IP addresses and no
8933 DirPort notice more quickly when their IP address changes, fixes a few
8934 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
8936 o New directory authorities:
8937 - Take lefkada out of the list of v3 directory authorities, since
8938 it has been down for months.
8939 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
8943 - Detect address changes more quickly on non-directory mirror
8944 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
8946 o Minor features (security):
8947 - Reject requests for reverse-dns lookup of names that are in
8948 a private address space. Patch from lodger.
8949 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
8952 o Minor bugfixes (crashes):
8953 - Avoid a rare assert that can trigger when Tor doesn't have much
8954 directory information yet and it tries to fetch a v2 hidden
8955 service descriptor. Fixes bug 651, reported by nwf.
8956 - Initialize log mutex before initializing dmalloc. Otherwise,
8957 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
8958 - Use recursive pthread mutexes in order to avoid deadlock when
8959 logging debug-level messages to a controller. Bug spotted by nwf,
8960 bugfix on 0.2.0.16-alpha.
8962 o Minor bugfixes (resource management):
8963 - Keep address policies from leaking memory: start their refcount
8964 at 1, not 2. Bugfix on 0.2.0.16-alpha.
8965 - Free authority certificates on exit, so they don't look like memory
8966 leaks. Bugfix on 0.2.0.19-alpha.
8967 - Free static hashtables for policy maps and for TLS connections on
8968 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
8969 - Avoid allocating extra space when computing consensuses on 64-bit
8970 platforms. Bug spotted by aakova.
8972 o Minor bugfixes (misc):
8973 - Do not read the configuration file when we've only been told to
8974 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
8975 based on patch from Sebastian Hahn.
8976 - Exit relays that are used as a client can now reach themselves
8977 using the .exit notation, rather than just launching an infinite
8978 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
8979 - When attempting to open a logfile fails, tell us why.
8980 - Fix a dumb bug that was preventing us from knowing that we should
8981 preemptively build circuits to handle expected directory requests.
8982 Fixes bug 660. Bugfix on 0.1.2.x.
8983 - Warn less verbosely about clock skew from netinfo cells from
8984 untrusted sources. Fixes bug 663.
8985 - Make controller stream events for DNS requests more consistent,
8986 by adding "new stream" events for DNS requests, and removing
8987 spurious "stream closed" events" for cached reverse resolves.
8988 Patch from mwenge. Fixes bug 646.
8989 - Correctly notify one-hop connections when a circuit build has
8990 failed. Possible fix for bug 669. Found by lodger.
8993 Changes in version 0.2.0.23-rc - 2008-03-24
8994 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
8995 makes bootstrapping faster if the first directory mirror you contact
8996 is down. The bundles also include the new Vidalia 0.1.2 release.
8999 - When a tunneled directory request is made to a directory server
9000 that's down, notice after 30 seconds rather than 120 seconds. Also,
9001 fail any begindir streams that are pending on it, so they can
9002 retry elsewhere. This was causing multi-minute delays on bootstrap.
9005 Changes in version 0.2.0.22-rc - 2008-03-18
9006 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9007 enables encrypted directory connections by default for non-relays, fixes
9008 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9009 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9012 - Enable encrypted directory connections by default for non-relays,
9013 so censor tools that block Tor directory connections based on their
9014 plaintext patterns will no longer work. This means Tor works in
9015 certain censored countries by default again.
9018 - Make sure servers always request certificates from clients during
9019 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9020 - Do not enter a CPU-eating loop when a connection is closed in
9021 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9022 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9023 - Fix assertion failure that could occur when a blocked circuit
9024 became unblocked, and it had pending client DNS requests. Bugfix
9025 on 0.2.0.1-alpha. Fixes bug 632.
9027 o Minor bugfixes (on 0.1.2.x):
9028 - Generate "STATUS_SERVER" events rather than misspelled
9029 "STATUS_SEVER" events. Caught by mwenge.
9030 - When counting the number of bytes written on a TLS connection,
9031 look at the BIO actually used for writing to the network, not
9032 at the BIO used (sometimes) to buffer data for the network.
9033 Looking at different BIOs could result in write counts on the
9034 order of ULONG_MAX. Fixes bug 614.
9035 - On Windows, correctly detect errors when listing the contents of
9036 a directory. Fix from lodger.
9038 o Minor bugfixes (on 0.2.0.x):
9039 - Downgrade "sslv3 alert handshake failure" message to INFO.
9040 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9041 left BandwidthRate and BandwidthBurst at the default, we would be
9042 silently limited by those defaults. Now raise them to match the
9043 RelayBandwidth* values.
9044 - Fix the SVK version detection logic to work correctly on a branch.
9045 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9046 CPUs. Fixes bug 625.
9047 - Logging functions now check that the passed severity is sane.
9048 - Use proper log levels in the testsuite call of
9049 get_interface_address6().
9050 - When using a nonstandard malloc, do not use the platform values for
9051 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9052 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9054 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9055 - Avoid double-marked-for-close warning when certain kinds of invalid
9056 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9057 for bug 617. Bugfix on 0.2.0.1-alpha.
9058 - Make sure that the "NULL-means-reject *:*" convention is followed by
9059 all the policy manipulation functions, avoiding some possible crash
9060 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9061 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9062 actually works, and doesn't warn about every single reverse lookup.
9063 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9066 - Only log guard node status when guard node status has changed.
9067 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9068 make "INFO" 75% less verbose.
9071 Changes in version 0.2.0.21-rc - 2008-03-02
9072 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9073 makes Tor work well with Vidalia again, fixes a rare assert bug,
9074 and fixes a pair of more minor bugs. The bundles also include Vidalia
9075 0.1.0 and Torbutton 1.1.16.
9078 - The control port should declare that it requires password auth
9079 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9080 bugfix on 0.2.0.20-rc. Fixes bug 615.
9081 - Downgrade assert in connection_buckets_decrement() to a log message.
9082 This may help us solve bug 614, and in any case will make its
9083 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9084 - We were sometimes miscounting the number of bytes read from the
9085 network, causing our rate limiting to not be followed exactly.
9086 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9089 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9090 OpenSSL versions should have been working fine. Diagnosis and patch
9091 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9092 Bugfix on 0.2.0.20-rc.
9095 Changes in version 0.2.0.20-rc - 2008-02-24
9096 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9097 makes more progress towards normalizing Tor's TLS handshake, makes
9098 hidden services work better again, helps relays bootstrap if they don't
9099 know their IP address, adds optional support for linking in openbsd's
9100 allocator or tcmalloc, allows really fast relays to scale past 15000
9101 sockets, and fixes a bunch of minor bugs reported by Veracode.
9104 - Enable the revised TLS handshake based on the one designed by
9105 Steven Murdoch in proposal 124, as revised in proposal 130. It
9106 includes version negotiation for OR connections as described in
9107 proposal 105. The new handshake is meant to be harder for censors
9108 to fingerprint, and it adds the ability to detect certain kinds of
9109 man-in-the-middle traffic analysis attacks. The version negotiation
9110 feature will allow us to improve Tor's link protocol more safely
9112 - Choose which bridge to use proportional to its advertised bandwidth,
9113 rather than uniformly at random. This should speed up Tor for
9114 bridge users. Also do this for people who set StrictEntryNodes.
9115 - When a TrackHostExits-chosen exit fails too many times in a row,
9116 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9119 - Resolved problems with (re-)fetching hidden service descriptors.
9120 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9122 - If we only ever used Tor for hidden service lookups or posts, we
9123 would stop building circuits and start refusing connections after
9124 24 hours, since we falsely believed that Tor was dormant. Reported
9125 by nwf; bugfix on 0.1.2.x.
9126 - Servers that don't know their own IP address should go to the
9127 authorities for their first directory fetch, even if their DirPort
9128 is off or if they don't know they're reachable yet. This will help
9129 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9130 - When counting the number of open sockets, count not only the number
9131 of sockets we have received from the socket() call, but also
9132 the number we've gotten from accept() and socketpair(). This bug
9133 made us fail to count all sockets that we were using for incoming
9134 connections. Bugfix on 0.2.0.x.
9135 - Fix code used to find strings within buffers, when those strings
9136 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9137 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9138 - Add a new __HashedControlSessionPassword option for controllers
9139 to use for one-off session password hashes that shouldn't get
9140 saved to disk by SAVECONF --- Vidalia users were accumulating a
9141 pile of HashedControlPassword lines in their torrc files, one for
9142 each time they had restarted Tor and then clicked Save. Make Tor
9143 automatically convert "HashedControlPassword" to this new option but
9144 only when it's given on the command line. Partial fix for bug 586.
9146 o Minor features (performance):
9147 - Tune parameters for cell pool allocation to minimize amount of
9149 - Add OpenBSD malloc code from phk as an optional malloc
9150 replacement on Linux: some glibc libraries do very poorly
9151 with Tor's memory allocation patterns. Pass
9152 --enable-openbsd-malloc to get the replacement malloc code.
9153 - Add a --with-tcmalloc option to the configure script to link
9154 against tcmalloc (if present). Does not yet search for
9155 non-system include paths.
9156 - Stop imposing an arbitrary maximum on the number of file descriptors
9157 used for busy servers. Bug reported by Olaf Selke; patch from
9160 o Minor features (other):
9161 - When SafeLogging is disabled, log addresses along with all TLS
9163 - When building with --enable-gcc-warnings, check for whether Apple's
9164 warning "-Wshorten-64-to-32" is available.
9165 - Add a --passphrase-fd argument to the tor-gencert command for
9168 o Minor bugfixes (memory leaks and code problems):
9169 - We were leaking a file descriptor if Tor started with a zero-length
9170 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9171 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9173 - We were comparing the raw BridgePassword entry with a base64'ed
9174 version of it, when handling a "/tor/networkstatus-bridges"
9175 directory request. Now compare correctly. Noticed by Veracode.
9176 - Recover from bad tracked-since value in MTBF-history file.
9178 - Alter the code that tries to recover from unhandled write
9179 errors, to not try to flush onto a socket that's given us
9180 unhandled errors. Bugfix on 0.1.2.x.
9181 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9182 tup. Bugfix on 0.2.0.3-alpha.
9184 o Minor bugfixes (other):
9185 - If we have an extra-info document for our server, always make
9186 it available on the control port, even if we haven't gotten
9187 a copy of it from an authority yet. Patch from mwenge.
9188 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9189 - Directory mirrors no longer include a guess at the client's IP
9190 address if the connection appears to be coming from the same /24
9191 network; it was producing too many wrong guesses.
9192 - Make the new hidden service code respect the SafeLogging setting.
9193 Bugfix on 0.2.0.x. Patch from Karsten.
9194 - When starting as an authority, do not overwrite all certificates
9195 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9196 - If we're trying to flush the last bytes on a connection (for
9197 example, when answering a directory request), reset the
9198 time-to-give-up timeout every time we manage to write something
9199 on the socket. Bugfix on 0.1.2.x.
9200 - Change the behavior of "getinfo status/good-server-descriptor"
9201 so it doesn't return failure when any authority disappears.
9202 - Even though the man page said that "TrackHostExits ." should
9203 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9204 - Report TLS "zero return" case as a "clean close" and "IO error"
9205 as a "close". Stop calling closes "unexpected closes": existing
9206 Tors don't use SSL_close(), so having a connection close without
9207 the TLS shutdown handshake is hardly unexpected.
9208 - Send NAMESERVER_STATUS messages for a single failed nameserver
9211 o Code simplifications and refactoring:
9212 - Remove the tor_strpartition function: its logic was confused,
9213 and it was only used for one thing that could be implemented far
9217 Changes in version 0.2.0.19-alpha - 2008-02-09
9218 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9219 handshake, makes path selection for relays more secure and IP address
9220 guessing more robust, and generally fixes a lot of bugs in preparation
9221 for calling the 0.2.0 branch stable.
9224 - Do not include recognizeable strings in the commonname part of
9225 Tor's x509 certificates.
9228 - If we're a relay, avoid picking ourselves as an introduction point,
9229 a rendezvous point, or as the final hop for internal circuits. Bug
9230 reported by taranis and lodger. Bugfix on 0.1.2.x.
9231 - Patch from "Andrew S. Lists" to catch when we contact a directory
9232 mirror at IP address X and he says we look like we're coming from
9233 IP address X. Bugfix on 0.1.2.x.
9235 o Minor features (security):
9236 - Be more paranoid about overwriting sensitive memory on free(),
9237 as a defensive programming tactic to ensure forward secrecy.
9239 o Minor features (directory authority):
9240 - Actually validate the options passed to AuthDirReject,
9241 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9242 - Reject router descriptors with out-of-range bandwidthcapacity or
9243 bandwidthburst values.
9245 o Minor features (controller):
9246 - Reject controller commands over 1MB in length. This keeps rogue
9247 processes from running us out of memory.
9249 o Minor features (misc):
9250 - Give more descriptive well-formedness errors for out-of-range
9251 hidden service descriptor/protocol versions.
9252 - Make memory debugging information describe more about history
9253 of cell allocation, so we can help reduce our memory use.
9255 o Deprecated features (controller):
9256 - The status/version/num-versioning and status/version/num-concurring
9257 GETINFO options are no longer useful in the v3 directory protocol:
9258 treat them as deprecated, and warn when they're used.
9261 - When our consensus networkstatus has been expired for a while, stop
9262 being willing to build circuits using it. Fixes bug 401. Bugfix
9264 - Directory caches now fetch certificates from all authorities
9265 listed in a networkstatus consensus, even when they do not
9266 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9267 - When connecting to a bridge without specifying its key, insert
9268 the connection into the identity-to-connection map as soon as
9269 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9270 - Detect versions of OS X where malloc_good_size() is present in the
9271 library but never actually declared. Resolves bug 587. Bugfix
9273 - Stop incorrectly truncating zlib responses to directory authority
9274 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9275 - Stop recommending that every server operator send mail to tor-ops.
9276 Resolves bug 597. Bugfix on 0.1.2.x.
9277 - Don't trigger an assert if we start a directory authority with a
9278 private IP address (like 127.0.0.1).
9279 - Avoid possible failures when generating a directory with routers
9280 with over-long versions strings, or too many flags set. Bugfix
9282 - If an attempt to launch a DNS resolve request over the control
9283 port fails because we have overrun the limit on the number of
9284 connections, tell the controller that the request has failed.
9285 - Avoid using too little bandwidth when our clock skips a few
9286 seconds. Bugfix on 0.1.2.x.
9287 - Fix shell error when warning about missing packages in configure
9288 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9289 - Do not become confused when receiving a spurious VERSIONS-like
9290 cell from a confused v1 client. Bugfix on 0.2.0.x.
9291 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9292 introduction points for a hidden service have failed. Patch from
9293 Karsten Loesing. Bugfix on 0.2.0.x.
9295 o Code simplifications and refactoring:
9296 - Remove some needless generality from cpuworker code, for improved
9298 - Stop overloading the circuit_t.onionskin field for both "onionskin
9299 from a CREATE cell that we are waiting for a cpuworker to be
9300 assigned" and "onionskin from an EXTEND cell that we are going to
9301 send to an OR as soon as we are connected". Might help with bug 600.
9302 - Add an in-place version of aes_crypt() so that we can avoid doing a
9303 needless memcpy() call on each cell payload.
9306 Changes in version 0.2.0.18-alpha - 2008-01-25
9307 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9308 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9309 that can warn or reject connections to ports generally associated with
9310 vulnerable-plaintext protocols.
9312 o New directory authorities:
9313 - Set up dannenberg (run by CCC) as the sixth v3 directory
9317 - Fix a major memory leak when attempting to use the v2 TLS
9318 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9319 - We accidentally enabled the under-development v2 TLS handshake
9320 code, which was causing log entries like "TLS error while
9321 renegotiating handshake". Disable it again. Resolves bug 590.
9322 - We were computing the wrong Content-Length: header for directory
9323 responses that need to be compressed on the fly, causing clients
9324 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9328 - Avoid going directly to the directory authorities even if you're a
9329 relay, if you haven't found yourself reachable yet or if you've
9330 decided not to advertise your dirport yet. Addresses bug 556.
9331 - If we've gone 12 hours since our last bandwidth check, and we
9332 estimate we have less than 50KB bandwidth capacity but we could
9333 handle more, do another bandwidth test.
9334 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9335 Tor can warn and/or refuse connections to ports commonly used with
9336 vulnerable-plaintext protocols. Currently we warn on ports 23,
9337 109, 110, and 143, but we don't reject any.
9340 - When we setconf ClientOnly to 1, close any current OR and Dir
9341 listeners. Reported by mwenge.
9342 - When we get a consensus that's been signed by more people than
9343 we expect, don't log about it; it's not a big deal. Reported
9347 - Don't answer "/tor/networkstatus-bridges" directory requests if
9348 the request isn't encrypted.
9349 - Make "ClientOnly 1" config option disable directory ports too.
9350 - Patches from Karsten Loesing to make v2 hidden services more
9351 robust: work even when there aren't enough HSDir relays available;
9352 retry when a v2 rend desc fetch fails; but don't retry if we
9353 already have a usable v0 rend desc.
9356 Changes in version 0.2.0.17-alpha - 2008-01-17
9357 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9360 - Make the tor-gencert man page get included correctly in the tarball.
9363 Changes in version 0.2.0.16-alpha - 2008-01-17
9364 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9365 Loesing, and generally cleans up a lot of features and minor bugs.
9367 o New directory authorities:
9368 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9371 o Major performance improvements:
9372 - Switch our old ring buffer implementation for one more like that
9373 used by free Unix kernels. The wasted space in a buffer with 1mb
9374 of data will now be more like 8k than 1mb. The new implementation
9375 also avoids realloc();realloc(); patterns that can contribute to
9376 memory fragmentation.
9379 - Configuration files now accept C-style strings as values. This
9380 helps encode characters not allowed in the current configuration
9381 file format, such as newline or #. Addresses bug 557.
9382 - Although we fixed bug 539 (where servers would send HTTP status 503
9383 responses _and_ send a body too), there are still servers out
9384 there that haven't upgraded. Therefore, make clients parse such
9385 bodies when they receive them.
9386 - When we're not serving v2 directory information, there is no reason
9387 to actually keep any around. Remove the obsolete files and directory
9388 on startup if they are very old and we aren't going to serve them.
9390 o Minor performance improvements:
9391 - Reference-count and share copies of address policy entries; only 5%
9392 of them were actually distinct.
9393 - Never walk through the list of logs if we know that no log is
9394 interested in a given message.
9397 - When an authority has not signed a consensus, do not try to
9398 download a nonexistent "certificate with key 00000000". Bugfix
9399 on 0.2.0.x. Fixes bug 569.
9400 - Fix a rare assert error when we're closing one of our threads:
9401 use a mutex to protect the list of logs, so we never write to the
9402 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9403 bug 575, which is kind of the revenge of bug 222.
9404 - Patch from Karsten Loesing to complain less at both the client
9405 and the relay when a relay used to have the HSDir flag but doesn't
9406 anymore, and we try to upload a hidden service descriptor.
9407 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9409 - Do not try to download missing certificates until we have tried
9410 to check our fallback consensus. Fixes bug 583.
9411 - Make bridges round reported GeoIP stats info up to the nearest
9412 estimate, not down. Now we can distinguish between "0 people from
9413 this country" and "1 person from this country".
9414 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9415 - Avoid possible segfault if key generation fails in
9416 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9417 - Avoid segfault in the case where a badly behaved v2 versioning
9418 directory sends a signed networkstatus with missing client-versions.
9420 - Avoid segfaults on certain complex invocations of
9421 router_get_by_hexdigest(). Bugfix on 0.1.2.
9422 - Correct bad index on array access in parse_http_time(). Bugfix
9424 - Fix possible bug in vote generation when server versions are present
9425 but client versions are not.
9426 - Fix rare bug on REDIRECTSTREAM control command when called with no
9427 port set: it could erroneously report an error when none had
9429 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9430 compressing large objects and find ourselves with more than 4k
9431 left over. Bugfix on 0.2.0.
9432 - Fix a small memory leak when setting up a hidden service.
9433 - Fix a few memory leaks that could in theory happen under bizarre
9435 - Fix an assert if we post a general-purpose descriptor via the
9436 control port but that descriptor isn't mentioned in our current
9437 network consensus. Bug reported by Jon McLachlan; bugfix on
9440 o Minor features (controller):
9441 - Get NS events working again. Patch from tup.
9442 - The GETCONF command now escapes and quotes configuration values
9443 that don't otherwise fit into the torrc file.
9444 - The SETCONF command now handles quoted values correctly.
9446 o Minor features (directory authorities):
9447 - New configuration options to override default maximum number of
9448 servers allowed on a single IP address. This is important for
9449 running a test network on a single host.
9450 - Actually implement the -s option to tor-gencert.
9451 - Add a manual page for tor-gencert.
9453 o Minor features (bridges):
9454 - Bridge authorities no longer serve bridge descriptors over
9455 unencrypted connections.
9457 o Minor features (other):
9458 - Add hidden services and DNSPorts to the list of things that make
9459 Tor accept that it has running ports. Change starting Tor with no
9460 ports from a fatal error to a warning; we might change it back if
9461 this turns out to confuse anybody. Fixes bug 579.
9464 Changes in version 0.1.2.19 - 2008-01-17
9465 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9466 exit policy a little bit more conservative so it's safer to run an
9467 exit relay on a home system, and fixes a variety of smaller issues.
9470 - Exit policies now reject connections that are addressed to a
9471 relay's public (external) IP address too, unless
9472 ExitPolicyRejectPrivate is turned off. We do this because too
9473 many relays are running nearby to services that trust them based
9477 - When the clock jumps forward a lot, do not allow the bandwidth
9478 buckets to become negative. Fixes bug 544.
9479 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9480 on every successful resolve. Reported by Mike Perry.
9481 - Purge old entries from the "rephist" database and the hidden
9482 service descriptor database even when DirPort is zero.
9483 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9484 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9485 crashing or mis-answering these requests.
9486 - When we decide to send a 503 response to a request for servers, do
9487 not then also send the server descriptors: this defeats the whole
9488 purpose. Fixes bug 539.
9491 - Changing the ExitPolicyRejectPrivate setting should cause us to
9492 rebuild our server descriptor.
9493 - Fix handling of hex nicknames when answering controller requests for
9494 networkstatus by name, or when deciding whether to warn about
9495 unknown routers in a config option. (Patch from mwenge.)
9496 - Fix a couple of hard-to-trigger autoconf problems that could result
9497 in really weird results on platforms whose sys/types.h files define
9498 nonstandard integer types.
9499 - Don't try to create the datadir when running --verify-config or
9500 --hash-password. Resolves bug 540.
9501 - If we were having problems getting a particular descriptor from the
9502 directory caches, and then we learned about a new descriptor for
9503 that router, we weren't resetting our failure count. Reported
9505 - Although we fixed bug 539 (where servers would send HTTP status 503
9506 responses _and_ send a body too), there are still servers out there
9507 that haven't upgraded. Therefore, make clients parse such bodies
9508 when they receive them.
9509 - Run correctly on systems where rlim_t is larger than unsigned long.
9510 This includes some 64-bit systems.
9511 - Run correctly on platforms (like some versions of OS X 10.5) where
9512 the real limit for number of open files is OPEN_FILES, not rlim_max
9513 from getrlimit(RLIMIT_NOFILES).
9514 - Avoid a spurious free on base64 failure.
9515 - Avoid segfaults on certain complex invocations of
9516 router_get_by_hexdigest().
9517 - Fix rare bug on REDIRECTSTREAM control command when called with no
9518 port set: it could erroneously report an error when none had
9522 Changes in version 0.2.0.15-alpha - 2007-12-25
9523 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9524 features added in 0.2.0.13-alpha.
9527 - Fix several remotely triggerable asserts based on DirPort requests
9528 for a v2 or v3 networkstatus object before we were prepared. This
9529 was particularly bad for 0.2.0.13 and later bridge relays, who
9530 would never have a v2 networkstatus and would thus always crash
9531 when used. Bugfixes on 0.2.0.x.
9532 - Estimate the v3 networkstatus size more accurately, rather than
9533 estimating it at zero bytes and giving it artificially high priority
9534 compared to other directory requests. Bugfix on 0.2.0.x.
9537 - Fix configure.in logic for cross-compilation.
9538 - When we load a bridge descriptor from the cache, and it was
9539 previously unreachable, mark it as retriable so we won't just
9540 ignore it. Also, try fetching a new copy immediately. Bugfixes
9542 - The bridge GeoIP stats were counting other relays, for example
9543 self-reachability and authority-reachability tests.
9546 - Support compilation to target iPhone; patch from cjacker huang.
9547 To build for iPhone, pass the --enable-iphone option to configure.
9550 Changes in version 0.2.0.14-alpha - 2007-12-23
9552 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9553 without a datadirectory from a previous Tor install. Reported
9555 - Fix a crash when we fetch a descriptor that turns out to be
9556 unexpected (it used to be in our networkstatus when we started
9557 fetching it, but it isn't in our current networkstatus), and we
9558 aren't using bridges. Bugfix on 0.2.0.x.
9559 - Fix a crash when accessing hidden services: it would work the first
9560 time you use a given introduction point for your service, but
9561 on subsequent requests we'd be using garbage memory. Fixed by
9562 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9563 - Fix a crash when we load a bridge descriptor from disk but we don't
9564 currently have a Bridge line for it in our torrc. Bugfix on
9568 - If bridge authorities set BridgePassword, they will serve a
9569 snapshot of known bridge routerstatuses from their DirPort to
9570 anybody who knows that password. Unset by default.
9573 - Make the unit tests build again.
9574 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9575 - Make PublishServerDescriptor default to 1, so the default doesn't
9576 have to change as we invent new directory protocol versions.
9577 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9578 be included unless sys/time.h is already included. Fixes
9579 bug 553. Bugfix on 0.2.0.x.
9580 - If we receive a general-purpose descriptor and then receive an
9581 identical bridge-purpose descriptor soon after, don't discard
9582 the next one as a duplicate.
9585 - If BridgeRelay is set to 1, then the default for
9586 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9587 - If the user sets RelayBandwidthRate but doesn't set
9588 RelayBandwidthBurst, then make them equal rather than erroring out.
9591 Changes in version 0.2.0.13-alpha - 2007-12-21
9592 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9593 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9596 o New directory authorities:
9597 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9601 - Only update guard status (usable / not usable) once we have
9602 enough directory information. This was causing us to always pick
9603 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9604 causing us to discard all our guards on startup if we hadn't been
9605 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9606 - Purge old entries from the "rephist" database and the hidden
9607 service descriptor databases even when DirPort is zero. Bugfix
9609 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9610 after opening a circuit -- even a relayed circuit. Bugfix on
9612 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9613 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9614 crashing or mis-answering these types of requests.
9615 - Relays were publishing their server descriptor to v1 and v2
9616 directory authorities, but they didn't try publishing to v3-only
9617 authorities. Fix this; and also stop publishing to v1 authorities.
9619 - When we were reading router descriptors from cache, we were ignoring
9620 the annotations -- so for example we were reading in bridge-purpose
9621 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9622 - When we decided to send a 503 response to a request for servers, we
9623 were then also sending the server descriptors: this defeats the
9624 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9627 - Bridge relays now behave like clients with respect to time
9628 intervals for downloading new consensus documents -- otherwise they
9629 stand out. Bridge users now wait until the end of the interval,
9630 so their bridge relay will be sure to have a new consensus document.
9631 - Three new config options (AlternateDirAuthority,
9632 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9633 user selectively replace the default directory authorities by type,
9634 rather than the all-or-nothing replacement that DirServer offers.
9635 - Tor can now be configured to read a GeoIP file from disk in one
9636 of two formats. This can be used by controllers to map IP addresses
9637 to countries. Eventually, it may support exit-by-country.
9638 - When possible, bridge relays remember which countries users
9639 are coming from, and report aggregate information in their
9640 extra-info documents, so that the bridge authorities can learn
9641 where Tor is blocked.
9642 - Bridge directory authorities now do reachability testing on the
9643 bridges they know. They provide router status summaries to the
9644 controller via "getinfo ns/purpose/bridge", and also dump summaries
9645 to a file periodically.
9646 - Stop fetching directory info so aggressively if your DirPort is
9647 on but your ORPort is off; stop fetching v2 dir info entirely.
9648 You can override these choices with the new FetchDirInfoEarly
9652 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9653 consensus documents when there are too many relays at a single
9654 IP address. Now clear it in v2 network status documents too, and
9655 also clear it in routerinfo_t when the relay is no longer listed
9656 in the relevant networkstatus document.
9657 - Don't crash if we get an unexpected value for the
9658 PublishServerDescriptor config option. Reported by Matt Edman;
9659 bugfix on 0.2.0.9-alpha.
9660 - Our new v2 hidden service descriptor format allows descriptors
9661 that have no introduction points. But Tor crashed when we tried
9662 to build a descriptor with no intro points (and it would have
9663 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9665 - Fix building with dmalloc 5.5.2 with glibc.
9666 - Reject uploaded descriptors and extrainfo documents if they're
9667 huge. Otherwise we'll cache them all over the network and it'll
9668 clog everything up. Reported by Aljosha Judmayer.
9669 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9670 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9671 - When the DANGEROUS_VERSION controller status event told us we're
9672 running an obsolete version, it used the string "OLD" to describe
9673 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9674 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9675 - If we can't expand our list of entry guards (e.g. because we're
9676 using bridges or we have StrictEntryNodes set), don't mark relays
9677 down when they fail a directory request. Otherwise we're too quick
9678 to mark all our entry points down. Bugfix on 0.1.2.x.
9679 - Fix handling of hex nicknames when answering controller requests for
9680 networkstatus by name, or when deciding whether to warn about unknown
9681 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9682 - Fix a couple of hard-to-trigger autoconf problems that could result
9683 in really weird results on platforms whose sys/types.h files define
9684 nonstandard integer types. Bugfix on 0.1.2.x.
9685 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9686 - Don't crash on name lookup when we have no current consensus. Fixes
9687 bug 538; bugfix on 0.2.0.x.
9688 - Only Tors that want to mirror the v2 directory info should
9689 create the "cached-status" directory in their datadir. (All Tors
9690 used to create it.) Bugfix on 0.2.0.9-alpha.
9691 - Directory authorities should only automatically download Extra Info
9692 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9695 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9696 consumers. (We already do this on HUP.)
9697 - Authorities and caches fetch the v2 networkstatus documents
9698 less often, now that v3 is encouraged.
9699 - Add a new config option BridgeRelay that specifies you want to
9700 be a bridge relay. Right now the only difference is that it makes
9701 you answer begin_dir requests, and it makes you cache dir info,
9702 even if your DirPort isn't on.
9703 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9704 ask about source, timestamp of arrival, purpose, etc. We need
9705 something like this to help Vidalia not do GeoIP lookups on bridge
9707 - Allow multiple HashedControlPassword config lines, to support
9708 multiple controller passwords.
9709 - Authorities now decide whether they're authoritative for a given
9710 router based on the router's purpose.
9711 - New config options AuthDirBadDir and AuthDirListBadDirs for
9712 authorities to mark certain relays as "bad directories" in the
9713 networkstatus documents. Also supports the "!baddir" directive in
9714 the approved-routers file.
9717 Changes in version 0.2.0.12-alpha - 2007-11-16
9718 This twelfth development snapshot fixes some more build problems as
9719 well as a few minor bugs.
9722 - Make it build on OpenBSD again. Patch from tup.
9723 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9724 package-building for Red Hat, OS X, etc.
9726 o Minor bugfixes (on 0.1.2.x):
9727 - Changing the ExitPolicyRejectPrivate setting should cause us to
9728 rebuild our server descriptor.
9730 o Minor bugfixes (on 0.2.0.x):
9731 - When we're lacking a consensus, don't try to perform rendezvous
9732 operations. Reported by Karsten Loesing.
9733 - Fix a small memory leak whenever we decide against using a
9734 newly picked entry guard. Reported by Mike Perry.
9735 - When authorities detected more than two relays running on the same
9736 IP address, they were clearing all the status flags but forgetting
9737 to clear the "hsdir" flag. So clients were being told that a
9738 given relay was the right choice for a v2 hsdir lookup, yet they
9739 never had its descriptor because it was marked as 'not running'
9741 - If we're trying to fetch a bridge descriptor and there's no way
9742 the bridge authority could help us (for example, we don't know
9743 a digest, or there is no bridge authority), don't be so eager to
9744 fall back to asking the bridge authority.
9745 - If we're using bridges or have strictentrynodes set, and our
9746 chosen exit is in the same family as all our bridges/entry guards,
9747 then be flexible about families.
9750 - When we negotiate a v2 link-layer connection (not yet implemented),
9751 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9752 negotiated a v1 connection for their next step. Initial code for
9756 Changes in version 0.2.0.11-alpha - 2007-11-12
9757 This eleventh development snapshot fixes some build problems with
9758 the previous snapshot. It also includes a more secure-by-default exit
9759 policy for relays, fixes an enormous memory leak for exit relays, and
9760 fixes another bug where servers were falling out of the directory list.
9763 - Exit policies now reject connections that are addressed to a
9764 relay's public (external) IP address too, unless
9765 ExitPolicyRejectPrivate is turned off. We do this because too
9766 many relays are running nearby to services that trust them based
9767 on network address. Bugfix on 0.1.2.x.
9770 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9771 on every successful resolve. Reported by Mike Perry; bugfix
9773 - On authorities, never downgrade to old router descriptors simply
9774 because they're listed in the consensus. This created a catch-22
9775 where we wouldn't list a new descriptor because there was an
9776 old one in the consensus, and we couldn't get the new one in the
9777 consensus because we wouldn't list it. Possible fix for bug 548.
9778 Also, this might cause bug 543 to appear on authorities; if so,
9779 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
9781 o Packaging fixes on 0.2.0.10-alpha:
9782 - We were including instructions about what to do with the
9783 src/config/fallback-consensus file, but we weren't actually
9784 including it in the tarball. Disable all of that for now.
9787 - Allow people to say PreferTunnelledDirConns rather than
9788 PreferTunneledDirConns, for those alternate-spellers out there.
9791 - Don't reevaluate all the information from our consensus document
9792 just because we've downloaded a v2 networkstatus that we intend
9793 to cache. Fixes bug 545; bugfix on 0.2.0.x.
9796 Changes in version 0.2.0.10-alpha - 2007-11-10
9797 This tenth development snapshot adds a third v3 directory authority
9798 run by Mike Perry, adds most of Karsten Loesing's new hidden service
9799 descriptor format, fixes a bad crash bug and new bridge bugs introduced
9800 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
9801 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
9802 addresses many more minor issues.
9804 o New directory authorities:
9805 - Set up ides (run by Mike Perry) as the third v3 directory authority.
9808 - Allow tunnelled directory connections to ask for an encrypted
9809 "begin_dir" connection or an anonymized "uses a full Tor circuit"
9810 connection independently. Now we can make anonymized begin_dir
9811 connections for (e.g.) more secure hidden service posting and
9813 - More progress on proposal 114: code from Karsten Loesing to
9814 implement new hidden service descriptor format.
9815 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
9816 accommodate the growing number of servers that use the default
9817 and are reaching it.
9818 - Directory authorities use a new formula for selecting which nodes
9819 to advertise as Guards: they must be in the top 7/8 in terms of
9820 how long we have known about them, and above the median of those
9821 nodes in terms of weighted fractional uptime.
9822 - Make "not enough dir info yet" warnings describe *why* Tor feels
9823 it doesn't have enough directory info yet.
9826 - Stop servers from crashing if they set a Family option (or
9827 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
9829 - Make bridge users work again -- the move to v3 directories in
9830 0.2.0.9-alpha had introduced a number of bugs that made bridges
9831 no longer work for clients.
9832 - When the clock jumps forward a lot, do not allow the bandwidth
9833 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
9835 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
9836 - When the consensus lists a router descriptor that we previously were
9837 mirroring, but that we considered non-canonical, reload the
9838 descriptor as canonical. This fixes bug 543 where Tor servers
9839 would start complaining after a few days that they don't have
9840 enough directory information to build a circuit.
9841 - Consider replacing the current consensus when certificates arrive
9842 that make the pending consensus valid. Previously, we were only
9843 considering replacement when the new certs _didn't_ help.
9844 - Fix an assert error on startup if we didn't already have the
9845 consensus and certs cached in our datadirectory: we were caching
9846 the consensus in consensus_waiting_for_certs but then free'ing it
9848 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
9849 Request) if we need more v3 certs but we've already got pending
9850 requests for all of them.
9851 - Correctly back off from failing certificate downloads. Fixes
9853 - Authorities don't vote on the Running flag if they have been running
9854 for less than 30 minutes themselves. Fixes bug 547, where a newly
9855 started authority would vote that everyone was down.
9858 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
9859 it, it had no AES, and it hasn't seen any security patches since
9863 - Clients now hold circuitless TLS connections open for 1.5 times
9864 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
9865 rebuild a new circuit over them within that timeframe. Previously,
9866 they held them open only for KeepalivePeriod (5 minutes).
9867 - Use "If-Modified-Since" to avoid retrieving consensus
9868 networkstatuses that we already have.
9869 - When we have no consensus, check FallbackNetworkstatusFile (defaults
9870 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
9871 we start knowing some directory caches.
9872 - When we receive a consensus from the future, warn about skew.
9873 - Improve skew reporting: try to give the user a better log message
9874 about how skewed they are, and how much this matters.
9875 - When we have a certificate for an authority, believe that
9876 certificate's claims about the authority's IP address.
9877 - New --quiet command-line option to suppress the default console log.
9878 Good in combination with --hash-password.
9879 - Authorities send back an X-Descriptor-Not-New header in response to
9880 an accepted-but-discarded descriptor upload. Partially implements
9882 - Make the log message for "tls error. breaking." more useful.
9883 - Better log messages about certificate downloads, to attempt to
9884 track down the second incarnation of bug 546.
9886 o Minor features (bridges):
9887 - If bridge users set UpdateBridgesFromAuthority, but the digest
9888 they ask for is a 404 from the bridge authority, they now fall
9889 back to trying the bridge directly.
9890 - Bridges now use begin_dir to publish their server descriptor to
9891 the bridge authority, even when they haven't set TunnelDirConns.
9893 o Minor features (controller):
9894 - When reporting clock skew, and we know that the clock is _at least
9895 as skewed_ as some value, but we don't know the actual value,
9896 report the value as a "minimum skew."
9899 - Update linux-tor-prio.sh script to allow QoS based on the uid of
9900 the Tor process. Patch from Marco Bonetti with tweaks from Mike
9904 - Refuse to start if both ORPort and UseBridges are set. Bugfix
9905 on 0.2.0.x, suggested by Matt Edman.
9906 - Don't stop fetching descriptors when FetchUselessDescriptors is
9907 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
9908 reported by tup and ioerror.
9909 - Better log message on vote from unknown authority.
9910 - Don't log "Launching 0 request for 0 router" message.
9912 o Minor bugfixes (memory leaks):
9913 - Stop leaking memory every time we parse a v3 certificate. Bugfix
9915 - Stop leaking memory every time we load a v3 certificate. Bugfix
9916 on 0.2.0.1-alpha. Fixes bug 536.
9917 - Stop leaking a cached networkstatus on exit. Bugfix on
9919 - Stop leaking voter information every time we free a consensus.
9920 Bugfix on 0.2.0.3-alpha.
9921 - Stop leaking signed data every time we check a voter signature.
9922 Bugfix on 0.2.0.3-alpha.
9923 - Stop leaking a signature every time we fail to parse a consensus or
9924 a vote. Bugfix on 0.2.0.3-alpha.
9925 - Stop leaking v2_download_status_map on shutdown. Bugfix on
9927 - Stop leaking conn->nickname every time we make a connection to a
9928 Tor relay without knowing its expected identity digest (e.g. when
9929 using bridges). Bugfix on 0.2.0.3-alpha.
9931 - Minor bugfixes (portability):
9932 - Run correctly on platforms where rlim_t is larger than unsigned
9933 long, and/or where the real limit for number of open files is
9934 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
9935 particular, these may be needed for OS X 10.5.
9938 Changes in version 0.1.2.18 - 2007-10-28
9939 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
9940 hidden service introduction that were causing huge delays, and a big
9941 bug that was causing some servers to disappear from the network status
9942 lists for a few hours each day.
9944 o Major bugfixes (crashes):
9945 - If a connection is shut down abruptly because of something that
9946 happened inside connection_flushed_some(), do not call
9947 connection_finished_flushing(). Should fix bug 451:
9948 "connection_stop_writing: Assertion conn->write_event failed"
9949 Bugfix on 0.1.2.7-alpha.
9950 - Fix possible segfaults in functions called from
9951 rend_process_relay_cell().
9953 o Major bugfixes (hidden services):
9954 - Hidden services were choosing introduction points uniquely by
9955 hexdigest, but when constructing the hidden service descriptor
9956 they merely wrote the (potentially ambiguous) nickname.
9957 - Clients now use the v2 intro format for hidden service
9958 connections: they specify their chosen rendezvous point by identity
9959 digest rather than by (potentially ambiguous) nickname. These
9960 changes could speed up hidden service connections dramatically.
9962 o Major bugfixes (other):
9963 - Stop publishing a new server descriptor just because we get a
9964 HUP signal. This led (in a roundabout way) to some servers getting
9965 dropped from the networkstatus lists for a few hours each day.
9966 - When looking for a circuit to cannibalize, consider family as well
9967 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9968 circuit cannibalization).
9969 - When a router wasn't listed in a new networkstatus, we were leaving
9970 the flags for that router alone -- meaning it remained Named,
9971 Running, etc -- even though absence from the networkstatus means
9972 that it shouldn't be considered to exist at all anymore. Now we
9973 clear all the flags for routers that fall out of the networkstatus
9974 consensus. Fixes bug 529.
9977 - Don't try to access (or alter) the state file when running
9978 --list-fingerprint or --verify-config or --hash-password. Resolves
9980 - When generating information telling us how to extend to a given
9981 router, do not try to include the nickname if it is
9982 absent. Resolves bug 467.
9983 - Fix a user-triggerable segfault in expand_filename(). (There isn't
9984 a way to trigger this remotely.)
9985 - When sending a status event to the controller telling it that an
9986 OR address is reachable, set the port correctly. (Previously we
9987 were reporting the dir port.)
9988 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9989 command. Bugfix on 0.1.2.17.
9990 - When loading bandwidth history, do not believe any information in
9991 the future. Fixes bug 434.
9992 - When loading entry guard information, do not believe any information
9994 - When we have our clock set far in the future and generate an
9995 onion key, then re-set our clock to be correct, we should not stop
9996 the onion key from getting rotated.
9997 - On some platforms, accept() can return a broken address. Detect
9998 this more quietly, and deal accordingly. Fixes bug 483.
9999 - It's not actually an error to find a non-pending entry in the DNS
10000 cache when canceling a pending resolve. Don't log unless stuff
10001 is fishy. Resolves bug 463.
10002 - Don't reset trusted dir server list when we set a configuration
10003 option. Patch from Robert Hogan.
10004 - Don't try to create the datadir when running --verify-config or
10005 --hash-password. Resolves bug 540.
10008 Changes in version 0.2.0.9-alpha - 2007-10-24
10009 This ninth development snapshot switches clients to the new v3 directory
10010 system; allows servers to be listed in the network status even when they
10011 have the same nickname as a registered server; and fixes many other
10012 bugs including a big one that was causing some servers to disappear
10013 from the network status lists for a few hours each day.
10015 o Major features (directory system):
10016 - Clients now download v3 consensus networkstatus documents instead
10017 of v2 networkstatus documents. Clients and caches now base their
10018 opinions about routers on these consensus documents. Clients only
10019 download router descriptors listed in the consensus.
10020 - Authorities now list servers who have the same nickname as
10021 a different named server, but list them with a new flag,
10022 "Unnamed". Now we can list servers that happen to pick the same
10023 nickname as a server that registered two years ago and then
10024 disappeared. Partially implements proposal 122.
10025 - If the consensus lists a router as "Unnamed", the name is assigned
10026 to a different router: do not identify the router by that name.
10027 Partially implements proposal 122.
10028 - Authorities can now come to a consensus on which method to use to
10029 compute the consensus. This gives us forward compatibility.
10032 - Stop publishing a new server descriptor just because we HUP or
10033 when we find our DirPort to be reachable but won't actually publish
10034 it. New descriptors without any real changes are dropped by the
10035 authorities, and can screw up our "publish every 18 hours" schedule.
10037 - When a router wasn't listed in a new networkstatus, we were leaving
10038 the flags for that router alone -- meaning it remained Named,
10039 Running, etc -- even though absence from the networkstatus means
10040 that it shouldn't be considered to exist at all anymore. Now we
10041 clear all the flags for routers that fall out of the networkstatus
10042 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10043 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10044 extrainfo documents and then discard them immediately for not
10045 matching the latest router. Bugfix on 0.2.0.1-alpha.
10047 o Minor features (v3 directory protocol):
10048 - Allow tor-gencert to generate a new certificate without replacing
10050 - Allow certificates to include an address.
10051 - When we change our directory-cache settings, reschedule all voting
10052 and download operations.
10053 - Reattempt certificate downloads immediately on failure, as long as
10054 we haven't failed a threshold number of times yet.
10055 - Delay retrying consensus downloads while we're downloading
10056 certificates to verify the one we just got. Also, count getting a
10057 consensus that we already have (or one that isn't valid) as a failure,
10058 and count failing to get the certificates after 20 minutes as a
10060 - Build circuits and download descriptors even if our consensus is a
10061 little expired. (This feature will go away once authorities are
10064 o Minor features (router descriptor cache):
10065 - If we find a cached-routers file that's been sitting around for more
10066 than 28 days unmodified, then most likely it's a leftover from
10067 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10069 - When we (as a cache) download a descriptor because it was listed
10070 in a consensus, remember when the consensus was supposed to expire,
10071 and don't expire the descriptor until then.
10073 o Minor features (performance):
10074 - Call routerlist_remove_old_routers() much less often. This should
10075 speed startup, especially on directory caches.
10076 - Don't try to launch new descriptor downloads quite so often when we
10077 already have enough directory information to build circuits.
10078 - Base64 decoding was actually showing up on our profile when parsing
10079 the initial descriptor file; switch to an in-process all-at-once
10080 implementation that's about 3.5x times faster than calling out to
10083 o Minor features (compilation):
10084 - Detect non-ASCII platforms (if any still exist) and refuse to
10085 build there: some of our code assumes that 'A' is 65 and so on.
10087 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10088 - Make the "next period" votes into "current period" votes immediately
10089 after publishing the consensus; avoid a heisenbug that made them
10090 stick around indefinitely.
10091 - When we discard a vote as a duplicate, do not report this as
10093 - Treat missing v3 keys or certificates as an error when running as a
10094 v3 directory authority.
10095 - When we're configured to be a v3 authority, but we're only listed
10096 as a non-v3 authority in our DirServer line for ourself, correct
10098 - If an authority doesn't have a qualified hostname, just put
10099 its address in the vote. This fixes the problem where we referred to
10100 "moria on moria:9031."
10101 - Distinguish between detached signatures for the wrong period, and
10102 detached signatures for a divergent vote.
10103 - Fix a small memory leak when computing a consensus.
10104 - When there's no concensus, we were forming a vote every 30
10105 minutes, but writing the "valid-after" line in our vote based
10106 on our configured V3AuthVotingInterval: so unless the intervals
10107 matched up, we immediately rejected our own vote because it didn't
10108 start at the voting interval that caused us to construct a vote.
10110 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10111 - Delete unverified-consensus when the real consensus is set.
10112 - Consider retrying a consensus networkstatus fetch immediately
10113 after one fails: don't wait 60 seconds to notice.
10114 - When fetching a consensus as a cache, wait until a newer consensus
10115 should exist before trying to replace the current one.
10116 - Use a more forgiving schedule for retrying failed consensus
10117 downloads than for other types.
10119 o Minor bugfixes (other directory issues):
10120 - Correct the implementation of "download votes by digest." Bugfix on
10122 - Authorities no longer send back "400 you're unreachable please fix
10123 it" errors to Tor servers that aren't online all the time. We're
10124 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10126 o Minor bugfixes (controller):
10127 - Don't reset trusted dir server list when we set a configuration
10128 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10129 - Respond to INT and TERM SIGNAL commands before we execute the
10130 signal, in case the signal shuts us down. We had a patch in
10131 0.1.2.1-alpha that tried to do this by queueing the response on
10132 the connection's buffer before shutting down, but that really
10133 isn't the same thing at all. Bug located by Matt Edman.
10135 o Minor bugfixes (misc):
10136 - Correctly check for bad options to the "PublishServerDescriptor"
10137 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10138 - Stop leaking memory on failing case of base32_decode, and make
10139 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10140 - Don't try to download extrainfo documents when we're trying to
10141 fetch enough directory info to build a circuit: having enough
10142 info should get priority. Bugfix on 0.2.0.x.
10143 - Don't complain that "your server has not managed to confirm that its
10144 ports are reachable" if we haven't been able to build any circuits
10145 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10147 - Detect the reason for failing to mmap a descriptor file we just
10148 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10151 o Code simplifications and refactoring:
10152 - Remove support for the old bw_accounting file: we've been storing
10153 bandwidth accounting information in the state file since
10154 0.1.2.5-alpha. This may result in bandwidth accounting errors
10155 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10156 downgrade to 0.1.1.x or earlier.
10157 - New convenience code to locate a file within the DataDirectory.
10158 - Move non-authority functionality out of dirvote.c.
10159 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10160 so that they all take the same named flags.
10163 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10164 Unix users an easy way to script their Tor process (e.g. by
10165 adjusting bandwidth based on the time of the day).
10168 Changes in version 0.2.0.8-alpha - 2007-10-12
10169 This eighth development snapshot fixes a crash bug that's been bothering
10170 us since February 2007, lets bridge authorities store a list of bridge
10171 descriptors they've seen, gets v3 directory voting closer to working,
10172 starts caching v3 directory consensus documents on directory mirrors,
10173 and fixes a variety of smaller issues including some minor memory leaks.
10175 o Major features (router descriptor cache):
10176 - Store routers in a file called cached-descriptors instead of in
10177 cached-routers. Initialize cached-descriptors from cached-routers
10178 if the old format is around. The new format allows us to store
10179 annotations along with descriptors.
10180 - Use annotations to record the time we received each descriptor, its
10181 source, and its purpose.
10182 - Disable the SETROUTERPURPOSE controller command: it is now
10184 - Controllers should now specify cache=no or cache=yes when using
10185 the +POSTDESCRIPTOR command.
10186 - Bridge authorities now write bridge descriptors to disk, meaning
10187 we can export them to other programs and begin distributing them
10190 o Major features (directory authorities):
10191 - When a v3 authority is missing votes or signatures, it now tries
10193 - Directory authorities track weighted fractional uptime as well as
10194 weighted mean-time-between failures. WFU is suitable for deciding
10195 whether a node is "usually up", while MTBF is suitable for deciding
10196 whether a node is "likely to stay up." We need both, because
10197 "usually up" is a good requirement for guards, while "likely to
10198 stay up" is a good requirement for long-lived connections.
10200 o Major features (v3 directory system):
10201 - Caches now download v3 network status documents as needed,
10202 and download the descriptors listed in them.
10203 - All hosts now attempt to download and keep fresh v3 authority
10204 certificates, and re-attempt after failures.
10205 - More internal-consistency checks for vote parsing.
10207 o Major bugfixes (crashes):
10208 - If a connection is shut down abruptly because of something that
10209 happened inside connection_flushed_some(), do not call
10210 connection_finished_flushing(). Should fix bug 451. Bugfix on
10213 o Major bugfixes (performance):
10214 - Fix really bad O(n^2) performance when parsing a long list of
10215 routers: Instead of searching the entire list for an "extra-info "
10216 string which usually wasn't there, once for every routerinfo
10217 we read, just scan lines forward until we find one we like.
10219 - When we add data to a write buffer in response to the data on that
10220 write buffer getting low because of a flush, do not consider the
10221 newly added data as a candidate for immediate flushing, but rather
10222 make it wait until the next round of writing. Otherwise, we flush
10223 and refill recursively, and a single greedy TLS connection can
10224 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10226 o Minor features (v3 authority system):
10227 - Add more ways for tools to download the votes that lead to the
10229 - Send a 503 when low on bandwidth and a vote, consensus, or
10230 certificate is requested.
10231 - If-modified-since is now implemented properly for all kinds of
10232 certificate requests.
10234 o Minor bugfixes (network statuses):
10235 - Tweak the implementation of proposal 109 slightly: allow at most
10236 two Tor servers on the same IP address, except if it's the location
10237 of a directory authority, in which case allow five. Bugfix on
10240 o Minor bugfixes (controller):
10241 - When sending a status event to the controller telling it that an
10242 OR address is reachable, set the port correctly. (Previously we
10243 were reporting the dir port.) Bugfix on 0.1.2.x.
10245 o Minor bugfixes (v3 directory system):
10246 - Fix logic to look up a cert by its signing key digest. Bugfix on
10248 - Only change the reply to a vote to "OK" if it's not already
10249 set. This gets rid of annoying "400 OK" log messages, which may
10250 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10251 - When we get a valid consensus, recompute the voting schedule.
10252 - Base the valid-after time of a vote on the consensus voting
10253 schedule, not on our preferred schedule.
10254 - Make the return values and messages from signature uploads and
10255 downloads more sensible.
10256 - Fix a memory leak when serving votes and consensus documents, and
10257 another when serving certificates.
10259 o Minor bugfixes (performance):
10260 - Use a slightly simpler string hashing algorithm (copying Python's
10261 instead of Java's) and optimize our digest hashing algorithm to take
10262 advantage of 64-bit platforms and to remove some possibly-costly
10264 - Fix a minor memory leak whenever we parse guards from our state
10265 file. Bugfix on 0.2.0.7-alpha.
10266 - Fix a minor memory leak whenever we write out a file. Bugfix on
10268 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10269 command. Bugfix on 0.2.0.5-alpha.
10271 o Minor bugfixes (portability):
10272 - On some platforms, accept() can return a broken address. Detect
10273 this more quietly, and deal accordingly. Fixes bug 483.
10274 - Stop calling tor_strlower() on uninitialized memory in some cases.
10275 Bugfix in 0.2.0.7-alpha.
10277 o Minor bugfixes (usability):
10278 - Treat some 403 responses from directory servers as INFO rather than
10279 WARN-severity events.
10280 - It's not actually an error to find a non-pending entry in the DNS
10281 cache when canceling a pending resolve. Don't log unless stuff is
10282 fishy. Resolves bug 463.
10284 o Minor bugfixes (anonymity):
10285 - Never report that we've used more bandwidth than we're willing to
10286 relay: it leaks how much non-relay traffic we're using. Resolves
10288 - When looking for a circuit to cannibalize, consider family as well
10289 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10290 circuit cannibalization).
10292 o Code simplifications and refactoring:
10293 - Make a bunch of functions static. Remove some dead code.
10294 - Pull out about a third of the really big routerlist.c; put it in a
10295 new module, networkstatus.c.
10296 - Merge the extra fields in local_routerstatus_t back into
10297 routerstatus_t: we used to need one routerstatus_t for each
10298 authority's opinion, plus a local_routerstatus_t for the locally
10299 computed consensus opinion. To save space, we put the locally
10300 modified fields into local_routerstatus_t, and only the common
10301 stuff into routerstatus_t. But once v3 directories are in use,
10302 clients and caches will no longer need to hold authority opinions;
10303 thus, the rationale for keeping the types separate is now gone.
10304 - Make the code used to reschedule and reattempt downloads more
10306 - Turn all 'Are we a directory server/mirror?' logic into a call to
10308 - Remove the code to generate the oldest (v1) directory format.
10309 The code has been disabled since 0.2.0.5-alpha.
10312 Changes in version 0.2.0.7-alpha - 2007-09-21
10313 This seventh development snapshot makes bridges work again, makes bridge
10314 authorities work for the first time, fixes two huge performance flaws
10315 in hidden services, and fixes a variety of minor issues.
10317 o New directory authorities:
10318 - Set up moria1 and tor26 as the first v3 directory authorities. See
10319 doc/spec/dir-spec.txt for details on the new directory design.
10321 o Major bugfixes (crashes):
10322 - Fix possible segfaults in functions called from
10323 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10325 o Major bugfixes (bridges):
10326 - Fix a bug that made servers send a "404 Not found" in response to
10327 attempts to fetch their server descriptor. This caused Tor servers
10328 to take many minutes to establish reachability for their DirPort,
10329 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10330 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10331 users configure that and specify a bridge with an identity
10332 fingerprint, now they will lookup the bridge descriptor at the
10333 default bridge authority via a one-hop tunnel, but once circuits
10334 are established they will switch to a three-hop tunnel for later
10335 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10337 o Major bugfixes (hidden services):
10338 - Hidden services were choosing introduction points uniquely by
10339 hexdigest, but when constructing the hidden service descriptor
10340 they merely wrote the (potentially ambiguous) nickname.
10341 - Clients now use the v2 intro format for hidden service
10342 connections: they specify their chosen rendezvous point by identity
10343 digest rather than by (potentially ambiguous) nickname. Both
10344 are bugfixes on 0.1.2.x, and they could speed up hidden service
10345 connections dramatically. Thanks to Karsten Loesing.
10347 o Minor features (security):
10348 - As a client, do not believe any server that tells us that an
10349 address maps to an internal address space.
10350 - Make it possible to enable HashedControlPassword and
10351 CookieAuthentication at the same time.
10353 o Minor features (guard nodes):
10354 - Tag every guard node in our state file with the version that
10355 we believe added it, or with our own version if we add it. This way,
10356 if a user temporarily runs an old version of Tor and then switches
10357 back to a new one, she doesn't automatically lose her guards.
10359 o Minor features (speed):
10360 - When implementing AES counter mode, update only the portions of the
10361 counter buffer that need to change, and don't keep separate
10362 network-order and host-order counters when they are the same (i.e.,
10363 on big-endian hosts.)
10365 o Minor features (controller):
10366 - Accept LF instead of CRLF on controller, since some software has a
10367 hard time generating real Internet newlines.
10368 - Add GETINFO values for the server status events
10369 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10372 o Removed features:
10373 - Routers no longer include bandwidth-history lines in their
10374 descriptors; this information is already available in extra-info
10375 documents, and including it in router descriptors took up 60%
10376 (!) of compressed router descriptor downloads. Completes
10377 implementation of proposal 104.
10378 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10379 and TorControl.py, as they use the old v0 controller protocol,
10380 and are obsoleted by TorFlow anyway.
10381 - Drop support for v1 rendezvous descriptors, since we never used
10382 them anyway, and the code has probably rotted by now. Based on
10383 patch from Karsten Loesing.
10384 - On OSX, stop warning the user that kqueue support in libevent is
10385 "experimental", since it seems to have worked fine for ages.
10388 - When generating information telling us how to extend to a given
10389 router, do not try to include the nickname if it is absent. Fixes
10390 bug 467. Bugfix on 0.2.0.3-alpha.
10391 - Fix a user-triggerable (but not remotely-triggerable) segfault
10392 in expand_filename(). Bugfix on 0.1.2.x.
10393 - Fix a memory leak when freeing incomplete requests from DNSPort.
10394 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10395 - Don't try to access (or alter) the state file when running
10396 --list-fingerprint or --verify-config or --hash-password. (Resolves
10397 bug 499.) Bugfix on 0.1.2.x.
10398 - Servers used to decline to publish their DirPort if their
10399 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10400 were below a threshold. Now they only look at BandwidthRate and
10401 RelayBandwidthRate. Bugfix on 0.1.2.x.
10402 - Remove an optimization in the AES counter-mode code that assumed
10403 that the counter never exceeded 2^68. When the counter can be set
10404 arbitrarily as an IV (as it is by Karsten's new hidden services
10405 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10406 - Resume listing "AUTHORITY" flag for authorities in network status.
10407 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10409 o Code simplifications and refactoring:
10410 - Revamp file-writing logic so we don't need to have the entire
10411 contents of a file in memory at once before we write to disk. Tor,
10413 - Turn "descriptor store" into a full-fledged type.
10414 - Move all NT services code into a separate source file.
10415 - Unify all code that computes medians, percentile elements, etc.
10416 - Get rid of a needless malloc when parsing address policies.
10419 Changes in version 0.1.2.17 - 2007-08-30
10420 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10421 X bundles. Vidalia 0.0.14 makes authentication required for the
10422 ControlPort in the default configuration, which addresses important
10423 security risks. Everybody who uses Vidalia (or another controller)
10426 In addition, this Tor update fixes major load balancing problems with
10427 path selection, which should speed things up a lot once many people
10430 o Major bugfixes (security):
10431 - We removed support for the old (v0) control protocol. It has been
10432 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10433 become more of a headache than it's worth.
10435 o Major bugfixes (load balancing):
10436 - When choosing nodes for non-guard positions, weight guards
10437 proportionally less, since they already have enough load. Patch
10439 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10440 will allow fast Tor servers to get more attention.
10441 - When we're upgrading from an old Tor version, forget our current
10442 guards and pick new ones according to the new weightings. These
10443 three load balancing patches could raise effective network capacity
10444 by a factor of four. Thanks to Mike Perry for measurements.
10446 o Major bugfixes (stream expiration):
10447 - Expire not-yet-successful application streams in all cases if
10448 they've been around longer than SocksTimeout. Right now there are
10449 some cases where the stream will live forever, demanding a new
10450 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10452 o Minor features (controller):
10453 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10454 is valid before any authentication has been received. It tells
10455 a controller what kind of authentication is expected, and what
10456 protocol is spoken. Implements proposal 119.
10458 o Minor bugfixes (performance):
10459 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10460 greatly speeding up loading cached-routers from disk on startup.
10461 - Disable sentinel-based debugging for buffer code: we squashed all
10462 the bugs that this was supposed to detect a long time ago, and now
10463 its only effect is to change our buffer sizes from nice powers of
10464 two (which platform mallocs tend to like) to values slightly over
10465 powers of two (which make some platform mallocs sad).
10467 o Minor bugfixes (misc):
10468 - If exit bandwidth ever exceeds one third of total bandwidth, then
10469 use the correct formula to weight exit nodes when choosing paths.
10470 Based on patch from Mike Perry.
10471 - Choose perfectly fairly among routers when choosing by bandwidth and
10472 weighting by fraction of bandwidth provided by exits. Previously, we
10473 would choose with only approximate fairness, and correct ourselves
10474 if we ran off the end of the list.
10475 - If we require CookieAuthentication but we fail to write the
10476 cookie file, we would warn but not exit, and end up in a state
10477 where no controller could authenticate. Now we exit.
10478 - If we require CookieAuthentication, stop generating a new cookie
10479 every time we change any piece of our config.
10480 - Refuse to start with certain directory authority keys, and
10481 encourage people using them to stop.
10482 - Terminate multi-line control events properly. Original patch
10484 - Fix a minor memory leak when we fail to find enough suitable
10485 servers to choose a circuit.
10486 - Stop leaking part of the descriptor when we run into a particularly
10487 unparseable piece of it.
10490 Changes in version 0.2.0.6-alpha - 2007-08-26
10491 This sixth development snapshot features a new Vidalia version in the
10492 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10493 the ControlPort in the default configuration, which addresses important
10496 In addition, this snapshot fixes major load balancing problems
10497 with path selection, which should speed things up a lot once many
10498 people have upgraded. The directory authorities also use a new
10499 mean-time-between-failure approach to tracking which servers are stable,
10500 rather than just looking at the most recent uptime.
10502 o New directory authorities:
10503 - Set up Tonga as the default bridge directory authority.
10506 - Directory authorities now track servers by weighted
10507 mean-times-between-failures. When we have 4 or more days of data,
10508 use measured MTBF rather than declared uptime to decide whether
10509 to call a router Stable. Implements proposal 108.
10511 o Major bugfixes (load balancing):
10512 - When choosing nodes for non-guard positions, weight guards
10513 proportionally less, since they already have enough load. Patch
10515 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10516 will allow fast Tor servers to get more attention.
10517 - When we're upgrading from an old Tor version, forget our current
10518 guards and pick new ones according to the new weightings. These
10519 three load balancing patches could raise effective network capacity
10520 by a factor of four. Thanks to Mike Perry for measurements.
10522 o Major bugfixes (descriptor parsing):
10523 - Handle unexpected whitespace better in malformed descriptors. Bug
10524 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10527 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10528 GETINFO for Torstat to use until it can switch to using extrainfos.
10529 - Optionally (if built with -DEXPORTMALLINFO) export the output
10530 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10534 - Do not intermix bridge routers with controller-added
10535 routers. (Bugfix on 0.2.0.x)
10536 - Do not fail with an assert when accept() returns an unexpected
10537 address family. Addresses but does not wholly fix bug 483. (Bugfix
10539 - Let directory authorities startup even when they can't generate
10540 a descriptor immediately, e.g. because they don't know their
10542 - Stop putting the authentication cookie in a file called "0"
10543 in your working directory if you don't specify anything for the
10544 new CookieAuthFile option. Reported by Matt Edman.
10545 - Make it possible to read the PROTOCOLINFO response in a way that
10546 conforms to our control-spec. Reported by Matt Edman.
10547 - Fix a minor memory leak when we fail to find enough suitable
10548 servers to choose a circuit. Bugfix on 0.1.2.x.
10549 - Stop leaking part of the descriptor when we run into a particularly
10550 unparseable piece of it. Bugfix on 0.1.2.x.
10551 - Unmap the extrainfo cache file on exit.
10554 Changes in version 0.2.0.5-alpha - 2007-08-19
10555 This fifth development snapshot fixes compilation on Windows again;
10556 fixes an obnoxious client-side bug that slowed things down and put
10557 extra load on the network; gets us closer to using the v3 directory
10558 voting scheme; makes it easier for Tor controllers to use cookie-based
10559 authentication; and fixes a variety of other bugs.
10561 o Removed features:
10562 - Version 1 directories are no longer generated in full. Instead,
10563 authorities generate and serve "stub" v1 directories that list
10564 no servers. This will stop Tor versions 0.1.0.x and earlier from
10565 working, but (for security reasons) nobody should be running those
10568 o Major bugfixes (compilation, 0.2.0.x):
10569 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10570 - Try to fix MSVC compilation: build correctly on platforms that do
10571 not define s6_addr16 or s6_addr32.
10572 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10575 o Major bugfixes (stream expiration):
10576 - Expire not-yet-successful application streams in all cases if
10577 they've been around longer than SocksTimeout. Right now there are
10578 some cases where the stream will live forever, demanding a new
10579 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10580 reported by lodger.
10582 o Minor features (directory servers):
10583 - When somebody requests a list of statuses or servers, and we have
10584 none of those, return a 404 rather than an empty 200.
10586 o Minor features (directory voting):
10587 - Store v3 consensus status consensuses on disk, and reload them
10590 o Minor features (security):
10591 - Warn about unsafe ControlPort configurations.
10592 - Refuse to start with certain directory authority keys, and
10593 encourage people using them to stop.
10595 o Minor features (controller):
10596 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10597 is valid before any authentication has been received. It tells
10598 a controller what kind of authentication is expected, and what
10599 protocol is spoken. Implements proposal 119.
10600 - New config option CookieAuthFile to choose a new location for the
10601 cookie authentication file, and config option
10602 CookieAuthFileGroupReadable to make it group-readable.
10604 o Minor features (unit testing):
10605 - Add command-line arguments to unit-test executable so that we can
10606 invoke any chosen test from the command line rather than having
10607 to run the whole test suite at once; and so that we can turn on
10608 logging for the unit tests.
10610 o Minor bugfixes (on 0.1.2.x):
10611 - If we require CookieAuthentication but we fail to write the
10612 cookie file, we would warn but not exit, and end up in a state
10613 where no controller could authenticate. Now we exit.
10614 - If we require CookieAuthentication, stop generating a new cookie
10615 every time we change any piece of our config.
10616 - When loading bandwidth history, do not believe any information in
10617 the future. Fixes bug 434.
10618 - When loading entry guard information, do not believe any information
10620 - When we have our clock set far in the future and generate an
10621 onion key, then re-set our clock to be correct, we should not stop
10622 the onion key from getting rotated.
10623 - Clean up torrc sample config file.
10624 - Do not automatically run configure from autogen.sh. This
10625 non-standard behavior tended to annoy people who have built other
10628 o Minor bugfixes (on 0.2.0.x):
10629 - Fix a bug with AutomapHostsOnResolve that would always cause
10630 the second request to fail. Bug reported by Kate. Bugfix on
10632 - Fix a bug in ADDRMAP controller replies that would sometimes
10633 try to print a NULL. Patch from tup.
10634 - Read v3 directory authority keys from the right location.
10635 - Numerous bugfixes to directory voting code.
10638 Changes in version 0.1.2.16 - 2007-08-01
10639 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10640 remote attacker in certain situations to rewrite the user's torrc
10641 configuration file. This can completely compromise anonymity of users
10642 in most configurations, including those running the Vidalia bundles,
10643 TorK, etc. Or worse.
10645 o Major security fixes:
10646 - Close immediately after missing authentication on control port;
10647 do not allow multiple authentication attempts.
10650 Changes in version 0.2.0.4-alpha - 2007-08-01
10651 This fourth development snapshot fixes a critical security vulnerability
10652 for most users, specifically those running Vidalia, TorK, etc. Everybody
10653 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10655 o Major security fixes:
10656 - Close immediately after missing authentication on control port;
10657 do not allow multiple authentication attempts.
10659 o Major bugfixes (compilation):
10660 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10663 o Minor features (performance):
10664 - Be even more aggressive about releasing RAM from small
10665 empty buffers. Thanks to our free-list code, this shouldn't be too
10666 performance-intensive.
10667 - Disable sentinel-based debugging for buffer code: we squashed all
10668 the bugs that this was supposed to detect a long time ago, and
10669 now its only effect is to change our buffer sizes from nice
10670 powers of two (which platform mallocs tend to like) to values
10671 slightly over powers of two (which make some platform mallocs sad).
10672 - Log malloc statistics from mallinfo() on platforms where it
10676 Changes in version 0.2.0.3-alpha - 2007-07-29
10677 This third development snapshot introduces new experimental
10678 blocking-resistance features and a preliminary version of the v3
10679 directory voting design, and includes many other smaller features
10683 - The first pieces of our "bridge" design for blocking-resistance
10684 are implemented. People can run bridge directory authorities;
10685 people can run bridges; and people can configure their Tor clients
10686 with a set of bridges to use as the first hop into the Tor network.
10687 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10689 - Create listener connections before we setuid to the configured
10690 User and Group. Now non-Windows users can choose port values
10691 under 1024, start Tor as root, and have Tor bind those ports
10692 before it changes to another UID. (Windows users could already
10694 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10695 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10696 on "vserver" accounts. (Patch from coderman.)
10697 - Be even more aggressive about separating local traffic from relayed
10698 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10700 o Major features (experimental):
10701 - First cut of code for "v3 dir voting": directory authorities will
10702 vote on a common network status document rather than each publishing
10703 their own opinion. This code needs more testing and more corner-case
10704 handling before it's ready for use.
10707 - Directory authorities now call routers Fast if their bandwidth is
10708 at least 100KB/s, and consider their bandwidth adequate to be a
10709 Guard if it is at least 250KB/s, no matter the medians. This fix
10710 complements proposal 107. [Bugfix on 0.1.2.x]
10711 - Directory authorities now never mark more than 3 servers per IP as
10712 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10714 - Minor change to organizationName and commonName generation
10715 procedures in TLS certificates during Tor handshakes, to invalidate
10716 some earlier censorware approaches. This is not a long-term
10717 solution, but applying it will give us a bit of time to look into
10718 the epidemiology of countermeasures as they spread.
10720 o Major bugfixes (directory):
10721 - Rewrite directory tokenization code to never run off the end of
10722 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10724 o Minor features (controller):
10725 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10726 match requests to applications. (Patch from Robert Hogan.)
10727 - Report address and port correctly on connections to DNSPort. (Patch
10728 from Robert Hogan.)
10729 - Add a RESOLVE command to launch hostname lookups. (Original patch
10730 from Robert Hogan.)
10731 - Add GETINFO status/enough-dir-info to let controllers tell whether
10732 Tor has downloaded sufficient directory information. (Patch
10734 - You can now use the ControlSocket option to tell Tor to listen for
10735 controller connections on Unix domain sockets on systems that
10736 support them. (Patch from Peter Palfrader.)
10737 - STREAM NEW events are generated for DNSPort requests and for
10738 tunneled directory connections. (Patch from Robert Hogan.)
10739 - New "GETINFO address-mappings/*" command to get address mappings
10740 with expiry information. "addr-mappings/*" is now deprecated.
10743 o Minor features (misc):
10744 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10746 - The tor-gencert tool for v3 directory authorities now creates all
10747 files as readable to the file creator only, and write-protects
10748 the authority identity key.
10749 - When dumping memory usage, list bytes used in buffer memory
10751 - When running with dmalloc, dump more stats on hup and on exit.
10752 - Directory authorities now fail quickly and (relatively) harmlessly
10753 if they generate a network status document that is somehow
10756 o Traffic load balancing improvements:
10757 - If exit bandwidth ever exceeds one third of total bandwidth, then
10758 use the correct formula to weight exit nodes when choosing paths.
10759 (Based on patch from Mike Perry.)
10760 - Choose perfectly fairly among routers when choosing by bandwidth and
10761 weighting by fraction of bandwidth provided by exits. Previously, we
10762 would choose with only approximate fairness, and correct ourselves
10763 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10765 o Performance improvements:
10766 - Be more aggressive with freeing buffer RAM or putting it on the
10768 - Use Critical Sections rather than Mutexes for synchronizing threads
10769 on win32; Mutexes are heavier-weight, and designed for synchronizing
10772 o Deprecated and removed features:
10773 - RedirectExits is now deprecated.
10774 - Stop allowing address masks that do not correspond to bit prefixes.
10775 We have warned about these for a really long time; now it's time
10776 to reject them. (Patch from croup.)
10778 o Minor bugfixes (directory):
10779 - Fix another crash bug related to extra-info caching. (Bug found by
10780 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
10781 - Directories no longer return a "304 not modified" when they don't
10782 have the networkstatus the client asked for. Also fix a memory
10783 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
10784 - We had accidentally labelled 0.1.2.x directory servers as not
10785 suitable for begin_dir requests, and had labelled no directory
10786 servers as suitable for uploading extra-info documents. [Bugfix
10789 o Minor bugfixes (dns):
10790 - Fix a crash when DNSPort is set more than once. (Patch from Robert
10791 Hogan.) [Bugfix on 0.2.0.2-alpha]
10792 - Add DNSPort connections to the global connection list, so that we
10793 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
10795 - Fix a dangling reference that could lead to a crash when DNSPort is
10796 changed or closed (Patch from Robert Hogan.) [Bugfix on
10799 o Minor bugfixes (controller):
10800 - Provide DNS expiry times in GMT, not in local time. For backward
10801 compatibility, ADDRMAP events only provide GMT expiry in an extended
10802 field. "GETINFO address-mappings" always does the right thing.
10803 - Use CRLF line endings properly in NS events.
10804 - Terminate multi-line control events properly. (Original patch
10805 from tup.) [Bugfix on 0.1.2.x-alpha]
10806 - Do not include spaces in SOURCE_ADDR fields in STREAM
10807 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
10810 Changes in version 0.1.2.15 - 2007-07-17
10811 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
10812 problems, fixes compilation on BSD, and fixes a variety of other
10813 bugs. Everybody should upgrade.
10815 o Major bugfixes (compilation):
10816 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
10818 o Major bugfixes (crashes):
10819 - Try even harder not to dereference the first character after
10820 an mmap(). Reported by lodger.
10821 - Fix a crash bug in directory authorities when we re-number the
10822 routerlist while inserting a new router.
10823 - When the cached-routers file is an even multiple of the page size,
10824 don't run off the end and crash. (Fixes bug 455; based on idea
10826 - Fix eventdns.c behavior on Solaris: It is critical to include
10827 orconfig.h _before_ sys/types.h, so that we can get the expected
10828 definition of _FILE_OFFSET_BITS.
10830 o Major bugfixes (security):
10831 - Fix a possible buffer overrun when using BSD natd support. Bug
10833 - When sending destroy cells from a circuit's origin, don't include
10834 the reason for tearing down the circuit. The spec says we didn't,
10835 and now we actually don't. Reported by lodger.
10836 - Keep streamids from different exits on a circuit separate. This
10837 bug may have allowed other routers on a given circuit to inject
10838 cells into streams. Reported by lodger; fixes bug 446.
10839 - If there's a never-before-connected-to guard node in our list,
10840 never choose any guards past it. This way we don't expand our
10841 guard list unless we need to.
10843 o Minor bugfixes (guard nodes):
10844 - Weight guard selection by bandwidth, so that low-bandwidth nodes
10845 don't get overused as guards.
10847 o Minor bugfixes (directory):
10848 - Correctly count the number of authorities that recommend each
10849 version. Previously, we were under-counting by 1.
10850 - Fix a potential crash bug when we load many server descriptors at
10851 once and some of them make others of them obsolete. Fixes bug 458.
10853 o Minor bugfixes (hidden services):
10854 - Stop tearing down the whole circuit when the user asks for a
10855 connection to a port that the hidden service didn't configure.
10858 o Minor bugfixes (misc):
10859 - On Windows, we were preventing other processes from reading
10860 cached-routers while Tor was running. Reported by janbar.
10861 - Fix a possible (but very unlikely) bug in picking routers by
10862 bandwidth. Add a log message to confirm that it is in fact
10863 unlikely. Patch from lodger.
10864 - Backport a couple of memory leak fixes.
10865 - Backport miscellaneous cosmetic bugfixes.
10868 Changes in version 0.2.0.2-alpha - 2007-06-02
10869 o Major bugfixes on 0.2.0.1-alpha:
10870 - Fix an assertion failure related to servers without extra-info digests.
10871 Resolves bugs 441 and 442.
10873 o Minor features (directory):
10874 - Support "If-Modified-Since" when answering HTTP requests for
10875 directories, running-routers documents, and network-status documents.
10876 (There's no need to support it for router descriptors, since those
10877 are downloaded by descriptor digest.)
10879 o Minor build issues:
10880 - Clear up some MIPSPro compiler warnings.
10881 - When building from a tarball on a machine that happens to have SVK
10882 installed, report the micro-revision as whatever version existed
10883 in the tarball, not as "x".
10886 Changes in version 0.2.0.1-alpha - 2007-06-01
10887 This early development snapshot provides new features for people running
10888 Tor as both a client and a server (check out the new RelayBandwidth
10889 config options); lets Tor run as a DNS proxy; and generally moves us
10890 forward on a lot of fronts.
10892 o Major features, server usability:
10893 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10894 a separate set of token buckets for relayed traffic. Right now
10895 relayed traffic is defined as answers to directory requests, and
10896 OR connections that don't have any local circuits on them.
10898 o Major features, client usability:
10899 - A client-side DNS proxy feature to replace the need for
10900 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10901 for DNS requests on port 9999, use the Tor network to resolve them
10902 anonymously, and send the reply back like a regular DNS server.
10903 The code still only implements a subset of DNS.
10904 - Make PreferTunneledDirConns and TunnelDirConns work even when
10905 we have no cached directory info. This means Tor clients can now
10906 do all of their connections protected by TLS.
10908 o Major features, performance and efficiency:
10909 - Directory authorities accept and serve "extra info" documents for
10910 routers. These documents contain fields from router descriptors
10911 that aren't usually needed, and that use a lot of excess
10912 bandwidth. Once these fields are removed from router descriptors,
10913 the bandwidth savings should be about 60%. [Partially implements
10915 - Servers upload extra-info documents to any authority that accepts
10916 them. Authorities (and caches that have been configured to download
10917 extra-info documents) download them as needed. [Partially implements
10919 - Change the way that Tor buffers data that it is waiting to write.
10920 Instead of queueing data cells in an enormous ring buffer for each
10921 client->OR or OR->OR connection, we now queue cells on a separate
10922 queue for each circuit. This lets us use less slack memory, and
10923 will eventually let us be smarter about prioritizing different kinds
10925 - Use memory pools to allocate cells with better speed and memory
10926 efficiency, especially on platforms where malloc() is inefficient.
10927 - Stop reading on edge connections when their corresponding circuit
10928 buffers are full; start again as the circuits empty out.
10930 o Major features, other:
10931 - Add an HSAuthorityRecordStats option that hidden service authorities
10932 can use to track statistics of overall hidden service usage without
10933 logging information that would be very useful to an attacker.
10934 - Start work implementing multi-level keys for directory authorities:
10935 Add a standalone tool to generate key certificates. (Proposal 103.)
10938 - Directory authorities now call routers Stable if they have an
10939 uptime of at least 30 days, even if that's not the median uptime
10940 in the network. Implements proposal 107, suggested by Kevin Bauer
10943 o Minor fixes (resource management):
10944 - Count the number of open sockets separately from the number
10945 of active connection_t objects. This will let us avoid underusing
10946 our allocated connection limit.
10947 - We no longer use socket pairs to link an edge connection to an
10948 anonymous directory connection or a DirPort test connection.
10949 Instead, we track the link internally and transfer the data
10950 in-process. This saves two sockets per "linked" connection (at the
10951 client and at the server), and avoids the nasty Windows socketpair()
10953 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10954 for every single inactive connection_t. Free items from the
10955 4k/16k-buffer free lists when they haven't been used for a while.
10957 o Minor features (build):
10958 - Make autoconf search for libevent, openssl, and zlib consistently.
10959 - Update deprecated macros in configure.in.
10960 - When warning about missing headers, tell the user to let us
10961 know if the compile succeeds anyway, so we can downgrade the
10963 - Include the current subversion revision as part of the version
10964 string: either fetch it directly if we're in an SVN checkout, do
10965 some magic to guess it if we're in an SVK checkout, or use
10966 the last-detected version if we're building from a .tar.gz.
10967 Use this version consistently in log messages.
10969 o Minor features (logging):
10970 - Always prepend "Bug: " to any log message about a bug.
10971 - Put a platform string (e.g. "Linux i686") in the startup log
10972 message, so when people paste just their logs, we know if it's
10973 OpenBSD or Windows or what.
10974 - When logging memory usage, break down memory used in buffers by
10977 o Minor features (directory system):
10978 - New config option V2AuthoritativeDirectory that all directory
10979 authorities should set. This will let future authorities choose
10980 not to serve V2 directory information.
10981 - Directory authorities allow multiple router descriptors and/or extra
10982 info documents to be uploaded in a single go. This will make
10983 implementing proposal 104 simpler.
10985 o Minor features (controller):
10986 - Add a new config option __DisablePredictedCircuits designed for
10987 use by the controller, when we don't want Tor to build any circuits
10989 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
10990 so we can exit from the middle of the circuit.
10991 - Implement "getinfo status/circuit-established".
10992 - Implement "getinfo status/version/..." so a controller can tell
10993 whether the current version is recommended, and whether any versions
10994 are good, and how many authorities agree. (Patch from shibz.)
10996 o Minor features (hidden services):
10997 - Allow multiple HiddenServicePort directives with the same virtual
10998 port; when they occur, the user is sent round-robin to one
10999 of the target ports chosen at random. Partially fixes bug 393 by
11000 adding limited ad-hoc round-robining.
11002 o Minor features (other):
11004 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11005 resolve request for hosts matching a given pattern causes Tor to
11006 generate an internal virtual address mapping for that host. This
11007 allows DNSPort to work sensibly with hidden service users. By
11008 default, .exit and .onion addresses are remapped; the list of
11009 patterns can be reconfigured with AutomapHostsSuffixes.
11010 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11011 address. Thanks to the AutomapHostsOnResolve option, this is no
11012 longer a completely silly thing to do.
11013 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11014 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11015 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11016 minus 1 byte: the actual maximum declared bandwidth.
11018 o Removed features:
11019 - Removed support for the old binary "version 0" controller protocol.
11020 This has been deprecated since 0.1.1, and warnings have been issued
11021 since 0.1.2. When we encounter a v0 control message, we now send
11022 back an error and close the connection.
11023 - Remove the old "dns worker" server DNS code: it hasn't been default
11024 since 0.1.2.2-alpha, and all the servers seem to be using the new
11027 o Minor bugfixes (portability):
11028 - Even though Windows is equally happy with / and \ as path separators,
11029 try to use \ consistently on Windows and / consistently on Unix: it
11030 makes the log messages nicer.
11031 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11032 - Read resolv.conf files correctly on platforms where read() returns
11033 partial results on small file reads.
11035 o Minor bugfixes (directory):
11036 - Correctly enforce that elements of directory objects do not appear
11037 more often than they are allowed to appear.
11038 - When we are reporting the DirServer line we just parsed, we were
11039 logging the second stanza of the key fingerprint, not the first.
11041 o Minor bugfixes (logging):
11042 - When we hit an EOF on a log (probably because we're shutting down),
11043 don't try to remove the log from the list: just mark it as
11044 unusable. (Bulletproofs against bug 222.)
11046 o Minor bugfixes (other):
11047 - In the exitlist script, only consider the most recently published
11048 server descriptor for each server. Also, when the user requests
11049 a list of servers that _reject_ connections to a given address,
11050 explicitly exclude the IPs that also have servers that accept
11051 connections to that address. (Resolves bug 405.)
11052 - Stop allowing hibernating servers to be "stable" or "fast".
11053 - On Windows, we were preventing other processes from reading
11054 cached-routers while Tor was running. (Reported by janbar)
11055 - Make the NodeFamilies config option work. (Reported by
11056 lodger -- it has never actually worked, even though we added it
11058 - Check return values from pthread_mutex functions.
11059 - Don't save non-general-purpose router descriptors to the disk cache,
11060 because we have no way of remembering what their purpose was when
11062 - Add even more asserts to hunt down bug 417.
11063 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11064 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11065 Add a log message to confirm that it is in fact unlikely.
11067 o Minor bugfixes (controller):
11068 - Make 'getinfo fingerprint' return a 551 error if we're not a
11069 server, so we match what the control spec claims we do. Reported
11071 - Fix a typo in an error message when extendcircuit fails that
11072 caused us to not follow the \r\n-based delimiter protocol. Reported
11075 o Code simplifications and refactoring:
11076 - Stop passing around circuit_t and crypt_path_t pointers that are
11077 implicit in other procedure arguments.
11078 - Drop the old code to choke directory connections when the
11079 corresponding OR connections got full: thanks to the cell queue
11080 feature, OR conns don't get full any more.
11081 - Make dns_resolve() handle attaching connections to circuits
11082 properly, so the caller doesn't have to.
11083 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11084 - Keep the connection array as a dynamic smartlist_t, rather than as
11085 a fixed-sized array. This is important, as the number of connections
11086 is becoming increasingly decoupled from the number of sockets.
11089 Changes in version 0.1.2.14 - 2007-05-25
11090 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11091 change especially affects those who serve or use hidden services),
11092 and fixes several other crash- and security-related bugs.
11094 o Directory authority changes:
11095 - Two directory authorities (moria1 and moria2) just moved to new
11096 IP addresses. This change will particularly affect those who serve
11097 or use hidden services.
11099 o Major bugfixes (crashes):
11100 - If a directory server runs out of space in the connection table
11101 as it's processing a begin_dir request, it will free the exit stream
11102 but leave it attached to the circuit, leading to unpredictable
11103 behavior. (Reported by seeess, fixes bug 425.)
11104 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11105 to corrupt memory under some really unlikely scenarios.
11106 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11107 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11110 o Major bugfixes (security):
11111 - When choosing an entry guard for a circuit, avoid using guards
11112 that are in the same family as the chosen exit -- not just guards
11113 that are exactly the chosen exit. (Reported by lodger.)
11115 o Major bugfixes (resource management):
11116 - If a directory authority is down, skip it when deciding where to get
11117 networkstatus objects or descriptors. Otherwise we keep asking
11118 every 10 seconds forever. Fixes bug 384.
11119 - Count it as a failure if we fetch a valid network-status but we
11120 don't want to keep it. Otherwise we'll keep fetching it and keep
11121 not wanting to keep it. Fixes part of bug 422.
11122 - If all of our dirservers have given us bad or no networkstatuses
11123 lately, then stop hammering them once per minute even when we
11124 think they're failed. Fixes another part of bug 422.
11127 - Actually set the purpose correctly for descriptors inserted with
11128 purpose=controller.
11129 - When we have k non-v2 authorities in our DirServer config,
11130 we ignored the last k authorities in the list when updating our
11132 - Correctly back-off from requesting router descriptors that we are
11133 having a hard time downloading.
11134 - Read resolv.conf files correctly on platforms where read() returns
11135 partial results on small file reads.
11136 - Don't rebuild the entire router store every time we get 32K of
11137 routers: rebuild it when the journal gets very large, or when
11138 the gaps in the store get very large.
11141 - When routers publish SVN revisions in their router descriptors,
11142 authorities now include those versions correctly in networkstatus
11144 - Warn when using a version of libevent before 1.3b to run a server on
11145 OSX or BSD: these versions interact badly with userspace threads.
11148 Changes in version 0.1.2.13 - 2007-04-24
11149 This release features some major anonymity fixes, such as safer path
11150 selection; better client performance; faster bootstrapping, better
11151 address detection, and better DNS support for servers; write limiting as
11152 well as read limiting to make servers easier to run; and a huge pile of
11153 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11155 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11156 of the Freenode IRC network, remembering his patience and vision for
11157 free speech on the Internet.
11160 - Fix a memory leak when we ask for "all" networkstatuses and we
11161 get one we don't recognize.
11162 - Add more asserts to hunt down bug 417.
11163 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11166 Changes in version 0.1.2.12-rc - 2007-03-16
11168 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11169 directory information requested inside Tor connections (i.e. via
11170 begin_dir cells). It only triggered when the same connection was
11171 serving other data at the same time. Reported by seeess.
11174 - When creating a circuit via the controller, send a 'launched'
11175 event when we're done, so we follow the spec better.
11178 Changes in version 0.1.2.11-rc - 2007-03-15
11179 o Minor bugfixes (controller), reported by daejees:
11180 - Correct the control spec to match how the code actually responds
11181 to 'getinfo addr-mappings/*'.
11182 - The control spec described a GUARDS event, but the code
11183 implemented a GUARD event. Standardize on GUARD, but let people
11184 ask for GUARDS too.
11187 Changes in version 0.1.2.10-rc - 2007-03-07
11188 o Major bugfixes (Windows):
11189 - Do not load the NT services library functions (which may not exist)
11190 just to detect if we're a service trying to shut down. Now we run
11191 on Win98 and friends again.
11193 o Minor bugfixes (other):
11194 - Clarify a couple of log messages.
11195 - Fix a misleading socks5 error number.
11198 Changes in version 0.1.2.9-rc - 2007-03-02
11199 o Major bugfixes (Windows):
11200 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11201 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11202 int configuration values: the high-order 32 bits would get
11203 truncated. In particular, we were being bitten by the default
11204 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11205 and maybe also bug 397.)
11207 o Minor bugfixes (performance):
11208 - Use OpenSSL's AES implementation on platforms where it's faster.
11209 This could save us as much as 10% CPU usage.
11211 o Minor bugfixes (server):
11212 - Do not rotate onion key immediately after setting it for the first
11215 o Minor bugfixes (directory authorities):
11216 - Stop calling servers that have been hibernating for a long time
11217 "stable". Also, stop letting hibernating or obsolete servers affect
11218 uptime and bandwidth cutoffs.
11219 - Stop listing hibernating servers in the v1 directory.
11221 o Minor bugfixes (hidden services):
11222 - Upload hidden service descriptors slightly less often, to reduce
11223 load on authorities.
11225 o Minor bugfixes (other):
11226 - Fix an assert that could trigger if a controller quickly set then
11227 cleared EntryNodes. Bug found by Udo van den Heuvel.
11228 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11230 - Fix a potential race condition in the rpm installer. Found by
11232 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11233 of 2 as indicating that the server is completely bad; it sometimes
11234 means that the server is just bad for the request in question. (may fix
11235 the last of bug 326.)
11236 - Disable encrypted directory connections when we don't have a server
11237 descriptor for the destination. We'll get this working again in
11241 Changes in version 0.1.2.8-beta - 2007-02-26
11242 o Major bugfixes (crashes):
11243 - Stop crashing when the controller asks us to resetconf more than
11244 one config option at once. (Vidalia 0.0.11 does this.)
11245 - Fix a crash that happened on Win98 when we're given command-line
11246 arguments: don't try to load NT service functions from advapi32.dll
11247 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11249 - Fix a longstanding obscure crash bug that could occur when
11250 we run out of DNS worker processes. (Resolves bug 390.)
11252 o Major bugfixes (hidden services):
11253 - Correctly detect whether hidden service descriptor downloads are
11254 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11256 o Major bugfixes (accounting):
11257 - When we start during an accounting interval before it's time to wake
11258 up, remember to wake up at the correct time. (May fix bug 342.)
11260 o Minor bugfixes (controller):
11261 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11262 clear the corresponding on_circuit variable, and remember later
11263 that we don't need to send a redundant CLOSED event. Resolves part
11265 - Report events where a resolve succeeded or where we got a socks
11266 protocol error correctly, rather than calling both of them
11268 - Change reported stream target addresses to IP consistently when
11269 we finally get the IP from an exit node.
11270 - Send log messages to the controller even if they happen to be very
11273 o Minor bugfixes (other):
11274 - Display correct results when reporting which versions are
11275 recommended, and how recommended they are. (Resolves bug 383.)
11276 - Improve our estimates for directory bandwidth to be less random:
11277 guess that an unrecognized directory will have the average bandwidth
11278 from all known directories, not that it will have the average
11279 bandwidth from those directories earlier than it on the list.
11280 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11281 and hup, stop triggering an assert based on an empty onion_key.
11282 - On platforms with no working mmap() equivalent, don't warn the
11283 user when cached-routers doesn't exist.
11284 - Warn the user when mmap() [or its equivalent] fails for some reason
11285 other than file-not-found.
11286 - Don't warn the user when cached-routers.new doesn't exist: that's
11287 perfectly fine when starting up for the first time.
11288 - When EntryNodes are configured, rebuild the guard list to contain,
11289 in order: the EntryNodes that were guards before; the rest of the
11290 EntryNodes; the nodes that were guards before.
11291 - Mask out all signals in sub-threads; only the libevent signal
11292 handler should be processing them. This should prevent some crashes
11293 on some machines using pthreads. (Patch from coderman.)
11294 - Fix switched arguments on memset in the implementation of
11295 tor_munmap() for systems with no mmap() call.
11296 - When Tor receives a router descriptor that it asked for, but
11297 no longer wants (because it has received fresh networkstatuses
11298 in the meantime), do not warn the user. Cache the descriptor if
11299 we're a cache; drop it if we aren't.
11300 - Make earlier entry guards _really_ get retried when the network
11302 - On a malformed DNS reply, always give an error to the corresponding
11304 - Build with recent libevents on platforms that do not define the
11305 nonstandard types "u_int8_t" and friends.
11307 o Minor features (controller):
11308 - Warn the user when an application uses the obsolete binary v0
11309 control protocol. We're planning to remove support for it during
11310 the next development series, so it's good to give people some
11312 - Add STREAM_BW events to report per-entry-stream bandwidth
11313 use. (Patch from Robert Hogan.)
11314 - Rate-limit SIGNEWNYM signals in response to controllers that
11315 impolitely generate them for every single stream. (Patch from
11316 mwenge; closes bug 394.)
11317 - Make REMAP stream events have a SOURCE (cache or exit), and
11318 make them generated in every case where we get a successful
11319 connected or resolved cell.
11321 o Minor bugfixes (performance):
11322 - Call router_have_min_dir_info half as often. (This is showing up in
11323 some profiles, but not others.)
11324 - When using GCC, make log_debug never get called at all, and its
11325 arguments never get evaluated, when no debug logs are configured.
11326 (This is showing up in some profiles, but not others.)
11329 - Remove some never-implemented options. Mark PathlenCoinWeight as
11331 - Implement proposal 106: Stop requiring clients to have well-formed
11332 certificates; stop checking nicknames in certificates. (Clients
11333 have certificates so that they can look like Tor servers, but in
11334 the future we might want to allow them to look like regular TLS
11335 clients instead. Nicknames in certificates serve no purpose other
11336 than making our protocol easier to recognize on the wire.)
11337 - Revise messages on handshake failure again to be even more clear about
11338 which are incoming connections and which are outgoing.
11339 - Discard any v1 directory info that's over 1 month old (for
11340 directories) or over 1 week old (for running-routers lists).
11341 - Do not warn when individual nodes in the configuration's EntryNodes,
11342 ExitNodes, etc are down: warn only when all possible nodes
11343 are down. (Fixes bug 348.)
11344 - Always remove expired routers and networkstatus docs before checking
11345 whether we have enough information to build circuits. (Fixes
11347 - Put a lower-bound on MaxAdvertisedBandwidth.
11350 Changes in version 0.1.2.7-alpha - 2007-02-06
11351 o Major bugfixes (rate limiting):
11352 - Servers decline directory requests much more aggressively when
11353 they're low on bandwidth. Otherwise they end up queueing more and
11354 more directory responses, which can't be good for latency.
11355 - But never refuse directory requests from local addresses.
11356 - Fix a memory leak when sending a 503 response for a networkstatus
11358 - Be willing to read or write on local connections (e.g. controller
11359 connections) even when the global rate limiting buckets are empty.
11360 - If our system clock jumps back in time, don't publish a negative
11361 uptime in the descriptor. Also, don't let the global rate limiting
11362 buckets go absurdly negative.
11363 - Flush local controller connection buffers periodically as we're
11364 writing to them, so we avoid queueing 4+ megabytes of data before
11367 o Major bugfixes (NT services):
11368 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11369 command-line flag so that admins can override the default by saying
11370 "tor --service install --user "SomeUser"". This will not affect
11371 existing installed services. Also, warn the user that the service
11372 will look for its configuration file in the service user's
11373 %appdata% directory. (We can't do the 'hardwire the user's appdata
11374 directory' trick any more, since we may not have read access to that
11377 o Major bugfixes (other):
11378 - Previously, we would cache up to 16 old networkstatus documents
11379 indefinitely, if they came from nontrusted authorities. Now we
11380 discard them if they are more than 10 days old.
11381 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11383 - Detect and reject malformed DNS responses containing circular
11385 - If exits are rare enough that we're not marking exits as guards,
11386 ignore exit bandwidth when we're deciding the required bandwidth
11388 - When we're handling a directory connection tunneled over Tor,
11389 don't fill up internal memory buffers with all the data we want
11390 to tunnel; instead, only add it if the OR connection that will
11391 eventually receive it has some room for it. (This can lead to
11392 slowdowns in tunneled dir connections; a better solution will have
11393 to wait for 0.2.0.)
11395 o Minor bugfixes (dns):
11396 - Add some defensive programming to eventdns.c in an attempt to catch
11397 possible memory-stomping bugs.
11398 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11399 an incorrect number of bytes. (Previously, we would ignore the
11401 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11402 in the correct order, and doesn't crash.
11403 - Free memory held in recently-completed DNS lookup attempts on exit.
11404 This was not a memory leak, but may have been hiding memory leaks.
11405 - Handle TTL values correctly on reverse DNS lookups.
11406 - Treat failure to parse resolv.conf as an error.
11408 o Minor bugfixes (other):
11409 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11410 - When computing clock skew from directory HTTP headers, consider what
11411 time it was when we finished asking for the directory, not what
11413 - Expire socks connections if they spend too long waiting for the
11414 handshake to finish. Previously we would let them sit around for
11415 days, if the connecting application didn't close them either.
11416 - And if the socks handshake hasn't started, don't send a
11417 "DNS resolve socks failed" handshake reply; just close it.
11418 - Stop using C functions that OpenBSD's linker doesn't like.
11419 - Don't launch requests for descriptors unless we have networkstatuses
11420 from at least half of the authorities. This delays the first
11421 download slightly under pathological circumstances, but can prevent
11422 us from downloading a bunch of descriptors we don't need.
11423 - Do not log IPs with TLS failures for incoming TLS
11424 connections. (Fixes bug 382.)
11425 - If the user asks to use invalid exit nodes, be willing to use
11427 - Stop using the reserved ac_cv namespace in our configure script.
11428 - Call stat() slightly less often; use fstat() when possible.
11429 - Refactor the way we handle pending circuits when an OR connection
11430 completes or fails, in an attempt to fix a rare crash bug.
11431 - Only rewrite a conn's address based on X-Forwarded-For: headers
11432 if it's a parseable public IP address; and stop adding extra quotes
11433 to the resulting address.
11436 - Weight directory requests by advertised bandwidth. Now we can
11437 let servers enable write limiting but still allow most clients to
11438 succeed at their directory requests. (We still ignore weights when
11439 choosing a directory authority; I hope this is a feature.)
11442 - Create a new file ReleaseNotes which was the old ChangeLog. The
11443 new ChangeLog file now includes the summaries for all development
11445 - Check for addresses with invalid characters at the exit as well
11446 as at the client, and warn less verbosely when they fail. You can
11447 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11448 - Adapt a patch from goodell to let the contrib/exitlist script
11449 take arguments rather than require direct editing.
11450 - Inform the server operator when we decide not to advertise a
11451 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11452 was confusing Zax, so now we're hopefully more helpful.
11453 - Bring us one step closer to being able to establish an encrypted
11454 directory tunnel without knowing a descriptor first. Still not
11455 ready yet. As part of the change, now assume we can use a
11456 create_fast cell if we don't know anything about a router.
11457 - Allow exit nodes to use nameservers running on ports other than 53.
11458 - Servers now cache reverse DNS replies.
11459 - Add an --ignore-missing-torrc command-line option so that we can
11460 get the "use sensible defaults if the configuration file doesn't
11461 exist" behavior even when specifying a torrc location on the command
11464 o Minor features (controller):
11465 - Track reasons for OR connection failure; make these reasons
11466 available via the controller interface. (Patch from Mike Perry.)
11467 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11468 can learn when clients are sending malformed hostnames to Tor.
11469 - Clean up documentation for controller status events.
11470 - Add a REMAP status to stream events to note that a stream's
11471 address has changed because of a cached address or a MapAddress
11475 Changes in version 0.1.2.6-alpha - 2007-01-09
11477 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11478 connection handles more than 4 gigs in either direction, we crash.
11479 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11480 advertised exit node, somebody might try to exit from us when
11481 we're bootstrapping and before we've built our descriptor yet.
11482 Refuse the connection rather than crashing.
11485 - Warn if we (as a server) find that we've resolved an address that we
11486 weren't planning to resolve.
11487 - Warn that using select() on any libevent version before 1.1 will be
11488 unnecessarily slow (even for select()).
11489 - Flush ERR-level controller status events just like we currently
11490 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11491 the controller from learning about current events.
11493 o Minor features (more controller status events):
11494 - Implement EXTERNAL_ADDRESS server status event so controllers can
11495 learn when our address changes.
11496 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11497 can learn when directories reject our descriptor.
11498 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11499 can learn when a client application is speaking a non-socks protocol
11501 - Implement DANGEROUS_SOCKS client status event so controllers
11502 can learn when a client application is leaking DNS addresses.
11503 - Implement BUG general status event so controllers can learn when
11504 Tor is unhappy about its internal invariants.
11505 - Implement CLOCK_SKEW general status event so controllers can learn
11506 when Tor thinks the system clock is set incorrectly.
11507 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11508 server status events so controllers can learn when their descriptors
11509 are accepted by a directory.
11510 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11511 server status events so controllers can learn about Tor's progress in
11512 deciding whether it's reachable from the outside.
11513 - Implement BAD_LIBEVENT general status event so controllers can learn
11514 when we have a version/method combination in libevent that needs to
11516 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11517 and DNS_USELESS server status events so controllers can learn
11518 about changes to DNS server status.
11520 o Minor features (directory):
11521 - Authorities no longer recommend exits as guards if this would shift
11522 too much load to the exit nodes.
11525 Changes in version 0.1.2.5-alpha - 2007-01-06
11527 - Enable write limiting as well as read limiting. Now we sacrifice
11528 capacity if we're pushing out lots of directory traffic, rather
11529 than overrunning the user's intended bandwidth limits.
11530 - Include TLS overhead when counting bandwidth usage; previously, we
11531 would count only the bytes sent over TLS, but not the bytes used
11533 - Support running the Tor service with a torrc not in the same
11534 directory as tor.exe and default to using the torrc located in
11535 the %appdata%\Tor\ of the user who installed the service. Patch
11537 - Servers now check for the case when common DNS requests are going to
11538 wildcarded addresses (i.e. all getting the same answer), and change
11539 their exit policy to reject *:* if it's happening.
11540 - Implement BEGIN_DIR cells, so we can connect to the directory
11541 server via TLS to do encrypted directory requests rather than
11542 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11543 config options if you like.
11545 o Minor features (config and docs):
11546 - Start using the state file to store bandwidth accounting data:
11547 the bw_accounting file is now obsolete. We'll keep generating it
11548 for a while for people who are still using 0.1.2.4-alpha.
11549 - Try to batch changes to the state file so that we do as few
11550 disk writes as possible while still storing important things in
11552 - The state file and the bw_accounting file get saved less often when
11553 the AvoidDiskWrites config option is set.
11554 - Make PIDFile work on Windows (untested).
11555 - Add internal descriptions for a bunch of configuration options:
11556 accessible via controller interface and in comments in saved
11558 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11559 NNTP by default, so this seems like a sensible addition.
11560 - Clients now reject hostnames with invalid characters. This should
11561 avoid some inadvertent info leaks. Add an option
11562 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11563 is running a private network with hosts called @, !, and #.
11564 - Add a maintainer script to tell us which options are missing
11565 documentation: "make check-docs".
11566 - Add a new address-spec.txt document to describe our special-case
11567 addresses: .exit, .onion, and .noconnnect.
11569 o Minor features (DNS):
11570 - Ongoing work on eventdns infrastructure: now it has dns server
11571 and ipv6 support. One day Tor will make use of it.
11572 - Add client-side caching for reverse DNS lookups.
11573 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11574 - When we change nameservers or IP addresses, reset and re-launch
11575 our tests for DNS hijacking.
11577 o Minor features (directory):
11578 - Authorities now specify server versions in networkstatus. This adds
11579 about 2% to the size of compressed networkstatus docs, and allows
11580 clients to tell which servers support BEGIN_DIR and which don't.
11581 The implementation is forward-compatible with a proposed future
11582 protocol version scheme not tied to Tor versions.
11583 - DirServer configuration lines now have an orport= option so
11584 clients can open encrypted tunnels to the authorities without
11585 having downloaded their descriptors yet. Enabled for moria1,
11586 moria2, tor26, and lefkada now in the default configuration.
11587 - Directory servers are more willing to send a 503 "busy" if they
11588 are near their write limit, especially for v1 directory requests.
11589 Now they can use their limited bandwidth for actual Tor traffic.
11590 - Clients track responses with status 503 from dirservers. After a
11591 dirserver has given us a 503, we try not to use it until an hour has
11592 gone by, or until we have no dirservers that haven't given us a 503.
11593 - When we get a 503 from a directory, and we're not a server, we don't
11594 count the failure against the total number of failures allowed
11595 for the thing we're trying to download.
11596 - Report X-Your-Address-Is correctly from tunneled directory
11597 connections; don't report X-Your-Address-Is when it's an internal
11598 address; and never believe reported remote addresses when they're
11600 - Protect against an unlikely DoS attack on directory servers.
11601 - Add a BadDirectory flag to network status docs so that authorities
11602 can (eventually) tell clients about caches they believe to be
11605 o Minor features (controller):
11606 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11607 - Reimplement GETINFO so that info/names stays in sync with the
11609 - Implement "GETINFO fingerprint".
11610 - Implement "SETEVENTS GUARD" so controllers can get updates on
11611 entry guard status as it changes.
11613 o Minor features (clean up obsolete pieces):
11614 - Remove some options that have been deprecated since at least
11615 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11616 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11617 to set log options.
11618 - We no longer look for identity and onion keys in "identity.key" and
11619 "onion.key" -- these were replaced by secret_id_key and
11620 secret_onion_key in 0.0.8pre1.
11621 - We no longer require unrecognized directory entries to be
11624 o Major bugfixes (security):
11625 - Stop sending the HttpProxyAuthenticator string to directory
11626 servers when directory connections are tunnelled through Tor.
11627 - Clients no longer store bandwidth history in the state file.
11628 - Do not log introduction points for hidden services if SafeLogging
11630 - When generating bandwidth history, round down to the nearest
11631 1k. When storing accounting data, round up to the nearest 1k.
11632 - When we're running as a server, remember when we last rotated onion
11633 keys, so that we will rotate keys once they're a week old even if
11634 we never stay up for a week ourselves.
11636 o Major bugfixes (other):
11637 - Fix a longstanding bug in eventdns that prevented the count of
11638 timed-out resolves from ever being reset. This bug caused us to
11639 give up on a nameserver the third time it timed out, and try it
11640 10 seconds later... and to give up on it every time it timed out
11642 - Take out the '5 second' timeout from the connection retry
11643 schedule. Now the first connect attempt will wait a full 10
11644 seconds before switching to a new circuit. Perhaps this will help
11645 a lot. Based on observations from Mike Perry.
11646 - Fix a bug on the Windows implementation of tor_mmap_file() that
11647 would prevent the cached-routers file from ever loading. Reported
11651 - Fix an assert failure when a directory authority sets
11652 AuthDirRejectUnlisted and then receives a descriptor from an
11653 unlisted router. Reported by seeess.
11654 - Avoid a double-free when parsing malformed DirServer lines.
11655 - Fix a bug when a BSD-style PF socket is first used. Patch from
11657 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11658 to resolve an address at a given exit node even when they ask for
11660 - Servers no longer ever list themselves in their "family" line,
11661 even if configured to do so. This makes it easier to configure
11662 family lists conveniently.
11663 - When running as a server, don't fall back to 127.0.0.1 when no
11664 nameservers are configured in /etc/resolv.conf; instead, make the
11665 user fix resolv.conf or specify nameservers explicitly. (Resolves
11667 - Stop accepting certain malformed ports in configured exit policies.
11668 - Don't re-write the fingerprint file every restart, unless it has
11670 - Stop warning when a single nameserver fails: only warn when _all_ of
11671 our nameservers have failed. Also, when we only have one nameserver,
11672 raise the threshold for deciding that the nameserver is dead.
11673 - Directory authorities now only decide that routers are reachable
11674 if their identity keys are as expected.
11675 - When the user uses bad syntax in the Log config line, stop
11676 suggesting other bad syntax as a replacement.
11677 - Correctly detect ipv6 DNS capability on OpenBSD.
11679 o Minor bugfixes (controller):
11680 - Report the circuit number correctly in STREAM CLOSED events. Bug
11681 reported by Mike Perry.
11682 - Do not report bizarre values for results of accounting GETINFOs
11683 when the last second's write or read exceeds the allotted bandwidth.
11684 - Report "unrecognized key" rather than an empty string when the
11685 controller tries to fetch a networkstatus that doesn't exist.
11688 Changes in version 0.1.1.26 - 2006-12-14
11689 o Security bugfixes:
11690 - Stop sending the HttpProxyAuthenticator string to directory
11691 servers when directory connections are tunnelled through Tor.
11692 - Clients no longer store bandwidth history in the state file.
11693 - Do not log introduction points for hidden services if SafeLogging
11697 - Fix an assert failure when a directory authority sets
11698 AuthDirRejectUnlisted and then receives a descriptor from an
11699 unlisted router (reported by seeess).
11702 Changes in version 0.1.2.4-alpha - 2006-12-03
11704 - Add support for using natd; this allows FreeBSDs earlier than
11705 5.1.2 to have ipfw send connections through Tor without using
11706 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11709 - Make all connections to addresses of the form ".noconnect"
11710 immediately get closed. This lets application/controller combos
11711 successfully test whether they're talking to the same Tor by
11712 watching for STREAM events.
11713 - Make cross.sh cross-compilation script work even when autogen.sh
11714 hasn't been run. (Patch from Michael Mohr.)
11715 - Statistics dumped by -USR2 now include a breakdown of public key
11716 operations, for profiling.
11719 - Fix a major leak when directory authorities parse their
11720 approved-routers list, a minor memory leak when we fail to pick
11721 an exit node, and a few rare leaks on errors.
11722 - Handle TransPort connections even when the server sends data before
11723 the client sends data. Previously, the connection would just hang
11724 until the client sent data. (Patch from tup based on patch from
11726 - Avoid assert failure when our cached-routers file is empty on
11730 - Don't log spurious warnings when we see a circuit close reason we
11731 don't recognize; it's probably just from a newer version of Tor.
11732 - Have directory authorities allow larger amounts of drift in uptime
11733 without replacing the server descriptor: previously, a server that
11734 restarted every 30 minutes could have 48 "interesting" descriptors
11736 - Start linking to the Tor specification and Tor reference manual
11737 correctly in the Windows installer.
11738 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11739 Tor/Privoxy we also uninstall Vidalia.
11740 - Resume building on Irix64, and fix a lot of warnings from its
11741 MIPSpro C compiler.
11742 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11743 when we're running as a client.
11746 Changes in version 0.1.1.25 - 2006-11-04
11748 - When a client asks us to resolve (rather than connect to)
11749 an address, and we have a cached answer, give them the cached
11750 answer. Previously, we would give them no answer at all.
11751 - We were building exactly the wrong circuits when we predict
11752 hidden service requirements, meaning Tor would have to build all
11753 its circuits on demand.
11754 - If none of our live entry guards have a high uptime, but we
11755 require a guard with a high uptime, try adding a new guard before
11756 we give up on the requirement. This patch should make long-lived
11757 connections more stable on average.
11758 - When testing reachability of our DirPort, don't launch new
11759 tests when there's already one in progress -- unreachable
11760 servers were stacking up dozens of testing streams.
11762 o Security bugfixes:
11763 - When the user sends a NEWNYM signal, clear the client-side DNS
11764 cache too. Otherwise we continue to act on previous information.
11767 - Avoid a memory corruption bug when creating a hash table for
11769 - Avoid possibility of controller-triggered crash when misusing
11770 certain commands from a v0 controller on platforms that do not
11771 handle printf("%s",NULL) gracefully.
11772 - Avoid infinite loop on unexpected controller input.
11773 - Don't log spurious warnings when we see a circuit close reason we
11774 don't recognize; it's probably just from a newer version of Tor.
11775 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11776 Tor/Privoxy we also uninstall Vidalia.
11779 Changes in version 0.1.2.3-alpha - 2006-10-29
11781 - Prepare for servers to publish descriptors less often: never
11782 discard a descriptor simply for being too old until either it is
11783 recommended by no authorities, or until we get a better one for
11784 the same router. Make caches consider retaining old recommended
11785 routers for even longer.
11786 - If most authorities set a BadExit flag for a server, clients
11787 don't think of it as a general-purpose exit. Clients only consider
11788 authorities that advertise themselves as listing bad exits.
11789 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11790 headers for content, so that we can work better in the presence of
11791 caching HTTP proxies.
11792 - Allow authorities to list nodes as bad exits by fingerprint or by
11795 o Minor features, controller:
11796 - Add a REASON field to CIRC events; for backward compatibility, this
11797 field is sent only to controllers that have enabled the extended
11798 event format. Also, add additional reason codes to explain why
11799 a given circuit has been destroyed or truncated. (Patches from
11801 - Add a REMOTE_REASON field to extended CIRC events to tell the
11802 controller about why a remote OR told us to close a circuit.
11803 - Stream events also now have REASON and REMOTE_REASON fields,
11804 working much like those for circuit events.
11805 - There's now a GETINFO ns/... field so that controllers can ask Tor
11806 about the current status of a router.
11807 - A new event type "NS" to inform a controller when our opinion of
11808 a router's status has changed.
11809 - Add a GETINFO events/names and GETINFO features/names so controllers
11810 can tell which events and features are supported.
11811 - A new CLEARDNSCACHE signal to allow controllers to clear the
11812 client-side DNS cache without expiring circuits.
11814 o Security bugfixes:
11815 - When the user sends a NEWNYM signal, clear the client-side DNS
11816 cache too. Otherwise we continue to act on previous information.
11819 - Avoid sending junk to controllers or segfaulting when a controller
11820 uses EVENT_NEW_DESC with verbose nicknames.
11821 - Stop triggering asserts if the controller tries to extend hidden
11822 service circuits (reported by mwenge).
11823 - Avoid infinite loop on unexpected controller input.
11824 - When the controller does a "GETINFO network-status", tell it
11825 about even those routers whose descriptors are very old, and use
11826 long nicknames where appropriate.
11827 - Change NT service functions to be loaded on demand. This lets us
11828 build with MinGW without breaking Tor for Windows 98 users.
11829 - Do DirPort reachability tests less often, since a single test
11830 chews through many circuits before giving up.
11831 - In the hidden service example in torrc.sample, stop recommending
11832 esoteric and discouraged hidden service options.
11833 - When stopping an NT service, wait up to 10 sec for it to actually
11834 stop. Patch from Matt Edman; resolves bug 295.
11835 - Fix handling of verbose nicknames with ORCONN controller events:
11836 make them show up exactly when requested, rather than exactly when
11838 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
11839 printing a duplicate "$" in the keys we send (reported by mwenge).
11840 - Correctly set maximum connection limit on Cygwin. (This time
11842 - Try to detect Windows correctly when cross-compiling.
11843 - Detect the size of the routers file correctly even if it is
11844 corrupted (on systems without mmap) or not page-aligned (on systems
11845 with mmap). This bug was harmless.
11846 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11847 to open a stream fails; now we do in more cases. This should
11848 make clients able to find a good exit faster in some cases, since
11849 unhandleable requests will now get an error rather than timing out.
11850 - Resolve two memory leaks when rebuilding the on-disk router cache
11851 (reported by fookoowa).
11852 - Clean up minor code warnings suggested by the MIPSpro C compiler,
11853 and reported by some Centos users.
11854 - Controller signals now work on non-Unix platforms that don't define
11855 SIGUSR1 and SIGUSR2 the way we expect.
11856 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
11857 values before failing, and always enables eventdns.
11858 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
11859 Try to fix this in configure.in by checking for most functions
11860 before we check for libevent.
11863 Changes in version 0.1.2.2-alpha - 2006-10-07
11865 - Make our async eventdns library on-by-default for Tor servers,
11866 and plan to deprecate the separate dnsworker threads.
11867 - Add server-side support for "reverse" DNS lookups (using PTR
11868 records so clients can determine the canonical hostname for a given
11869 IPv4 address). Only supported by servers using eventdns; servers
11870 now announce in their descriptors whether they support eventdns.
11871 - Specify and implement client-side SOCKS5 interface for reverse DNS
11872 lookups (see doc/socks-extensions.txt).
11873 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
11874 connect to directory servers through Tor. Previously, clients needed
11875 to find Tor exits to make private connections to directory servers.
11876 - Avoid choosing Exit nodes for entry or middle hops when the
11877 total bandwidth available from non-Exit nodes is much higher than
11878 the total bandwidth available from Exit nodes.
11879 - Workaround for name servers (like Earthlink's) that hijack failing
11880 DNS requests and replace the no-such-server answer with a "helpful"
11881 redirect to an advertising-driven search portal. Also work around
11882 DNS hijackers who "helpfully" decline to hijack known-invalid
11883 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11884 lets you turn it off.
11885 - Send out a burst of long-range padding cells once we've established
11886 that we're reachable. Spread them over 4 circuits, so hopefully
11887 a few will be fast. This exercises our bandwidth and bootstraps
11888 us into the directory more quickly.
11890 o New/improved config options:
11891 - Add new config option "ResolvConf" to let the server operator
11892 choose an alternate resolve.conf file when using eventdns.
11893 - Add an "EnforceDistinctSubnets" option to control our "exclude
11894 servers on the same /16" behavior. It's still on by default; this
11895 is mostly for people who want to operate private test networks with
11896 all the machines on the same subnet.
11897 - If one of our entry guards is on the ExcludeNodes list, or the
11898 directory authorities don't think it's a good guard, treat it as
11899 if it were unlisted: stop using it as a guard, and throw it off
11900 the guards list if it stays that way for a long time.
11901 - Allow directory authorities to be marked separately as authorities
11902 for the v1 directory protocol, the v2 directory protocol, and
11903 as hidden service directories, to make it easier to retire old
11904 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11905 to continue being hidden service authorities too.
11906 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11908 o Minor features, controller:
11909 - Fix CIRC controller events so that controllers can learn the
11910 identity digests of non-Named servers used in circuit paths.
11911 - Let controllers ask for more useful identifiers for servers. Instead
11912 of learning identity digests for un-Named servers and nicknames
11913 for Named servers, the new identifiers include digest, nickname,
11914 and indication of Named status. Off by default; see control-spec.txt
11915 for more information.
11916 - Add a "getinfo address" controller command so it can display Tor's
11917 best guess to the user.
11918 - New controller event to alert the controller when our server
11919 descriptor has changed.
11920 - Give more meaningful errors on controller authentication failure.
11922 o Minor features, other:
11923 - When asked to resolve a hostname, don't use non-exit servers unless
11924 requested to do so. This allows servers with broken DNS to be
11925 useful to the network.
11926 - Divide eventdns log messages into warn and info messages.
11927 - Reserve the nickname "Unnamed" for routers that can't pick
11928 a hostname: any router can call itself Unnamed; directory
11929 authorities will never allocate Unnamed to any particular router;
11930 clients won't believe that any router is the canonical Unnamed.
11931 - Only include function names in log messages for info/debug messages.
11932 For notice/warn/err, the content of the message should be clear on
11933 its own, and printing the function name only confuses users.
11934 - Avoid some false positives during reachability testing: don't try
11935 to test via a server that's on the same /24 as us.
11936 - If we fail to build a circuit to an intended enclave, and it's
11937 not mandatory that we use that enclave, stop wanting it.
11938 - When eventdns is enabled, allow multithreaded builds on NetBSD and
11939 OpenBSD. (We had previously disabled threads on these platforms
11940 because they didn't have working thread-safe resolver functions.)
11942 o Major bugfixes, anonymity/security:
11943 - If a client asked for a server by name, and there's a named server
11944 in our network-status but we don't have its descriptor yet, we
11945 could return an unnamed server instead.
11946 - Fix NetBSD bug that could allow someone to force uninitialized RAM
11947 to be sent to a server's DNS resolver. This only affects NetBSD
11948 and other platforms that do not bounds-check tolower().
11949 - Reject (most) attempts to use Tor circuits with length one. (If
11950 many people start using Tor as a one-hop proxy, exit nodes become
11951 a more attractive target for compromise.)
11952 - Just because your DirPort is open doesn't mean people should be
11953 able to remotely teach you about hidden service descriptors. Now
11954 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11956 o Major bugfixes, other:
11957 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
11958 - When a client asks the server to resolve (not connect to)
11959 an address, and it has a cached answer, give them the cached answer.
11960 Previously, the server would give them no answer at all.
11961 - Allow really slow clients to not hang up five minutes into their
11962 directory downloads (suggested by Adam J. Richter).
11963 - We were building exactly the wrong circuits when we anticipated
11964 hidden service requirements, meaning Tor would have to build all
11965 its circuits on demand.
11966 - Avoid crashing when we mmap a router cache file of size 0.
11967 - When testing reachability of our DirPort, don't launch new
11968 tests when there's already one in progress -- unreachable
11969 servers were stacking up dozens of testing streams.
11971 o Minor bugfixes, correctness:
11972 - If we're a directory mirror and we ask for "all" network status
11973 documents, we would discard status documents from authorities
11974 we don't recognize.
11975 - Avoid a memory corruption bug when creating a hash table for
11977 - Avoid controller-triggered crash when misusing certain commands
11978 from a v0 controller on platforms that do not handle
11979 printf("%s",NULL) gracefully.
11980 - Don't crash when a controller sends a third argument to an
11981 "extendcircuit" request.
11982 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11983 response; fix error code when "getinfo dir/status/" fails.
11984 - Avoid crash when telling controller stream-status and a stream
11986 - Patch from Adam Langley to fix assert() in eventdns.c.
11987 - Fix a debug log message in eventdns to say "X resolved to Y"
11988 instead of "X resolved to X".
11989 - Make eventdns give strings for DNS errors, not just error numbers.
11990 - Track unreachable entry guards correctly: don't conflate
11991 'unreachable by us right now' with 'listed as down by the directory
11992 authorities'. With the old code, if a guard was unreachable by
11993 us but listed as running, it would clog our guard list forever.
11994 - Behave correctly in case we ever have a network with more than
11995 2GB/s total advertised capacity.
11996 - Make TrackExitHosts case-insensitive, and fix the behavior of
11997 ".suffix" TrackExitHosts items to avoid matching in the middle of
11999 - Finally fix the openssl warnings from newer gccs that believe that
12000 ignoring a return value is okay, but casting a return value and
12001 then ignoring it is a sign of madness.
12002 - Prevent the contrib/exitlist script from printing the same
12003 result more than once.
12004 - Patch from Steve Hildrey: Generate network status correctly on
12005 non-versioning dirservers.
12006 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12007 via Tor; otherwise you'll think you're the exit node's IP address.
12009 o Minor bugfixes, performance:
12010 - Two small performance improvements on parsing descriptors.
12011 - Major performance improvement on inserting descriptors: change
12012 algorithm from O(n^2) to O(n).
12013 - Make the common memory allocation path faster on machines where
12014 malloc(0) returns a pointer.
12015 - Start remembering X-Your-Address-Is directory hints even if you're
12016 a client, so you can become a server more smoothly.
12017 - Avoid duplicate entries on MyFamily line in server descriptor.
12019 o Packaging, features:
12020 - Remove architecture from OS X builds. The official builds are
12021 now universal binaries.
12022 - The Debian package now uses --verify-config when (re)starting,
12023 to distinguish configuration errors from other errors.
12024 - Update RPMs to require libevent 1.1b.
12026 o Packaging, bugfixes:
12027 - Patches so Tor builds with MinGW on Windows.
12028 - Patches so Tor might run on Cygwin again.
12029 - Resume building on non-gcc compilers and ancient gcc. Resume
12030 building with the -O0 compile flag. Resume building cleanly on
12032 - Run correctly on OS X platforms with case-sensitive filesystems.
12033 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12034 - Add autoconf checks so Tor can build on Solaris x86 again.
12037 - Documented (and renamed) ServerDNSSearchDomains and
12038 ServerDNSResolvConfFile options.
12039 - Be clearer that the *ListenAddress directives can be repeated
12043 Changes in version 0.1.1.24 - 2006-09-29
12045 - Allow really slow clients to not hang up five minutes into their
12046 directory downloads (suggested by Adam J. Richter).
12047 - Fix major performance regression from 0.1.0.x: instead of checking
12048 whether we have enough directory information every time we want to
12049 do something, only check when the directory information has changed.
12050 This should improve client CPU usage by 25-50%.
12051 - Don't crash if, after a server has been running for a while,
12052 it can't resolve its hostname.
12055 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12056 - Don't crash when the controller receives a third argument to an
12057 "extendcircuit" request.
12058 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12059 response; fix error code when "getinfo dir/status/" fails.
12060 - Fix configure.in to not produce broken configure files with
12061 more recent versions of autoconf. Thanks to Clint for his auto*
12063 - Fix security bug on NetBSD that could allow someone to force
12064 uninitialized RAM to be sent to a server's DNS resolver. This
12065 only affects NetBSD and other platforms that do not bounds-check
12067 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12068 methods: these are known to be buggy.
12069 - If we're a directory mirror and we ask for "all" network status
12070 documents, we would discard status documents from authorities
12071 we don't recognize.
12074 Changes in version 0.1.2.1-alpha - 2006-08-27
12076 - Add "eventdns" async dns library from Adam Langley, tweaked to
12077 build on OSX and Windows. Only enabled if you pass the
12078 --enable-eventdns argument to configure.
12079 - Allow servers with no hostname or IP address to learn their
12080 IP address by asking the directory authorities. This code only
12081 kicks in when you would normally have exited with a "no address"
12082 error. Nothing's authenticated, so use with care.
12083 - Rather than waiting a fixed amount of time between retrying
12084 application connections, we wait only 5 seconds for the first,
12085 10 seconds for the second, and 15 seconds for each retry after
12086 that. Hopefully this will improve the expected user experience.
12087 - Patch from Tup to add support for transparent AP connections:
12088 this basically bundles the functionality of trans-proxy-tor
12089 into the Tor mainline. Now hosts with compliant pf/netfilter
12090 implementations can redirect TCP connections straight to Tor
12091 without diverting through SOCKS. Needs docs.
12092 - Busy directory servers save lots of memory by spooling server
12093 descriptors, v1 directories, and v2 networkstatus docs to buffers
12094 as needed rather than en masse. Also mmap the cached-routers
12095 files, so we don't need to keep the whole thing in memory too.
12096 - Automatically avoid picking more than one node from the same
12097 /16 network when constructing a circuit.
12098 - Revise and clean up the torrc.sample that we ship with; add
12099 a section for BandwidthRate and BandwidthBurst.
12102 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12103 split connection_t into edge, or, dir, control, and base structs.
12104 These will save quite a bit of memory on busy servers, and they'll
12105 also help us track down bugs in the code and bugs in the spec.
12106 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12107 or later. Log when we are doing this, so we can diagnose it when
12108 it fails. (Also, recommend libevent 1.1b for kqueue and
12109 win32 methods; deprecate libevent 1.0b harder; make libevent
12110 recommendation system saner.)
12111 - Start being able to build universal binaries on OS X (thanks
12113 - Export the default exit policy via the control port, so controllers
12114 don't need to guess what it is / will be later.
12115 - Add a man page entry for ProtocolWarnings.
12116 - Add TestVia config option to the man page.
12117 - Remove even more protocol-related warnings from Tor server logs,
12118 such as bad TLS handshakes and malformed begin cells.
12119 - Stop fetching descriptors if you're not a dir mirror and you
12120 haven't tried to establish any circuits lately. [This currently
12121 causes some dangerous behavior, because when you start up again
12122 you'll use your ancient server descriptors.]
12123 - New DirPort behavior: if you have your dirport set, you download
12124 descriptors aggressively like a directory mirror, whether or not
12125 your ORPort is set.
12126 - Get rid of the router_retry_connections notion. Now routers
12127 no longer try to rebuild long-term connections to directory
12128 authorities, and directory authorities no longer try to rebuild
12129 long-term connections to all servers. We still don't hang up
12130 connections in these two cases though -- we need to look at it
12131 more carefully to avoid flapping, and we likely need to wait til
12132 0.1.1.x is obsolete.
12133 - Drop compatibility with obsolete Tors that permit create cells
12134 to have the wrong circ_id_type.
12135 - Re-enable per-connection rate limiting. Get rid of the "OP
12136 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12137 separate global buckets that apply depending on what sort of conn
12139 - Start publishing one minute or so after we find our ORPort
12140 to be reachable. This will help reduce the number of descriptors
12141 we have for ourselves floating around, since it's quite likely
12142 other things (e.g. DirPort) will change during that minute too.
12143 - Fork the v1 directory protocol into its own spec document,
12144 and mark dir-spec.txt as the currently correct (v2) spec.
12147 - When we find our DirPort to be reachable, publish a new descriptor
12148 so we'll tell the world (reported by pnx).
12149 - Publish a new descriptor after we hup/reload. This is important
12150 if our config has changed such that we'll want to start advertising
12151 our DirPort now, etc.
12152 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12153 - When we have a state file we cannot parse, tell the user and
12154 move it aside. Now we avoid situations where the user starts
12155 Tor in 1904, Tor writes a state file with that timestamp in it,
12156 the user fixes her clock, and Tor refuses to start.
12157 - Fix configure.in to not produce broken configure files with
12158 more recent versions of autoconf. Thanks to Clint for his auto*
12160 - "tor --verify-config" now exits with -1(255) or 0 depending on
12161 whether the config options are bad or good.
12162 - Resolve bug 321 when using dnsworkers: append a period to every
12163 address we resolve at the exit node, so that we do not accidentally
12164 pick up local addresses, and so that failing searches are retried
12165 in the resolver search domains. (This is already solved for
12166 eventdns.) (This breaks Blossom servers for now.)
12167 - If we are using an exit enclave and we can't connect, e.g. because
12168 its webserver is misconfigured to not listen on localhost, then
12169 back off and try connecting from somewhere else before we fail.
12172 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12173 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12174 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12175 when the IP address is mapped through MapAddress to a hostname.
12176 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12177 useless IPv6 DNS resolves.
12178 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12179 before we execute the signal, in case the signal shuts us down.
12180 - Clean up AllowInvalidNodes man page entry.
12181 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12182 - Add more asserts to track down an assert error on a windows Tor
12183 server with connection_add being called with socket == -1.
12184 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12185 - Fix misleading log messages: an entry guard that is "unlisted",
12186 as well as not known to be "down" (because we've never heard
12187 of it), is not therefore "up".
12188 - Remove code to special-case "-cvs" ending, since it has not
12189 actually mattered since 0.0.9.
12190 - Make our socks5 handling more robust to broken socks clients:
12191 throw out everything waiting on the buffer in between socks
12192 handshake phases, since they can't possibly (so the theory
12193 goes) have predicted what we plan to respond to them.
12196 Changes in version 0.1.1.23 - 2006-07-30
12198 - Fast Tor servers, especially exit nodes, were triggering asserts
12199 due to a bug in handling the list of pending DNS resolves. Some
12200 bugs still remain here; we're hunting them.
12201 - Entry guards could crash clients by sending unexpected input.
12202 - More fixes on reachability testing: if you find yourself reachable,
12203 then don't ever make any client requests (so you stop predicting
12204 circuits), then hup or have your clock jump, then later your IP
12205 changes, you won't think circuits are working, so you won't try to
12206 test reachability, so you won't publish.
12209 - Avoid a crash if the controller does a resetconf firewallports
12210 and then a setconf fascistfirewall=1.
12211 - Avoid an integer underflow when the dir authority decides whether
12212 a router is stable: we might wrongly label it stable, and compute
12213 a slightly wrong median stability, when a descriptor is published
12215 - Fix a place where we might trigger an assert if we can't build our
12216 own server descriptor yet.
12219 Changes in version 0.1.1.22 - 2006-07-05
12221 - Fix a big bug that was causing servers to not find themselves
12222 reachable if they changed IP addresses. Since only 0.1.1.22+
12223 servers can do reachability testing correctly, now we automatically
12224 make sure to test via one of these.
12225 - Fix to allow clients and mirrors to learn directory info from
12226 descriptor downloads that get cut off partway through.
12227 - Directory authorities had a bug in deciding if a newly published
12228 descriptor was novel enough to make everybody want a copy -- a few
12229 servers seem to be publishing new descriptors many times a minute.
12231 - Fix a rare bug that was causing some servers to complain about
12232 "closing wedged cpuworkers" and skip some circuit create requests.
12233 - Make the Exit flag in directory status documents actually work.
12236 Changes in version 0.1.1.21 - 2006-06-10
12237 o Crash and assert fixes from 0.1.1.20:
12238 - Fix a rare crash on Tor servers that have enabled hibernation.
12239 - Fix a seg fault on startup for Tor networks that use only one
12240 directory authority.
12241 - Fix an assert from a race condition that occurs on Tor servers
12242 while exiting, where various threads are trying to log that they're
12243 exiting, and delete the logs, at the same time.
12244 - Make our unit tests pass again on certain obscure platforms.
12247 - Add support for building SUSE RPM packages.
12248 - Speed up initial bootstrapping for clients: if we are making our
12249 first ever connection to any entry guard, then don't mark it down
12251 - When only one Tor server in the network is labelled as a guard,
12252 and we've already picked him, we would cycle endlessly picking him
12253 again, being unhappy about it, etc. Now we specifically exclude
12254 current guards when picking a new guard.
12255 - Servers send create cells more reliably after the TLS connection
12256 is established: we were sometimes forgetting to send half of them
12257 when we had more than one pending.
12258 - If we get a create cell that asks us to extend somewhere, but the
12259 Tor server there doesn't match the expected digest, we now send
12260 a destroy cell back, rather than silently doing nothing.
12261 - Make options->RedirectExit work again.
12262 - Make cookie authentication for the controller work again.
12263 - Stop being picky about unusual characters in the arguments to
12264 mapaddress. It's none of our business.
12265 - Add a new config option "TestVia" that lets you specify preferred
12266 middle hops to use for test circuits. Perhaps this will let me
12267 debug the reachability problems better.
12269 o Log / documentation fixes:
12270 - If we're a server and some peer has a broken TLS certificate, don't
12271 log about it unless ProtocolWarnings is set, i.e., we want to hear
12272 about protocol violations by others.
12273 - Fix spelling of VirtualAddrNetwork in man page.
12274 - Add a better explanation at the top of the autogenerated torrc file
12275 about what happened to our old torrc.
12278 Changes in version 0.1.1.20 - 2006-05-23
12280 - Downgrade a log severity where servers complain that they're
12282 - Avoid a compile warning on FreeBSD.
12283 - Remove string size limit on NEWDESC messages; solve bug 291.
12284 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12285 more thoroughly when we're running on windows.
12288 Changes in version 0.1.1.19-rc - 2006-05-03
12290 - Regenerate our local descriptor if it's dirty and we try to use
12291 it locally (e.g. if it changes during reachability detection).
12292 - If we setconf our ORPort to 0, we continued to listen on the
12293 old ORPort and receive connections.
12294 - Avoid a second warning about machine/limits.h on Debian
12296 - Be willing to add our own routerinfo into the routerlist.
12297 Now authorities will include themselves in their directories
12298 and network-statuses.
12299 - Stop trying to upload rendezvous descriptors to every
12300 directory authority: only try the v1 authorities.
12301 - Servers no longer complain when they think they're not
12302 registered with the directory authorities. There were too many
12304 - Backport dist-rpm changes so rpms can be built without errors.
12307 - Implement an option, VirtualAddrMask, to set which addresses
12308 get handed out in response to mapaddress requests. This works
12309 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12312 Changes in version 0.1.1.18-rc - 2006-04-10
12314 - Work harder to download live network-statuses from all the
12315 directory authorities we know about. Improve the threshold
12316 decision logic so we're more robust to edge cases.
12317 - When fetching rendezvous descriptors, we were willing to ask
12318 v2 authorities too, which would always return 404.
12321 - Stop listing down or invalid nodes in the v1 directory. This will
12322 reduce its bulk by about 1/3, and reduce load on directory
12324 - When deciding whether a router is Fast or Guard-worthy, consider
12325 his advertised BandwidthRate and not just the BandwidthCapacity.
12326 - No longer ship INSTALL and README files -- they are useless now.
12327 - Force rpmbuild to behave and honor target_cpu.
12328 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12329 - Start to include translated versions of the tor-doc-*.html
12330 files, along with the screenshots. Still needs more work.
12331 - Start sending back 512 and 451 errors if mapaddress fails,
12332 rather than not sending anything back at all.
12333 - When we fail to bind or listen on an incoming or outgoing
12334 socket, we should close it before failing. otherwise we just
12335 leak it. (thanks to weasel for finding.)
12336 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12337 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12338 - Make NoPublish (even though deprecated) work again.
12339 - Fix a minor security flaw where a versioning auth dirserver
12340 could list a recommended version many times in a row to make
12341 clients more convinced that it's recommended.
12342 - Fix crash bug if there are two unregistered servers running
12343 with the same nickname, one of them is down, and you ask for
12344 them by nickname in your EntryNodes or ExitNodes. Also, try
12345 to pick the one that's running rather than an arbitrary one.
12346 - Fix an infinite loop we could hit if we go offline for too long.
12347 - Complain when we hit WSAENOBUFS on recv() or write() too.
12348 Perhaps this will help us hunt the bug.
12349 - If you're not a versioning dirserver, don't put the string
12350 "client-versions \nserver-versions \n" in your network-status.
12351 - Lower the minimum required number of file descriptors to 1000,
12352 so we can have some overhead for Valgrind on Linux, where the
12353 default ulimit -n is 1024.
12356 - Add tor.dizum.com as the fifth authoritative directory server.
12357 - Add a new config option FetchUselessDescriptors, off by default,
12358 for when you plan to run "exitlist" on your client and you want
12359 to know about even the non-running descriptors.
12362 Changes in version 0.1.1.17-rc - 2006-03-28
12364 - Clients and servers since 0.1.1.10-alpha have been expiring
12365 connections whenever they are idle for 5 minutes and they *do*
12366 have circuits on them. Oops. With this new version, clients will
12367 discard their previous entry guard choices and avoid choosing
12368 entry guards running these flawed versions.
12369 - Fix memory leak when uncompressing concatenated zlib streams. This
12370 was causing substantial leaks over time on Tor servers.
12371 - The v1 directory was including servers as much as 48 hours old,
12372 because that's how the new routerlist->routers works. Now only
12373 include them if they're 20 hours old or less.
12376 - Resume building on irix64, netbsd 2.0, etc.
12377 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12379 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12380 and it is confusing some users.
12381 - Mirrors stop caching the v1 directory so often.
12382 - Make the max number of old descriptors that a cache will hold
12383 rise with the number of directory authorities, so we can scale.
12384 - Change our win32 uname() hack to be more forgiving about what
12385 win32 versions it thinks it's found.
12388 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12390 - When the controller's *setconf commands fail, collect an error
12391 message in a string and hand it back to the controller.
12392 - Make the v2 dir's "Fast" flag based on relative capacity, just
12393 like "Stable" is based on median uptime. Name everything in the
12394 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12395 - Log server fingerprint on startup, so new server operators don't
12396 have to go hunting around their filesystem for it.
12397 - Return a robots.txt on our dirport to discourage google indexing.
12398 - Let the controller ask for GETINFO dir/status/foo so it can ask
12399 directly rather than connecting to the dir port. Only works when
12400 dirport is set for now.
12402 o New config options rather than constants in the code:
12403 - SocksTimeout: How long do we let a socks connection wait
12404 unattached before we fail it?
12405 - CircuitBuildTimeout: Cull non-open circuits that were born
12406 at least this many seconds ago.
12407 - CircuitIdleTimeout: Cull open clean circuits that were born
12408 at least this many seconds ago.
12411 Changes in version 0.1.1.16-rc - 2006-03-18
12412 o Bugfixes on 0.1.1.15-rc:
12413 - Fix assert when the controller asks to attachstream a connect-wait
12414 or resolve-wait stream.
12415 - Now do address rewriting when the controller asks us to attach
12416 to a particular circuit too. This will let Blossom specify
12417 "moria2.exit" without having to learn what moria2's IP address is.
12418 - Make the "tor --verify-config" command-line work again, so people
12419 can automatically check if their torrc will parse.
12420 - Authoritative dirservers no longer require an open connection from
12421 a server to consider him "reachable". We need this change because
12422 when we add new auth dirservers, old servers won't know not to
12424 - Let Tor build on Sun CC again.
12425 - Fix an off-by-one buffer size in dirserv.c that magically never
12426 hit our three authorities but broke sjmurdoch's own tor network.
12427 - If we as a directory mirror don't know of any v1 directory
12428 authorities, then don't try to cache any v1 directories.
12429 - Stop warning about unknown servers in our family when they are
12430 given as hex digests.
12431 - Stop complaining as quickly to the server operator that he
12432 hasn't registered his nickname/key binding.
12433 - Various cleanups so we can add new V2 Auth Dirservers.
12434 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12435 reflect the updated flags in our v2 dir protocol.
12436 - Resume allowing non-printable characters for exit streams (both
12437 for connecting and for resolving). Now we tolerate applications
12438 that don't follow the RFCs. But continue to block malformed names
12441 o Bugfixes on 0.1.0.x:
12442 - Fix assert bug in close_logs(): when we close and delete logs,
12443 remove them all from the global "logfiles" list.
12444 - Fix minor integer overflow in calculating when we expect to use up
12445 our bandwidth allocation before hibernating.
12446 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12447 there are multiple SSLs installed with different versions.
12448 - When we try to be a server and Address is not explicitly set and
12449 our hostname resolves to a private IP address, try to use an
12450 interface address if it has a public address. Now Windows machines
12451 that think of themselves as localhost can work by default.
12454 - Let the controller ask for GETINFO dir/server/foo so it can ask
12455 directly rather than connecting to the dir port.
12456 - Let the controller tell us about certain router descriptors
12457 that it doesn't want Tor to use in circuits. Implement
12458 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12459 - New config option SafeSocks to reject all application connections
12460 using unsafe socks protocols. Defaults to off.
12463 Changes in version 0.1.1.15-rc - 2006-03-11
12464 o Bugfixes and cleanups:
12465 - When we're printing strings from the network, don't try to print
12466 non-printable characters. This protects us against shell escape
12467 sequence exploits, and also against attacks to fool humans into
12468 misreading their logs.
12469 - Fix a bug where Tor would fail to establish any connections if you
12470 left it off for 24 hours and then started it: we were happy with
12471 the obsolete network statuses, but they all referred to router
12472 descriptors that were too old to fetch, so we ended up with no
12473 valid router descriptors.
12474 - Fix a seg fault in the controller's "getinfo orconn-status"
12475 command while listing status on incoming handshaking connections.
12476 Introduce a status name "NEW" for these connections.
12477 - If we get a linelist or linelist_s config option from the torrc
12478 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12479 silently resetting it to its default.
12480 - Don't abandon entry guards until they've been down or gone for
12482 - Cleaner and quieter log messages.
12485 - New controller signal NEWNYM that makes new application requests
12486 use clean circuits.
12487 - Add a new circuit purpose 'controller' to let the controller ask
12488 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12489 controller command to let you specify the purpose if you're
12490 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12491 command to let you change a circuit's purpose after it's been
12493 - Accept "private:*" in routerdesc exit policies; not generated yet
12494 because older Tors do not understand it.
12495 - Add BSD-style contributed startup script "rc.subr" from Peter
12499 Changes in version 0.1.1.14-alpha - 2006-02-20
12500 o Bugfixes on 0.1.1.x:
12501 - Don't die if we ask for a stdout or stderr log (even implicitly)
12502 and we're set to RunAsDaemon -- just warn.
12503 - We still had a few bugs in the OR connection rotation code that
12504 caused directory servers to slowly aggregate connections to other
12505 fast Tor servers. This time for sure!
12506 - Make log entries on Win32 include the name of the function again.
12507 - We were treating a pair of exit policies if they were equal even
12508 if one said accept and the other said reject -- causing us to
12509 not always publish a new descriptor since we thought nothing
12511 - Retry pending server downloads as well as pending networkstatus
12512 downloads when we unexpectedly get a socks request.
12513 - We were ignoring the IS_FAST flag in the directory status,
12514 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12516 - If the controller's SAVECONF command fails (e.g. due to file
12517 permissions), let the controller know that it failed.
12520 - If we're trying to be a Tor server and running Windows 95/98/ME
12521 as a server, explain that we'll likely crash.
12522 - When we're a server, a client asks for an old-style directory,
12523 and our write bucket is empty, don't give it to him. This way
12524 small servers can continue to serve the directory *sometimes*,
12525 without getting overloaded.
12526 - Compress exit policies even more -- look for duplicate lines
12528 - Clients now honor the "guard" flag in the router status when
12529 picking entry guards, rather than looking at is_fast or is_stable.
12530 - Retain unrecognized lines in $DATADIR/state file, so that we can
12531 be forward-compatible.
12532 - Generate 18.0.0.0/8 address policy format in descs when we can;
12533 warn when the mask is not reducible to a bit-prefix.
12534 - Let the user set ControlListenAddress in the torrc. This can be
12535 dangerous, but there are some cases (like a secured LAN) where it
12537 - Split ReachableAddresses into ReachableDirAddresses and
12538 ReachableORAddresses, so we can restrict Dir conns to port 80
12539 and OR conns to port 443.
12540 - Now we can target arch and OS in rpm builds (contributed by
12541 Phobos). Also make the resulting dist-rpm filename match the
12543 - New config options to help controllers: FetchServerDescriptors
12544 and FetchHidServDescriptors for whether to fetch server
12545 info and hidserv info or let the controller do it, and
12546 PublishServerDescriptor and PublishHidServDescriptors.
12547 - Also let the controller set the __AllDirActionsPrivate config
12548 option if you want all directory fetches/publishes to happen via
12549 Tor (it assumes your controller bootstraps your circuits).
12552 Changes in version 0.1.0.17 - 2006-02-17
12553 o Crash bugfixes on 0.1.0.x:
12554 - When servers with a non-zero DirPort came out of hibernation,
12555 sometimes they would trigger an assert.
12557 o Other important bugfixes:
12558 - On platforms that don't have getrlimit (like Windows), we were
12559 artificially constraining ourselves to a max of 1024
12560 connections. Now just assume that we can handle as many as 15000
12561 connections. Hopefully this won't cause other problems.
12563 o Backported features:
12564 - When we're a server, a client asks for an old-style directory,
12565 and our write bucket is empty, don't give it to him. This way
12566 small servers can continue to serve the directory *sometimes*,
12567 without getting overloaded.
12568 - Whenever you get a 503 in response to a directory fetch, try
12569 once more. This will become important once servers start sending
12570 503's whenever they feel busy.
12571 - Fetch a new directory every 120 minutes, not every 40 minutes.
12572 Now that we have hundreds of thousands of users running the old
12573 directory algorithm, it's starting to hurt a lot.
12574 - Bump up the period for forcing a hidden service descriptor upload
12575 from 20 minutes to 1 hour.
12578 Changes in version 0.1.1.13-alpha - 2006-02-09
12579 o Crashes in 0.1.1.x:
12580 - When you tried to setconf ORPort via the controller, Tor would
12581 crash. So people using TorCP to become a server were sad.
12582 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12583 servers. The problem appears to be something do with OpenSSL's
12584 random number generation, or how we call it, or something. Let me
12585 know if the crashes continue.
12586 - Turn crypto hardware acceleration off by default, until we find
12587 somebody smart who can test it for us. (It appears to produce
12588 seg faults in at least some cases.)
12589 - Fix a rare assert error when we've tried all intro points for
12590 a hidden service and we try fetching the service descriptor again:
12591 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12594 - Fix a major load balance bug: we were round-robining in 16 KB
12595 chunks, and servers with bandwidthrate of 20 KB, while downloading
12596 a 600 KB directory, would starve their other connections. Now we
12597 try to be a bit more fair.
12598 - Dir authorities and mirrors were never expiring the newest
12599 descriptor for each server, causing memory and directory bloat.
12600 - Fix memory-bloating and connection-bloating bug on servers: We
12601 were never closing any connection that had ever had a circuit on
12602 it, because we were checking conn->n_circuits == 0, yet we had a
12603 bug that let it go negative.
12604 - Make Tor work using squid as your http proxy again -- squid
12605 returns an error if you ask for a URL that's too long, and it uses
12606 a really generic error message. Plus, many people are behind a
12607 transparent squid so they don't even realize it.
12608 - On platforms that don't have getrlimit (like Windows), we were
12609 artificially constraining ourselves to a max of 1024
12610 connections. Now just assume that we can handle as many as 15000
12611 connections. Hopefully this won't cause other problems.
12612 - Add a new config option ExitPolicyRejectPrivate which defaults to
12613 1. This means all exit policies will begin with rejecting private
12614 addresses, unless the server operator explicitly turns it off.
12617 - Clients no longer download descriptors for non-running
12619 - Before we add new directory authorities, we should make it
12620 clear that only v1 authorities should receive/publish hidden
12621 service descriptors.
12624 - As soon as we've fetched some more directory info, immediately
12625 try to download more server descriptors. This way we don't have
12626 a 10 second pause during initial bootstrapping.
12627 - Remove even more loud log messages that the server operator can't
12629 - When we're running an obsolete or un-recommended version, make
12630 the log message more clear about what the problem is and what
12631 versions *are* still recommended.
12632 - Provide a more useful warn message when our onion queue gets full:
12633 the CPU is too slow or the exit policy is too liberal.
12634 - Don't warn when we receive a 503 from a dirserver/cache -- this
12635 will pave the way for them being able to refuse if they're busy.
12636 - When we fail to bind a listener, try to provide a more useful
12637 log message: e.g., "Is Tor already running?"
12638 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12639 Goldberg can prove things about our handshake protocol more
12641 - MaxConn has been obsolete for a while now. Document the ConnLimit
12642 config option, which is a *minimum* number of file descriptors
12643 that must be available else Tor refuses to start.
12644 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12645 if you log to syslog and want something other than LOG_DAEMON.
12646 - Make dirservers generate a separate "guard" flag to mean,
12647 "would make a good entry guard". Make clients parse it and vote
12648 on it. Not used by clients yet.
12649 - Implement --with-libevent-dir option to ./configure. Also, improve
12650 search techniques to find libevent, and use those for openssl too.
12651 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12652 - Only start testing reachability once we've established a
12653 circuit. This will make startup on dirservers less noisy.
12654 - Don't try to upload hidden service descriptors until we have
12655 established a circuit.
12656 - Fix the controller's "attachstream 0" command to treat conn like
12657 it just connected, doing address remapping, handling .exit and
12658 .onion idioms, and so on. Now we're more uniform in making sure
12659 that the controller hears about new and closing connections.
12662 Changes in version 0.1.1.12-alpha - 2006-01-11
12663 o Bugfixes on 0.1.1.x:
12664 - The fix to close duplicate server connections was closing all
12665 Tor client connections if they didn't establish a circuit
12666 quickly enough. Oops.
12667 - Fix minor memory issue (double-free) that happened on exit.
12669 o Bugfixes on 0.1.0.x:
12670 - Tor didn't warn when it failed to open a log file.
12673 Changes in version 0.1.1.11-alpha - 2006-01-10
12674 o Crashes in 0.1.1.x:
12675 - Include all the assert/crash fixes from 0.1.0.16.
12676 - If you start Tor and then quit very quickly, there were some
12677 races that tried to free things that weren't allocated yet.
12678 - Fix a rare memory stomp if you're running hidden services.
12679 - Fix segfault when specifying DirServer in config without nickname.
12680 - Fix a seg fault when you finish connecting to a server but at
12681 that moment you dump his server descriptor.
12682 - Extendcircuit and Attachstream controller commands would
12683 assert/crash if you don't give them enough arguments.
12684 - Fix an assert error when we're out of space in the connection_list
12685 and we try to post a hidden service descriptor (reported by weasel).
12686 - If you specify a relative torrc path and you set RunAsDaemon in
12687 your torrc, then it chdir()'s to the new directory. If you HUP,
12688 it tries to load the new torrc location, fails, and exits.
12689 The fix: no longer allow a relative path to torrc using -f.
12692 - Implement "entry guards": automatically choose a handful of entry
12693 nodes and stick with them for all circuits. Only pick new guards
12694 when the ones you have are unsuitable, and if the old guards
12695 become suitable again, switch back. This will increase security
12696 dramatically against certain end-point attacks. The EntryNodes
12697 config option now provides some hints about which entry guards you
12698 want to use most; and StrictEntryNodes means to only use those.
12699 - New directory logic: download by descriptor digest, not by
12700 fingerprint. Caches try to download all listed digests from
12701 authorities; clients try to download "best" digests from caches.
12702 This avoids partitioning and isolating attacks better.
12703 - Make the "stable" router flag in network-status be the median of
12704 the uptimes of running valid servers, and make clients pay
12705 attention to the network-status flags. Thus the cutoff adapts
12706 to the stability of the network as a whole, making IRC, IM, etc
12707 connections more reliable.
12710 - Tor servers with dynamic IP addresses were needing to wait 18
12711 hours before they could start doing reachability testing using
12712 the new IP address and ports. This is because they were using
12713 the internal descriptor to learn what to test, yet they were only
12714 rebuilding the descriptor once they decided they were reachable.
12715 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12716 to download certain server descriptors, throw them away, and then
12717 fetch them again after 30 minutes. Now mirrors throw away these
12718 server descriptors so clients can't get them.
12719 - We were leaving duplicate connections to other ORs open for a week,
12720 rather than closing them once we detect a duplicate. This only
12721 really affected authdirservers, but it affected them a lot.
12722 - Spread the authdirservers' reachability testing over the entire
12723 testing interval, so we don't try to do 500 TLS's at once every
12727 - If the network is down, and we try to connect to a conn because
12728 we have a circuit in mind, and we timeout (30 seconds) because the
12729 network never answers, we were expiring the circuit, but we weren't
12730 obsoleting the connection or telling the entry_guards functions.
12731 - Some Tor servers process billions of cells per day. These statistics
12732 need to be uint64_t's.
12733 - Check for integer overflows in more places, when adding elements
12734 to smartlists. This could possibly prevent a buffer overflow
12735 on malicious huge inputs. I don't see any, but I haven't looked
12737 - ReachableAddresses kept growing new "reject *:*" lines on every
12739 - When you "setconf log" via the controller, it should remove all
12740 logs. We were automatically adding back in a "log notice stdout".
12741 - Newly bootstrapped Tor networks couldn't establish hidden service
12742 circuits until they had nodes with high uptime. Be more tolerant.
12743 - We were marking servers down when they could not answer every piece
12744 of the directory request we sent them. This was far too harsh.
12745 - Fix the torify (tsocks) config file to not use Tor for localhost
12747 - Directory authorities now go to the proper authority when asking for
12748 a networkstatus, even when they want a compressed one.
12749 - Fix a harmless bug that was causing Tor servers to log
12750 "Got an end because of misc error, but we're not an AP. Closing."
12751 - Authorities were treating their own descriptor changes as cosmetic,
12752 meaning the descriptor available in the network-status and the
12753 descriptor that clients downloaded were different.
12754 - The OS X installer was adding a symlink for tor_resolve but
12755 the binary was called tor-resolve (reported by Thomas Hardly).
12756 - Workaround a problem with some http proxies where they refuse GET
12757 requests that specify "Content-Length: 0" (reported by Adrian).
12758 - Fix wrong log message when you add a "HiddenServiceNodes" config
12759 line without any HiddenServiceDir line (reported by Chris Thomas).
12762 - Write the TorVersion into the state file so we have a prayer of
12763 keeping forward and backward compatibility.
12764 - Revive the FascistFirewall config option rather than eliminating it:
12765 now it's a synonym for ReachableAddresses *:80,*:443.
12766 - Clients choose directory servers from the network status lists,
12767 not from their internal list of router descriptors. Now they can
12768 go to caches directly rather than needing to go to authorities
12770 - Directory authorities ignore router descriptors that have only
12771 cosmetic differences: do this for 0.1.0.x servers now too.
12772 - Add a new flag to network-status indicating whether the server
12773 can answer v2 directory requests too.
12774 - Authdirs now stop whining so loudly about bad descriptors that
12775 they fetch from other dirservers. So when there's a log complaint,
12776 it's for sure from a freshly uploaded descriptor.
12777 - Reduce memory requirements in our structs by changing the order
12779 - There used to be two ways to specify your listening ports in a
12780 server descriptor: on the "router" line and with a separate "ports"
12781 line. Remove support for the "ports" line.
12782 - New config option "AuthDirRejectUnlisted" for auth dirservers as
12783 a panic button: if we get flooded with unusable servers we can
12784 revert to only listing servers in the approved-routers file.
12785 - Auth dir servers can now mark a fingerprint as "!reject" or
12786 "!invalid" in the approved-routers file (as its nickname), to
12787 refuse descriptors outright or include them but marked as invalid.
12788 - Servers store bandwidth history across restarts/crashes.
12789 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12790 get a better idea of why their circuits failed. Not used yet.
12791 - Directory mirrors now cache up to 16 unrecognized network-status
12792 docs. Now we can add new authdirservers and they'll be cached too.
12793 - When picking a random directory, prefer non-authorities if any
12795 - New controller option "getinfo desc/all-recent" to fetch the
12796 latest server descriptor for every router that Tor knows about.
12799 Changes in version 0.1.0.16 - 2006-01-02
12800 o Crash bugfixes on 0.1.0.x:
12801 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12802 corrupting the heap, losing FDs, or crashing when we need to resize
12803 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12804 - It turns out sparc64 platforms crash on unaligned memory access
12805 too -- so detect and avoid this.
12806 - Handle truncated compressed data correctly (by detecting it and
12808 - Fix possible-but-unlikely free(NULL) in control.c.
12809 - When we were closing connections, there was a rare case that
12810 stomped on memory, triggering seg faults and asserts.
12811 - Avoid potential infinite recursion when building a descriptor. (We
12812 don't know that it ever happened, but better to fix it anyway.)
12813 - We were neglecting to unlink marked circuits from soon-to-close OR
12814 connections, which caused some rare scribbling on freed memory.
12815 - Fix a memory stomping race bug when closing the joining point of two
12816 rendezvous circuits.
12817 - Fix an assert in time parsing found by Steven Murdoch.
12819 o Other bugfixes on 0.1.0.x:
12820 - When we're doing reachability testing, provide more useful log
12821 messages so the operator knows what to expect.
12822 - Do not check whether DirPort is reachable when we are suppressing
12823 advertising it because of hibernation.
12824 - When building with -static or on Solaris, we sometimes needed -ldl.
12825 - When we're deciding whether a stream has enough circuits around
12826 that can handle it, count the freshly dirty ones and not the ones
12827 that are so dirty they won't be able to handle it.
12828 - When we're expiring old circuits, we had a logic error that caused
12829 us to close new rendezvous circuits rather than old ones.
12830 - Give a more helpful log message when you try to change ORPort via
12831 the controller: you should upgrade Tor if you want that to work.
12832 - We were failing to parse Tor versions that start with "Tor ".
12833 - Tolerate faulty streams better: when a stream fails for reason
12834 exitpolicy, stop assuming that the router is lying about his exit
12835 policy. When a stream fails for reason misc, allow it to retry just
12836 as if it was resolvefailed. When a stream has failed three times,
12837 reset its failure count so we can try again and get all three tries.
12840 Changes in version 0.1.1.10-alpha - 2005-12-11
12841 o Correctness bugfixes on 0.1.0.x:
12842 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12843 corrupting the heap, losing FDs, or crashing when we need to resize
12844 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12845 - Stop doing the complex voodoo overkill checking for insecure
12846 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12847 - When we were closing connections, there was a rare case that
12848 stomped on memory, triggering seg faults and asserts.
12849 - We were neglecting to unlink marked circuits from soon-to-close OR
12850 connections, which caused some rare scribbling on freed memory.
12851 - When we're deciding whether a stream has enough circuits around
12852 that can handle it, count the freshly dirty ones and not the ones
12853 that are so dirty they won't be able to handle it.
12854 - Recover better from TCP connections to Tor servers that are
12855 broken but don't tell you (it happens!); and rotate TLS
12856 connections once a week.
12857 - When we're expiring old circuits, we had a logic error that caused
12858 us to close new rendezvous circuits rather than old ones.
12859 - Fix a scary-looking but apparently harmless bug where circuits
12860 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12861 servers, and never switch to state CIRCUIT_STATE_OPEN.
12862 - When building with -static or on Solaris, we sometimes needed to
12864 - Give a useful message when people run Tor as the wrong user,
12865 rather than telling them to start chowning random directories.
12866 - We were failing to inform the controller about new .onion streams.
12868 o Security bugfixes on 0.1.0.x:
12869 - Refuse server descriptors if the fingerprint line doesn't match
12870 the included identity key. Tor doesn't care, but other apps (and
12871 humans) might actually be trusting the fingerprint line.
12872 - We used to kill the circuit when we receive a relay command we
12873 don't recognize. Now we just drop it.
12874 - Start obeying our firewall options more rigorously:
12875 . If we can't get to a dirserver directly, try going via Tor.
12876 . Don't ever try to connect (as a client) to a place our
12877 firewall options forbid.
12878 . If we specify a proxy and also firewall options, obey the
12879 firewall options even when we're using the proxy: some proxies
12880 can only proxy to certain destinations.
12881 - Fix a bug found by Lasse Overlier: when we were making internal
12882 circuits (intended to be cannibalized later for rendezvous and
12883 introduction circuits), we were picking them so that they had
12884 useful exit nodes. There was no need for this, and it actually
12885 aids some statistical attacks.
12886 - Start treating internal circuits and exit circuits separately.
12887 It's important to keep them separate because internal circuits
12888 have their last hops picked like middle hops, rather than like
12889 exit hops. So exiting on them will break the user's expectations.
12891 o Bugfixes on 0.1.1.x:
12892 - Take out the mis-feature where we tried to detect IP address
12893 flapping for people with DynDNS, and chose not to upload a new
12894 server descriptor sometimes.
12895 - Try to be compatible with OpenSSL 0.9.6 again.
12896 - Log fix: when the controller is logging about .onion addresses,
12897 sometimes it didn't include the ".onion" part of the address.
12898 - Don't try to modify options->DirServers internally -- if the
12899 user didn't specify any, just add the default ones directly to
12900 the trusted dirserver list. This fixes a bug where people running
12901 controllers would use SETCONF on some totally unrelated config
12902 option, and Tor would start yelling at them about changing their
12904 - Let the controller's redirectstream command specify a port, in
12905 case the controller wants to change that too.
12906 - When we requested a pile of server descriptors, we sometimes
12907 accidentally launched a duplicate request for the first one.
12908 - Bugfix for trackhostexits: write down the fingerprint of the
12909 chosen exit, not its nickname, because the chosen exit might not
12911 - When parsing foo.exit, if foo is unknown, and we are leaving
12912 circuits unattached, set the chosen_exit field and leave the
12913 address empty. This matters because controllers got confused
12915 - Directory authorities no longer try to download server
12916 descriptors that they know they will reject.
12918 o Features and updates:
12919 - Replace balanced trees with hash tables: this should make stuff
12920 significantly faster.
12921 - Resume using the AES counter-mode implementation that we ship,
12922 rather than OpenSSL's. Ours is significantly faster.
12923 - Many other CPU and memory improvements.
12924 - Add a new config option FastFirstHopPK (on by default) so clients
12925 do a trivial crypto handshake for their first hop, since TLS has
12926 already taken care of confidentiality and authentication.
12927 - Add a new config option TestSocks so people can see if their
12928 applications are using socks4, socks4a, socks5-with-ip, or
12929 socks5-with-hostname. This way they don't have to keep mucking
12930 with tcpdump and wondering if something got cached somewhere.
12931 - Warn when listening on a public address for socks. I suspect a
12932 lot of people are setting themselves up as open socks proxies,
12933 and they have no idea that jerks on the Internet are using them,
12934 since they simply proxy the traffic into the Tor network.
12935 - Add "private:*" as an alias in configuration for policies. Now
12936 you can simplify your exit policy rather than needing to list
12937 every single internal or nonroutable network space.
12938 - Add a new controller event type that allows controllers to get
12939 all server descriptors that were uploaded to a router in its role
12940 as authoritative dirserver.
12941 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12942 tor-doc-server.html, and stylesheet.css in the tarball.
12943 - Stop shipping tor-doc.html in the tarball.
12946 Changes in version 0.1.1.9-alpha - 2005-11-15
12947 o Usability improvements:
12948 - Start calling it FooListenAddress rather than FooBindAddress,
12949 since few of our users know what it means to bind an address
12951 - Reduce clutter in server logs. We're going to try to make
12952 them actually usable now. New config option ProtocolWarnings that
12953 lets you hear about how _other Tors_ are breaking the protocol. Off
12955 - Divide log messages into logging domains. Once we put some sort
12956 of interface on this, it will let people looking at more verbose
12957 log levels specify the topics they want to hear more about.
12958 - Make directory servers return better http 404 error messages
12959 instead of a generic "Servers unavailable".
12960 - Check for even more Windows version flags when writing the platform
12961 string in server descriptors, and note any we don't recognize.
12962 - Clean up more of the OpenSSL memory when exiting, so we can detect
12963 memory leaks better.
12964 - Make directory authorities be non-versioning, non-naming by
12965 default. Now we can add new directory servers without requiring
12966 their operators to pay close attention.
12967 - When logging via syslog, include the pid whenever we provide
12968 a log entry. Suggested by Todd Fries.
12970 o Performance improvements:
12971 - Directory servers now silently throw away new descriptors that
12972 haven't changed much if the timestamps are similar. We do this to
12973 tolerate older Tor servers that upload a new descriptor every 15
12974 minutes. (It seemed like a good idea at the time.)
12975 - Inline bottleneck smartlist functions; use fast versions by default.
12976 - Add a "Map from digest to void*" abstraction digestmap_t so we
12977 can do less hex encoding/decoding. Use it in router_get_by_digest()
12978 to resolve a performance bottleneck.
12979 - Allow tor_gzip_uncompress to extract as much as possible from
12980 truncated compressed data. Try to extract as many
12981 descriptors as possible from truncated http responses (when
12982 DIR_PURPOSE_FETCH_ROUTERDESC).
12983 - Make circ->onionskin a pointer, not a static array. moria2 was using
12984 125000 circuit_t's after it had been up for a few weeks, which
12985 translates to 20+ megs of wasted space.
12986 - The private half of our EDH handshake keys are now chosen out
12987 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
12989 o Security improvements:
12990 - Start making directory caches retain old routerinfos, so soon
12991 clients can start asking by digest of descriptor rather than by
12992 fingerprint of server.
12993 - Add half our entropy from RAND_poll in OpenSSL. This knows how
12994 to use egd (if present), openbsd weirdness (if present), vms/os2
12995 weirdness (if we ever port there), and more in the future.
12997 o Bugfixes on 0.1.0.x:
12998 - Do round-robin writes of at most 16 kB per write. This might be
12999 more fair on loaded Tor servers, and it might resolve our Windows
13000 crash bug. It might also slow things down.
13001 - Our TLS handshakes were generating a single public/private
13002 keypair for the TLS context, rather than making a new one for
13003 each new connections. Oops. (But we were still rotating them
13004 periodically, so it's not so bad.)
13005 - When we were cannibalizing a circuit with a particular exit
13006 node in mind, we weren't checking to see if that exit node was
13007 already present earlier in the circuit. Oops.
13008 - When a Tor server's IP changes (e.g. from a dyndns address),
13009 upload a new descriptor so clients will learn too.
13010 - Really busy servers were keeping enough circuits open on stable
13011 connections that they were wrapping around the circuit_id
13012 space. (It's only two bytes.) This exposed a bug where we would
13013 feel free to reuse a circuit_id even if it still exists but has
13014 been marked for close. Try to fix this bug. Some bug remains.
13015 - If we would close a stream early (e.g. it asks for a .exit that
13016 we know would refuse it) but the LeaveStreamsUnattached config
13017 option is set by the controller, then don't close it.
13019 o Bugfixes on 0.1.1.8-alpha:
13020 - Fix a big pile of memory leaks, some of them serious.
13021 - Do not try to download a routerdesc if we would immediately reject
13023 - Resume inserting a newline between all router descriptors when
13024 generating (old style) signed directories, since our spec says
13026 - When providing content-type application/octet-stream for
13027 server descriptors using .z, we were leaving out the
13028 content-encoding header. Oops. (Everything tolerated this just
13029 fine, but that doesn't mean we need to be part of the problem.)
13030 - Fix a potential seg fault in getconf and getinfo using version 1
13031 of the controller protocol.
13032 - Avoid crash: do not check whether DirPort is reachable when we
13033 are suppressing it because of hibernation.
13034 - Make --hash-password not crash on exit.
13037 Changes in version 0.1.1.8-alpha - 2005-10-07
13038 o New features (major):
13039 - Clients don't download or use the directory anymore. Now they
13040 download and use network-statuses from the trusted dirservers,
13041 and fetch individual server descriptors as needed from mirrors.
13042 See dir-spec.txt for all the gory details.
13043 - Be more conservative about whether to advertise our DirPort.
13044 The main change is to not advertise if we're running at capacity
13045 and either a) we could hibernate or b) our capacity is low and
13046 we're using a default DirPort.
13047 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13049 o New features (minor):
13050 - Try to be smart about when to retry network-status and
13051 server-descriptor fetches. Still needs some tuning.
13052 - Stop parsing, storing, or using running-routers output (but
13053 mirrors still cache and serve it).
13054 - Consider a threshold of versioning dirservers (dirservers who have
13055 an opinion about which Tor versions are still recommended) before
13056 deciding whether to warn the user that he's obsolete.
13057 - Dirservers can now reject/invalidate by key and IP, with the
13058 config options "AuthDirInvalid" and "AuthDirReject". This is
13059 useful since currently we automatically list servers as running
13060 and usable even if we know they're jerks.
13061 - Provide dire warnings to any users who set DirServer; move it out
13062 of torrc.sample and into torrc.complete.
13063 - Add MyFamily to torrc.sample in the server section.
13064 - Add nicknames to the DirServer line, so we can refer to them
13065 without requiring all our users to memorize their IP addresses.
13066 - When we get an EOF or a timeout on a directory connection, note
13067 how many bytes of serverdesc we are dropping. This will help
13068 us determine whether it is smart to parse incomplete serverdesc
13070 - Add a new function to "change pseudonyms" -- that is, to stop
13071 using any currently-dirty circuits for new streams, so we don't
13072 link new actions to old actions. Currently it's only called on
13073 HUP (or SIGNAL RELOAD).
13074 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13075 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13076 OpenSSL. Also, reseed our entropy every hour, not just at
13077 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13079 o Fixes on 0.1.1.7-alpha:
13080 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13081 version 0, so don't let version 0 controllers ask for it.
13082 - If you requested something with too many newlines via the
13083 v1 controller protocol, you could crash tor.
13084 - Fix a number of memory leaks, including some pretty serious ones.
13085 - Re-enable DirPort testing again, so Tor servers will be willing
13086 to advertise their DirPort if it's reachable.
13087 - On TLS handshake, only check the other router's nickname against
13088 its expected nickname if is_named is set.
13090 o Fixes forward-ported from 0.1.0.15:
13091 - Don't crash when we don't have any spare file descriptors and we
13092 try to spawn a dns or cpu worker.
13093 - Make the numbers in read-history and write-history into uint64s,
13094 so they don't overflow and publish negatives in the descriptor.
13096 o Fixes on 0.1.0.x:
13097 - For the OS X package's modified privoxy config file, comment
13098 out the "logfile" line so we don't log everything passed
13100 - We were whining about using socks4 or socks5-with-local-lookup
13101 even when it's an IP in the "virtual" range we designed exactly
13103 - We were leaking some memory every time the client changes IPs.
13104 - Never call free() on tor_malloc()d memory. This will help us
13105 use dmalloc to detect memory leaks.
13106 - Check for named servers when looking them up by nickname;
13107 warn when we'recalling a non-named server by its nickname;
13108 don't warn twice about the same name.
13109 - Try to list MyFamily elements by key, not by nickname, and warn
13110 if we've not heard of the server.
13111 - Make windows platform detection (uname equivalent) smarter.
13112 - It turns out sparc64 doesn't like unaligned access either.
13115 Changes in version 0.1.0.15 - 2005-09-23
13116 o Bugfixes on 0.1.0.x:
13117 - Reject ports 465 and 587 (spam targets) in default exit policy.
13118 - Don't crash when we don't have any spare file descriptors and we
13119 try to spawn a dns or cpu worker.
13120 - Get rid of IgnoreVersion undocumented config option, and make us
13121 only warn, never exit, when we're running an obsolete version.
13122 - Don't try to print a null string when your server finds itself to
13123 be unreachable and the Address config option is empty.
13124 - Make the numbers in read-history and write-history into uint64s,
13125 so they don't overflow and publish negatives in the descriptor.
13126 - Fix a minor memory leak in smartlist_string_remove().
13127 - We were only allowing ourselves to upload a server descriptor at
13128 most every 20 minutes, even if it changed earlier than that.
13129 - Clean up log entries that pointed to old URLs.
13132 Changes in version 0.1.1.7-alpha - 2005-09-14
13133 o Fixes on 0.1.1.6-alpha:
13134 - Exit servers were crashing when people asked them to make a
13135 connection to an address not in their exit policy.
13136 - Looking up a non-existent stream for a v1 control connection would
13138 - Fix a seg fault if we ask a dirserver for a descriptor by
13139 fingerprint but he doesn't know about him.
13140 - SETCONF was appending items to linelists, not clearing them.
13141 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13142 out and refuse the setconf if it would fail.
13143 - Downgrade the dirserver log messages when whining about
13147 - Add Peter Palfrader's check-tor script to tor/contrib/
13148 It lets you easily check whether a given server (referenced by
13149 nickname) is reachable by you.
13150 - Numerous changes to move towards client-side v2 directories. Not
13153 o Fixes on 0.1.0.x:
13154 - If the user gave tor an odd number of command-line arguments,
13155 we were silently ignoring the last one. Now we complain and fail.
13156 [This wins the oldest-bug prize -- this bug has been present since
13157 November 2002, as released in Tor 0.0.0.]
13158 - Do not use unaligned memory access on alpha, mips, or mipsel.
13159 It *works*, but is very slow, so we treat them as if it doesn't.
13160 - Retry directory requests if we fail to get an answer we like
13161 from a given dirserver (we were retrying before, but only if
13162 we fail to connect).
13163 - When writing the RecommendedVersions line, sort them first.
13164 - When the client asked for a rendezvous port that the hidden
13165 service didn't want to provide, we were sending an IP address
13166 back along with the end cell. Fortunately, it was zero. But stop
13168 - Correct "your server is reachable" log entries to indicate that
13169 it was self-testing that told us so.
13172 Changes in version 0.1.1.6-alpha - 2005-09-09
13173 o Fixes on 0.1.1.5-alpha:
13174 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13175 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13176 - Fix bug with tor_memmem finding a match at the end of the string.
13177 - Make unit tests run without segfaulting.
13178 - Resolve some solaris x86 compile warnings.
13179 - Handle duplicate lines in approved-routers files without warning.
13180 - Fix bug where as soon as a server refused any requests due to his
13181 exit policy (e.g. when we ask for localhost and he tells us that's
13182 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13183 exit policy using him for any exits.
13184 - Only do openssl hardware accelerator stuff if openssl version is
13187 o New controller features/fixes:
13188 - Add a "RESETCONF" command so you can set config options like
13189 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13190 a config option in the torrc with no value, then it clears it
13191 entirely (rather than setting it to its default).
13192 - Add a "GETINFO config-file" to tell us where torrc is.
13193 - Avoid sending blank lines when GETINFO replies should be empty.
13194 - Add a QUIT command for the controller (for using it manually).
13195 - Fix a bug in SAVECONF that was adding default dirservers and
13196 other redundant entries to the torrc file.
13198 o Start on the new directory design:
13199 - Generate, publish, cache, serve new network-status format.
13200 - Publish individual descriptors (by fingerprint, by "all", and by
13202 - Publish client and server recommended versions separately.
13203 - Allow tor_gzip_uncompress() to handle multiple concatenated
13204 compressed strings. Serve compressed groups of router
13205 descriptors. The compression logic here could be more
13207 - Distinguish v1 authorities (all currently trusted directories)
13208 from v2 authorities (all trusted directories).
13209 - Change DirServers config line to note which dirs are v1 authorities.
13210 - Add configuration option "V1AuthoritativeDirectory 1" which
13211 moria1, moria2, and tor26 should set.
13212 - Remove option when getting directory cache to see whether they
13213 support running-routers; they all do now. Replace it with one
13214 to see whether caches support v2 stuff.
13217 - Dirservers now do their own external reachability testing of each
13218 Tor server, and only list them as running if they've been found to
13219 be reachable. We also send back warnings to the server's logs if
13220 it uploads a descriptor that we already believe is unreachable.
13221 - Implement exit enclaves: if we know an IP address for the
13222 destination, and there's a running Tor server at that address
13223 which allows exit to the destination, then extend the circuit to
13224 that exit first. This provides end-to-end encryption and end-to-end
13225 authentication. Also, if the user wants a .exit address or enclave,
13226 use 4 hops rather than 3, and cannibalize a general circ for it
13228 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13229 controller. Also, rotate dns and cpu workers if the controller
13230 changes options that will affect them; and initialize the dns
13231 worker cache tree whether or not we start out as a server.
13232 - Only upload a new server descriptor when options change, 18
13233 hours have passed, uptime is reset, or bandwidth changes a lot.
13234 - Check [X-]Forwarded-For headers in HTTP requests when generating
13235 log messages. This lets people run dirservers (and caches) behind
13236 Apache but still know which IP addresses are causing warnings.
13238 o Config option changes:
13239 - Replace (Fascist)Firewall* config options with a new
13240 ReachableAddresses option that understands address policies.
13241 For example, "ReachableAddresses *:80,*:443"
13242 - Get rid of IgnoreVersion undocumented config option, and make us
13243 only warn, never exit, when we're running an obsolete version.
13244 - Make MonthlyAccountingStart config option truly obsolete now.
13246 o Fixes on 0.1.0.x:
13247 - Reject ports 465 and 587 in the default exit policy, since
13248 people have started using them for spam too.
13249 - It turns out we couldn't bootstrap a network since we added
13250 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13251 has never gone down. Add an AssumeReachable config option to let
13252 servers and dirservers bootstrap. When we're trying to build a
13253 high-uptime or high-bandwidth circuit but there aren't enough
13254 suitable servers, try being less picky rather than simply failing.
13255 - Our logic to decide if the OR we connected to was the right guy
13256 was brittle and maybe open to a mitm for unverified routers.
13257 - We weren't cannibalizing circuits correctly for
13258 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13259 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13260 build those from scratch. This should make hidden services faster.
13261 - Predict required circuits better, with an eye toward making hidden
13262 services faster on the service end.
13263 - Retry streams if the exit node sends back a 'misc' failure. This
13264 should result in fewer random failures. Also, after failing
13265 from resolve failed or misc, reset the num failures, so we give
13266 it a fair shake next time we try.
13267 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13268 - Reduce severity on logs about dns worker spawning and culling.
13269 - When we're shutting down and we do something like try to post a
13270 server descriptor or rendezvous descriptor, don't complain that
13271 we seem to be unreachable. Of course we are, we're shutting down.
13272 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13273 We don't use them yet, but maybe one day our DNS resolver will be
13274 able to discover them.
13275 - Make ContactInfo mandatory for authoritative directory servers.
13276 - Require server descriptors to list IPv4 addresses -- hostnames
13277 are no longer allowed. This also fixes some potential security
13278 problems with people providing hostnames as their address and then
13279 preferentially resolving them to partition users.
13280 - Change log line for unreachability to explicitly suggest /etc/hosts
13281 as the culprit. Also make it clearer what IP address and ports we're
13282 testing for reachability.
13283 - Put quotes around user-supplied strings when logging so users are
13284 more likely to realize if they add bad characters (like quotes)
13286 - Let auth dir servers start without specifying an Address config
13288 - Make unit tests (and other invocations that aren't the real Tor)
13289 run without launching listeners, creating subdirectories, and so on.
13292 Changes in version 0.1.1.5-alpha - 2005-08-08
13293 o Bugfixes included in 0.1.0.14.
13295 o Bugfixes on 0.1.0.x:
13296 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13297 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13298 it would silently using ignore the 6668.
13301 Changes in version 0.1.0.14 - 2005-08-08
13302 o Bugfixes on 0.1.0.x:
13303 - Fix the other half of the bug with crypto handshakes
13305 - Fix an assert trigger if you send a 'signal term' via the
13306 controller when it's listening for 'event info' messages.
13309 Changes in version 0.1.1.4-alpha - 2005-08-04
13310 o Bugfixes included in 0.1.0.13.
13313 - Improve tor_gettimeofday() granularity on windows.
13314 - Make clients regenerate their keys when their IP address changes.
13315 - Implement some more GETINFO goodness: expose helper nodes, config
13316 options, getinfo keys.
13319 Changes in version 0.1.0.13 - 2005-08-04
13320 o Bugfixes on 0.1.0.x:
13321 - Fix a critical bug in the security of our crypto handshakes.
13322 - Fix a size_t underflow in smartlist_join_strings2() that made
13323 it do bad things when you hand it an empty smartlist.
13324 - Fix Windows installer to ship Tor license (thanks to Aphex for
13325 pointing out this oversight) and put a link to the doc directory
13327 - Explicitly set no-unaligned-access for sparc: it turns out the
13328 new gcc's let you compile broken code, but that doesn't make it
13332 Changes in version 0.1.1.3-alpha - 2005-07-23
13333 o Bugfixes on 0.1.1.2-alpha:
13334 - Fix a bug in handling the controller's "post descriptor"
13336 - Fix several bugs in handling the controller's "extend circuit"
13338 - Fix a bug in handling the controller's "stream status" event.
13339 - Fix an assert failure if we have a controller listening for
13340 circuit events and we go offline.
13341 - Re-allow hidden service descriptors to publish 0 intro points.
13342 - Fix a crash when generating your hidden service descriptor if
13343 you don't have enough intro points already.
13345 o New features on 0.1.1.2-alpha:
13346 - New controller function "getinfo accounting", to ask how
13347 many bytes we've used in this time period.
13348 - Experimental support for helper nodes: a lot of the risk from
13349 a small static adversary comes because users pick new random
13350 nodes every time they rebuild a circuit. Now users will try to
13351 stick to the same small set of entry nodes if they can. Not
13352 enabled by default yet.
13354 o Bugfixes on 0.1.0.12:
13355 - If you're an auth dir server, always publish your dirport,
13356 even if you haven't yet found yourself to be reachable.
13357 - Fix a size_t underflow in smartlist_join_strings2() that made
13358 it do bad things when you hand it an empty smartlist.
13361 Changes in version 0.1.0.12 - 2005-07-18
13362 o New directory servers:
13363 - tor26 has changed IP address.
13365 o Bugfixes on 0.1.0.x:
13366 - Fix a possible double-free in tor_gzip_uncompress().
13367 - When --disable-threads is set, do not search for or link against
13368 pthreads libraries.
13369 - Don't trigger an assert if an authoritative directory server
13370 claims its dirport is 0.
13371 - Fix bug with removing Tor as an NT service: some people were
13372 getting "The service did not return an error." Thanks to Matt
13376 Changes in version 0.1.1.2-alpha - 2005-07-15
13377 o New directory servers:
13378 - tor26 has changed IP address.
13380 o Bugfixes on 0.1.0.x, crashes/leaks:
13381 - Port the servers-not-obeying-their-exit-policies fix from
13383 - Fix an fd leak in start_daemon().
13384 - On Windows, you can't always reopen a port right after you've
13385 closed it. So change retry_listeners() to only close and re-open
13386 ports that have changed.
13387 - Fix a possible double-free in tor_gzip_uncompress().
13389 o Bugfixes on 0.1.0.x, usability:
13390 - When tor_socketpair() fails in Windows, give a reasonable
13391 Windows-style errno back.
13392 - Let people type "tor --install" as well as "tor -install" when
13394 want to make it an NT service.
13395 - NT service patch from Matt Edman to improve error messages.
13396 - When the controller asks for a config option with an abbreviated
13397 name, give the full name in our response.
13398 - Correct the man page entry on TrackHostExitsExpire.
13399 - Looks like we were never delivering deflated (i.e. compressed)
13400 running-routers lists, even when asked. Oops.
13401 - When --disable-threads is set, do not search for or link against
13402 pthreads libraries.
13404 o Bugfixes on 0.1.1.x:
13405 - Fix a seg fault with autodetecting which controller version is
13409 - New hidden service descriptor format: put a version in it, and
13410 let people specify introduction/rendezvous points that aren't
13411 in "the directory" (which is subjective anyway).
13412 - Allow the DEBUG controller event to work again. Mark certain log
13413 entries as "don't tell this to controllers", so we avoid cycles.
13416 Changes in version 0.1.0.11 - 2005-06-30
13417 o Bugfixes on 0.1.0.x:
13418 - Fix major security bug: servers were disregarding their
13419 exit policies if clients behaved unexpectedly.
13420 - Make OS X init script check for missing argument, so we don't
13421 confuse users who invoke it incorrectly.
13422 - Fix a seg fault in "tor --hash-password foo".
13423 - The MAPADDRESS control command was broken.
13426 Changes in version 0.1.1.1-alpha - 2005-06-29
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 - Fix a possible way to DoS dirservers.
13432 - When we complain that your exit policy implicitly allows local or
13433 private address spaces, name them explicitly so operators can
13435 - Make the log message less scary when all the dirservers are
13436 temporarily unreachable.
13437 - We were printing the number of idle dns workers incorrectly when
13441 - Revised controller protocol (version 1) that uses ascii rather
13442 than binary. Add supporting libraries in python and java so you
13443 can use the controller from your applications without caring how
13444 our protocol works.
13445 - Spiffy new support for crypto hardware accelerators. Can somebody
13449 Changes in version 0.0.9.10 - 2005-06-16
13450 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13451 - Refuse relay cells that claim to have a length larger than the
13452 maximum allowed. This prevents a potential attack that could read
13453 arbitrary memory (e.g. keys) from an exit server's process
13457 Changes in version 0.1.0.10 - 2005-06-14
13458 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13459 libevent before 1.1a.
13462 Changes in version 0.1.0.9-rc - 2005-06-09
13464 - Reset buf->highwater every time buf_shrink() is called, not just on
13465 a successful shrink. This was causing significant memory bloat.
13466 - Fix buffer overflow when checking hashed passwords.
13467 - Security fix: if seeding the RNG on Win32 fails, quit.
13468 - Allow seeding the RNG on Win32 even when you're not running as
13470 - Disable threading on Solaris too. Something is wonky with it,
13471 cpuworkers, and reentrant libs.
13472 - Reenable the part of the code that tries to flush as soon as an
13473 OR outbuf has a full TLS record available. Perhaps this will make
13474 OR outbufs not grow as huge except in rare cases, thus saving lots
13475 of CPU time plus memory.
13476 - Reject malformed .onion addresses rather then passing them on as
13477 normal web requests.
13478 - Adapt patch from Adam Langley: fix possible memory leak in
13479 tor_lookup_hostname().
13480 - Initialize libevent later in the startup process, so the logs are
13481 already established by the time we start logging libevent warns.
13482 - Use correct errno on win32 if libevent fails.
13483 - Check and warn about known-bad/slow libevent versions.
13484 - Pay more attention to the ClientOnly config option.
13485 - Have torctl.in/tor.sh.in check for location of su binary (needed
13487 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13488 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13489 HttpProxyAuthenticator
13490 - Stop warning about sigpipes in the logs. We're going to
13491 pretend that getting these occassionally is normal and fine.
13492 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13494 installer screens; and don't put stuff into StartupItems unless
13495 the user asks you to.
13496 - Require servers that use the default dirservers to have public IP
13497 addresses. We have too many servers that are configured with private
13498 IPs and their admins never notice the log entries complaining that
13499 their descriptors are being rejected.
13500 - Add OSX uninstall instructions. An actual uninstall script will
13504 Changes in version 0.1.0.8-rc - 2005-05-23
13506 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13507 panics. Disable kqueue on all OS X Tors.
13508 - Fix RPM: remove duplicate line accidentally added to the rpm
13510 - Disable threads on openbsd too, since its gethostaddr is not
13512 - Tolerate libevent 0.8 since it still works, even though it's
13514 - Enable building on Red Hat 9.0 again.
13515 - Allow the middle hop of the testing circuit to be running any
13516 version, now that most of them have the bugfix to let them connect
13517 to unknown servers. This will allow reachability testing to work
13518 even when 0.0.9.7-0.0.9.9 become obsolete.
13519 - Handle relay cells with rh.length too large. This prevents
13520 a potential attack that could read arbitrary memory (maybe even
13521 keys) from the exit server's process.
13522 - We screwed up the dirport reachability testing when we don't yet
13523 have a cached version of the directory. Hopefully now fixed.
13524 - Clean up router_load_single_router() (used by the controller),
13525 so it doesn't seg fault on error.
13526 - Fix a minor memory leak when somebody establishes an introduction
13527 point at your Tor server.
13528 - If a socks connection ends because read fails, don't warn that
13529 you're not sending a socks reply back.
13532 - Add HttpProxyAuthenticator config option too, that works like
13533 the HttpsProxyAuthenticator config option.
13534 - Encode hashed controller passwords in hex instead of base64,
13535 to make it easier to write controllers.
13538 Changes in version 0.1.0.7-rc - 2005-05-17
13540 - Fix a bug in the OS X package installer that prevented it from
13541 installing on Tiger.
13542 - Fix a script bug in the OS X package installer that made it
13543 complain during installation.
13544 - Find libevent even if it's hiding in /usr/local/ and your
13545 CFLAGS and LDFLAGS don't tell you to look there.
13546 - Be able to link with libevent as a shared library (the default
13547 after 1.0d), even if it's hiding in /usr/local/lib and even
13548 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13549 assuming you're running gcc. Otherwise fail and give a useful
13551 - Fix a bug in the RPM packager: set home directory for _tor to
13552 something more reasonable when first installing.
13553 - Free a minor amount of memory that is still reachable on exit.
13556 Changes in version 0.1.0.6-rc - 2005-05-14
13558 - Implement --disable-threads configure option. Disable threads on
13559 netbsd by default, because it appears to have no reentrant resolver
13561 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13562 release (1.1) detects and disables kqueue if it's broken.
13563 - Append default exit policy before checking for implicit internal
13564 addresses. Now we don't log a bunch of complaints on startup
13565 when using the default exit policy.
13566 - Some people were putting "Address " in their torrc, and they had
13567 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13568 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13569 LOCALSTATEDIR/tor instead.
13570 - Fix fragmented-message bug in TorControl.py.
13571 - Resolve a minor bug which would prevent unreachable dirports
13572 from getting suppressed in the published descriptor.
13573 - When the controller gave us a new descriptor, we weren't resolving
13574 it immediately, so Tor would think its address was 0.0.0.0 until
13575 we fetched a new directory.
13576 - Fix an uppercase/lowercase case error in suppressing a bogus
13577 libevent warning on some Linuxes.
13580 - Begin scrubbing sensitive strings from logs by default. Turn off
13581 the config option SafeLogging if you need to do debugging.
13582 - Switch to a new buffer management algorithm, which tries to avoid
13583 reallocing and copying quite as much. In first tests it looks like
13584 it uses *more* memory on average, but less cpu.
13585 - First cut at support for "create-fast" cells. Clients can use
13586 these when extending to their first hop, since the TLS already
13587 provides forward secrecy and authentication. Not enabled on
13589 - When dirservers refuse a router descriptor, we now log its
13590 contactinfo, platform, and the poster's IP address.
13591 - Call tor_free_all instead of connections_free_all after forking, to
13592 save memory on systems that need to fork.
13593 - Whine at you if you're a server and you don't set your contactinfo.
13594 - Implement --verify-config command-line option to check if your torrc
13595 is valid without actually launching Tor.
13596 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13597 rather than just rejecting it.
13600 Changes in version 0.1.0.5-rc - 2005-04-27
13602 - Stop trying to print a null pointer if an OR conn fails because
13603 we didn't like its cert.
13605 - Switch our internal buffers implementation to use a ring buffer,
13606 to hopefully improve performance for fast servers a lot.
13607 - Add HttpsProxyAuthenticator support (basic auth only), based
13608 on patch from Adam Langley.
13609 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13610 the fast servers that have been joining lately.
13611 - Give hidden service accesses extra time on the first attempt,
13612 since 60 seconds is often only barely enough. This might improve
13614 - Improve performance for dirservers: stop re-parsing the whole
13615 directory every time you regenerate it.
13616 - Add more debugging info to help us find the weird dns freebsd
13617 pthreads bug; cleaner debug messages to help track future issues.
13620 Changes in version 0.0.9.9 - 2005-04-23
13621 o Bugfixes on 0.0.9.x:
13622 - If unofficial Tor clients connect and send weird TLS certs, our
13623 Tor server triggers an assert. This release contains a minimal
13624 backport from the broader fix that we put into 0.1.0.4-rc.
13627 Changes in version 0.1.0.4-rc - 2005-04-23
13629 - If unofficial Tor clients connect and send weird TLS certs, our
13630 Tor server triggers an assert. Stop asserting, and start handling
13631 TLS errors better in other situations too.
13632 - When the controller asks us to tell it about all the debug-level
13633 logs, it turns out we were generating debug-level logs while
13634 telling it about them, which turns into a bad loop. Now keep
13635 track of whether you're sending a debug log to the controller,
13636 and don't log when you are.
13637 - Fix the "postdescriptor" feature of the controller interface: on
13638 non-complete success, only say "done" once.
13640 - Clients are now willing to load balance over up to 2mB, not 1mB,
13641 of advertised bandwidth capacity.
13642 - Add a NoPublish config option, so you can be a server (e.g. for
13643 testing running Tor servers in other Tor networks) without
13644 publishing your descriptor to the primary dirservers.
13647 Changes in version 0.1.0.3-rc - 2005-04-08
13648 o Improvements on 0.1.0.2-rc:
13649 - Client now retries when streams end early for 'hibernating' or
13650 'resource limit' reasons, rather than failing them.
13651 - More automated handling for dirserver operators:
13652 - Automatically approve nodes running 0.1.0.2-rc or later,
13653 now that the the reachability detection stuff is working.
13654 - Now we allow two unverified servers with the same nickname
13655 but different keys. But if a nickname is verified, only that
13656 nickname+key are allowed.
13657 - If you're an authdirserver connecting to an address:port,
13658 and it's not the OR you were expecting, forget about that
13659 descriptor. If he *was* the one you were expecting, then forget
13660 about all other descriptors for that address:port.
13661 - Allow servers to publish descriptors from 12 hours in the future.
13662 Corollary: only whine about clock skew from the dirserver if
13663 he's a trusted dirserver (since now even verified servers could
13664 have quite wrong clocks).
13665 - Adjust maximum skew and age for rendezvous descriptors: let skew
13666 be 48 hours rather than 90 minutes.
13667 - Efficiency improvements:
13668 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13669 it much faster to look up a circuit for each relay cell.
13670 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13671 since they're eating our cpu on exit nodes.
13672 - Stop wasting time doing a case insensitive comparison for every
13673 dns name every time we do any lookup. Canonicalize the names to
13674 lowercase and be done with it.
13675 - Start sending 'truncated' cells back rather than destroy cells,
13676 if the circuit closes in front of you. This means we won't have
13677 to abandon partially built circuits.
13678 - Only warn once per nickname from add_nickname_list_to_smartlist
13679 per failure, so an entrynode or exitnode choice that's down won't
13681 - Put a note in the torrc about abuse potential with the default
13683 - Revise control spec and implementation to allow all log messages to
13684 be sent to controller with their severities intact (suggested by
13685 Matt Edman). Update TorControl to handle new log event types.
13686 - Provide better explanation messages when controller's POSTDESCRIPTOR
13688 - Stop putting nodename in the Platform string in server descriptors.
13689 It doesn't actually help, and it is confusing/upsetting some people.
13691 o Bugfixes on 0.1.0.2-rc:
13692 - We were printing the host mask wrong in exit policies in server
13693 descriptors. This isn't a critical bug though, since we were still
13694 obeying the exit policy internally.
13695 - Fix Tor when compiled with libevent but without pthreads: move
13696 connection_unregister() from _connection_free() to
13698 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13699 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13700 when we look through the connection array, we'll find any of the
13701 cpu/dnsworkers. This is no good.
13703 o Bugfixes on 0.0.9.8:
13704 - Fix possible bug on threading platforms (e.g. win32) which was
13705 leaking a file descriptor whenever a cpuworker or dnsworker died.
13706 - When using preferred entry or exit nodes, ignore whether the
13707 circuit wants uptime or capacity. They asked for the nodes, they
13709 - chdir() to your datadirectory at the *end* of the daemonize process,
13710 not the beginning. This was a problem because the first time you
13711 run tor, if your datadir isn't there, and you have runasdaemon set
13712 to 1, it will try to chdir to it before it tries to create it. Oops.
13713 - Handle changed router status correctly when dirserver reloads
13714 fingerprint file. We used to be dropping all unverified descriptors
13715 right then. The bug was hidden because we would immediately
13716 fetch a directory from another dirserver, which would include the
13717 descriptors we just dropped.
13718 - When we're connecting to an OR and he's got a different nickname/key
13719 than we were expecting, only complain loudly if we're an OP or a
13720 dirserver. Complaining loudly to the OR admins just confuses them.
13721 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13722 artificially capped at 500kB.
13725 Changes in version 0.0.9.8 - 2005-04-07
13726 o Bugfixes on 0.0.9.x:
13727 - We have a bug that I haven't found yet. Sometimes, very rarely,
13728 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13729 thinks of itself as idle. This meant that no new circuits ever got
13730 established. Here's a workaround to kill any cpuworker that's been
13731 busy for more than 100 seconds.
13734 Changes in version 0.1.0.2-rc - 2005-04-01
13735 o Bugfixes on 0.1.0.1-rc:
13736 - Fixes on reachability detection:
13737 - Don't check for reachability while hibernating.
13738 - If ORPort is reachable but DirPort isn't, still publish the
13739 descriptor, but zero out DirPort until it's found reachable.
13740 - When building testing circs for ORPort testing, use only
13741 high-bandwidth nodes, so fewer circuits fail.
13742 - Complain about unreachable ORPort separately from unreachable
13743 DirPort, so the user knows what's going on.
13744 - Make sure we only conclude ORPort reachability if we didn't
13745 initiate the conn. Otherwise we could falsely conclude that
13746 we're reachable just because we connected to the guy earlier
13747 and he used that same pipe to extend to us.
13748 - Authdirservers shouldn't do ORPort reachability detection,
13749 since they're in clique mode, so it will be rare to find a
13750 server not already connected to them.
13751 - When building testing circuits, always pick middle hops running
13752 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13753 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13755 - When we decide we're reachable, actually publish our descriptor
13757 - Fix bug in redirectstream in the controller.
13758 - Fix the state descriptor strings so logs don't claim edge streams
13759 are in a different state than they actually are.
13760 - Use recent libevent features when possible (this only really affects
13761 win32 and osx right now, because the new libevent with these
13762 features hasn't been released yet). Add code to suppress spurious
13764 - Prevent possible segfault in connection_close_unattached_ap().
13765 - Fix newlines on torrc in win32.
13766 - Improve error msgs when tor-resolve fails.
13768 o Improvements on 0.0.9.x:
13769 - New experimental script tor/contrib/ExerciseServer.py (needs more
13770 work) that uses the controller interface to build circuits and
13771 fetch pages over them. This will help us bootstrap servers that
13772 have lots of capacity but haven't noticed it yet.
13773 - New experimental script tor/contrib/PathDemo.py (needs more work)
13774 that uses the controller interface to let you choose whole paths
13776 "<hostname>.<path,separated by dots>.<length of path>.path"
13777 - When we've connected to an OR and handshaked but didn't like
13778 the result, we were closing the conn without sending destroy
13779 cells back for pending circuits. Now send those destroys.
13782 Changes in version 0.0.9.7 - 2005-04-01
13783 o Bugfixes on 0.0.9.x:
13784 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13785 - Compare identity to identity, not to nickname, when extending to
13786 a router not already in the directory. This was preventing us from
13787 extending to unknown routers. Oops.
13788 - Make sure to create OS X Tor user in <500 range, so we aren't
13789 creating actual system users.
13790 - Note where connection-that-hasn't-sent-end was marked, and fix
13791 a few really loud instances of this harmless bug (it's fixed more
13795 Changes in version 0.1.0.1-rc - 2005-03-28
13797 - Add reachability testing. Your Tor server will automatically try
13798 to see if its ORPort and DirPort are reachable from the outside,
13799 and it won't upload its descriptor until it decides they are.
13800 - Handle unavailable hidden services better. Handle slow or busy
13801 hidden services better.
13802 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13804 - New exit policy: accept most low-numbered ports, rather than
13805 rejecting most low-numbered ports.
13806 - More Tor controller support (still experimental). See
13807 http://tor.eff.org/doc/control-spec.txt for all the new features,
13808 including signals to emulate unix signals from any platform;
13809 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13810 closestream; closecircuit; etc.
13811 - Make nt services work and start on startup on win32 (based on
13812 patch by Matt Edman).
13813 - Add a new AddressMap config directive to rewrite incoming socks
13814 addresses. This lets you, for example, declare an implicit
13815 required exit node for certain sites.
13816 - Add a new TrackHostExits config directive to trigger addressmaps
13817 for certain incoming socks addresses -- for sites that break when
13818 your exit keeps changing (based on patch by Mike Perry).
13819 - Redo the client-side dns cache so it's just an addressmap too.
13820 - Notice when our IP changes, and reset stats/uptime/reachability.
13821 - When an application is using socks5, give him the whole variety of
13822 potential socks5 responses (connect refused, host unreachable, etc),
13823 rather than just "success" or "failure".
13824 - A more sane version numbering system. See
13825 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13826 - New contributed script "exitlist": a simple python script to
13827 parse directories and find Tor nodes that exit to listed
13829 - New contributed script "privoxy-tor-toggle" to toggle whether
13830 Privoxy uses Tor. Seems to be configured for Debian by default.
13831 - Report HTTP reasons to client when getting a response from directory
13832 servers -- so you can actually know what went wrong.
13833 - New config option MaxAdvertisedBandwidth which lets you advertise
13834 a low bandwidthrate (to not attract as many circuits) while still
13835 allowing a higher bandwidthrate in reality.
13837 o Robustness/stability fixes:
13838 - Make Tor use Niels Provos's libevent instead of its current
13839 poll-but-sometimes-select mess. This will let us use faster async
13840 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
13842 - pthread support now too. This was forced because when we forked,
13843 we ended up wasting a lot of duplicate ram over time. Also switch
13844 to foo_r versions of some library calls to allow reentry and
13846 - Better handling for heterogeneous / unreliable nodes:
13847 - Annotate circuits w/ whether they aim to contain high uptime nodes
13848 and/or high capacity nodes. When building circuits, choose
13850 - This means that every single node in an intro rend circuit,
13851 not just the last one, will have a minimum uptime.
13852 - New config option LongLivedPorts to indicate application streams
13853 that will want high uptime circuits.
13854 - Servers reset uptime when a dir fetch entirely fails. This
13855 hopefully reflects stability of the server's network connectivity.
13856 - If somebody starts his tor server in Jan 2004 and then fixes his
13857 clock, don't make his published uptime be a year.
13858 - Reset published uptime when you wake up from hibernation.
13859 - Introduce a notion of 'internal' circs, which are chosen without
13860 regard to the exit policy of the last hop. Intro and rendezvous
13861 circs must be internal circs, to avoid leaking information. Resolve
13862 and connect streams can use internal circs if they want.
13863 - New circuit pooling algorithm: make sure to have enough circs around
13864 to satisfy any predicted ports, and also make sure to have 2 internal
13865 circs around if we've required internal circs lately (and with high
13866 uptime if we've seen that lately too).
13867 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13868 which describes how often we retry making new circuits if current
13869 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13870 how long we're willing to make use of an already-dirty circuit.
13871 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13872 circ as necessary, if there are any completed ones lying around
13873 when we try to launch one.
13874 - Make hidden services try to establish a rendezvous for 30 seconds,
13875 rather than for n (where n=3) attempts to build a circuit.
13876 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
13877 "ShutdownWaitLength".
13878 - Try to be more zealous about calling connection_edge_end when
13879 things go bad with edge conns in connection.c.
13880 - Revise tor-spec to add more/better stream end reasons.
13881 - Revise all calls to connection_edge_end to avoid sending "misc",
13882 and to take errno into account where possible.
13885 - Fix a race condition that can trigger an assert, when we have a
13886 pending create cell and an OR connection fails right then.
13887 - Fix several double-mark-for-close bugs, e.g. where we were finding
13888 a conn for a cell even if that conn is already marked for close.
13889 - Make sequence of log messages when starting on win32 with no config
13890 file more reasonable.
13891 - When choosing an exit node for a new non-internal circ, don't take
13892 into account whether it'll be useful for any pending x.onion
13893 addresses -- it won't.
13894 - Turn addr_policy_compare from a tristate to a quadstate; this should
13895 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13896 for google.com" problem.
13897 - Make "platform" string in descriptor more accurate for Win32 servers,
13898 so it's not just "unknown platform".
13899 - Fix an edge case in parsing config options (thanks weasel).
13900 If they say "--" on the commandline, it's not an option.
13901 - Reject odd-looking addresses at the client (e.g. addresses that
13902 contain a colon), rather than having the server drop them because
13904 - tor-resolve requests were ignoring .exit if there was a working circuit
13905 they could use instead.
13906 - REUSEADDR on normal platforms means you can rebind to the port
13907 right after somebody else has let it go. But REUSEADDR on win32
13908 means to let you bind to the port _even when somebody else
13909 already has it bound_! So, don't do that on Win32.
13910 - Change version parsing logic: a version is "obsolete" if it is not
13911 recommended and (1) there is a newer recommended version in the
13912 same series, or (2) there are no recommended versions in the same
13913 series, but there are some recommended versions in a newer series.
13914 A version is "new" if it is newer than any recommended version in
13916 - Stop most cases of hanging up on a socks connection without sending
13920 - Require BandwidthRate to be at least 20kB/s for servers.
13921 - When a dirserver causes you to give a warn, mention which dirserver
13923 - New config option DirAllowPrivateAddresses for authdirservers.
13924 Now by default they refuse router descriptors that have non-IP or
13925 private-IP addresses.
13926 - Stop publishing socksport in the directory, since it's not
13927 actually meant to be public. For compatibility, publish a 0 there
13929 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13930 smart" value, that is low for servers and high for clients.
13931 - If our clock jumps forward by 100 seconds or more, assume something
13932 has gone wrong with our network and abandon all not-yet-used circs.
13933 - Warn when exit policy implicitly allows local addresses.
13934 - If we get an incredibly skewed timestamp from a dirserver mirror
13935 that isn't a verified OR, don't warn -- it's probably him that's
13937 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13938 cookies to disk and doesn't log each web request to disk. (Thanks
13939 to Brett Carrington for pointing this out.)
13940 - When a client asks us for a dir mirror and we don't have one,
13941 launch an attempt to get a fresh one.
13942 - If we're hibernating and we get a SIGINT, exit immediately.
13943 - Add --with-dmalloc ./configure option, to track memory leaks.
13944 - And try to free all memory on closing, so we can detect what
13946 - Cache local dns resolves correctly even when they're .exit
13948 - Give a better warning when some other server advertises an
13949 ORPort that is actually an apache running ssl.
13950 - Add "opt hibernating 1" to server descriptor to make it clearer
13951 whether the server is hibernating.
13954 Changes in version 0.0.9.6 - 2005-03-24
13955 o Bugfixes on 0.0.9.x (crashes and asserts):
13956 - Add new end stream reasons to maintainance branch. Fix bug where
13957 reason (8) could trigger an assert. Prevent bug from recurring.
13958 - Apparently win32 stat wants paths to not end with a slash.
13959 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13960 blowing away the circuit that conn->cpath_layer points to, then
13961 checking to see if the circ is well-formed. Backport check to make
13962 sure we dont use the cpath on a closed connection.
13963 - Prevent circuit_resume_edge_reading_helper() from trying to package
13964 inbufs for marked-for-close streams.
13965 - Don't crash on hup if your options->address has become unresolvable.
13966 - Some systems (like OS X) sometimes accept() a connection and tell
13967 you the remote host is 0.0.0.0:0. If this happens, due to some
13968 other mis-features, we get confused; so refuse the conn for now.
13970 o Bugfixes on 0.0.9.x (other):
13971 - Fix harmless but scary "Unrecognized content encoding" warn message.
13972 - Add new stream error reason: TORPROTOCOL reason means "you are not
13973 speaking a version of Tor I understand; say bye-bye to your stream."
13974 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
13975 into the future, now that we are more tolerant of skew. This
13976 resolves a bug where a Tor server would refuse to cache a directory
13977 because all the directories it gets are too far in the future;
13978 yet the Tor server never logs any complaints about clock skew.
13979 - Mac packaging magic: make man pages useable, and do not overwrite
13980 existing torrc files.
13981 - Make OS X log happily to /var/log/tor/tor.log
13984 Changes in version 0.0.9.5 - 2005-02-22
13985 o Bugfixes on 0.0.9.x:
13986 - Fix an assert race at exit nodes when resolve requests fail.
13987 - Stop picking unverified dir mirrors--it only leads to misery.
13988 - Patch from Matt Edman to make NT services work better. Service
13989 support is still not compiled into the executable by default.
13990 - Patch from Dmitri Bely so the Tor service runs better under
13991 the win32 SYSTEM account.
13992 - Make tor-resolve actually work (?) on Win32.
13993 - Fix a sign bug when getrlimit claims to have 4+ billion
13994 file descriptors available.
13995 - Stop refusing to start when bandwidthburst == bandwidthrate.
13996 - When create cells have been on the onion queue more than five
13997 seconds, just send back a destroy and take them off the list.
14000 Changes in version 0.0.9.4 - 2005-02-03
14001 o Bugfixes on 0.0.9:
14002 - Fix an assert bug that took down most of our servers: when
14003 a server claims to have 1 GB of bandwidthburst, don't
14005 - Don't crash as badly if we have spawned the max allowed number
14006 of dnsworkers, or we're out of file descriptors.
14007 - Block more file-sharing ports in the default exit policy.
14008 - MaxConn is now automatically set to the hard limit of max
14009 file descriptors we're allowed (ulimit -n), minus a few for
14011 - Give a clearer message when servers need to raise their
14012 ulimit -n when they start running out of file descriptors.
14013 - SGI Compatibility patches from Jan Schaumann.
14014 - Tolerate a corrupt cached directory better.
14015 - When a dirserver hasn't approved your server, list which one.
14016 - Go into soft hibernation after 95% of the bandwidth is used,
14017 not 99%. This is especially important for daily hibernators who
14018 have a small accounting max. Hopefully it will result in fewer
14019 cut connections when the hard hibernation starts.
14020 - Load-balance better when using servers that claim more than
14021 800kB/s of capacity.
14022 - Make NT services work (experimental, only used if compiled in).
14025 Changes in version 0.0.9.3 - 2005-01-21
14026 o Bugfixes on 0.0.9:
14027 - Backport the cpu use fixes from main branch, so busy servers won't
14028 need as much processor time.
14029 - Work better when we go offline and then come back, or when we
14030 run Tor at boot before the network is up. We do this by
14031 optimistically trying to fetch a new directory whenever an
14032 application request comes in and we think we're offline -- the
14033 human is hopefully a good measure of when the network is back.
14034 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14035 long as you keep using them; actually publish hidserv descriptors
14036 shortly after they change, rather than waiting 20-40 minutes.
14037 - Enable Mac startup script by default.
14038 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14039 - When you update AllowUnverifiedNodes or FirewallPorts via the
14040 controller's setconf feature, we were always appending, never
14042 - When you update HiddenServiceDir via setconf, it was screwing up
14043 the order of reading the lines, making it fail.
14044 - Do not rewrite a cached directory back to the cache; otherwise we
14045 will think it is recent and not fetch a newer one on startup.
14046 - Workaround for webservers that lie about Content-Encoding: Tor
14047 now tries to autodetect compressed directories and compression
14048 itself. This lets us Proxypass dir fetches through apache.
14051 Changes in version 0.0.9.2 - 2005-01-04
14052 o Bugfixes on 0.0.9 (crashes and asserts):
14053 - Fix an assert on startup when the disk is full and you're logging
14055 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14056 style address, then we'd crash.
14057 - Fix an assert trigger when the running-routers string we get from
14058 a dirserver is broken.
14059 - Make worker threads start and run on win32. Now win32 servers
14061 - Bandaid (not actually fix, but now it doesn't crash) an assert
14062 where the dns worker dies mysteriously and the main Tor process
14063 doesn't remember anything about the address it was resolving.
14065 o Bugfixes on 0.0.9 (Win32):
14066 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14067 name out of the warning/assert messages.
14068 - Fix a superficial "unhandled error on read" bug on win32.
14069 - The win32 installer no longer requires a click-through for our
14070 license, since our Free Software license grants rights but does not
14072 - Win32: When connecting to a dirserver fails, try another one
14073 immediately. (This was already working for non-win32 Tors.)
14074 - Stop trying to parse $HOME on win32 when hunting for default
14076 - Make tor-resolve.c work on win32 by calling network_init().
14078 o Bugfixes on 0.0.9 (other):
14079 - Make 0.0.9.x build on Solaris again.
14080 - Due to a fencepost error, we were blowing away the \n when reporting
14081 confvalue items in the controller. So asking for multiple config
14082 values at once couldn't work.
14083 - When listing circuits that are pending on an opening OR connection,
14084 if we're an OR we were listing circuits that *end* at us as
14085 being pending on every listener, dns/cpu worker, etc. Stop that.
14086 - Dirservers were failing to create 'running-routers' or 'directory'
14087 strings if we had more than some threshold of routers. Fix them so
14088 they can handle any number of routers.
14089 - Fix a superficial "Duplicate mark for close" bug.
14090 - Stop checking for clock skew for OR connections, even for servers.
14091 - Fix a fencepost error that was chopping off the last letter of any
14092 nickname that is the maximum allowed nickname length.
14093 - Update URLs in log messages so they point to the new website.
14094 - Fix a potential problem in mangling server private keys while
14095 writing to disk (not triggered yet, as far as we know).
14096 - Include the licenses for other free software we include in Tor,
14097 now that we're shipping binary distributions more regularly.
14100 Changes in version 0.0.9.1 - 2004-12-15
14101 o Bugfixes on 0.0.9:
14102 - Make hibernation actually work.
14103 - Make HashedControlPassword config option work.
14104 - When we're reporting event circuit status to a controller,
14105 don't use the stream status code.
14108 Changes in version 0.0.9 - 2004-12-12
14110 - Clean up manpage and torrc.sample file.
14111 - Clean up severities and text of log warnings.
14113 - Make servers trigger an assert when they enter hibernation.
14116 Changes in version 0.0.9rc7 - 2004-12-08
14117 o Bugfixes on 0.0.9rc:
14118 - Fix a stack-trashing crash when an exit node begins hibernating.
14119 - Avoid looking at unallocated memory while considering which
14120 ports we need to build circuits to cover.
14121 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14122 we shouldn't hold-open-until-flush if the eof arrived first.
14123 - Fix a bug with init_cookie_authentication() in the controller.
14124 - When recommending new-format log lines, if the upper bound is
14125 LOG_ERR, leave it implicit.
14127 o Bugfixes on 0.0.8.1:
14128 - Fix a whole slew of memory leaks.
14129 - Fix isspace() and friends so they still make Solaris happy
14130 but also so they don't trigger asserts on win32.
14131 - Fix parse_iso_time on platforms without strptime (eg win32).
14132 - win32: tolerate extra "readable" events better.
14133 - win32: when being multithreaded, leave parent fdarray open.
14134 - Make unit tests work on win32.
14137 Changes in version 0.0.9rc6 - 2004-12-06
14138 o Bugfixes on 0.0.9pre:
14139 - Clean up some more integer underflow opportunities (not exploitable
14141 - While hibernating, hup should not regrow our listeners.
14142 - Send an end to the streams we close when we hibernate, rather
14143 than just chopping them off.
14144 - React to eof immediately on non-open edge connections.
14146 o Bugfixes on 0.0.8.1:
14147 - Calculate timeout for waiting for a connected cell from the time
14148 we sent the begin cell, not from the time the stream started. If
14149 it took a long time to establish the circuit, we would time out
14150 right after sending the begin cell.
14151 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14152 of * as always matching, so we were picking reject *:* nodes as
14153 exit nodes too. Oops.
14156 - New circuit building strategy: keep a list of ports that we've
14157 used in the past 6 hours, and always try to have 2 circuits open
14158 or on the way that will handle each such port. Seed us with port
14159 80 so web users won't complain that Tor is "slow to start up".
14160 - Make kill -USR1 dump more useful stats about circuits.
14161 - When warning about retrying or giving up, print the address, so
14162 the user knows which one it's talking about.
14163 - If you haven't used a clean circuit in an hour, throw it away,
14164 just to be on the safe side. (This means after 6 hours a totally
14165 unused Tor client will have no circuits open.)
14168 Changes in version 0.0.9rc5 - 2004-12-01
14169 o Bugfixes on 0.0.8.1:
14170 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14171 - Let resolve conns retry/expire also, rather than sticking around
14173 - If we are using select, make sure we stay within FD_SETSIZE.
14175 o Bugfixes on 0.0.9pre:
14176 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14177 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14179 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14180 instead. Impose minima and maxima for all *Period options; impose
14181 even tighter maxima for fetching if we are a caching dirserver.
14182 Clip rather than rejecting.
14183 - Fetch cached running-routers from servers that serve it (that is,
14184 authdirservers and servers running 0.0.9rc5-cvs or later.)
14187 - Accept *:706 (silc) in default exit policy.
14188 - Implement new versioning format for post 0.1.
14189 - Support "foo.nickname.exit" addresses, to let Alice request the
14190 address "foo" as viewed by exit node "nickname". Based on a patch
14192 - Make tor --version --version dump the cvs Id of every file.
14195 Changes in version 0.0.9rc4 - 2004-11-28
14196 o Bugfixes on 0.0.8.1:
14197 - Make windows sockets actually non-blocking (oops), and handle
14198 win32 socket errors better.
14200 o Bugfixes on 0.0.9rc1:
14201 - Actually catch the -USR2 signal.
14204 Changes in version 0.0.9rc3 - 2004-11-25
14205 o Bugfixes on 0.0.8.1:
14206 - Flush the log file descriptor after we print "Tor opening log file",
14207 so we don't see those messages days later.
14209 o Bugfixes on 0.0.9rc1:
14210 - Make tor-resolve work again.
14211 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14212 - Fix an assert trigger for clients/servers handling resolves.
14215 Changes in version 0.0.9rc2 - 2004-11-24
14216 o Bugfixes on 0.0.9rc1:
14217 - I broke socks5 support while fixing the eof bug.
14218 - Allow unitless bandwidths and intervals; they default to bytes
14220 - New servers don't start out hibernating; they are active until
14221 they run out of bytes, so they have a better estimate of how
14222 long it takes, and so their operators can know they're working.
14225 Changes in version 0.0.9rc1 - 2004-11-23
14226 o Bugfixes on 0.0.8.1:
14227 - Finally fix a bug that's been plaguing us for a year:
14228 With high load, circuit package window was reaching 0. Whenever
14229 we got a circuit-level sendme, we were reading a lot on each
14230 socket, but only writing out a bit. So we would eventually reach
14231 eof. This would be noticed and acted on even when there were still
14232 bytes sitting in the inbuf.
14233 - When poll() is interrupted, we shouldn't believe the revents values.
14235 o Bugfixes on 0.0.9pre6:
14236 - Fix hibernate bug that caused pre6 to be broken.
14237 - Don't keep rephist info for routers that haven't had activity for
14238 24 hours. (This matters now that clients have keys, since we track
14240 - Never call close_temp_logs while validating log options.
14241 - Fix backslash-escaping on tor.sh.in and torctl.in.
14244 - Implement weekly/monthly/daily accounting: now you specify your
14245 hibernation properties by
14246 AccountingMax N bytes|KB|MB|GB|TB
14247 AccountingStart day|week|month [day] HH:MM
14248 Defaults to "month 1 0:00".
14249 - Let bandwidth and interval config options be specified as 5 bytes,
14250 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14251 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14252 get back to normal.)
14253 - If your requested entry or exit node has advertised bandwidth 0,
14255 - Be more greedy about filling up relay cells -- we try reading again
14256 once we've processed the stuff we read, in case enough has arrived
14257 to fill the last cell completely.
14258 - Apply NT service patch from Osamu Fujino. Still needs more work.
14261 Changes in version 0.0.9pre6 - 2004-11-15
14262 o Bugfixes on 0.0.8.1:
14263 - Fix assert failure on malformed socks4a requests.
14264 - Use identity comparison, not nickname comparison, to choose which
14265 half of circuit-ID-space each side gets to use. This is needed
14266 because sometimes we think of a router as a nickname, and sometimes
14267 as a hex ID, and we can't predict what the other side will do.
14268 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14269 write() call will fail and we handle it there.
14270 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14271 and smartlist_len, which are two major profiling offenders.
14273 o Bugfixes on 0.0.9pre5:
14274 - Fix a bug in read_all that was corrupting config files on windows.
14275 - When we're raising the max number of open file descriptors to
14276 'unlimited', don't log that we just raised it to '-1'.
14277 - Include event code with events, as required by control-spec.txt.
14278 - Don't give a fingerprint when clients do --list-fingerprint:
14279 it's misleading, because it will never be the same again.
14280 - Stop using strlcpy in tor_strndup, since it was slowing us
14282 - Remove warn on startup about missing cached-directory file.
14283 - Make kill -USR1 work again.
14284 - Hibernate if we start tor during the "wait for wakeup-time" phase
14285 of an accounting interval. Log our hibernation plans better.
14286 - Authoritative dirservers now also cache their directory, so they
14287 have it on start-up.
14290 - Fetch running-routers; cache running-routers; compress
14291 running-routers; serve compressed running-routers.z
14292 - Add NSI installer script contributed by J Doe.
14293 - Commit VC6 and VC7 workspace/project files.
14294 - Commit a tor.spec for making RPM files, with help from jbash.
14295 - Add contrib/torctl.in contributed by Glenn Fink.
14296 - Implement the control-spec's SAVECONF command, to write your
14297 configuration to torrc.
14298 - Get cookie authentication for the controller closer to working.
14299 - Include control-spec.txt in the tarball.
14300 - When set_conf changes our server descriptor, upload a new copy.
14301 But don't upload it too often if there are frequent changes.
14302 - Document authentication config in man page, and document signals
14304 - Clean up confusing parts of man page and torrc.sample.
14305 - Make expand_filename handle ~ and ~username.
14306 - Use autoconf to enable largefile support where necessary. Use
14307 ftello where available, since ftell can fail at 2GB.
14308 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14309 log more informatively.
14310 - Give a slightly more useful output for "tor -h".
14311 - Refuse application socks connections to port 0.
14312 - Check clock skew for verified servers, but allow unverified
14313 servers and clients to have any clock skew.
14314 - Break DirFetchPostPeriod into:
14315 - DirFetchPeriod for fetching full directory,
14316 - StatusFetchPeriod for fetching running-routers,
14317 - DirPostPeriod for posting server descriptor,
14318 - RendPostPeriod for posting hidden service descriptors.
14319 - Make sure the hidden service descriptors are at a random offset
14320 from each other, to hinder linkability.
14323 Changes in version 0.0.9pre5 - 2004-11-09
14324 o Bugfixes on 0.0.9pre4:
14325 - Fix a seg fault in unit tests (doesn't affect main program).
14326 - Fix an assert bug where a hidden service provider would fail if
14327 the first hop of his rendezvous circuit was down.
14328 - Hidden service operators now correctly handle version 1 style
14329 INTRODUCE1 cells (nobody generates them still, so not a critical
14331 - If do_hup fails, actually notice.
14332 - Handle more errnos from accept() without closing the listener.
14333 Some OpenBSD machines were closing their listeners because
14334 they ran out of file descriptors.
14335 - Send resolve cells to exit routers that are running a new
14336 enough version of the resolve code to work right.
14337 - Better handling of winsock includes on non-MSV win32 compilers.
14338 - Some people had wrapped their tor client/server in a script
14339 that would restart it whenever it died. This did not play well
14340 with our "shut down if your version is obsolete" code. Now people
14341 don't fetch a new directory if their local cached version is
14343 - Make our autogen.sh work on ksh as well as bash.
14346 - Hibernation: New config option "AccountingMaxKB" lets you
14347 set how many KBytes per month you want to allow your server to
14348 consume. Rather than spreading those bytes out evenly over the
14349 month, we instead hibernate for some of the month and pop up
14350 at a deterministic time, work until the bytes are consumed, then
14351 hibernate again. Config option "MonthlyAccountingStart" lets you
14352 specify which day of the month your billing cycle starts on.
14353 - Control interface: a separate program can now talk to your
14354 client/server over a socket, and get/set config options, receive
14355 notifications of circuits and streams starting/finishing/dying,
14356 bandwidth used, etc. The next step is to get some GUIs working.
14357 Let us know if you want to help out. See doc/control-spec.txt .
14358 - Ship a contrib/tor-control.py as an example script to interact
14359 with the control port.
14360 - "tor --hash-password zzyxz" will output a salted password for
14361 use in authenticating to the control interface.
14362 - New log format in config:
14363 "Log minsev[-maxsev] stdout|stderr|syslog" or
14364 "Log minsev[-maxsev] file /var/foo"
14367 - DirPolicy config option, to let people reject incoming addresses
14368 from their dirserver.
14369 - "tor --list-fingerprint" will list your identity key fingerprint
14371 - Add "pass" target for RedirectExit, to make it easier to break
14372 out of a sequence of RedirectExit rules.
14373 - Clients now generate a TLS cert too, in preparation for having
14374 them act more like real nodes.
14375 - Ship src/win32/ in the tarball, so people can use it to build.
14376 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14378 - New "router-status" line in directory, to better bind each verified
14379 nickname to its identity key.
14380 - Deprecate unofficial config option abbreviations, and abbreviations
14381 not on the command line.
14382 - Add a pure-C tor-resolve implementation.
14383 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14384 1024) file descriptors.
14386 o Code security improvements, inspired by Ilja:
14387 - Replace sprintf with snprintf. (I think they were all safe, but
14389 - Replace strcpy/strncpy with strlcpy in more places.
14390 - Avoid strcat; use snprintf or strlcat instead.
14391 - snprintf wrapper with consistent (though not C99) overflow behavior.
14394 Changes in version 0.0.9pre4 - 2004-10-17
14395 o Bugfixes on 0.0.9pre3:
14396 - If the server doesn't specify an exit policy, use the real default
14397 exit policy, not reject *:*.
14398 - Ignore fascistfirewall when uploading/downloading hidden service
14399 descriptors, since we go through Tor for those; and when using
14400 an HttpProxy, since we assume it can reach them all.
14401 - When looking for an authoritative dirserver, use only the ones
14402 configured at boot. Don't bother looking in the directory.
14403 - The rest of the fix for get_default_conf_file() on older win32.
14404 - Make 'Routerfile' config option obsolete.
14407 - New 'MyFamily nick1,...' config option for a server to
14408 specify other servers that shouldn't be used in the same circuit
14409 with it. Only believed if nick1 also specifies us.
14410 - New 'NodeFamily nick1,nick2,...' config option for a client to
14411 specify nodes that it doesn't want to use in the same circuit.
14412 - New 'Redirectexit pattern address:port' config option for a
14413 server to redirect exit connections, e.g. to a local squid.
14416 Changes in version 0.0.9pre3 - 2004-10-13
14417 o Bugfixes on 0.0.8.1:
14418 - Better torrc example lines for dirbindaddress and orbindaddress.
14419 - Improved bounds checking on parsed ints (e.g. config options and
14420 the ones we find in directories.)
14421 - Better handling of size_t vs int, so we're more robust on 64
14423 - Fix the rest of the bug where a newly started OR would appear
14424 as unverified even after we've added his fingerprint and hupped
14426 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14427 close it without sending back an end. So 'connection refused'
14428 would simply be ignored and the user would get no response.
14430 o Bugfixes on 0.0.9pre2:
14431 - Serving the cached-on-disk directory to people is bad. We now
14432 provide no directory until we've fetched a fresh one.
14433 - Workaround for bug on windows where cached-directories get crlf
14435 - Make get_default_conf_file() work on older windows too.
14436 - If we write a *:* exit policy line in the descriptor, don't write
14437 any more exit policy lines.
14440 - Use only 0.0.9pre1 and later servers for resolve cells.
14441 - Make the dirservers file obsolete.
14442 - Include a dir-signing-key token in directories to tell the
14443 parsing entity which key is being used to sign.
14444 - Remove the built-in bulky default dirservers string.
14445 - New config option "Dirserver %s:%d [fingerprint]", which can be
14446 repeated as many times as needed. If no dirservers specified,
14447 default to moria1,moria2,tor26.
14448 - Make moria2 advertise a dirport of 80, so people behind firewalls
14449 will be able to get a directory.
14450 - Http proxy support
14451 - Dirservers translate requests for http://%s:%d/x to /x
14452 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14453 be routed through this host.
14454 - Clients ask for /tor/x rather than /x for new enough dirservers.
14455 This way we can one day coexist peacefully with apache.
14456 - Clients specify a "Host: %s%d" http header, to be compatible
14457 with more proxies, and so running squid on an exit node can work.
14460 Changes in version 0.0.8.1 - 2004-10-13
14462 - Fix a seg fault that can be triggered remotely for Tor
14463 clients/servers with an open dirport.
14464 - Fix a rare assert trigger, where routerinfos for entries in
14465 our cpath would expire while we're building the path.
14466 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14467 - Fix a rare seg fault for people running hidden services on
14468 intermittent connections.
14469 - Fix a bug in parsing opt keywords with objects.
14470 - Fix a stale pointer assert bug when a stream detaches and
14472 - Fix a string format vulnerability (probably not exploitable)
14473 in reporting stats locally.
14474 - Fix an assert trigger: sometimes launching circuits can fail
14475 immediately, e.g. because too many circuits have failed recently.
14476 - Fix a compile warning on 64 bit platforms.
14479 Changes in version 0.0.9pre2 - 2004-10-03
14481 - Make fetching a cached directory work for 64-bit platforms too.
14482 - Make zlib.h a required header, not an optional header.
14485 Changes in version 0.0.9pre1 - 2004-10-01
14487 - Stop using separate defaults for no-config-file and
14488 empty-config-file. Now you have to explicitly turn off SocksPort,
14489 if you don't want it open.
14490 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14491 - Improve man page to mention more of the 0.0.8 features.
14492 - Fix a rare seg fault for people running hidden services on
14493 intermittent connections.
14494 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14496 - Fix more dns related bugs: send back resolve_failed and end cells
14497 more reliably when the resolve fails, rather than closing the
14498 circuit and then trying to send the cell. Also attach dummy resolve
14499 connections to a circuit *before* calling dns_resolve(), to fix
14500 a bug where cached answers would never be sent in RESOLVED cells.
14501 - When we run out of disk space, or other log writing error, don't
14502 crash. Just stop logging to that log and continue.
14503 - We were starting to daemonize before we opened our logs, so if
14504 there were any problems opening logs, we would complain to stderr,
14505 which wouldn't work, and then mysteriously exit.
14506 - Fix a rare bug where sometimes a verified OR would connect to us
14507 before he'd uploaded his descriptor, which would cause us to
14508 assign conn->nickname as though he's unverified. Now we look through
14509 the fingerprint list to see if he's there.
14510 - Fix a rare assert trigger, where routerinfos for entries in
14511 our cpath would expire while we're building the path.
14514 - Clients can ask dirservers for /dir.z to get a compressed version
14515 of the directory. Only works for servers running 0.0.9, of course.
14516 - Make clients cache directories and use them to seed their router
14517 lists at startup. This means clients have a datadir again.
14518 - Configuration infrastructure support for warning on obsolete
14520 - Respond to content-encoding headers by trying to uncompress as
14522 - Reply with a deflated directory when a client asks for "dir.z".
14523 We could use allow-encodings instead, but allow-encodings isn't
14524 specified in HTTP 1.0.
14525 - Raise the max dns workers from 50 to 100.
14526 - Discourage people from setting their dirfetchpostperiod more often
14527 than once per minute.
14528 - Protect dirservers from overzealous descriptor uploading -- wait
14529 10 seconds after directory gets dirty, before regenerating.
14532 Changes in version 0.0.8 - 2004-08-25
14533 o Port it to SunOS 5.9 / Athena
14536 Changes in version 0.0.8rc2 - 2004-08-20
14537 o Make it compile on cygwin again.
14538 o When picking unverified routers, skip those with low uptime and/or
14539 low bandwidth, depending on what properties you care about.
14542 Changes in version 0.0.8rc1 - 2004-08-18
14543 o Changes from 0.0.7.3:
14545 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14546 don't put it into the client dns cache.
14547 - If a begin failed due to exit policy, but we believe the IP address
14548 should have been allowed, switch that router to exitpolicy reject *:*
14549 until we get our next directory.
14551 - Clients choose nodes proportional to advertised bandwidth.
14552 - Avoid using nodes with low uptime as introduction points.
14553 - Handle servers with dynamic IP addresses: don't replace
14554 options->Address with the resolved one at startup, and
14555 detect our address right before we make a routerinfo each time.
14556 - 'FascistFirewall' option to pick dirservers and ORs on specific
14557 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14558 which ports are open. (Defaults to 80,443)
14559 - Be more aggressive about trying to make circuits when the network
14560 has changed (e.g. when you unsuspend your laptop).
14561 - Check for time skew on http headers; report date in response to
14563 - If the entrynode config line has only one node, don't pick it as
14565 - Add strict{entry|exit}nodes config options. If set to 1, then
14566 we refuse to build circuits that don't include the specified entry
14568 - OutboundBindAddress config option, to bind to a specific
14569 IP address for outgoing connect()s.
14570 - End truncated log entries (e.g. directories) with "[truncated]".
14572 o Patches to 0.0.8preX:
14574 - Patches to compile and run on win32 again (maybe)?
14575 - Fix crash when looking for ~/.torrc with no $HOME set.
14576 - Fix a race bug in the unit tests.
14577 - Handle verified/unverified name collisions better when new
14578 routerinfo's arrive in a directory.
14579 - Sometimes routers were getting entered into the stats before
14580 we'd assigned their identity_digest. Oops.
14581 - Only pick and establish intro points after we've gotten a
14584 - AllowUnverifiedNodes config option to let circuits choose no-name
14585 routers in entry,middle,exit,introduction,rendezvous positions.
14586 Allow middle and rendezvous positions by default.
14587 - Add a man page for tor-resolve.
14590 Changes in version 0.0.7.3 - 2004-08-12
14591 o Stop dnsworkers from triggering an assert failure when you
14592 ask them to resolve the host "".
14595 Changes in version 0.0.8pre3 - 2004-08-09
14596 o Changes from 0.0.7.2:
14597 - Allow multiple ORs with same nickname in routerlist -- now when
14598 people give us one identity key for a nickname, then later
14599 another, we don't constantly complain until the first expires.
14600 - Remember used bandwidth (both in and out), and publish 15-minute
14601 snapshots for the past day into our descriptor.
14602 - You can now fetch $DIRURL/running-routers to get just the
14603 running-routers line, not the whole descriptor list. (But
14604 clients don't use this yet.)
14605 - When people mistakenly use Tor as an http proxy, point them
14606 at the tor-doc.html rather than the INSTALL.
14607 - Remove our mostly unused -- and broken -- hex_encode()
14608 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14609 for pointing out this bug.)
14610 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14611 fewer problems with people using the wrong key.
14612 - Change the default exit policy to reject the default edonkey,
14613 kazaa, gnutella ports.
14614 - Add replace_file() to util.[ch] to handle win32's rename().
14616 o Changes from 0.0.8preX:
14617 - Fix two bugs in saving onion keys to disk when rotating, so
14618 hopefully we'll get fewer people using old onion keys.
14619 - Fix an assert error that was making SocksPolicy not work.
14620 - Be willing to expire routers that have an open dirport -- it's
14621 just the authoritative dirservers we want to not forget.
14622 - Reject tor-resolve requests for .onion addresses early, so we
14623 don't build a whole rendezvous circuit and then fail.
14624 - When you're warning a server that he's unverified, don't cry
14625 wolf unpredictably.
14626 - Fix a race condition: don't try to extend onto a connection
14627 that's still handshaking.
14628 - For servers in clique mode, require the conn to be open before
14629 you'll choose it for your path.
14630 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14631 end relay cell, etc.
14632 - Measure bandwidth capacity over the last 24 hours, not just 12
14633 - Bugfix: authoritative dirservers were making and signing a new
14634 directory for each client, rather than reusing the cached one.
14637 Changes in version 0.0.8pre2 - 2004-08-04
14638 o Changes from 0.0.7.2:
14640 - Check directory signature _before_ you decide whether you're
14641 you're running an obsolete version and should exit.
14642 - Check directory signature _before_ you parse the running-routers
14643 list to decide who's running or verified.
14644 - Bugfixes and features:
14645 - Check return value of fclose while writing to disk, so we don't
14646 end up with broken files when servers run out of disk space.
14647 - Log a warning if the user uses an unsafe socks variant, so people
14648 are more likely to learn about privoxy or socat.
14649 - Dirservers now include RFC1123-style dates in the HTTP headers,
14650 which one day we will use to better detect clock skew.
14652 o Changes from 0.0.8pre1:
14653 - Make it compile without warnings again on win32.
14654 - Log a warning if you're running an unverified server, to let you
14655 know you might want to get it verified.
14656 - Only pick a default nickname if you plan to be a server.
14659 Changes in version 0.0.8pre1 - 2004-07-23
14661 - Made our unit tests compile again on OpenBSD 3.5, and tor
14662 itself compile again on OpenBSD on a sparc64.
14663 - We were neglecting milliseconds when logging on win32, so
14664 everything appeared to happen at the beginning of each second.
14666 o Protocol changes:
14667 - 'Extend' relay cell payloads now include the digest of the
14668 intended next hop's identity key. Now we can verify that we're
14669 extending to the right router, and also extend to routers we
14670 hadn't heard of before.
14673 - Tor nodes can now act as relays (with an advertised ORPort)
14674 without being manually verified by the dirserver operators.
14675 - Uploaded descriptors of unverified routers are now accepted
14676 by the dirservers, and included in the directory.
14677 - Verified routers are listed by nickname in the running-routers
14678 list; unverified routers are listed as "$<fingerprint>".
14679 - We now use hash-of-identity-key in most places rather than
14680 nickname or addr:port, for improved security/flexibility.
14681 - To avoid Sybil attacks, paths still use only verified servers.
14682 But now we have a chance to play around with hybrid approaches.
14683 - Nodes track bandwidth usage to estimate capacity (not used yet).
14684 - ClientOnly option for nodes that never want to become servers.
14685 - Directory caching.
14686 - "AuthoritativeDir 1" option for the official dirservers.
14687 - Now other nodes (clients and servers) will cache the latest
14688 directory they've pulled down.
14689 - They can enable their DirPort to serve it to others.
14690 - Clients will pull down a directory from any node with an open
14691 DirPort, and check the signature/timestamp correctly.
14692 - Authoritative dirservers now fetch directories from other
14693 authdirservers, to stay better synced.
14694 - Running-routers list tells who's down also, along with noting
14695 if they're verified (listed by nickname) or unverified (listed
14697 - Allow dirservers to serve running-router list separately.
14698 This isn't used yet.
14699 - ORs connect-on-demand to other ORs
14700 - If you get an extend cell to an OR you're not connected to,
14701 connect, handshake, and forward the create cell.
14702 - The authoritative dirservers stay connected to everybody,
14703 and everybody stays connected to 0.0.7 servers, but otherwise
14704 clients/servers expire unused connections after 5 minutes.
14705 - When servers get a sigint, they delay 30 seconds (refusing new
14706 connections) then exit. A second sigint causes immediate exit.
14707 - File and name management:
14708 - Look for .torrc if no CONFDIR "torrc" is found.
14709 - If no datadir is defined, then choose, make, and secure ~/.tor
14711 - If torrc not found, exitpolicy reject *:*.
14712 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14713 - If no nickname is defined, derive default from hostname.
14714 - Rename secret key files, e.g. identity.key -> secret_id_key,
14715 to discourage people from mailing their identity key to tor-ops.
14716 - Refuse to build a circuit before the directory has arrived --
14717 it won't work anyway, since you won't know the right onion keys
14719 - Try other dirservers immediately if the one you try is down. This
14720 should tolerate down dirservers better now.
14721 - Parse tor version numbers so we can do an is-newer-than check
14722 rather than an is-in-the-list check.
14723 - New socks command 'resolve', to let us shim gethostbyname()
14725 - A 'tor_resolve' script to access the socks resolve functionality.
14726 - A new socks-extensions.txt doc file to describe our
14727 interpretation and extensions to the socks protocols.
14728 - Add a ContactInfo option, which gets published in descriptor.
14729 - Publish OR uptime in descriptor (and thus in directory) too.
14730 - Write tor version at the top of each log file
14731 - New docs in the tarball:
14733 - Document that you should proxy your SSL traffic too.
14736 Changes in version 0.0.7.2 - 2004-07-07
14737 o A better fix for the 0.0.0.0 problem, that will hopefully
14738 eliminate the remaining related assertion failures.
14741 Changes in version 0.0.7.1 - 2004-07-04
14742 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14743 since internally we use 0.0.0.0 to signify "not yet resolved".
14746 Changes in version 0.0.7 - 2004-06-07
14747 o Updated the man page to reflect the new features.
14750 Changes in version 0.0.7rc2 - 2004-06-06
14751 o Changes from 0.0.7rc1:
14752 - Make it build on Win32 again.
14753 o Changes from 0.0.6.2:
14754 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14758 Changes in version 0.0.7rc1 - 2004-06-02
14760 - On sighup, we were adding another log without removing the first
14761 one. So log messages would get duplicated n times for n sighups.
14762 - Several cases of using a connection after we'd freed it. The
14763 problem was that connections that are pending resolve are in both
14764 the pending_resolve tree, and also the circuit's resolving_streams
14765 list. When you want to remove one, you must remove it from both.
14766 - Fix a double-mark-for-close where an end cell arrived for a
14767 resolving stream, and then the resolve failed.
14768 - Check directory signatures based on name of signer, not on whom
14769 we got the directory from. This will let us cache directories more
14772 - Crank up some of our constants to handle more users.
14775 Changes in version 0.0.7pre1 - 2004-06-02
14776 o Fixes for crashes and other obnoxious bugs:
14777 - Fix an epipe bug: sometimes when directory connections failed
14778 to connect, we would give them a chance to flush before closing
14780 - When we detached from a circuit because of resolvefailed, we
14781 would immediately try the same circuit twice more, and then
14782 give up on the resolve thinking we'd tried three different
14784 - Limit the number of intro circuits we'll attempt to build for a
14785 hidden service per 15-minute period.
14786 - Check recommended-software string *early*, before actually parsing
14787 the directory. Thus we can detect an obsolete version and exit,
14788 even if the new directory format doesn't parse.
14789 o Fixes for security bugs:
14790 - Remember which nodes are dirservers when you startup, and if a
14791 random OR enables his dirport, don't automatically assume he's
14792 a trusted dirserver.
14794 - Directory connections were asking the wrong poll socket to
14795 start writing, and not asking themselves to start writing.
14796 - When we detached from a circuit because we sent a begin but
14797 didn't get a connected, we would use it again the first time;
14798 but after that we would correctly switch to a different one.
14799 - Stop warning when the first onion decrypt attempt fails; they
14800 will sometimes legitimately fail now that we rotate keys.
14801 - Override unaligned-access-ok check when $host_cpu is ia64 or
14802 arm. Apparently they allow it but the kernel whines.
14803 - Dirservers try to reconnect periodically too, in case connections
14805 - Fix some memory leaks in directory servers.
14806 - Allow backslash in Win32 filenames.
14807 - Made Tor build complain-free on FreeBSD, hopefully without
14808 breaking other BSD builds. We'll see.
14810 - Doxygen markup on all functions and global variables.
14811 - Make directory functions update routerlist, not replace it. So
14812 now directory disagreements are not so critical a problem.
14813 - Remove the upper limit on number of descriptors in a dirserver's
14814 directory (not that we were anywhere close).
14815 - Allow multiple logfiles at different severity ranges.
14816 - Allow *BindAddress to specify ":port" rather than setting *Port
14817 separately. Allow multiple instances of each BindAddress config
14818 option, so you can bind to multiple interfaces if you want.
14819 - Allow multiple exit policy lines, which are processed in order.
14820 Now we don't need that huge line with all the commas in it.
14821 - Enable accept/reject policies on SOCKS connections, so you can bind
14822 to 0.0.0.0 but still control who can use your OP.
14825 Changes in version 0.0.6.2 - 2004-05-16
14826 o Our integrity-checking digest was checking only the most recent cell,
14827 not the previous cells like we'd thought.
14828 Thanks to Stefan Mark for finding the flaw!
14831 Changes in version 0.0.6.1 - 2004-05-06
14832 o Fix two bugs in our AES counter-mode implementation (this affected
14833 onion-level stream encryption, but not TLS-level). It turns
14834 out we were doing something much more akin to a 16-character
14835 polyalphabetic cipher. Oops.
14836 Thanks to Stefan Mark for finding the flaw!
14837 o Retire moria3 as a directory server, and add tor26 as a directory
14841 Changes in version 0.0.6 - 2004-05-02
14842 [version bump only]
14845 Changes in version 0.0.6rc4 - 2004-05-01
14846 o Update the built-in dirservers list to use the new directory format
14847 o Fix a rare seg fault: if a node offering a hidden service attempts
14848 to build a circuit to Alice's rendezvous point and fails before it
14849 reaches the last hop, it retries with a different circuit, but
14851 o Handle windows socket errors correctly.
14854 Changes in version 0.0.6rc3 - 2004-04-28
14855 o Don't expire non-general excess circuits (if we had enough
14856 circuits open, we were expiring rendezvous circuits -- even
14857 when they had a stream attached. oops.)
14858 o Fetch randomness from /dev/urandom better (not via fopen/fread)
14859 o Better debugging for tls errors
14860 o Some versions of openssl have an SSL_pending function that erroneously
14861 returns bytes when there is a non-application record pending.
14862 o Set Content-Type on the directory and hidserv descriptor.
14863 o Remove IVs from cipher code, since AES-ctr has none.
14864 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14865 o We were using an array of length zero in a few places.
14866 o win32's gethostbyname can't resolve an IP to an IP.
14867 o win32's close can't close a socket.
14870 Changes in version 0.0.6rc2 - 2004-04-26
14871 o Fix a bug where we were closing tls connections intermittently.
14872 It turns out openssl keeps its errors around -- so if an error
14873 happens, and you don't ask about it, and then another openssl
14874 operation happens and succeeds, and you ask if there was an error,
14875 it tells you about the first error. Fun fun.
14876 o Fix a bug that's been lurking since 27 may 03 (!)
14877 When passing back a destroy cell, we would use the wrong circ id.
14878 'Mostly harmless', but still worth fixing.
14879 o Since we don't support truncateds much, don't bother sending them;
14880 just close the circ.
14881 o check for <machine/limits.h> so we build on NetBSD again (I hope).
14882 o don't crash if a conn that sent a begin has suddenly lost its circuit
14883 (this was quite rare).
14886 Changes in version 0.0.6rc1 - 2004-04-25
14887 o We now rotate link (tls context) keys and onion keys.
14888 o CREATE cells now include oaep padding, so you can tell
14889 if you decrypted them correctly.
14890 o Add bandwidthburst to server descriptor.
14891 o Directories now say which dirserver signed them.
14892 o Use a tor_assert macro that logs failed assertions too.
14895 Changes in version 0.0.6pre5 - 2004-04-18
14896 o changes from 0.0.6pre4:
14897 - make tor build on broken freebsd 5.2 installs
14898 - fix a failed assert when you try an intro point, get a nack, and try
14899 a second one and it works.
14900 - when alice uses a port that the hidden service doesn't accept,
14901 it now sends back an end cell (denied by exit policy). otherwise
14902 alice would just have to wait to time out.
14903 - fix another rare bug: when we had tried all the intro
14904 points for a hidden service, we fetched the descriptor
14905 again, but we left our introcirc thinking it had already
14906 sent an intro, so it kept waiting for a response...
14907 - bugfix: when you sleep your hidden-service laptop, as soon
14908 as it wakes up it tries to upload a service descriptor, but
14909 socketpair fails for some reason (localhost not up yet?).
14910 now we simply give up on that upload, and we'll try again later.
14911 i'd still like to find the bug though.
14912 - if an intro circ waiting for an ack dies before getting one, then
14914 - we were reusing stale service descriptors and refetching usable
14918 Changes in version 0.0.6pre4 - 2004-04-14
14919 o changes from 0.0.6pre3:
14920 - when bob fails to connect to the rendezvous point, and his
14921 circ didn't fail because of the rendezvous point itself, then
14922 he retries a couple of times
14923 - we expire introduction and rendezvous circs more thoroughly
14924 (sometimes they were hanging around forever)
14925 - we expire unattached rendezvous streams that have been around
14926 too long (they were sticking around forever).
14927 - fix a measly fencepost error that was crashing everybody with
14931 Changes in version 0.0.6pre3 - 2004-04-14
14932 o changes from 0.0.6pre2:
14933 - make hup work again
14934 - fix some memory leaks for dirservers
14935 - allow more skew in rendezvous descriptor timestamps, to help
14936 handle people like blanu who don't know what time it is
14937 - normal circs are 3 hops, but some rend/intro circs are 4, if
14938 the initiator doesn't get to choose the last hop
14939 - send acks for introductions, so alice can know whether to try
14941 - bob publishes intro points more correctly
14942 o changes from 0.0.5:
14943 - fix an assert trigger that's been plaguing us since the days
14944 of 0.0.2prexx (thanks weasel!)
14945 - retry stream correctly when we fail to connect because of
14946 exit-policy-reject (should try another) or can't-resolve-address
14947 (also should try another, because dns on random internet servers
14949 - when we hup a dirserver and we've *removed* a server from the
14950 approved-routers list, now we remove that server from the
14951 in-memory directories too
14954 Changes in version 0.0.6pre2 - 2004-04-08
14955 o We fixed our base32 implementation. Now it works on all architectures.
14958 Changes in version 0.0.6pre1 - 2004-04-08
14960 - Hidden services and rendezvous points are implemented. Go to
14961 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14962 hidden services. (This only works via a socks4a proxy such as
14963 Privoxy, and currently it's quite slow.)
14966 Changes in version 0.0.5 - 2004-03-30
14967 [version bump only]
14970 Changes in version 0.0.5rc3 - 2004-03-29
14971 o Install torrc as torrc.sample -- we no longer clobber your
14973 o Re-enable recommendedversion checking (we broke it in rc2, oops)
14974 o Add in a 'notice' log level for things the operator should hear
14975 but that aren't warnings
14978 Changes in version 0.0.5rc2 - 2004-03-29
14979 o Hold socks connection open until reply is flushed (if possible)
14980 o Make exit nodes resolve IPs to IPs immediately, rather than asking
14981 the dns farm to do it.
14982 o Fix c99 aliasing warnings in rephist.c
14983 o Don't include server descriptors that are older than 24 hours in the
14985 o Give socks 'reject' replies their whole 15s to attempt to flush,
14986 rather than seeing the 60s timeout and assuming the flush had failed.
14987 o Clean automake droppings from the cvs repository
14990 Changes in version 0.0.5rc1 - 2004-03-28
14991 o Fix mangled-state bug in directory fetching (was causing sigpipes).
14992 o Only build circuits after we've fetched the directory: clients were
14993 using only the directory servers before they'd fetched a directory.
14994 This also means longer startup time; so it goes.
14995 o Fix an assert trigger where an OP would fail to handshake, and we'd
14996 expect it to have a nickname.
14997 o Work around a tsocks bug: do a socks reject when AP connection dies
14998 early, else tsocks goes into an infinite loop.
15001 Changes in version 0.0.4 - 2004-03-26
15002 o When connecting to a dirserver or OR and the network is down,
15006 Changes in version 0.0.3 - 2004-03-26
15007 o Warn and fail if server chose a nickname with illegal characters
15008 o Port to Solaris and Sparc:
15009 - include missing header fcntl.h
15010 - have autoconf find -lsocket -lnsl automatically
15011 - deal with hardware word alignment
15012 - make uname() work (solaris has a different return convention)
15013 - switch from using signal() to sigaction()
15014 o Preliminary work on reputation system:
15015 - Keep statistics on success/fail of connect attempts; they're published
15016 by kill -USR1 currently.
15017 - Add a RunTesting option to try to learn link state by creating test
15018 circuits, even when SocksPort is off.
15019 - Remove unused open circuits when there are too many.
15022 Changes in version 0.0.2 - 2004-03-19
15023 - Include strlcpy and strlcat for safer string ops
15024 - define INADDR_NONE so we compile (but still not run) on solaris
15027 Changes in version 0.0.2pre27 - 2004-03-14
15029 - Allow internal tor networks (we were rejecting internal IPs,
15030 now we allow them if they're set explicitly).
15031 - And fix a few endian issues.
15034 Changes in version 0.0.2pre26 - 2004-03-14
15036 - If a stream times out after 15s without a connected cell, don't
15037 try that circuit again: try a new one.
15038 - Retry streams at most 4 times. Then give up.
15039 - When a dirserver gets a descriptor from an unknown router, it
15040 logs its fingerprint (so the dirserver operator can choose to
15041 accept it even without mail from the server operator).
15042 - Inform unapproved servers when we reject their descriptors.
15043 - Make tor build on Windows again. It works as a client, who knows
15045 - Clearer instructions in the torrc for how to set up a server.
15046 - Be more efficient about reading fd's when our global token bucket
15047 (used for rate limiting) becomes empty.
15049 - Stop asserting that computers always go forward in time. It's
15051 - When we sent a cell (e.g. destroy) and then marked an OR connection
15052 expired, we might close it before finishing a flush if the other
15053 side isn't reading right then.
15054 - Don't allow dirservers to start if they haven't defined
15055 RecommendedVersions
15056 - We were caching transient dns failures. Oops.
15057 - Prevent servers from publishing an internal IP as their address.
15058 - Address a strcat vulnerability in circuit.c
15061 Changes in version 0.0.2pre25 - 2004-03-04
15063 - Put the OR's IP in its router descriptor, not its fqdn. That way
15064 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15067 - If the user typed in an address that didn't resolve, the server
15071 Changes in version 0.0.2pre24 - 2004-03-03
15073 - Fix an assertion failure in dns.c, where we were trying to dequeue
15074 a pending dns resolve even if it wasn't pending
15075 - Fix a spurious socks5 warning about still trying to write after the
15076 connection is finished.
15077 - Hold certain marked_for_close connections open until they're finished
15078 flushing, rather than losing bytes by closing them too early.
15079 - Correctly report the reason for ending a stream
15080 - Remove some duplicate calls to connection_mark_for_close
15081 - Put switch_id and start_daemon earlier in the boot sequence, so it
15082 will actually try to chdir() to options.DataDirectory
15083 - Make 'make test' exit(1) if a test fails; fix some unit tests
15084 - Make tor fail when you use a config option it doesn't know about,
15085 rather than warn and continue.
15086 - Make --version work
15087 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15090 Changes in version 0.0.2pre23 - 2004-02-29
15092 - Print a statement when the first circ is finished, so the user
15093 knows it's working.
15094 - If a relay cell is unrecognized at the end of the circuit,
15095 send back a destroy. (So attacks to mutate cells are more
15097 - New config option 'excludenodes' to avoid certain nodes for circuits.
15098 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15099 so you can collect coredumps there.
15101 - Fix a bug in tls flushing where sometimes data got wedged and
15102 didn't flush until more data got sent. Hopefully this bug was
15103 a big factor in the random delays we were seeing.
15104 - Make 'connected' cells include the resolved IP, so the client
15105 dns cache actually gets populated.
15106 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15107 - When we time-out on a stream and detach from the circuit, send an
15108 end cell down it first.
15109 - Only warn about an unknown router (in exitnodes, entrynodes,
15110 excludenodes) after we've fetched a directory.
15113 Changes in version 0.0.2pre22 - 2004-02-26
15115 - Servers publish less revealing uname information in descriptors.
15116 - More memory tracking and assertions, to crash more usefully when
15118 - If the default torrc isn't there, just use some default defaults.
15119 Plus provide an internal dirservers file if they don't have one.
15120 - When the user tries to use Tor as an http proxy, give them an http
15121 501 failure explaining that we're a socks proxy.
15122 - Dump a new router.desc on hup, to help confused people who change
15123 their exit policies and then wonder why router.desc doesn't reflect
15125 - Clean up the generic tor.sh init script that we ship with.
15127 - If the exit stream is pending on the resolve, and a destroy arrives,
15128 then the stream wasn't getting removed from the pending list. I
15129 think this was the one causing recent server crashes.
15130 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15131 - When it couldn't resolve any dirservers, it was useless from then on.
15132 Now it reloads the RouterFile (or default dirservers) if it has no
15134 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15135 many users don't even *have* a /usr/local/sbin/.
15138 Changes in version 0.0.2pre21 - 2004-02-18
15140 - There's a ChangeLog file that actually reflects the changelog.
15141 - There's a 'torify' wrapper script, with an accompanying
15142 tor-tsocks.conf, that simplifies the process of using tsocks for
15143 tor. It even has a man page.
15144 - The tor binary gets installed to sbin rather than bin now.
15145 - Retry streams where the connected cell hasn't arrived in 15 seconds
15146 - Clean up exit policy handling -- get the default out of the torrc,
15147 so we can update it without forcing each server operator to fix
15149 - Allow imaps and pop3s in default exit policy
15151 - Prevent picking middleman nodes as the last node in the circuit
15154 Changes in version 0.0.2pre20 - 2004-01-30
15156 - We now have a deb package, and it's in debian unstable. Go to
15157 it, apt-getters. :)
15158 - I've split the TotalBandwidth option into BandwidthRate (how many
15159 bytes per second you want to allow, long-term) and
15160 BandwidthBurst (how many bytes you will allow at once before the cap
15161 kicks in). This better token bucket approach lets you, say, set
15162 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15163 performance while not exceeding your monthly bandwidth quota.
15164 - Push out a tls record's worth of data once you've got it, rather
15165 than waiting until you've read everything waiting to be read. This
15166 may improve performance by pipelining better. We'll see.
15167 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15168 from failed circuits (if they haven't been connected yet) and attach
15170 - Expire old streams that haven't managed to connect. Some day we'll
15171 have them reattach to new circuits instead.
15174 - Fix several memory leaks that were causing servers to become bloated
15176 - Fix a few very rare assert triggers. A few more remain.
15177 - Setuid to User _before_ complaining about running as root.
15180 Changes in version 0.0.2pre19 - 2004-01-07
15182 - Fix deadlock condition in dns farm. We were telling a child to die by
15183 closing the parent's file descriptor to him. But newer children were
15184 inheriting the open file descriptor from the parent, and since they
15185 weren't closing it, the socket never closed, so the child never read
15186 eof, so he never knew to exit. Similarly, dns workers were holding
15187 open other sockets, leading to all sorts of chaos.
15188 - New cleaner daemon() code for forking and backgrounding.
15189 - If you log to a file, it now prints an entry at the top of the
15190 logfile so you know it's working.
15191 - The onionskin challenge length was 30 bytes longer than necessary.
15192 - Started to patch up the spec so it's not quite so out of date.
15195 Changes in version 0.0.2pre18 - 2004-01-02
15197 - Fix endian issues with the 'integrity' field in the relay header.
15198 - Fix a potential bug where connections in state
15199 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15202 Changes in version 0.0.2pre17 - 2003-12-30
15204 - Made --debuglogfile (or any second log file, actually) work.
15205 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15206 adversary could force us into an infinite loop.
15209 - Each onionskin handshake now includes a hash of the computed key,
15210 to prove the server's identity and help perfect forward secrecy.
15211 - Changed cell size from 256 to 512 bytes (working toward compatibility
15213 - Changed cell length to 2 bytes, and moved it to the relay header.
15214 - Implemented end-to-end integrity checking for the payloads of
15216 - Separated streamid from 'recognized' (otherwise circuits will get
15217 messed up when we try to have streams exit from the middle). We
15218 use the integrity-checking to confirm that a cell is addressed to
15220 - Randomize the initial circid and streamid values, so an adversary who
15221 breaks into a node can't learn how many circuits or streams have
15225 Changes in version 0.0.2pre16 - 2003-12-14
15227 - Fixed a bug that made HUP trigger an assert
15228 - Fixed a bug where a circuit that immediately failed wasn't being
15229 counted as a failed circuit in counting retries.
15232 - Now we close the circuit when we get a truncated cell: otherwise we're
15233 open to an anonymity attack where a bad node in the path truncates
15234 the circuit and then we open streams at him.
15235 - Add port ranges to exit policies
15236 - Add a conservative default exit policy
15237 - Warn if you're running tor as root
15238 - on HUP, retry OR connections and close/rebind listeners
15239 - options.EntryNodes: try these nodes first when picking the first node
15240 - options.ExitNodes: if your best choices happen to include any of
15241 your preferred exit nodes, you choose among just those preferred
15243 - options.ExcludedNodes: nodes that are never picked in path building
15246 Changes in version 0.0.2pre15 - 2003-12-03
15247 o Robustness and bugfixes:
15248 - Sometimes clients would cache incorrect DNS resolves, which would
15249 really screw things up.
15250 - An OP that goes offline would slowly leak all its sockets and stop
15252 - A wide variety of bugfixes in exit node selection, exit policy
15253 handling, and processing pending streams when a new circuit is
15255 - Pick nodes for a path only from those the directory says are up
15256 - Choose randomly from all running dirservers, not always the first one
15257 - Increase allowed http header size for directory fetch.
15258 - Stop writing to stderr (if we're daemonized it will be closed).
15259 - Enable -g always, so cores will be more useful to me.
15260 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15263 - Wrote a man page. It lists commonly used options.
15266 - Change default loglevel to warn.
15267 - Make PidFile default to null rather than littering in your CWD.
15268 - OnionRouter config option is now obsolete. Instead it just checks
15270 - Moved to a single unified torrc file for both clients and servers.
15273 Changes in version 0.0.2pre14 - 2003-11-29
15274 o Robustness and bugfixes:
15275 - Force the admin to make the DataDirectory himself
15276 - to get ownership/permissions right
15277 - so clients no longer make a DataDirectory and then never use it
15278 - fix bug where a client who was offline for 45 minutes would never
15279 pull down a directory again
15280 - fix (or at least hide really well) the dns assert bug that was
15281 causing server crashes
15282 - warnings and improved robustness wrt clockskew for certs
15283 - use the native daemon(3) to daemonize, when available
15284 - exit if bind() fails
15285 - exit if neither socksport nor orport is defined
15286 - include our own tor_timegm (Win32 doesn't have its own)
15287 - bugfix for win32 with lots of connections
15288 - fix minor bias in PRNG
15289 - make dirserver more robust to corrupt cached directory
15292 - Wrote the design document (woo)
15294 o Circuit building and exit policies:
15295 - Circuits no longer try to use nodes that the directory has told them
15297 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15298 bitcounts (18.0.0.0/8).
15299 - Make AP connections standby for a circuit if no suitable circuit
15300 exists, rather than failing
15301 - Circuits choose exit node based on addr/port, exit policies, and
15302 which AP connections are standing by
15303 - Bump min pathlen from 2 to 3
15304 - Relay end cells have a payload to describe why the stream ended.
15305 - If the stream failed because of exit policy, try again with a new
15307 - Clients have a dns cache to remember resolved addresses.
15308 - Notice more quickly when we have no working circuits
15311 - APPort is now called SocksPort
15312 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15314 - RecommendedVersions is now a config variable rather than
15315 hardcoded (for dirservers)
15316 - Reloads config on HUP
15317 - Usage info on -h or --help
15318 - If you set User and Group config vars, it'll setu/gid to them.
15321 Changes in version 0.0.2pre13 - 2003-10-19
15322 o General stability:
15323 - SSL_write no longer fails when it returns WANTWRITE and the number
15324 of bytes in the buf has changed by the next SSL_write call.
15325 - Fix segfault fetching directory when network is down
15326 - Fix a variety of minor memory leaks
15327 - Dirservers reload the fingerprints file on HUP, so I don't have
15328 to take down the network when I approve a new router
15329 - Default server config file has explicit Address line to specify fqdn
15332 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15333 - Make listener connections not ever alloc bufs
15335 o Autoconf improvements:
15336 - don't clobber an external CFLAGS in ./configure
15337 - Make install now works
15338 - create var/lib/tor on make install
15339 - autocreate a tor.sh initscript to help distribs
15340 - autocreate the torrc and sample-server-torrc with correct paths
15342 o Log files and Daemonizing now work:
15343 - If --DebugLogFile is specified, log to it at -l debug
15344 - If --LogFile is specified, use it instead of commandline
15345 - If --RunAsDaemon is set, tor forks and backgrounds on startup