1 Changes in version 0.2.4.14-alpha - 2013-06-18
2 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
3 present in 0.2.4.13-alpha.
6 - When we have too much memory queued in circuits (according to a new
7 MaxMemInCellQueues option), close the circuits consuming the most
8 memory. This prevents us from running out of memory as a relay if
9 circuits fill up faster than they can be drained. Fixes bug 9063;
10 bugfix on the 54th commit of Tor. This bug is a further fix beyond
11 bug 6252, whose fix was merged into 0.2.3.21-rc.
13 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
14 where we tried to solve this issue simply by imposing an upper limit
15 on the number of queued cells for a single circuit. That approach
16 proved to be problematic, since there are ways to provoke clients to
17 send a number of cells in excess of any such reasonable limit. Fixes
18 bug 9072; bugfix on 0.2.4.13-alpha.
20 - Limit hidden service descriptors to at most ten introduction
21 points, to slow one kind of guard enumeration. Fixes bug 9002;
22 bugfix on 0.1.1.11-alpha.
25 Changes in version 0.2.4.13-alpha - 2013-06-14
26 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
27 vulnerabilities, makes socks5 username/password circuit isolation
28 actually actually work (this time for sure!), and cleans up a bunch
29 of other issues in preparation for a release candidate.
31 o Major bugfixes (robustness):
32 - Close any circuit that has too many cells queued on it. Fixes
33 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
34 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
35 - Prevent the get_freelists() function from running off the end of
36 the list of freelists if it somehow gets an unrecognized
37 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
39 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
40 when an exit connection with optimistic data succeeds immediately
41 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
43 - Fix a directory authority crash bug when building a consensus
44 using an older consensus as its basis. Fixes bug 8833. Bugfix
48 - Avoid a memory leak where we would leak a consensus body when we
49 find that a consensus which we couldn't previously verify due to
50 missing certificates is now verifiable. Fixes bug 8719; bugfix
52 - We used to always request authority certificates by identity digest,
53 meaning we'd get the newest one even when we wanted one with a
54 different signing key. Then we would complain about being given
55 a certificate we already had, and never get the one we really
56 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
57 resource to request the one we want. Fixes bug 5595; bugfix on
59 - Follow the socks5 protocol when offering username/password
60 authentication. The fix for bug 8117 exposed this bug, and it
61 turns out real-world applications like Pidgin do care. Bugfix on
62 0.2.3.2-alpha; fixes bug 8879.
63 - Prevent failures on Windows Vista and later when rebuilding the
64 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
65 bugfix on 0.2.4.12-alpha.
68 - Fix an impossible buffer overrun in the AES unit tests. Fixes
69 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
70 - If for some reason we fail to write a microdescriptor while
71 rebuilding the cache, do not let the annotations from that
72 microdescriptor linger in the cache file, and do not let the
73 microdescriptor stay recorded as present in its old location.
74 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
75 - Fix a memory leak that would occur whenever a configuration
76 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
77 - Paste the description for PathBias parameters from the man
78 page into or.h, so the code documents them too. Fixes bug 7982;
79 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
80 - Relays now treat a changed IPv6 ORPort as sufficient reason to
81 publish an updated descriptor. Fixes bug 6026; bugfix on
83 - When launching a resolve request on behalf of an AF_UNIX control
84 socket, omit the address field of the new entry connection, used in
85 subsequent controller events, rather than letting tor_dup_addr()
86 set it to "<unknown address type>". Fixes bug 8639; bugfix on
89 o Minor bugfixes (log messages):
90 - Fix a scaling issue in the path bias accounting code that
91 resulted in "Bug:" log messages from either
92 pathbias_scale_close_rates() or pathbias_count_build_success().
93 This represents a bugfix on a previous bugfix: the original fix
94 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
96 - Give a less useless error message when the user asks for an IPv4
97 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
101 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
102 to tolerate bug 8093 for now.
103 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
104 in directory authority votes to describe whether they have enough
105 measured bandwidths to ignore advertised (relay descriptor)
106 bandwidth claims. Resolves ticket 8711.
107 - Update to the June 5 2013 Maxmind GeoLite Country database.
109 o Removed documentation:
110 - Remove some of the older contents of doc/ as obsolete; move others
111 to torspec.git. Fixes bug 8965.
113 o Code simplification and refactoring:
114 - Avoid using character buffers when constructing most directory
115 objects: this approach was unwieldy and error-prone. Instead,
116 build smartlists of strings, and concatenate them when done.
119 Changes in version 0.2.4.12-alpha - 2013-04-18
120 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
121 process for lengthening the guard rotation period, makes directory
122 authority opinions in the consensus a bit less gameable, makes socks5
123 username/password circuit isolation actually work, and fixes a wide
124 variety of other issues.
127 - Raise the default time that a client keeps an entry guard from
128 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
129 2012 paper. (We would make it even longer, but we need better client
130 load balancing first.) Also, make the guard lifetime controllable
131 via a new GuardLifetime torrc option and a GuardLifetime consensus
132 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
133 - Directory authorities now prefer using measured bandwidths to
134 advertised ones when computing flags and thresholds. Resolves
136 - Directory authorities that have more than a threshold number
137 of relays with measured bandwidths now treat relays with unmeasured
138 bandwidths as having bandwidth 0. Resolves ticket 8435.
140 o Major bugfixes (assert / resource use):
141 - Avoid a bug where our response to TLS renegotiation under certain
142 network conditions could lead to a busy-loop, with 100% CPU
143 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
144 - Avoid an assertion when we discover that we'd like to write a cell
145 onto a closing connection: just discard the cell. Fixes another
146 case of bug 7350; bugfix on 0.2.4.4-alpha.
148 o Major bugfixes (client-side privacy):
149 - When we mark a circuit as unusable for new circuits, have it
150 continue to be unusable for new circuits even if MaxCircuitDirtiness
151 is increased too much at the wrong time, or the system clock jumps
152 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
153 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
154 which have resolved to internal addresses") is set, apply that
155 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
156 - When an exit relay rejects a stream with reason "exit policy", but
157 we only know an exit policy summary (e.g. from the microdesc
158 consensus) for it, do not mark the relay as useless for all exiting.
159 Instead, mark just the circuit as unsuitable for that particular
160 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
161 - Allow applications to get proper stream isolation with
162 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
163 username/password authentication also offer "no authentication". Tor
164 had previously preferred "no authentication", so the applications
165 never actually sent Tor their auth details. Now Tor selects
166 username/password authentication if it's offered. You can disable
167 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
168 bug 8117; bugfix on 0.2.3.3-alpha.
170 o Major bugfixes (other):
171 - When unable to find any working directory nodes to use as a
172 directory guard, give up rather than adding the same non-working
173 nodes to the directory guard list over and over. Fixes bug 8231;
174 bugfix on 0.2.4.8-alpha.
177 - Reject as invalid most directory objects containing a NUL.
178 Belt-and-suspender fix for bug 8037.
179 - In our testsuite, create temporary directories with a bit more
180 entropy in their name to make name collisions less likely. Fixes
182 - Add CACHED keyword to ADDRMAP events in the control protocol
183 to indicate whether a DNS result will be cached or not. Resolves
185 - Update to the April 3 2013 Maxmind GeoLite Country database.
187 o Minor features (build):
188 - Detect and reject attempts to build Tor with threading support
189 when OpenSSL has been compiled without threading support.
191 - Clarify that when autoconf is checking for nacl, it is checking
192 specifically for nacl with a fast curve25519 implementation.
194 - Warn if building on a platform with an unsigned time_t: there
195 are too many places where Tor currently assumes that time_t can
196 hold negative values. We'd like to fix them all, but probably
199 o Minor bugfixes (build):
200 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
201 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
202 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
203 - Add the old src/or/micro-revision.i filename to CLEANFILES.
204 On the off chance that somebody has one, it will go away as soon
205 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
206 - Build Tor correctly on 32-bit platforms where the compiler can build
207 but not run code using the "uint128_t" construction. Fixes bug 8587;
208 bugfix on 0.2.4.8-alpha.
209 - Fix compilation warning with some versions of clang that would
210 prefer the -Wswitch-enum compiler flag to warn about switch
211 statements with missing enum values, even if those switch
212 statements have a "default:" statement. Fixes bug 8598; bugfix
215 o Minor bugfixes (protocol):
216 - Fix the handling of a TRUNCATE cell when it arrives while the
217 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
218 - Fix a misframing issue when reading the version numbers in a
219 VERSIONS cell. Previously we would recognize [00 01 00 02] as
220 'version 1, version 2, and version 0x100', when it should have
221 only included versions 1 and 2. Fixes bug 8059; bugfix on
222 0.2.0.10-alpha. Reported pseudonymously.
223 - Make the format and order of STREAM events for DNS lookups
224 consistent among the various ways to launch DNS lookups. Fixes
225 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
226 - Correct our check for which versions of Tor support the EXTEND2
227 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
228 later, when support was really added in version 0.2.4.8-alpha.
229 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
231 o Minor bugfixes (other):
232 - Correctly store microdescriptors and extrainfo descriptors with
233 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
234 Bug reported by "cypherpunks".
235 - Increase the width of the field used to remember a connection's
236 link protocol version to two bytes. Harmless for now, since the
237 only currently recognized versions are one byte long. Reported
238 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
239 - If the state file's path bias counts are invalid (presumably from a
240 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
241 additional checks and log messages to the scaling of Path Bias
242 counts, in case there still are remaining issues with scaling.
243 Should help resolve bug 8235.
244 - Eliminate several instances where we use "Nickname=ID" to refer to
245 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
246 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
247 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
249 o Minor bugfixes (syscalls):
250 - Always check the return values of functions fcntl() and
251 setsockopt(). We don't believe these are ever actually failing in
252 practice, but better safe than sorry. Also, checking these return
253 values should please analysis tools like Coverity. Patch from
254 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
255 - Use direct writes rather than stdio when building microdescriptor
256 caches, in an attempt to mitigate bug 8031, or at least make it
259 o Minor bugfixes (config):
260 - When rejecting a configuration because we were unable to parse a
261 quoted string, log an actual error message. Fixes bug 7950; bugfix
263 - Behave correctly when the user disables LearnCircuitBuildTimeout
264 but doesn't tell us what they would like the timeout to be. Fixes
265 bug 6304; bugfix on 0.2.2.14-alpha.
266 - When autodetecting the number of CPUs, use the number of available
267 CPUs in preference to the number of configured CPUs. Inform the
268 user if this reduces the number of available CPUs. Fixes bug 8002;
269 bugfix on 0.2.3.1-alpha.
270 - Make it an error when you set EntryNodes but disable UseGuardNodes,
271 since it will (surprisingly to some users) ignore EntryNodes. Fixes
272 bug 8180; bugfix on 0.2.3.11-alpha.
273 - Allow TestingTorNetworks to override the 4096-byte minimum for
274 the Fast threshold. Otherwise they can't bootstrap until they've
275 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
276 - Fix some logic errors when the user manually overrides the
277 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
280 o Minor bugfixes (log messages to help diagnose bugs):
281 - If we fail to free a microdescriptor because of bug 7164, log
282 the filename and line number from which we tried to free it.
283 - Add another diagnostic to the heartbeat message: track and log
284 overhead that TLS is adding to the data we write. If this is
285 high, we are sending too little data to SSL_write at a time.
286 Diagnostic for bug 7707.
287 - Add more detail to a log message about relaxed timeouts, to help
289 - Warn more aggressively when flushing microdescriptors to a
290 microdescriptor cache fails, in an attempt to mitigate bug 8031,
291 or at least make it more diagnosable.
292 - Improve debugging output to help track down bug 8185 ("Bug:
293 outgoing relay cell has n_chan==NULL. Dropping.")
294 - Log the purpose of a path-bias testing circuit correctly.
295 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
297 o Minor bugfixes (0.2.4.x log messages that were too noisy):
298 - Don't attempt to relax the timeout of already opened 1-hop circuits.
299 They might never timeout. This should eliminate some/all cases of
300 the relaxed timeout log message.
301 - Use circuit creation time for network liveness evaluation. This
302 should eliminate warning log messages about liveness caused
303 by changes in timeout evaluation. Fixes bug 6572; bugfix on
305 - Reduce a path bias length check from notice to info. The message
306 is triggered when creating controller circuits. Fixes bug 8196;
307 bugfix on 0.2.4.8-alpha.
308 - Fix a path state issue that triggered a notice during relay startup.
309 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
310 - Reduce occurrences of warns about circuit purpose in
311 connection_ap_expire_building(). Fixes bug 8477; bugfix on
314 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
315 - If we encounter a write failure on a SOCKS connection before we
316 finish our SOCKS handshake, don't warn that we closed the
317 connection before we could send a SOCKS reply. Fixes bug 8427;
318 bugfix on 0.1.0.1-rc.
319 - Correctly recognize that [::1] is a loopback address. Fixes
320 bug 8377; bugfix on 0.2.1.3-alpha.
321 - Fix a directory authority warn caused when we have a large amount
322 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
323 - Don't log inappropriate heartbeat messages when hibernating: a
324 hibernating node is _expected_ to drop out of the consensus,
325 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
326 bugfix on 0.2.3.1-alpha.
327 - Don't complain about bootstrapping problems while hibernating.
328 These complaints reflect a general code problem, but not one
329 with any problematic effects (no connections are actually
330 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
332 o Documentation fixes:
333 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
334 names match. Fixes bug 7768.
335 - Make the torify manpage no longer refer to tsocks; torify hasn't
336 supported tsocks since 0.2.3.14-alpha.
337 - Make the tor manpage no longer reference tsocks.
338 - Fix the GeoIPExcludeUnknown documentation to refer to
339 ExcludeExitNodes rather than the currently nonexistent
340 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
343 - The tor-tsocks.conf is no longer distributed or installed. We
344 recommend that tsocks users use torsocks instead. Resolves
348 Changes in version 0.2.4.11-alpha - 2013-03-11
349 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
350 more robust, makes hidden service authentication work again, and
351 resolves a DPI fingerprint for Tor's SSL transport.
353 o Major features (directory authorities):
354 - Directory authorities now support a new consensus method (17)
355 where they cap the published bandwidth of servers for which
356 insufficient bandwidth measurements exist. Fixes part of bug 2286.
357 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
358 serve any v2 directory information. Now we can test disabling the
359 old deprecated v2 directory format, and see whether doing so has
360 any effect on network load. Begins to fix bug 6783.
361 - Directory authorities now include inside each vote a statement of
362 the performance thresholds they used when assigning flags.
363 Implements ticket 8151.
365 o Major bugfixes (directory authorities):
366 - Stop marking every relay as having been down for one hour every
367 time we restart a directory authority. These artificial downtimes
368 were messing with our Stable and Guard flag calculations. Fixes
369 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
371 o Major bugfixes (hidden services):
372 - Allow hidden service authentication to succeed again. When we
373 refactored the hidden service introduction code back
374 in 0.2.4.1-alpha, we didn't update the code that checks
375 whether authentication information is present, causing all
376 authentication checks to return "false". Fix for bug 8207; bugfix
377 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
379 o Minor features (relays, bridges):
380 - Make bridge relays check once a minute for whether their IP
381 address has changed, rather than only every 15 minutes. Resolves
383 - Refactor resolve_my_address() so it returns the method by which we
384 decided our public IP address (explicitly configured, resolved from
385 explicit hostname, guessed from interfaces, learned by gethostname).
386 Now we can provide more helpful log messages when a relay guesses
387 its IP address incorrectly (e.g. due to unexpected lines in
388 /etc/hosts). Resolves ticket 2267.
389 - Teach bridge-using clients to avoid 0.2.2 bridges when making
390 microdescriptor-related dir requests, and only fall back to normal
391 descriptors if none of their bridges can handle microdescriptors
392 (as opposed to the fix in ticket 4013, which caused them to fall
393 back to normal descriptors if *any* of their bridges preferred
394 them). Resolves ticket 4994.
395 - Randomize the lifetime of our SSL link certificate, so censors can't
396 use the static value for filtering Tor flows. Resolves ticket 8443;
397 related to ticket 4014 which was included in 0.2.2.33.
399 o Minor features (portability):
400 - Tweak the curve25519-donna*.c implementations to tolerate systems
401 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
402 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
403 the signs of types during autoconf. This is better than our old
404 approach, which didn't work when cross-compiling.
405 - Detect the sign of enum values, rather than assuming that MSC is the
406 only compiler where enum types are all signed. Fixes bug 7727;
407 bugfix on 0.2.4.10-alpha.
409 o Minor features (other):
410 - Say "KBytes" rather than "KB" in the man page (for various values
411 of K), to further reduce confusion about whether Tor counts in
412 units of memory or fractions of units of memory. Resolves ticket 7054.
413 - Clear the high bit on curve25519 public keys before passing them to
414 our backend, in case we ever wind up using a backend that doesn't do
415 so itself. If we used such a backend, and *didn't* clear the high bit,
416 we could wind up in a situation where users with such backends would
417 be distinguishable from users without. Fixes bug 8121; bugfix on
419 - Update to the March 6 2013 Maxmind GeoLite Country database.
421 o Minor bugfixes (clients):
422 - When we receive a RELAY_END cell with the reason DONE, or with no
423 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
424 status as "connection refused". Previously we reported these cases
425 as success but then immediately closed the connection. Fixes bug
426 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
427 - Downgrade an assertion in connection_ap_expire_beginning to an
428 LD_BUG message. The fix for bug 8024 should prevent this message
429 from displaying, but just in case, a warn that we can diagnose
430 is better than more assert crashes. Fixes bug 8065; bugfix on
432 - Lower path use bias thresholds to .80 for notice and .60 for warn.
433 Also make the rate limiting flags for the path use bias log messages
434 independent from the original path bias flags. Fixes bug 8161;
435 bugfix on 0.2.4.10-alpha.
437 o Minor bugfixes (relays):
438 - Stop trying to resolve our hostname so often (e.g. every time we
439 think about doing a directory fetch). Now we reuse the cached
440 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
441 and 2410 (bugfix on 0.1.2.2-alpha).
442 - Stop sending a stray "(null)" in some cases for the server status
443 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
445 - When choosing which stream on a formerly stalled circuit to wake
446 first, make better use of the platform's weak RNG. Previously,
447 we had been using the % ("modulo") operator to try to generate a
448 1/N chance of picking each stream, but this behaves badly with
449 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
451 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
452 Irix's random() only return 15 bits; Solaris's random() returns more
453 bits but its RAND_MAX says it only returns 15, and so on. Motivated
454 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
456 o Minor bugfixes (directory authorities):
457 - Directory authorities now use less space when formatting identical
458 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
461 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
462 - Avoid leaking memory if we fail to compute a consensus signature
463 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
464 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
466 - Fix a memory leak during safe-cookie controller authentication.
467 Bugfix on 0.2.3.13-alpha.
468 - Avoid memory leak of IPv6 policy content if we fail to format it into
469 a router descriptor. Bugfix on 0.2.4.7-alpha.
471 o Minor bugfixes (other code correctness issues):
472 - Avoid a crash if we fail to generate an extrainfo descriptor.
473 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
475 - When detecting the largest possible file descriptor (in order to
476 close all file descriptors when launching a new program), actually
477 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
478 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
480 - Fix a copy-and-paste error when adding a missing A1 to a routerset
481 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
482 Bugfix on 0.2.4.10-alpha.
483 - Fix an impossible-to-trigger integer overflow when estimating how
484 long our onionskin queue would take. (This overflow would require us
485 to accept 4 million onionskins before processing 100 of them.) Fixes
486 bug 8210; bugfix on 0.2.4.10-alpha.
488 o Code simplification and refactoring:
489 - Add a wrapper function for the common "log a message with a
493 Changes in version 0.2.4.10-alpha - 2013-02-04
494 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
495 certain attacks that flood the network with relays; changes the queue
496 for circuit create requests from a sized-based limit to a time-based
497 limit; resumes building with MSVC on Windows; and fixes a wide variety
500 o Major bugfixes (directory authority):
501 - When computing directory thresholds, ignore any rejected-as-sybil
502 nodes during the computation so that they can't influence Fast,
503 Guard, etc. (We should have done this for proposal 109.) Fixes
505 - When marking a node as a likely sybil, reset its uptime metrics
506 to zero, so that it cannot time towards getting marked as Guard,
507 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
511 - When a TLS write is partially successful but incomplete, remember
512 that the flushed part has been flushed, and notice that bytes were
513 actually written. Reported and fixed pseudonymously. Fixes bug
514 7708; bugfix on Tor 0.1.0.5-rc.
515 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
516 ID: these could be used to create unexpected streams and circuits
517 which would count as "present" to some parts of Tor but "absent"
518 to others, leading to zombie circuits and streams or to a bandwidth
519 denial-of-service. Fixes bug 7889; bugfix on every released version
520 of Tor. Reported by "oftc_must_be_destroyed".
521 - Rename all macros in our local copy of queue.h to begin with "TOR_".
522 This change seems the only good way to permanently prevent conflicts
523 with queue.h on various operating systems. Fixes bug 8107; bugfix
526 o Major features (relay):
527 - Instead of limiting the number of queued onionskins (aka circuit
528 create requests) to a fixed, hard-to-configure number, we limit
529 the size of the queue based on how many we expect to be able to
530 process in a given amount of time. We estimate the time it will
531 take to process an onionskin based on average processing time
532 of previous onionskins. Closes ticket 7291. You'll never have to
533 configure MaxOnionsPending again.
535 o Major features (portability):
536 - Resume building correctly with MSVC and Makefile.nmake. This patch
537 resolves numerous bugs and fixes reported by ultramage, including
538 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
539 - Make the ntor and curve25519 code build correctly with MSVC.
540 Fix on 0.2.4.8-alpha.
543 - When directory authorities are computing thresholds for flags,
544 never let the threshold for the Fast flag fall below 4096
545 bytes. Also, do not consider nodes with extremely low bandwidths
546 when deciding thresholds for various directory flags. This change
547 should raise our threshold for Fast relays, possibly in turn
548 improving overall network performance; see ticket 1854. Resolves
550 - The Tor client now ignores sub-domain components of a .onion
551 address. This change makes HTTP "virtual" hosting
552 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
553 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
554 hosted on the same hidden service. Implements proposal 204.
555 - We compute the overhead from passing onionskins back and forth to
556 cpuworkers, and report it when dumping statistics in response to
557 SIGUSR1. Supports ticket 7291.
559 o Minor features (path selection):
560 - When deciding whether we have enough descriptors to build circuits,
561 instead of looking at raw relay counts, look at which fraction
562 of (bandwidth-weighted) paths we're able to build. This approach
563 keeps clients from building circuits if their paths are likely to
564 stand out statistically. The default fraction of paths needed is
565 taken from the consensus directory; you can override it with the
566 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
567 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
568 and we have GeoIP information, also exclude all nodes with unknown
569 countries "??" and "A1". This behavior is controlled by the
570 new GeoIPExcludeUnknown option: you can make such nodes always
571 excluded with "GeoIPExcludeUnknown 1", and disable the feature
572 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
573 gets you the default behavior. Implements feature 7706.
574 - Path Use Bias: Perform separate accounting for successful circuit
575 use. Keep separate statistics on stream attempt rates versus stream
576 success rates for each guard. Provide configurable thresholds to
577 determine when to emit log messages or disable use of guards that
578 fail too many stream attempts. Resolves ticket 7802.
580 o Minor features (log messages):
581 - When learning a fingerprint for a bridge, log its corresponding
582 transport type. Implements ticket 7896.
583 - Improve the log message when "Bug/attack: unexpected sendme cell
584 from client" occurs, to help us track bug 8093.
587 - Remove a couple of extraneous semicolons that were upsetting the
588 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
589 bugfix on 0.2.2.1-alpha.
590 - Remove a source of rounding error during path bias count scaling;
591 don't count cannibalized circuits as used for path bias until we
592 actually try to use them; and fix a circuit_package_relay_cell()
593 warning message about n_chan==NULL. Fixes bug 7802.
594 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
595 actually link against nacl when we're configured to use it. Fixes
596 bug 7972; bugfix on 0.2.4.8-alpha.
597 - Compile correctly with the --disable-curve25519 option. Fixes
598 bug 8153; bugfix on 0.2.4.8-alpha.
600 o Build improvements:
601 - Do not report status verbosely from autogen.sh unless the -v flag
602 is specified. Fixes issue 4664. Patch from Onizuka.
603 - Replace all calls to snprintf() outside of src/ext with
604 tor_snprintf(). Also remove the #define to replace snprintf with
605 _snprintf on Windows; they have different semantics, and all of
606 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
607 - Try to detect if we are ever building on a platform where
608 memset(...,0,...) does not set the value of a double to 0.0. Such
609 platforms are permitted by the C standard, though in practice
610 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
611 currently support them, but it's better to detect them and fail
612 than to perform erroneously.
615 - Stop exporting estimates of v2 and v3 directory traffic shares
616 in extrainfo documents. They were unneeded and sometimes inaccurate.
617 Also stop exporting any v2 directory request statistics. Resolves
619 - Drop support for detecting and warning about versions of Libevent
620 before 1.3e. Nothing reasonable ships with them any longer;
621 warning the user about them shouldn't be needed. Resolves ticket
624 o Code simplifications and refactoring:
625 - Rename "isin" functions to "contains", for grammar. Resolves
627 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
628 with the natural logarithm function from the system libm. Resolves
632 Changes in version 0.2.4.9-alpha - 2013-01-15
633 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
637 - Fix backward compatibility logic when receiving an embedded ntor
638 handshake tunneled in a CREATE cell. This clears up the "Bug:
639 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
643 Changes in version 0.2.4.8-alpha - 2013-01-14
644 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
645 risks, adds a new stronger and faster circuit handshake, and offers
646 stronger and faster link encryption when both sides support it.
649 - Preliminary support for directory guards (proposal 207): when
650 possible, clients now use their entry guards for non-anonymous
651 directory requests. This can help prevent client enumeration. Note
652 that this behavior only works when we have a usable consensus
653 directory, and when options about what to download are more or less
654 standard. In the future we should re-bootstrap from our guards,
655 rather than re-bootstrapping from the preconfigured list of
656 directory sources that ships with Tor. Resolves ticket 6526.
657 - Tor relays and clients now support a better CREATE/EXTEND cell
658 format, allowing the sender to specify multiple address, identity,
659 and handshake types. Implements Robert Ransom's proposal 200;
662 o Major features (new circuit handshake):
663 - Tor now supports a new circuit extension handshake designed by Ian
664 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
665 circuit extension handshake, later called "TAP", was a bit slow
666 (especially on the relay side), had a fragile security proof, and
667 used weaker keys than we'd now prefer. The new circuit handshake
668 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
669 function, making it significantly more secure than the older
670 handshake, and significantly faster. Tor can use one of two built-in
671 pure-C curve25519-donna implementations by Adam Langley, or it
672 can link against the "nacl" library for a tuned version if present.
674 The built-in version is very fast for 64-bit systems when building
675 with GCC. The built-in 32-bit version is still faster than the
676 old TAP protocol, but using libnacl is better on most such hosts.
678 Clients don't currently use this protocol by default, since
679 comparatively few clients support it so far. To try it, set
680 UseNTorHandshake to 1.
682 Implements proposal 216; closes ticket 7202.
684 o Major features (better link encryption):
685 - Relays can now enable the ECDHE TLS ciphersuites when available
686 and appropriate. These ciphersuites let us negotiate forward-secure
687 TLS secret keys more safely and more efficiently than with our
688 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
689 public relays prefer the (faster) P224 group, and bridges prefer
690 the (more common) P256 group; you can override this with the
693 Enabling these ciphers was a little tricky, since for a long time,
694 clients had been claiming to support them without actually doing
695 so, in order to foil fingerprinting. But with the client-side
696 implementation of proposal 198 in 0.2.3.17-beta, clients can now
697 match the ciphers from recent Firefox versions *and* list the
698 ciphers they actually mean, so relays can believe such clients
699 when they advertise ECDHE support in their TLS ClientHello messages.
701 This feature requires clients running 0.2.3.17-beta or later,
702 and requires both sides to be running OpenSSL 1.0.0 or later
703 with ECC support. OpenSSL 1.0.1, with the compile-time option
704 "enable-ec_nistp_64_gcc_128", is highly recommended.
706 Implements the relay side of proposal 198; closes ticket 7200.
709 - Avoid crashing when, as a relay without IPv6-exit support, a
710 client insists on getting an IPv6 address or nothing. Fixes bug
711 7814; bugfix on 0.2.4.7-alpha.
714 - Improve circuit build timeout handling for hidden services.
715 In particular: adjust build timeouts more accurately depending
716 upon the number of hop-RTTs that a particular circuit type
717 undergoes. Additionally, launch intro circuits in parallel
718 if they timeout, and take the first one to reply as valid.
719 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
720 separate error codes; or at least, don't break for that reason.
721 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
722 - Update to the January 2 2013 Maxmind GeoLite Country database.
724 o Minor features (testing):
725 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
726 (P-256) Diffie-Hellman handshakes to src/or/bench.
727 - Add benchmark functions to test onion handshake performance.
729 o Minor features (path bias detection):
730 - Alter the Path Bias log messages to be more descriptive in terms
731 of reporting timeouts and other statistics.
732 - Create three levels of Path Bias log messages, as opposed to just
733 two. These are configurable via consensus as well as via the torrc
734 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
735 The default values are 0.70, 0.50, and 0.30 respectively.
736 - Separate the log message levels from the decision to drop guards,
737 which also is available via torrc option PathBiasDropGuards.
738 PathBiasDropGuards still defaults to 0 (off).
739 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
740 in combination with PathBiasExtremeRate.
741 - Increase the default values for PathBiasScaleThreshold and
742 PathBiasCircThreshold from (200, 20) to (300, 150).
743 - Add in circuit usage accounting to path bias. If we try to use a
744 built circuit but fail for any reason, it counts as path bias.
745 Certain classes of circuits where the adversary gets to pick your
746 destination node are exempt from this accounting. Usage accounting
747 can be specifically disabled via consensus parameter or torrc.
748 - Convert all internal path bias state to double-precision floating
749 point, to avoid roundoff error and other issues.
750 - Only record path bias information for circuits that have completed
751 *two* hops. Assuming end-to-end tagging is the attack vector, this
752 makes us more resilient to ambient circuit failure without any
753 detection capability loss.
755 o Minor bugfixes (log messages):
756 - Rate-limit the "No circuits are opened. Relaxed timeout for a
757 circuit with channel state open..." message to once per hour to
758 keep it from filling the notice logs. Mitigates bug 7799 but does
759 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
760 - Avoid spurious warnings when configuring multiple client ports of
761 which only some are nonlocal. Previously, we had claimed that some
762 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
765 o Code simplifications and refactoring:
766 - Get rid of a couple of harmless clang warnings, where we compared
767 enums to ints. These warnings are newly introduced in clang 3.2.
768 - Split the onion.c file into separate modules for the onion queue
769 and the different handshakes it supports.
770 - Remove the marshalling/unmarshalling code for sending requests to
771 cpuworkers over a socket, and instead just send structs. The
772 recipient will always be the same Tor binary as the sender, so
773 any encoding is overkill.
776 Changes in version 0.2.4.7-alpha - 2012-12-24
777 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
778 directory mirrors for more robust bootstrapping; fixes more issues where
779 clients with changing network conditions refuse to make any circuits;
780 adds initial support for exiting to IPv6 addresses; resumes being able
781 to update our GeoIP database, and includes the geoip6 file this time;
782 turns off the client-side DNS cache by default due to privacy risks;
783 and fixes a variety of other issues.
785 o Major features (client resilience):
786 - Add a new "FallbackDir" torrc option to use when we can't use
787 a directory mirror from the consensus (either because we lack a
788 consensus, or because they're all down). Currently, all authorities
789 are fallbacks by default, and there are no other default fallbacks,
790 but that will change. This option will allow us to give clients a
791 longer list of servers to try to get a consensus from when first
792 connecting to the Tor network, and thereby reduce load on the
793 directory authorities. Implements proposal 206, "Preconfigured
794 directory sources for bootstrapping". We also removed the old
795 "FallbackNetworkstatus" option, since we never got it working well
796 enough to use it. Closes bug 572.
797 - If we have no circuits open, use a relaxed timeout (the
798 95-percentile cutoff) until a circuit succeeds. This heuristic
799 should allow Tor to succeed at building circuits even when the
800 network connection drastically changes. Should help with bug 3443.
802 o Major features (IPv6):
803 - Tor now has (alpha) support for exiting to IPv6 addresses. To
804 enable it as an exit node, make sure that you have IPv6
805 connectivity, then set the IPv6Exit flag to 1. Also make sure your
806 exit policy reads as you would like: the address * applies to all
807 address families, whereas *4 is IPv4 address only, and *6 is IPv6
808 addresses only. On the client side, you'll need to wait until the
809 authorities have upgraded, wait for enough exits to support IPv6,
810 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
811 ticket 5547, implements proposal 117 as revised in proposal 208.
813 We DO NOT recommend that clients with actual anonymity needs start
814 using IPv6 over Tor yet, since not enough exits support it yet.
816 o Major features (geoip database):
817 - Maxmind began labelling Tor relays as being in country "A1",
818 which breaks by-country node selection inside Tor. Now we use a
819 script to replace "A1" ("Anonymous Proxy") entries in our geoip
820 file with real country codes. This script fixes about 90% of "A1"
821 entries automatically and uses manual country code assignments to
822 fix the remaining 10%. See src/config/README.geoip for details.
823 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
824 Country database, as modified above.
826 o Major bugfixes (client-side DNS):
827 - Turn off the client-side DNS cache by default. Updating and using
828 the DNS cache is now configurable on a per-client-port
829 level. SOCKSPort, DNSPort, etc lines may now contain
830 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
831 cache these types of DNS answers when we receive them from an
832 exit node in response to an application request on this port, and
833 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
834 cached DNS answers of these types, we shouldn't use them. It's
835 potentially risky to use cached DNS answers at the client, since
836 doing so can indicate to one exit what answers we've gotten
837 for DNS lookups in the past. With IPv6, this becomes especially
838 problematic. Using cached DNS answers for requests on the same
839 circuit would present less linkability risk, since all traffic
840 on a circuit is already linkable, but it would also provide
841 little performance benefit: the exit node caches DNS replies
842 too. Implements a simplified version of Proposal 205. Implements
845 o Major bugfixes (other):
846 - Alter circuit build timeout measurement to start at the point
847 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
848 initialization). This should make our timeout measurements more
849 uniform. Previously, we were sometimes including ORconn setup time
850 in our circuit build time measurements. Should resolve bug 3443.
851 - Fix an assertion that could trigger in hibernate_go_dormant() when
852 closing an or_connection_t: call channel_mark_for_close() rather
853 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
855 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
856 7655; bugfix on 0.2.4.6-alpha.
859 - Add a new torrc option "ServerTransportListenAddr" to let bridge
860 operators select the address where their pluggable transports will
861 listen for connections. Resolves ticket 7013.
862 - Allow an optional $ before the node identity digest in the
863 controller command GETINFO ns/id/<identity>, for consistency with
864 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
865 - Log packaged cell fullness as part of the heartbeat message.
866 Diagnosis to try to determine the extent of bug 7743.
868 o Minor features (IPv6):
869 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
870 prefer to hand out virtual IPv6 addresses, since there are more of
871 them and we can't run out. To override this behavior and make IPv4
872 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
873 or DNSPort you're using for resolving. Implements ticket 7571.
874 - AutomapHostsOnResolve responses are now randomized, to avoid
875 annoying situations where Tor is restarted and applications
876 connect to the wrong addresses.
877 - Never try more than 1000 times to pick a new virtual address when
878 AutomapHostsOnResolve is set. That's good enough so long as we
879 aren't close to handing out our entire virtual address space;
880 if you're getting there, it's best to switch to IPv6 virtual
884 - The ADDRMAP command can no longer generate an ill-formed error
885 code on a failed MAPADDRESS. It now says "internal" rather than
886 an English sentence fragment with spaces in the middle. Bugfix on
888 - Fix log messages and comments to avoid saying "GMT" when we mean
889 "UTC". Fixes bug 6113.
890 - Compile on win64 using mingw64. Fixes bug 7260; patches from
892 - Fix a crash when debugging unit tests on Windows: deallocate a
893 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
894 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
897 - The DirServer option is now DirAuthority, for consistency with
898 current naming patterns. You can still use the old DirServer form.
900 o Code simplification and refactoring:
901 - Move the client-side address-map/virtual-address/DNS-cache code
902 out of connection_edge.c into a new addressmap.c module.
903 - Remove unused code for parsing v1 directories and "running routers"
904 documents. Fixes bug 6887.
907 Changes in version 0.2.3.25 - 2012-11-19
908 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
909 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
910 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
911 programmer, and friend. Unstinting in his dedication to the cause of
912 freedom, he inspired and helped many of us as we began our work on
913 anonymity, and inspires us still. Please honor his memory by writing
914 software to protect people's freedoms, and by helping others to do so.
916 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
917 significantly reduced directory overhead (via microdescriptors),
918 enormous crypto performance improvements for fast relays on new
919 enough hardware, a new v3 TLS handshake protocol that can better
920 resist fingerprinting, support for protocol obfuscation plugins (aka
921 pluggable transports), better scalability for hidden services, IPv6
922 support for bridges, performance improvements like allowing clients
923 to skip the first round-trip on the circuit ("optimistic data") and
924 refilling token buckets more often, a new "stream isolation" design
925 to isolate different applications on different circuits, and many
926 stability, security, and privacy fixes.
929 - Tor tries to wipe potentially sensitive data after using it, so
930 that if some subsequent security failure exposes Tor's memory,
931 the damage will be limited. But we had a bug where the compiler
932 was eliminating these wipe operations when it decided that the
933 memory was no longer visible to a (correctly running) program,
934 hence defeating our attempt at defense in depth. We fix that
935 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
936 is unlikely to optimize away. Future versions of Tor may use
937 a less ridiculously heavy approach for this. Fixes bug 7352.
938 Reported in an article by Andrey Karpov.
941 - Fix a harmless bug when opting against publishing a relay descriptor
942 because DisableNetwork is set. Fixes bug 7464; bugfix on
946 Changes in version 0.2.4.6-alpha - 2012-11-13
947 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
948 makes our defense-in-depth memory wiping more reliable, and begins to
949 count IPv6 addresses in bridge statistics,
952 - Fix an assertion failure that could occur when closing a connection
953 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
955 - Tor tries to wipe potentially sensitive data after using it, so
956 that if some subsequent security failure exposes Tor's memory,
957 the damage will be limited. But we had a bug where the compiler
958 was eliminating these wipe operations when it decided that the
959 memory was no longer visible to a (correctly running) program,
960 hence defeating our attempt at defense in depth. We fix that
961 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
962 is unlikely to optimize away. Future versions of Tor may use
963 a less ridiculously heavy approach for this. Fixes bug 7352.
964 Reported in an article by Andrey Karpov.
967 - Add GeoIP database for IPv6 addresses. The new config option
969 - Bridge statistics now count bridge clients connecting over IPv6:
970 bridge statistics files now list "bridge-ip-versions" and
971 extra-info documents list "geoip6-db-digest". The control protocol
972 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
973 implementation by "shkoo", addressing ticket 5055.
976 - Warn when we are binding low ports when hibernation is enabled;
977 previously we had warned when we were _advertising_ low ports with
978 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
979 - Fix a harmless bug when opting against publishing a relay descriptor
980 because DisableNetwork is set. Fixes bug 7464; bugfix on
982 - Add warning message when a managed proxy dies during configuration.
983 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
984 - Fix a linking error when building tor-fw-helper without miniupnp.
985 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
986 - Check for closing an or_connection_t without going through correct
987 channel functions; emit a warning and then call
988 connection_or_close_for_error() so we don't assert as in bugs 7212
990 - Compile correctly on compilers without C99 designated initializer
991 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
992 - Avoid a possible assert that can occur when channel_send_destroy() is
993 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
994 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
995 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
996 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
997 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
999 o Code simplification and refactoring:
1000 - Start using OpenBSD's implementation of queue.h, so that we don't
1001 need to hand-roll our own pointer and list structures whenever we
1002 need them. (We can't rely on a sys/queue.h, since some operating
1003 systems don't have them, and the ones that do have them don't all
1004 present the same extensions.)
1007 Changes in version 0.2.4.5-alpha - 2012-10-25
1008 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1009 two important security vulnerabilities that could lead to remotely
1010 triggerable relay crashes, fix a major bug that was preventing clients
1011 from choosing suitable exit nodes, and refactor some of our code.
1013 o Major bugfixes (security, also in 0.2.3.24-rc):
1014 - Fix a group of remotely triggerable assertion failures related to
1015 incorrect link protocol negotiation. Found, diagnosed, and fixed
1016 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1018 - Fix a denial of service attack by which any directory authority
1019 could crash all the others, or by which a single v2 directory
1020 authority could crash everybody downloading v2 directory
1021 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1023 o Major bugfixes (also in 0.2.3.24-rc):
1024 - When parsing exit policy summaries from microdescriptors, we had
1025 previously been ignoring the last character in each one, so that
1026 "accept 80,443,8080" would be treated by clients as indicating
1027 a node that allows access to ports 80, 443, and 808. That would
1028 lead to clients attempting connections that could never work,
1029 and ignoring exit nodes that would support their connections. Now
1030 clients parse these exit policy summaries correctly. Fixes bug 7192;
1031 bugfix on 0.2.3.1-alpha.
1033 o Minor bugfixes (also in 0.2.3.24-rc):
1034 - Clients now consider the ClientRejectInternalAddresses config option
1035 when using a microdescriptor consensus stanza to decide whether
1036 an exit relay would allow exiting to an internal address. Fixes
1037 bug 7190; bugfix on 0.2.3.1-alpha.
1040 - Only disable TLS session ticket support when running as a TLS
1041 server. Now clients will blend better with regular Firefox
1042 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1044 o Code simplification and refactoring:
1045 - Start using OpenBSD's implementation of queue.h (originally by
1047 - Move the entry node code from circuitbuild.c to its own file.
1048 - Move the circuit build timeout tracking code from circuitbuild.c
1052 Changes in version 0.2.3.24-rc - 2012-10-25
1053 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1054 could lead to remotely triggerable relay crashes, and fixes
1055 a major bug that was preventing clients from choosing suitable exit
1058 o Major bugfixes (security):
1059 - Fix a group of remotely triggerable assertion failures related to
1060 incorrect link protocol negotiation. Found, diagnosed, and fixed
1061 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1063 - Fix a denial of service attack by which any directory authority
1064 could crash all the others, or by which a single v2 directory
1065 authority could crash everybody downloading v2 directory
1066 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1069 - When parsing exit policy summaries from microdescriptors, we had
1070 previously been ignoring the last character in each one, so that
1071 "accept 80,443,8080" would be treated by clients as indicating
1072 a node that allows access to ports 80, 443, and 808. That would
1073 lead to clients attempting connections that could never work,
1074 and ignoring exit nodes that would support their connections. Now
1075 clients parse these exit policy summaries correctly. Fixes bug 7192;
1076 bugfix on 0.2.3.1-alpha.
1079 - Clients now consider the ClientRejectInternalAddresses config option
1080 when using a microdescriptor consensus stanza to decide whether
1081 an exit relay would allow exiting to an internal address. Fixes
1082 bug 7190; bugfix on 0.2.3.1-alpha.
1085 Changes in version 0.2.4.4-alpha - 2012-10-20
1086 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1087 vulnerability introduced by a change in OpenSSL, fixes a remotely
1088 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1089 that will make it easier to test new connection transport and cell
1090 scheduling algorithms.
1092 o New directory authorities (also in 0.2.3.23-rc):
1093 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1094 authority. Closes ticket 5749.
1096 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1097 - Disable TLS session tickets. OpenSSL's implementation was giving
1098 our TLS session keys the lifetime of our TLS context objects, when
1099 perfect forward secrecy would want us to discard anything that
1100 could decrypt a link connection as soon as the link connection
1101 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1102 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1103 - Discard extraneous renegotiation attempts once the V3 link
1104 protocol has been initiated. Failure to do so left us open to
1105 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1106 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1108 o Internal abstraction features:
1109 - Introduce new channel_t abstraction between circuits and
1110 or_connection_t to allow for implementing alternate OR-to-OR
1111 transports. A channel_t is an abstract object which can either be a
1112 cell-bearing channel, which is responsible for authenticating and
1113 handshaking with the remote OR and transmitting cells to and from
1114 it, or a listening channel, which spawns new cell-bearing channels
1115 at the request of remote ORs. Implements part of ticket 6465.
1116 - Also new is the channel_tls_t subclass of channel_t, adapting it
1117 to the existing or_connection_t code. The V2/V3 protocol handshaking
1118 code which formerly resided in command.c has been moved below the
1119 channel_t abstraction layer and may be found in channeltls.c now.
1120 Implements the rest of ticket 6465.
1121 - Introduce new circuitmux_t storing the queue of circuits for
1122 a channel; this encapsulates and abstracts the queue logic and
1123 circuit selection policy, and allows the latter to be overridden
1124 easily by switching out a policy object. The existing EWMA behavior
1125 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1127 o Required libraries:
1128 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1129 strongly recommended.
1132 - Warn users who run hidden services on a Tor client with
1133 UseEntryGuards disabled that their hidden services will be
1134 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1135 attack which motivated Tor to support entry guards in the first
1136 place). Resolves ticket 6889.
1137 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1138 dhill. Resolves ticket 6982.
1139 - Option OutboundBindAddress can be specified multiple times and
1140 accepts IPv6 addresses. Resolves ticket 6876.
1142 o Minor bugfixes (also in 0.2.3.23-rc):
1143 - Don't serve or accept v2 hidden service descriptors over a
1144 relay's DirPort. It's never correct to do so, and disabling it
1145 might make it more annoying to exploit any bugs that turn up in the
1146 descriptor-parsing code. Fixes bug 7149.
1147 - Fix two cases in src/or/transports.c where we were calling
1148 fmt_addr() twice in a parameter list. Bug found by David
1149 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1150 - Fix memory leaks whenever we logged any message about the "path
1151 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1152 - When relays refuse a "create" cell because their queue of pending
1153 create cells is too big (typically because their cpu can't keep up
1154 with the arrival rate), send back reason "resource limit" rather
1155 than reason "internal", so network measurement scripts can get a
1156 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1159 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1160 - Free some more still-in-use memory at exit, to make hunting for
1161 memory leaks easier. Resolves bug 7029.
1162 - When a Tor client gets a "truncated" relay cell, the first byte of
1163 its payload specifies why the circuit was truncated. We were
1164 ignoring this 'reason' byte when tearing down the circuit, resulting
1165 in the controller not being told why the circuit closed. Now we
1166 pass the reason from the truncated cell to the controller. Bugfix
1167 on 0.1.2.3-alpha; fixes bug 7039.
1168 - Downgrade "Failed to hand off onionskin" messages to "debug"
1169 severity, since they're typically redundant with the "Your computer
1170 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1171 - Make clients running with IPv6 bridges connect over IPv6 again,
1172 even without setting new config options ClientUseIPv6 and
1173 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1174 - Use square brackets around IPv6 addresses in numerous places
1175 that needed them, including log messages, HTTPS CONNECT proxy
1176 requests, TransportProxy statefile entries, and pluggable transport
1177 extra-info lines. Fixes bug 7011; patch by David Fifield.
1179 o Code refactoring and cleanup:
1180 - Source files taken from other packages now reside in src/ext;
1181 previously they were scattered around the rest of Tor.
1182 - Avoid use of reserved identifiers in our C code. The C standard
1183 doesn't like us declaring anything that starts with an
1184 underscore, so let's knock it off before we get in trouble. Fix
1185 for bug 1031; bugfix on the first Tor commit.
1188 Changes in version 0.2.3.23-rc - 2012-10-20
1189 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1190 vulnerability introduced by a change in OpenSSL, and fixes a variety
1191 of smaller bugs in preparation for the release.
1193 o New directory authorities:
1194 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1195 authority. Closes ticket 5749.
1197 o Major bugfixes (security/privacy):
1198 - Disable TLS session tickets. OpenSSL's implementation was giving
1199 our TLS session keys the lifetime of our TLS context objects, when
1200 perfect forward secrecy would want us to discard anything that
1201 could decrypt a link connection as soon as the link connection
1202 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1203 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1204 - Discard extraneous renegotiation attempts once the V3 link
1205 protocol has been initiated. Failure to do so left us open to
1206 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1207 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1210 - Fix a possible crash bug when checking for deactivated circuits
1211 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1212 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1214 o Minor bugfixes (on 0.2.3.x):
1215 - Fix two cases in src/or/transports.c where we were calling
1216 fmt_addr() twice in a parameter list. Bug found by David
1217 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1218 - Convert an assert in the pathbias code to a log message. The assert
1219 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1220 bugfix on 0.2.3.17-beta.
1221 - Fix memory leaks whenever we logged any message about the "path
1222 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1224 o Minor bugfixes (on 0.2.2.x and earlier):
1225 - Don't serve or accept v2 hidden service descriptors over a relay's
1226 DirPort. It's never correct to do so, and disabling it might
1227 make it more annoying to exploit any bugs that turn up in the
1228 descriptor-parsing code. Fixes bug 7149.
1229 - When relays refuse a "create" cell because their queue of pending
1230 create cells is too big (typically because their cpu can't keep up
1231 with the arrival rate), send back reason "resource limit" rather
1232 than reason "internal", so network measurement scripts can get a
1233 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1234 - Correct file sizes when reading binary files on Cygwin, to avoid
1235 a bug where Tor would fail to read its state file. Fixes bug 6844;
1236 bugfix on 0.1.2.7-alpha.
1237 - Avoid undefined behaviour when parsing the list of supported
1238 rendezvous/introduction protocols in a hidden service descriptor.
1239 Previously, Tor would have confused (as-yet-unused) protocol version
1240 numbers greater than 32 with lower ones on many platforms. Fixes
1241 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1243 o Documentation fixes:
1244 - Clarify that hidden services are TCP only. Fixes bug 6024.
1247 Changes in version 0.2.4.3-alpha - 2012-09-22
1248 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1249 assertion, resumes letting relays test reachability of their DirPort,
1250 and cleans up a bunch of smaller bugs.
1253 - Fix an assertion failure in tor_timegm() that could be triggered
1254 by a badly formatted directory object. Bug found by fuzzing with
1255 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1258 - Fix a possible crash bug when checking for deactivated circuits
1259 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1260 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1261 - Allow routers to detect that their own DirPorts are running. When
1262 we removed support for versions_supports_begindir, we also
1263 accidentally removed the mechanism we used to self-test our
1264 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1265 bugfix on 0.2.4.2-alpha.
1267 o Security features:
1268 - Switch to a completely time-invariant approach for picking nodes
1269 weighted by bandwidth. Our old approach would run through the
1270 part of the loop after it had made its choice slightly slower
1271 than it ran through the part of the loop before it had made its
1272 choice. Addresses ticket 6538.
1273 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1274 by tor2web clients allows hidden services to identity tor2web
1275 clients through their repeated selection of the same rendezvous
1276 and introduction point circuit endpoints (their guards). Resolves
1280 - Enable Tor to read configuration, state, and key information from
1281 a FIFO. Previously Tor would only read from files with a positive
1282 stat.st_size. Code from meejah; fixes bug 6044.
1285 - Correct file sizes when reading binary files on Cygwin, to avoid
1286 a bug where Tor would fail to read its state file. Fixes bug 6844;
1287 bugfix on 0.1.2.7-alpha.
1288 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1289 bugfix on 0.2.0.3-alpha.
1290 - When complaining about a client port on a public address, log
1291 which address we're complaining about. Fixes bug 4020; bugfix on
1292 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1293 - Convert an assert in the pathbias code to a log message. The assert
1294 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1295 bugfix on 0.2.3.17-beta.
1296 - Our new buildsystem was overzealous about rebuilding manpages: it
1297 would rebuild them all whenever any one of them changed. Now our
1298 dependency checking should be correct. Fixes bug 6843; bugfix on
1300 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1301 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1302 - Correct log printout about which address family is preferred
1303 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1304 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1306 o Minor bugfixes (code cleanliness):
1307 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1308 with large values. This situation was untriggered, but nevertheless
1309 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1310 - Reject consensus votes with more than 64 known-flags. We aren't even
1311 close to that limit yet, and our code doesn't handle it correctly.
1312 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1313 - Avoid undefined behaviour when parsing the list of supported
1314 rendezvous/introduction protocols in a hidden service descriptor.
1315 Previously, Tor would have confused (as-yet-unused) protocol version
1316 numbers greater than 32 with lower ones on many platforms. Fixes
1317 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1318 - Fix handling of rendezvous client authorization types over 8.
1319 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1320 - Fix building with older versions of GCC (2.95, for one) that don't
1321 like preprocessor directives inside macro arguments. Found by
1322 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1323 - Switch weighted node selection rule from using a list of doubles
1324 to using a list of int64_t. This change should make the process
1325 slightly easier to debug and maintain. Needed to finish ticket 6538.
1327 o Code simplification and refactoring:
1328 - Move the generic "config" code into a new file, and have "config.c"
1329 hold only torrc- and state-related code. Resolves ticket 6823.
1330 - Move the core of our "choose a weighted element at random" logic
1331 into its own function, and give it unit tests. Now the logic is
1332 testable, and a little less fragile too.
1333 - Removed the testing_since field of node_t, which hasn't been used
1334 for anything since 0.2.0.9-alpha.
1336 o Documentation fixes:
1337 - Clarify that hidden services are TCP only. Fixes bug 6024.
1338 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1342 Changes in version 0.2.3.22-rc - 2012-09-11
1343 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1347 - Fix an assertion failure in tor_timegm() that could be triggered
1348 by a badly formatted directory object. Bug found by fuzzing with
1349 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1352 - Avoid segfault when starting up having run with an extremely old
1353 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1357 Changes in version 0.2.2.39 - 2012-09-11
1358 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1362 - Fix an assertion failure in tor_timegm() that could be triggered
1363 by a badly formatted directory object. Bug found by fuzzing with
1364 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1365 - Do not crash when comparing an address with port value 0 to an
1366 address policy. This bug could have been used to cause a remote
1367 assertion failure by or against directory authorities, or to
1368 allow some applications to crash clients. Fixes bug 6690; bugfix
1372 Changes in version 0.2.4.2-alpha - 2012-09-10
1373 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1374 raises the default rate limiting even more, and makes the bootstrapping
1375 log messages less noisy.
1378 - Automatically forward the TCP ports of pluggable transport
1379 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1383 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1384 to 1GB/1GB. The previous defaults were intended to be "basically
1385 infinite", but it turns out they're now limiting our 100mbit+
1386 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1387 last time we raised it).
1390 - Detect when we're running with a version of OpenSSL other than the
1391 one we compiled with. This has occasionally given people hard-to-
1393 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1394 versions and capabilities when everything is going right. Resolves
1395 part of ticket 6736.
1396 - Directory authorities no long accept descriptors for any version of
1397 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1398 These versions are insecure, unsupported, or both. Implements
1402 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1403 to start with a triple-underscore so the controller won't touch it.
1404 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1405 - Avoid segfault when starting up having run with an extremely old
1406 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1408 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1409 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1410 - Don't follow the NULL pointer if microdescriptor generation fails.
1411 (This does not appear to be triggerable, but it's best to be safe.)
1412 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1413 - Fix mis-declared dependencies on src/common/crypto.c and
1414 src/or/tor_main.c that could break out-of-tree builds under some
1415 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1416 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1417 6778; bugfix on 0.2.4.1-alpha.
1418 - Fix a harmless (in this case) build warning for implicitly
1419 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1422 - Now that all versions before 0.2.2.x are disallowed, we no longer
1423 need to work around their missing features. Thus we can remove a
1424 bunch of compatibility code.
1427 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1428 TCP ports to forward. In the past it only accepted two ports:
1429 the ORPort and the DirPort.
1432 Changes in version 0.2.4.1-alpha - 2012-09-05
1433 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1434 bridgedb; lets relays use IPv6 addresses and directory authorities
1435 advertise them; and switches to a cleaner build interface.
1437 This is the first alpha release in a new series, so expect there to
1438 be bugs. Users who would rather test out a more stable branch should
1439 stay with 0.2.3.x for now.
1441 o Major features (bridges):
1442 - Bridges now report the pluggable transports they support to the
1443 bridge authority, so it can pass the supported transports on to
1444 bridgedb and/or eventually do reachability testing. Implements
1447 o Major features (IPv6):
1448 - Bridge authorities now accept IPv6 bridge addresses and include
1449 them in network status documents. Implements ticket 5534.
1450 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1451 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1452 to happen. Implements ticket 5535.
1453 - All kind of relays, not just bridges, can now advertise an IPv6
1454 OR port. Implements ticket 6362.
1455 - Directory authorities vote on IPv6 OR ports using the new consensus
1456 method 14. Implements ticket 6363.
1458 o Major features (build):
1459 - Switch to a nonrecursive Makefile structure. Now instead of each
1460 Makefile.am invoking other Makefile.am's, there is a master
1461 Makefile.am that includes the others. This change makes our build
1462 process slightly more maintainable, and improves parallelism for
1463 building with make -j. Original patch by Stewart Smith; various
1464 fixes by Jim Meyering.
1465 - Where available, we now use automake's "silent" make rules by
1466 default, so that warnings are easier to spot. You can get the old
1467 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1469 o Minor features (code security and spec conformance):
1470 - Clear keys and key-derived material left on the stack in
1471 rendservice.c and rendclient.c. Check return value of
1472 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1473 These fixes should make us more forward-secure against cold-boot
1474 attacks and the like. Fixes bug 2385.
1475 - Reject EXTEND cells sent to nonexistent streams. According to the
1476 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1477 we were only checking for stream IDs that were currently in use.
1478 Found while hunting for more instances of bug 6271. Bugfix on
1479 0.0.2pre8, which introduced incremental circuit construction.
1481 o Minor features (streamlining);
1482 - No longer include the "opt" prefix when generating routerinfos
1483 or v2 directories: it has been needless since Tor 0.1.2. Closes
1485 - Remove some now-needless code that tried to aggressively flush
1486 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1487 cell queue logic has saved us from the failure mode that this code
1488 was supposed to prevent. Removing this code will limit the number
1489 of baroque control flow paths through Tor's network logic. Reported
1490 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1492 o Minor features (controller):
1493 - Add a "GETINFO signal/names" control port command. Implements
1495 - Provide default values for all options via "GETINFO config/defaults".
1496 Implements ticket 4971.
1498 o Minor features (IPv6):
1499 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1500 authorities should set if they have IPv6 connectivity and want to
1501 do reachability tests for IPv6 relays. Implements feature 5974.
1502 - A relay with an IPv6 OR port now sends that address in NETINFO
1503 cells (in addition to its other address). Implements ticket 6364.
1505 o Minor features (log messages):
1506 - Omit the first heartbeat log message, because it never has anything
1507 useful to say, and it clutters up the bootstrapping messages.
1508 Resolves ticket 6758.
1509 - Don't log about reloading the microdescriptor cache at startup. Our
1510 bootstrap warnings are supposed to tell the user when there's a
1511 problem, and our bootstrap notices say when there isn't. Resolves
1512 ticket 6759; bugfix on 0.2.2.6-alpha.
1513 - Don't log "I learned some more directory information" when we're
1514 reading cached directory information. Reserve it for when new
1515 directory information arrives in response to a fetch. Resolves
1517 - Prevent rounding error in path bias counts when scaling
1518 them down, and use the correct scale factor default. Also demote
1519 some path bias related log messages down a level and make others
1520 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1521 - We no longer warn so much when generating manpages from their
1524 o Code simplifications and refactoring:
1525 - Enhance our internal sscanf replacement so that we can eliminate
1526 the last remaining uses of the system sscanf. (Though those uses
1527 of sscanf were safe, sscanf itself is generally error prone, so
1528 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1530 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1531 - Move last_reachable and testing_since from routerinfo_t to node_t.
1532 Implements ticket 5529.
1533 - Add replaycache_t structure, functions and unit tests, then refactor
1534 rend_service_introduce() to be more clear to read, improve, debug,
1535 and test. Resolves bug 6177.
1536 - Finally remove support for malloc_good_size and malloc_usable_size.
1537 We had hoped that these functions would let us eke a little more
1538 memory out of our malloc implementation. Unfortunately, the only
1539 implementations that provided these functions are also ones that
1540 are already efficient about not overallocation: they never got us
1541 more than 7 or so bytes per allocation. Removing them saves us a
1542 little code complexity and a nontrivial amount of build complexity.
1545 - Tor maintainers now require Automake version 1.9 or later to build
1546 Tor from the Git repository. (Automake is not required when building
1547 from a source distribution.)
1550 Changes in version 0.2.3.21-rc - 2012-09-05
1551 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1552 series. It fixes a trio of potential security bugs, fixes a bug where
1553 we were leaving some of the fast relays out of the microdescriptor
1554 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1555 and cleans up other smaller issues.
1557 o Major bugfixes (security):
1558 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1559 could use this trick to make their circuits receive cells faster
1560 than our flow control would have allowed, or to gum up the network,
1561 or possibly to do targeted memory denial-of-service attacks on
1562 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1563 from July 2002, before the release of Tor 0.0.0. We had committed
1564 this patch previously, but we had to revert it because of bug 6271.
1565 Now that 6271 is fixed, this patch appears to work.
1566 - Reject any attempt to extend to an internal address. Without
1567 this fix, a router could be used to probe addresses on an internal
1568 network to see whether they were accepting connections. Fixes bug
1569 6710; bugfix on 0.0.8pre1.
1570 - Do not crash when comparing an address with port value 0 to an
1571 address policy. This bug could have been used to cause a remote
1572 assertion failure by or against directory authorities, or to
1573 allow some applications to crash clients. Fixes bug 6690; bugfix
1577 - Remove the upper bound on microdescriptor length. We were hitting
1578 the limit for routers with complex exit policies or family
1579 declarations, causing clients to not use them. Fixes the first
1580 piece of bug 6404; fix on 0.2.2.6-alpha.
1581 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1582 as a relay. Previously, some of our code would treat the presence
1583 of any ORPort line as meaning that we should act like a relay,
1584 even though our new listener code would correctly not open any
1585 ORPorts for ORPort 0. Similar bugs in other Port options are also
1586 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1589 - Avoid a pair of double-free and use-after-mark bugs that can
1590 occur with certain timings in canceled and re-received DNS
1591 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1592 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1593 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1594 - Allow one-hop directory fetching circuits the full "circuit build
1595 timeout" period, rather than just half of it, before failing them
1596 and marking the relay down. This fix should help reduce cases where
1597 clients declare relays (or worse, bridges) unreachable because
1598 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1599 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1601 - Authorities no longer include any router in their microdescriptor
1602 consensuses for which they couldn't generate or agree on a
1603 microdescriptor. Fixes the second piece of bug 6404; fix on
1605 - Detect and reject attempts to specify both "FooPort" and
1606 "FooPort 0" in the same configuration domain. (It's still okay
1607 to have a FooPort in your configuration file, and use "FooPort 0"
1608 on the command line to disable it.) Fixes the second half of bug
1609 6507; bugfix on 0.2.3.3-alpha.
1610 - Make wildcarded addresses (that is, ones beginning with "*.") work
1611 when provided via the controller's MapAddress command. Previously,
1612 they were accepted, but we never actually noticed that they were
1613 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1614 - Avoid crashing on a malformed state file where EntryGuardPathBias
1615 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1616 - Add a (probably redundant) memory clear between iterations of
1617 the router status voting loop, to prevent future coding errors
1618 where data might leak between iterations of the loop. Resolves
1621 o Minor bugfixes (log messages):
1622 - Downgrade "set buildtimeout to low value" messages to "info"
1623 severity; they were never an actual problem, there was never
1624 anything reasonable to do about them, and they tended to spam logs
1625 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1626 - Downgrade path-bias warning messages to "info". We'll try to get
1627 them working better in 0.2.4. Add internal circuit construction
1628 state to protect against the noisy warn message "Unexpectedly high
1629 circuit_successes". Also add some additional rate-limited notice
1630 messages to help determine the root cause of the warn. Fixes bug
1631 6475. Bugfix against 0.2.3.17-beta.
1632 - Move log message when unable to find a microdesc in a routerstatus
1633 entry to parse time. Previously we'd spam this warning every time
1634 we tried to figure out which microdescriptors to download. Fixes
1635 the third piece of bug 6404; fix on 0.2.3.18-rc.
1638 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1639 change when the authority is deciding whether to accept a newly
1640 uploaded descriptor. Implements ticket 6423.
1641 - Add missing documentation for consensus and microdesc files.
1642 Resolves ticket 6732.
1645 Changes in version 0.2.2.38 - 2012-08-12
1646 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1647 attack that could in theory leak path information.
1650 - Avoid an uninitialized memory read when reading a vote or consensus
1651 document that has an unrecognized flavor name. This read could
1652 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1653 - Try to leak less information about what relays a client is
1654 choosing to a side-channel attacker. Previously, a Tor client would
1655 stop iterating through the list of available relays as soon as it
1656 had chosen one, thus finishing a little earlier when it picked
1657 a router earlier in the list. If an attacker can recover this
1658 timing information (nontrivial but not proven to be impossible),
1659 they could learn some coarse-grained information about which relays
1660 a client was picking (middle nodes in particular are likelier to
1661 be affected than exits). The timing attack might be mitigated by
1662 other factors (see bug 6537 for some discussion), but it's best
1663 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1666 Changes in version 0.2.3.20-rc - 2012-08-05
1667 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1668 series. It fixes a pair of code security bugs and a potential anonymity
1669 issue, updates our RPM spec files, and cleans up other smaller issues.
1672 - Avoid read-from-freed-memory and double-free bugs that could occur
1673 when a DNS request fails while launching it. Fixes bug 6480;
1674 bugfix on 0.2.0.1-alpha.
1675 - Avoid an uninitialized memory read when reading a vote or consensus
1676 document that has an unrecognized flavor name. This read could
1677 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1678 - Try to leak less information about what relays a client is
1679 choosing to a side-channel attacker. Previously, a Tor client would
1680 stop iterating through the list of available relays as soon as it
1681 had chosen one, thus finishing a little earlier when it picked
1682 a router earlier in the list. If an attacker can recover this
1683 timing information (nontrivial but not proven to be impossible),
1684 they could learn some coarse-grained information about which relays
1685 a client was picking (middle nodes in particular are likelier to
1686 be affected than exits). The timing attack might be mitigated by
1687 other factors (see bug 6537 for some discussion), but it's best
1688 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1691 - Try to make the warning when giving an obsolete SOCKSListenAddress
1692 a little more useful.
1693 - Terminate active server managed proxies if Tor stops being a
1694 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
1695 - Provide a better error message about possible OSX Asciidoc failure
1696 reasons. Fixes bug 6436.
1697 - Warn when Tor is configured to use accounting in a way that can
1698 link a hidden service to some other hidden service or public
1699 address. Resolves ticket 6490.
1702 - Check return value of fputs() when writing authority certificate
1703 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1704 - Ignore ServerTransportPlugin lines when Tor is not configured as
1705 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
1706 - When disabling guards for having too high a proportion of failed
1707 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
1711 - Update our default RPM spec files to work with mock and rpmbuild
1712 on RHEL/Fedora. They have an updated set of dependencies and
1713 conflicts, a fix for an ancient typo when creating the "_tor"
1714 user, and better instructions. Thanks to Ondrej Mikle for the
1715 patch series. Fixes bug 6043.
1718 - Make it possible to set the TestingTorNetwork configuration
1719 option using AlternateDirAuthority and AlternateBridgeAuthority
1720 as an alternative to setting DirServer. Addresses ticket 6377.
1723 - Clarify the documentation for the Alternate*Authority options.
1725 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1727 o Code simplification and refactoring:
1728 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1729 10 lines. Also, don't nest them. Doing so in the past has
1730 led to hard-to-debug code. The new style is to use the
1731 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1734 Changes in version 0.2.3.19-rc - 2012-07-06
1735 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
1736 series. It fixes the compile on Windows, reverts to a GeoIP database
1737 that isn't as broken, and fixes a flow control bug that has been around
1738 since the beginning of Tor.
1741 - Fix a bug handling SENDME cells on nonexistent streams that could
1742 result in bizarre window values. Report and patch contributed
1743 pseudonymously. Fixes part of bug 6271. This bug was introduced
1744 before the first Tor release, in svn commit r152.
1745 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
1746 June 2012 database, Maxmind marked many Tor relays as country "A1",
1747 which will cause risky behavior for clients that set EntryNodes
1748 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
1749 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
1750 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
1753 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1754 bugfix on 0.2.1.10-alpha.
1757 Changes in version 0.2.3.18-rc - 2012-06-28
1758 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
1759 series. It fixes a few smaller bugs, but generally appears stable.
1760 Please test it and let us know whether it is!
1763 - Allow wildcarded mapaddress targets to be specified on the
1764 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
1765 - Make our linker option detection code more robust against linkers
1766 such as on FreeBSD 8, where a bad combination of options completes
1767 successfully but makes an unrunnable binary. Fixes bug 6173;
1768 bugfix on 0.2.3.17-beta.
1770 o Minor bugfixes (on 0.2.2.x and earlier):
1771 - Avoid a false positive in the util/threads unit test by increasing
1772 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1773 - Replace "Sending publish request" log messages with "Launching
1774 upload", so that they no longer confusingly imply that we're
1775 sending something to a directory we might not even be connected
1776 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1777 - Make sure to set *socket_error in all error cases in
1778 connection_connect(), so it can't produce a warning about
1779 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1780 0.2.1.1-alpha; resolves ticket 6028.
1781 - Downgrade "Got a certificate, but we already have it" log messages
1782 from warning to info, except when we're a dirauth. Fixes bug 5238;
1783 bugfix on 0.2.1.7-alpha.
1784 - When checking for requested signatures on the latest consensus
1785 before serving it to a client, make sure to check the right
1786 consensus flavor. Bugfix on 0.2.2.6-alpha.
1787 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1788 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1790 o Minor bugfixes (on 0.2.3.x):
1791 - Make format_helper_exit_status() avoid unnecessary space padding
1792 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
1794 - Downgrade a message about cleaning the microdescriptor cache to
1795 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
1796 - Log a BUG message at severity INFO if we have a networkstatus with
1797 a missing entry for some microdescriptor. Continues on a patch
1799 - Improve the log message when a managed proxy fails to launch. Fixes
1800 bug 5099; bugfix on 0.2.3.6-alpha.
1801 - Don't do DNS lookups when parsing corrupted managed proxy protocol
1802 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
1803 - When formatting wildcarded address mappings for the controller,
1804 be sure to include "*." as appropriate. Partially fixes bug 6244;
1805 bugfix on 0.2.3.9-alpha.
1806 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
1807 Bugfix on 0.2.3.13-alpha.
1808 - Stop logging messages about running with circuit timeout learning
1809 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
1810 - Disable a spurious warning about reading on a marked and flushing
1811 connection. We shouldn't be doing that, but apparently we
1812 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
1813 - Fix a bug that stopped AllowDotExit from working on addresses
1814 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
1817 o Code simplification, refactoring, unit tests:
1818 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
1819 Libevent's notion of cached time when possible.
1820 - Remove duplicate code for invoking getrlimit() from control.c.
1821 - Add a unit test for the environment_variable_names_equal function.
1824 - Document the --defaults-torrc option, and the new (in 0.2.3)
1825 semantics for overriding, extending, and clearing lists of
1826 options. Closes bug 4748.
1829 Changes in version 0.2.3.17-beta - 2012-06-15
1830 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
1831 gets our TLS handshake back on track for being able to blend in with
1832 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
1833 with Vidalia, and otherwise continues to get us closer to a release
1837 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1838 - Update TLS cipher list to match Firefox 8 and later. Resolves
1840 - Implement the client side of proposal 198: remove support for
1841 clients falsely claiming to support standard ciphersuites that
1842 they can actually provide. As of modern OpenSSL versions, it's not
1843 necessary to fake any standard ciphersuite, and doing so prevents
1844 us from using better ciphersuites in the future, since servers
1845 can't know whether an advertised ciphersuite is really supported or
1846 not. Some hosts -- notably, ones with very old versions of OpenSSL
1847 or where OpenSSL has been built with ECC disabled -- will stand
1848 out because of this change; TBB users should not be affected.
1851 - Change the default value for DynamicDHGroups (introduced in
1852 0.2.3.9-alpha) to 0. This feature can make Tor relays less
1853 identifiable by their use of the mod_ssl DH group, but at
1854 the cost of some usability (#4721) and bridge tracing (#6087)
1855 regressions. Resolves ticket 5598.
1856 - Send a CRLF at the end of each STATUS_* control protocol event. This
1857 bug tickled a bug in Vidalia which would make it freeze. Fixes
1858 bug 6094; bugfix on 0.2.3.16-alpha.
1861 - Disable writing on marked-for-close connections when they are
1862 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1863 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1864 case for flushing marked connections.
1865 - Detect SSL handshake even when the initial attempt to write the
1866 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
1867 - Change the AllowDotExit rules so they should actually work.
1868 We now enforce AllowDotExit only immediately after receiving an
1869 address via SOCKS or DNSPort: other sources are free to provide
1870 .exit addresses after the resolution occurs. Fixes bug 3940;
1871 bugfix on 0.2.2.1-alpha.
1872 - Fix a (harmless) integer overflow in cell statistics reported by
1873 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
1874 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
1875 right places and never depends on the consensus parameters or
1876 computes adaptive timeouts when it is disabled. Fixes bug 5049;
1877 bugfix on 0.2.2.14-alpha.
1878 - When building Tor on Windows with -DUNICODE (not default), ensure
1879 that error messages, filenames, and DNS server names are always
1880 NUL-terminated when we convert them to a single-byte encoding.
1881 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
1882 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
1883 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
1884 - Fix an edge case where TestingTorNetwork is set but the authorities
1885 and relays all have an uptime of zero, where the private Tor network
1886 could briefly lack support for hidden services. Fixes bug 3886;
1887 bugfix on 0.2.2.18-alpha.
1888 - Correct the manpage's descriptions for the default values of
1889 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
1891 - Fix the documentation for the --hush and --quiet command line
1892 options, which changed their behavior back in 0.2.3.3-alpha.
1893 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
1897 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
1898 more information to it, so that we can track it down in case it
1899 returns again. Mitigates bug 5235.
1900 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
1901 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
1902 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
1903 - Warn the user when HTTPProxy, but no other proxy type, is
1904 configured. This can cause surprising behavior: it doesn't send
1905 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
1906 directory traffic only. Resolves ticket 4663.
1907 - Issue a notice if a guard completes less than 40% of your circuits.
1908 Threshold is configurable by torrc option PathBiasNoticeRate and
1909 consensus parameter pb_noticepct. There is additional, off-by-
1910 default code to disable guards which fail too many circuits.
1911 Addresses ticket 5458.
1912 - Update to the June 6 2012 Maxmind GeoLite Country database.
1914 o Code simplifications and refactoring:
1915 - Remove validate_pluggable_transports_config(): its warning
1916 message is now handled by connection_or_connect().
1919 Changes in version 0.2.2.37 - 2012-06-06
1920 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
1921 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1925 - Work around a bug in OpenSSL that broke renegotiation with TLS
1926 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1927 the v2 Tor connection protocol when both sides were using OpenSSL
1928 1.0.1 would fail. Resolves ticket 6033.
1929 - When waiting for a client to renegotiate, don't allow it to add
1930 any bytes to the input buffer. This fixes a potential DoS issue.
1931 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1932 - Fix an edge case where if we fetch or publish a hidden service
1933 descriptor, we might build a 4-hop circuit and then use that circuit
1934 for exiting afterwards -- even if the new last hop doesn't obey our
1935 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1938 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1939 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1942 - Tell GCC and Clang to check for any errors in format strings passed
1943 to the tor_v*(print|scan)f functions.
1946 Changes in version 0.2.3.16-alpha - 2012-06-05
1947 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
1948 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1949 currently). It also fixes a variety of smaller bugs and other cleanups
1950 that get us closer to a release candidate.
1952 o Major bugfixes (general):
1953 - Work around a bug in OpenSSL that broke renegotiation with TLS
1954 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1955 the v2 Tor connection protocol when both sides were using OpenSSL
1956 1.0.1 would fail. Resolves ticket 6033.
1957 - When waiting for a client to renegotiate, don't allow it to add
1958 any bytes to the input buffer. This fixes a potential DoS issue.
1959 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1960 - Pass correct OR address to managed proxies (like obfsproxy),
1961 even when ORListenAddress is used. Fixes bug 4865; bugfix on
1963 - The advertised platform of a router now includes only its operating
1964 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
1965 service pack level (for Windows) or its CPU architecture (for Unix).
1966 We also no longer include the "git-XYZ" tag in the version. Resolves
1969 o Major bugfixes (clients):
1970 - If we are unable to find any exit that supports our predicted ports,
1971 stop calling them predicted, so that we don't loop and build
1972 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
1973 which introduced predicted ports.
1974 - Fix an edge case where if we fetch or publish a hidden service
1975 descriptor, we might build a 4-hop circuit and then use that circuit
1976 for exiting afterwards -- even if the new last hop doesn't obey our
1977 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1978 - Check at each new consensus whether our entry guards were picked
1979 long enough ago that we should rotate them. Previously, we only
1980 did this check at startup, which could lead to us holding a guard
1981 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
1982 - When fetching a bridge descriptor from a bridge authority,
1983 always do so anonymously, whether we have been able to open
1984 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
1985 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
1986 but we'll need to wait for bug 6010 before it's actually usable.
1988 o Major bugfixes (directory authorities):
1989 - When computing weight parameters, behave more robustly in the
1990 presence of a bad bwweightscale value. Previously, the authorities
1991 would crash if they agreed on a sufficiently broken weight_scale
1992 value: now, they use a reasonable default and carry on. Partial
1993 fix for 5786; bugfix on 0.2.2.17-alpha.
1994 - Check more thoroughly to prevent a rogue authority from
1995 double-voting on any consensus directory parameter. Previously,
1996 authorities would crash in this case if the total number of
1997 votes for any parameter exceeded the number of active voters,
1998 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2002 - Rate-limit log messages when asked to connect anonymously to
2003 a private address. When these hit, they tended to hit fast and
2004 often. Also, don't bother trying to connect to addresses that we
2005 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2006 reply makes us think we have been lied to, even when the address the
2007 client tried to connect to was "localhost." Resolves ticket 2822.
2008 - Allow packagers to insert an extra string in server descriptor
2009 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2010 Resolves the rest of ticket 2988.
2011 - Raise the threshold of server descriptors needed (75%) and exit
2012 server descriptors needed (50%) before we will declare ourselves
2013 bootstrapped. This will make clients start building circuits a
2014 little later, but makes the initially constructed circuits less
2015 skewed and less in conflict with further directory fetches. Fixes
2017 - Close any connection that sends unrecognized junk before the
2018 handshake. Solves an issue noted in bug 4369.
2019 - Improve log messages about managed transports. Resolves ticket 5070.
2020 - Tag a bridge's descriptor as "never to be sent unencrypted".
2021 This shouldn't matter, since bridges don't open non-anonymous
2022 connections to the bridge authority and don't allow unencrypted
2023 directory connections from clients, but we might as well make
2024 sure. Closes bug 5139.
2025 - Expose our view of whether we have gone dormant to the controller,
2026 via a new "GETINFO dormant" value. Torbutton and other controllers
2027 can use this to avoid doing periodic requests through Tor while
2028 it's dormant (bug 4718). Fixes bug 5954.
2029 - Tell GCC and Clang to check for any errors in format strings passed
2030 to the tor_v*(print|scan)f functions.
2031 - Update to the May 1 2012 Maxmind GeoLite Country database.
2033 o Minor bugfixes (already included in 0.2.2.36):
2034 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2035 Fixes bug 5346; bugfix on 0.0.8pre3.
2036 - Correct parsing of certain date types in parse_http_time().
2037 Without this patch, If-Modified-Since would behave
2038 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2039 Esteban Manchado Velázques.
2040 - Make our number-parsing functions always treat too-large values
2041 as an error, even when those values exceed the width of the
2042 underlying type. Previously, if the caller provided these
2043 functions with minima or maxima set to the extreme values of the
2044 underlying integer type, these functions would return those
2045 values on overflow rather than treating overflow as an error.
2046 Fixes part of bug 5786; bugfix on 0.0.9.
2047 - If we hit the error case where routerlist_insert() replaces an
2048 existing (old) server descriptor, make sure to remove that
2049 server descriptor from the old_routers list. Fix related to bug
2050 1776. Bugfix on 0.2.2.18-alpha.
2051 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2052 circuits. Fixes issue 5259.
2054 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2055 - Prevent a null-pointer dereference when receiving a data cell
2056 for a nonexistent stream when the circuit in question has an
2057 empty deliver window. We don't believe this is triggerable,
2058 since we don't currently allow deliver windows to become empty,
2059 but the logic is tricky enough that it's better to make the code
2060 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2061 - Fix a memory leak when trying to launch a DNS request when the
2062 network is disabled or the nameservers are unconfigurable. Fixes
2063 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2064 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2065 - Don't hold a Windows file handle open for every file mapping;
2066 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2068 - Avoid O(n^2) performance characteristics when parsing a large
2069 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2070 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2071 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2073 - Make our replacement implementation of strtok_r() compatible with
2074 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2075 bugfix on 0.2.2.1-alpha.
2076 - Fix a NULL-pointer dereference on a badly formed
2077 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2078 bugfix on 0.2.2.9-alpha.
2079 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2080 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2081 - Defensively refactor rend_mid_rendezvous() so that protocol
2082 violations and length checks happen in the beginning. Fixes
2084 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2085 that IPv6 stuff will compile on MSVC, and compilation issues
2086 will be easier to track down. Fixes bug 5861.
2088 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2089 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2090 resource exhaustion, so that clients can adjust their load to
2091 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2092 started using END_STREAM_REASON_RESOURCELIMIT.
2093 - Don't check for whether the address we're using for outbound
2094 connections has changed until after the outbound connection has
2095 completed. On Windows, getsockname() doesn't succeed until the
2096 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2097 - If the configuration tries to set MyFamily on a bridge, refuse to
2098 do so, and warn about the security implications. Fixes bug 4657;
2099 bugfix on 0.2.0.3-alpha.
2100 - If the client fails to set a reasonable set of ciphersuites
2101 during its v2 handshake renegotiation, allow the renegotiation to
2102 continue nevertheless (i.e. send all the required certificates).
2103 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2104 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2105 option is set to 0 (which Vidalia version 0.2.16 now does when
2106 a SAVECONF attempt fails), perform other actions that SIGHUP
2107 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2109 - If we fail to write a microdescriptor to the disk cache, do not
2110 continue replacing the old microdescriptor file. Fixes bug 2954;
2111 bugfix on 0.2.2.6-alpha.
2112 - Exit nodes don't need to fetch certificates for authorities that
2113 they don't recognize; only directory authorities, bridges,
2114 and caches need to do that. Fixes part of bug 2297; bugfix on
2116 - Correctly handle checking the permissions on the parent
2117 directory of a control socket in the root directory. Bug found
2118 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2120 - When told to add a bridge with the same digest as a preexisting
2121 bridge but a different addr:port, change the addr:port as
2122 requested. Previously we would not notice the change. Fixes half
2123 of bug 5603; fix on 0.2.2.26-beta.
2124 - End AUTHCHALLENGE error messages (in the control protocol) with
2125 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2127 o Minor bugfixes (on 0.2.3.x):
2128 - Turn an assertion (that the number of handshakes received as a
2129 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2131 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2132 we had reversed them when the answer was cached.) Fixes bug
2133 5723; bugfix on 0.2.3.1-alpha.
2134 - Work correctly on Linux systems with accept4 support advertised in
2135 their headers, but without accept4 support in the kernel. Fix
2136 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2137 - When told to add a bridge with the same addr:port as a preexisting
2138 bridge but a different transport, change the transport as
2139 requested. Previously we would not notice the change. Fixes half
2140 of bug 5603; fix on 0.2.3.2-alpha.
2141 - Avoid a "double-reply" warning when replying to a SOCKS request
2142 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2143 bugfix on 0.2.3.4-alpha.
2144 - Fix a bug where a bridge authority crashes if it has seen no
2145 directory requests when it's time to write statistics to disk.
2146 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2148 - Don't try to open non-control listeners when DisableNetwork is set.
2149 Previously, we'd open all listeners, then immediately close them.
2150 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2151 - Don't abort the managed proxy protocol if the managed proxy
2152 sends us an unrecognized line; ignore it instead. Fixes bug
2153 5910; bugfix on 0.2.3.9-alpha.
2154 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2155 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2156 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2157 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2158 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2159 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2160 - Resolve numerous small warnings and build issues with MSVC. Resolves
2163 o Documentation fixes:
2164 - Improve the manual's documentation for the NT Service command-line
2165 options. Addresses ticket 3964.
2166 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2167 - Document the changes to the ORPort and DirPort options, and the
2168 fact that {OR/Dir}ListenAddress is now unnecessary (and
2169 therefore deprecated). Resolves ticket 5597.
2172 - Remove the torrc.bridge file: we don't use it for anything, and
2173 it had become badly desynchronized from torrc.sample. Resolves
2177 Changes in version 0.2.2.36 - 2012-05-24
2178 Tor 0.2.2.36 updates the addresses for two of the eight directory
2179 authorities, fixes some potential anonymity and security issues,
2180 and fixes several crash bugs.
2182 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2183 known flaws, and nobody should be using them. You should upgrade. If
2184 you're using a Linux or BSD and its packages are obsolete, stop using
2185 those packages and upgrade anyway.
2187 o Directory authority changes:
2188 - Change IP address for maatuska (v3 directory authority).
2189 - Change IP address for ides (v3 directory authority), and rename
2193 - When building or running with any version of OpenSSL earlier
2194 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2195 versions have a bug (CVE-2011-4576) in which their block cipher
2196 padding includes uninitialized data, potentially leaking sensitive
2197 information to any peer with whom they make a SSLv3 connection. Tor
2198 does not use SSL v3 by default, but a hostile client or server
2199 could force an SSLv3 connection in order to gain information that
2200 they shouldn't have been able to get. The best solution here is to
2201 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2202 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2203 to make sure that the bug can't happen.
2204 - Never use a bridge or a controller-supplied node as an exit, even
2205 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2206 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2207 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2208 - Only build circuits if we have a sufficient threshold of the total
2209 descriptors that are marked in the consensus with the "Exit"
2210 flag. This mitigates an attack proposed by wanoskarnet, in which
2211 all of a client's bridges collude to restrict the exit nodes that
2212 the client knows about. Fixes bug 5343.
2213 - Provide controllers with a safer way to implement the cookie
2214 authentication mechanism. With the old method, if another locally
2215 running program could convince a controller that it was the Tor
2216 process, then that program could trick the controller into telling
2217 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2218 authentication method uses a challenge-response approach to prevent
2219 this attack. Fixes bug 5185; implements proposal 193.
2222 - Avoid logging uninitialized data when unable to decode a hidden
2223 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2224 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2225 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2227 - Fix builds when the path to sed, openssl, or sha1sum contains
2228 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2230 - Correct our replacements for the timeradd() and timersub() functions
2231 on platforms that lack them (for example, Windows). The timersub()
2232 function is used when expiring circuits, while timeradd() is
2233 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2234 bugfix on 0.2.2.24-alpha.
2235 - Fix the SOCKET_OK test that we use to tell when socket
2236 creation fails so that it works on Win64. Fixes part of bug 4533;
2237 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2240 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2241 Fixes bug 5346; bugfix on 0.0.8pre3.
2242 - Make our number-parsing functions always treat too-large values
2243 as an error, even when those values exceed the width of the
2244 underlying type. Previously, if the caller provided these
2245 functions with minima or maxima set to the extreme values of the
2246 underlying integer type, these functions would return those
2247 values on overflow rather than treating overflow as an error.
2248 Fixes part of bug 5786; bugfix on 0.0.9.
2249 - Older Linux kernels erroneously respond to strange nmap behavior
2250 by having accept() return successfully with a zero-length
2251 socket. When this happens, just close the connection. Previously,
2252 we would try harder to learn the remote address: but there was
2253 no such remote address to learn, and our method for trying to
2254 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2255 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2256 - Correct parsing of certain date types in parse_http_time().
2257 Without this patch, If-Modified-Since would behave
2258 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2259 Esteban Manchado Velázques.
2260 - Change the BridgePassword feature (part of the "bridge community"
2261 design, which is not yet implemented) to use a time-independent
2262 comparison. The old behavior might have allowed an adversary
2263 to use timing to guess the BridgePassword value. Fixes bug 5543;
2264 bugfix on 0.2.0.14-alpha.
2265 - Detect and reject certain misformed escape sequences in
2266 configuration values. Previously, these values would cause us
2267 to crash if received in a torrc file or over an authenticated
2268 control port. Bug found by Esteban Manchado Velázquez, and
2269 independently by Robert Connolly from Matta Consulting who further
2270 noted that it allows a post-authentication heap overflow. Patch
2271 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2272 bugfix on 0.2.0.16-alpha.
2273 - Fix a compile warning when using the --enable-openbsd-malloc
2274 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2275 - During configure, detect when we're building with clang version
2276 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2277 CFLAGS. clang doesn't support them yet.
2278 - When sending an HTTP/1.1 proxy request, include a Host header.
2279 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2280 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2281 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2282 - If we hit the error case where routerlist_insert() replaces an
2283 existing (old) server descriptor, make sure to remove that
2284 server descriptor from the old_routers list. Fix related to bug
2285 1776. Bugfix on 0.2.2.18-alpha.
2287 o Minor bugfixes (documentation and log messages):
2288 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2289 Fixes bug 4856; bugfix on Tor 0.0.6.
2290 - Update "ClientOnly" man page entry to explain that there isn't
2291 really any point to messing with it. Resolves ticket 5005.
2292 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2293 directory authority option (introduced in Tor 0.2.2.34).
2294 - Downgrade the "We're missing a certificate" message from notice
2295 to info: people kept mistaking it for a real problem, whereas it
2296 is seldom the problem even when we are failing to bootstrap. Fixes
2297 bug 5067; bugfix on 0.2.0.10-alpha.
2298 - Correctly spell "connect" in a log message on failure to create a
2299 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2300 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2301 circuits. Fixes issue 5259.
2304 - Directory authorities now reject versions of Tor older than
2305 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2306 inclusive. These versions accounted for only a small fraction of
2307 the Tor network, and have numerous known security issues. Resolves
2309 - Update to the May 1 2012 Maxmind GeoLite Country database.
2312 - When sending or relaying a RELAY_EARLY cell, we used to convert
2313 it to a RELAY cell if the connection was using the v1 link
2314 protocol. This was a workaround for older versions of Tor, which
2315 didn't handle RELAY_EARLY cells properly. Now that all supported
2316 versions can handle RELAY_EARLY cells, and now that we're enforcing
2317 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2318 remove this workaround. Addresses bug 4786.
2321 Changes in version 0.2.3.15-alpha - 2012-04-30
2322 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2323 the development branch build on Windows again.
2325 o Minor bugfixes (on 0.2.2.x and earlier):
2326 - Make sure that there are no unhandled pending TLS errors before
2327 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2328 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2329 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2330 - Fix an assert that directory authorities could trigger on sighup
2331 during some configuration state transitions. We now don't treat
2332 it as a fatal error when the new descriptor we just generated in
2333 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2334 - After we pick a directory mirror, we would refuse to use it if
2335 it's in our ExcludeExitNodes list, resulting in mysterious failures
2336 to bootstrap for people who just wanted to avoid exiting from
2337 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2338 - When building with --enable-static-tor on OpenBSD, do not
2339 erroneously attempt to link -lrt. Fixes bug 5103.
2341 o Minor bugfixes (on 0.2.3.x):
2342 - When Tor is built with kernel headers from a recent (last few
2343 years) Linux kernel, do not fail to run on older (pre-2.6.28
2344 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2345 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2347 - Fix compilation with miniupnpc version 1.6; patch from
2348 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2349 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2350 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2351 - Fix compilation on platforms without unistd.h, or where environ
2352 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2355 - Directory authorities are now a little more lenient at accepting
2356 older router descriptors, or newer router descriptors that don't
2357 make big changes. This should help ameliorate past and future
2358 issues where routers think they have uploaded valid descriptors,
2359 but the authorities don't think so. Fix for ticket 2479.
2360 - Make the code that clients use to detect an address change be
2361 IPv6-aware, so that it won't fill clients' logs with error
2362 messages when trying to get the IPv4 address of an IPv6
2363 connection. Implements ticket 5537.
2366 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2367 authorities needed to use it for a while to keep the network working
2368 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2369 that was six months ago. As of now, it should no longer be needed
2373 Changes in version 0.2.3.14-alpha - 2012-04-23
2374 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2375 candidate. It also dramatically speeds up AES: fast relays should
2376 consider switching to the newer OpenSSL library.
2378 o Directory authority changes:
2379 - Change IP address for ides (v3 directory authority), and rename
2383 - Avoid logging uninitialized data when unable to decode a hidden
2384 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2385 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2386 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2388 - If authorities are unable to get a v2 consensus document from other
2389 directory authorities, they no longer fall back to fetching
2390 them from regular directory caches. Fixes bug 5635; bugfix on
2391 0.2.2.26-beta, where routers stopped downloading v2 consensus
2393 - When we start a Tor client with a normal consensus already cached,
2394 be willing to download a microdescriptor consensus. Fixes bug 4011;
2395 fix on 0.2.3.1-alpha.
2397 o Major features (performance):
2398 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2399 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2400 vectorized AES implementations as appropriate. These can be much,
2401 much faster than other AES implementations.
2403 o Minor bugfixes (0.2.2.x and earlier):
2404 - Don't launch more than 10 service-side introduction-point circuits
2405 for a hidden service in five minutes. Previously, we would consider
2406 launching more introduction-point circuits if at least one second
2407 had passed without any introduction-point circuits failing. Fixes
2408 bug 4607; bugfix on 0.0.7pre1.
2409 - Change the BridgePassword feature (part of the "bridge community"
2410 design, which is not yet implemented) to use a time-independent
2411 comparison. The old behavior might have allowed an adversary
2412 to use timing to guess the BridgePassword value. Fixes bug 5543;
2413 bugfix on 0.2.0.14-alpha.
2414 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2415 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2416 - When sending an HTTP/1.1 proxy request, include a Host header.
2417 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2418 - Don't log that we have "decided to publish new relay descriptor"
2419 unless we are actually publishing a descriptor. Fixes bug 3942;
2420 bugfix on 0.2.2.28-beta.
2422 o Minor bugfixes (0.2.3.x):
2423 - Fix a bug where a bridge authority crashes (on a failed assert)
2424 if it has seen no directory requests when it's time to write
2425 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2426 - Fix bug stomping on ORPort option NoListen and ignoring option
2427 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2428 - In the testsuite, provide a large enough buffer in the tor_sscanf
2429 unit test. Otherwise we'd overrun that buffer and crash during
2430 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2432 - Make sure we create the keys directory if it doesn't exist and we're
2433 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2434 5572; bugfix on 0.2.3.13-alpha.
2435 - Fix a small memory leak when trying to decode incorrect base16
2436 authenticator during SAFECOOKIE authentication. Found by
2437 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2440 - Add more information to a log statement that might help track down
2441 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2442 non-IP address" messages (or any Bug messages, for that matter!),
2443 please let us know about it.
2444 - Relays now understand an IPv6 address when they get one from a
2445 directory server. Resolves ticket 4875.
2446 - Resolve IPv6 addresses in bridge and entry statistics to country
2447 code "??" which means we at least count them. Resolves ticket 5053;
2448 improves on 0.2.3.9-alpha.
2449 - Update to the April 3 2012 Maxmind GeoLite Country database.
2450 - Begin a doc/state-contents.txt file to explain the contents of
2451 the Tor state file. Fixes bug 2987.
2453 o Default torrc changes:
2454 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2455 port on 9050 by default anyway, so this should not change anything
2457 - Stop mentioning the deprecated *ListenAddress options in
2458 torrc.sample. Fixes bug 5438.
2459 - Document unit of bandwidth related options in sample torrc.
2463 - The "torify" script no longer supports the "tsocks" socksifier
2464 tool, since tsocks doesn't support DNS and UDP right for Tor.
2465 Everyone should be using torsocks instead. Fixes bugs 3530 and
2466 5180. Based on a patch by "ugh".
2469 - Change the symmetric cipher interface so that creating and
2470 initializing a stream cipher are no longer separate functions.
2471 - Remove all internal support for unpadded RSA. We never used it, and
2472 it would be a bad idea to start.
2475 Changes in version 0.2.3.13-alpha - 2012-03-26
2476 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2477 in managed pluggable transports, as well as providing other cleanups
2478 that get us closer to a release candidate.
2480 o Directory authority changes:
2481 - Change IP address for maatuska (v3 directory authority).
2484 - Provide controllers with a safer way to implement the cookie
2485 authentication mechanism. With the old method, if another locally
2486 running program could convince a controller that it was the Tor
2487 process, then that program could trick the controller into telling
2488 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2489 authentication method uses a challenge-response approach to prevent
2490 this attack. Fixes bug 5185, implements proposal 193.
2491 - Never use a bridge or a controller-supplied node as an exit, even
2492 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2493 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2494 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2495 - Only build circuits if we have a sufficient threshold of the total
2496 descriptors that are marked in the consensus with the "Exit"
2497 flag. This mitigates an attack proposed by wanoskarnet, in which
2498 all of a client's bridges collude to restrict the exit nodes that
2499 the client knows about. Fixes bug 5343.
2501 o Major bugfixes (on Tor 0.2.3.x):
2502 - Avoid an assert when managed proxies like obfsproxy are configured,
2503 and we receive HUP signals or setconf attempts too rapidly. This
2504 situation happens most commonly when Vidalia tries to attach to
2505 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2506 bugfix on 0.2.3.6-alpha.
2507 - Fix a relay-side pluggable transports bug where managed proxies were
2508 unreachable from the Internet, because Tor asked them to bind on
2509 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2510 - Stop discarding command-line arguments when TestingTorNetwork
2511 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2512 0.2.3.9-alpha, where task 4552 added support for two layers of
2514 - Resume allowing the unit tests to run in gdb. This was accidentally
2515 made impossible when the DisableDebuggerAttachment option was
2516 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2517 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2518 0.2.3.11-alpha. Reported by Anthony G. Basile.
2520 o Minor bugfixes (on 0.2.2.x and earlier):
2521 - Ensure we don't cannibalize circuits that are longer than three hops
2522 already, so we don't end up making circuits with 5 or more
2523 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2524 0.1.0.1-rc which introduced cannibalization.
2525 - Detect and reject certain misformed escape sequences in
2526 configuration values. Previously, these values would cause us
2527 to crash if received in a torrc file or over an authenticated
2528 control port. Bug found by Esteban Manchado Velázquez, and
2529 independently by Robert Connolly from Matta Consulting who further
2530 noted that it allows a post-authentication heap overflow. Patch
2531 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2532 bugfix on 0.2.0.16-alpha.
2533 - Fix a compile warning when using the --enable-openbsd-malloc
2534 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2535 - Directory caches no longer refuse to clean out descriptors because
2536 of missing v2 networkstatus documents, unless they're configured
2537 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2538 0.2.2.26-beta. Patch by Daniel Bryg.
2539 - Update to the latest version of the tinytest unit testing framework.
2540 This includes a couple of bugfixes that can be relevant for
2541 running forked unit tests on Windows, and removes all reserved
2544 o Minor bugfixes (on 0.2.3.x):
2545 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2546 4296; bugfix on 0.2.3.1-alpha.
2547 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2548 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2549 on 0.2.3.6-alpha. Patch by "frosty".
2550 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2551 option, so that the IP stack doesn't decide to use it for IPv4
2552 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2553 - Ensure that variables set in Tor's environment cannot override
2554 environment variables that Tor passes to a managed
2555 pluggable-transport proxy. Previously, Tor would pass every
2556 variable in its environment to managed proxies along with the new
2557 ones, in such a way that on many operating systems, the inherited
2558 environment variables would override those which Tor tried to
2559 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2560 bugfix on 0.2.3.9-alpha for Windows.
2563 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2564 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2565 - Update to the March 6 2012 Maxmind GeoLite Country database.
2568 Changes in version 0.2.3.12-alpha - 2012-02-13
2569 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2570 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2571 when Tor is configured to use a pluggable transport like obfsproxy.
2574 - Fix builds when the path to sed, openssl, or sha1sum contains
2575 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2577 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2578 connections. This change should allow busy exit relays to stop
2579 running out of available sockets as quickly. Fixes bug 4950;
2580 bugfix on 0.2.2.26-beta.
2581 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2582 would ask the bridge for microdescriptors, which are only supported
2583 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2584 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2585 - Properly set up obfsproxy's environment when in managed mode. The
2586 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2587 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2588 5076 and 5082; bugfix on 0.2.3.6-alpha.
2591 - Use the dead_strip option when building Tor on OS X. This reduces
2592 binary size by almost 19% when linking openssl and libevent
2593 statically, which we do for Tor Browser Bundle.
2594 - Fix broken URLs in the sample torrc file, and tell readers about
2595 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2596 PublishServerDescriptor options. Addresses bug 4652.
2597 - Update to the February 7 2012 Maxmind GeoLite Country database.
2600 - Downgrade the "We're missing a certificate" message from notice
2601 to info: people kept mistaking it for a real problem, whereas it
2602 is seldom the problem even when we are failing to bootstrap. Fixes
2603 bug 5067; bugfix on 0.2.0.10-alpha.
2604 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2605 managed pluggable transport server proxy's environment.
2606 Previously, we would put it there, even though Tor doesn't
2607 implement an 'extended server port' yet, and even though Tor
2608 almost certainly isn't listening at that address. For now, we set
2609 it to an empty string to avoid crashing older obfsproxies. Bugfix
2611 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2612 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2613 0.2.3.1-alpha. Bug reported by Scott Bennett.
2614 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2615 bugfix on 0.2.3.11-alpha.
2616 - Update "ClientOnly" man page entry to explain that there isn't
2617 really any point to messing with it. Resolves ticket 5005.
2618 - Use the correct CVE number for CVE-2011-4576 in our comments and
2619 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2622 o Code simplifications and refactoring:
2623 - Use the _WIN32 macro throughout our code to detect Windows.
2624 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2628 Changes in version 0.2.3.11-alpha - 2012-01-22
2629 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2630 the last step of the plan to limit maximum circuit length, includes
2631 a wide variety of hidden service performance and correctness fixes,
2632 works around an OpenSSL security flaw if your distro is too stubborn
2633 to upgrade, and fixes a bunch of smaller issues.
2636 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2637 part of "Proposal 110: Avoiding infinite length circuits" by
2638 refusing all circuit-extend requests that do not use a relay_early
2639 cell. This change helps Tor resist a class of denial-of-service
2640 attacks by limiting the maximum circuit length.
2641 - Adjust the number of introduction points that a hidden service
2642 will try to maintain based on how long its introduction points
2643 remain in use and how many introductions they handle. Fixes
2645 - Try to use system facilities for enumerating local interface
2646 addresses, before falling back to our old approach (which was
2647 binding a UDP socket, and calling getsockname() on it). That
2648 approach was scaring OS X users whose draconian firewall
2649 software warned about binding to UDP sockets, regardless of
2650 whether packets were sent. Now we try to use getifaddrs(),
2651 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2652 system supports. Resolves ticket 1827.
2654 o Major security workaround:
2655 - When building or running with any version of OpenSSL earlier
2656 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2657 versions have a bug (CVE-2011-4576) in which their block cipher
2658 padding includes uninitialized data, potentially leaking sensitive
2659 information to any peer with whom they make a SSLv3 connection. Tor
2660 does not use SSL v3 by default, but a hostile client or server
2661 could force an SSLv3 connection in order to gain information that
2662 they shouldn't have been able to get. The best solution here is to
2663 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2664 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2665 to make sure that the bug can't happen.
2668 - Fix the SOCKET_OK test that we use to tell when socket
2669 creation fails so that it works on Win64. Fixes part of bug 4533;
2670 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2671 - Correct our replacements for the timeradd() and timersub() functions
2672 on platforms that lack them (for example, Windows). The timersub()
2673 function is used when expiring circuits, while timeradd() is
2674 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2675 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2676 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2677 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2678 bug at runtime, not compile time, because some distributions hack
2679 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2680 on 0.2.3.9-alpha. Found by Pascal.
2682 o Minor features (controller):
2683 - Use absolute path names when reporting the torrc filename in the
2684 control protocol, so a controller can more easily find the torrc
2685 file. Resolves bug 1101.
2686 - Extend the control protocol to report flags that control a circuit's
2687 path selection in CIRC events and in replies to 'GETINFO
2688 circuit-status'. Implements part of ticket 2411.
2689 - Extend the control protocol to report the hidden service address
2690 and current state of a hidden-service-related circuit in CIRC
2691 events and in replies to 'GETINFO circuit-status'. Implements part
2693 - When reporting the path to the cookie file to the controller,
2694 give an absolute path. Resolves ticket 4881.
2695 - Allow controllers to request an event notification whenever a
2696 circuit is cannibalized or its purpose is changed. Implements
2697 part of ticket 3457.
2698 - Include the creation time of a circuit in CIRC and CIRC2
2699 control-port events and the list produced by the 'GETINFO
2700 circuit-status' control-port command.
2702 o Minor features (directory authorities):
2703 - Directory authorities now reject versions of Tor older than
2704 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2705 inclusive. These versions accounted for only a small fraction of
2706 the Tor network, and have numerous known security issues. Resolves
2708 - Authority operators can now vote for all relays in a given
2709 set of countries to be BadDir/BadExit/Invalid/Rejected.
2710 - Provide two consensus parameters (FastFlagMinThreshold and
2711 FastFlagMaxThreshold) to control the range of allowable bandwidths
2712 for the Fast directory flag. These allow authorities to run
2713 experiments on appropriate requirements for being a "Fast" node.
2714 The AuthDirFastGuarantee config value still applies. Implements
2716 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2717 directory authority option (introduced in Tor 0.2.2.34).
2719 o Minor features (other):
2720 - Don't disable the DirPort when we cannot exceed our AccountingMax
2721 limit during this interval because the effective bandwidthrate is
2722 low enough. This is useful in a situation where AccountMax is only
2723 used as an additional safeguard or to provide statistics.
2724 - Prepend an informative header to generated dynamic_dh_params files.
2725 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2726 EntryNodes will have no effect. Resolves issue 2571.
2727 - Log more useful messages when we fail to disable debugger
2729 - Log which authority we're missing votes from when we go to fetch
2730 them from the other auths.
2731 - Log (at debug level) whenever a circuit's purpose is changed.
2732 - Add missing documentation for the MaxClientCircuitsPending,
2733 UseMicrodescriptors, UserspaceIOCPBuffers, and
2734 _UseFilteringSSLBufferevents options, all introduced during
2736 - Update to the January 3 2012 Maxmind GeoLite Country database.
2738 o Minor bugfixes (hidden services):
2739 - Don't close hidden service client circuits which have almost
2740 finished connecting to their destination when they reach
2741 the normal circuit-build timeout. Previously, we would close
2742 introduction circuits which are waiting for an acknowledgement
2743 from the introduction point, and rendezvous circuits which have
2744 been specified in an INTRODUCE1 cell sent to a hidden service,
2745 after the normal CBT. Now, we mark them as 'timed out', and launch
2746 another rendezvous attempt in parallel. This behavior change can
2747 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2748 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2749 - Don't close hidden-service-side rendezvous circuits when they
2750 reach the normal circuit-build timeout. This behaviour change can
2751 be disabled using the new
2752 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2753 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2754 - Make sure we never mark the wrong rendezvous circuit as having
2755 had its introduction cell acknowleged by the introduction-point
2756 relay. Previously, when we received an INTRODUCE_ACK cell on a
2757 client-side hidden-service introduction circuit, we might have
2758 marked a rendezvous circuit other than the one we specified in
2759 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
2760 a warning message and interfered with the hidden service
2761 connection-establishment process. Fixes bug 4759; bugfix on
2762 0.2.3.3-alpha, when we added the stream-isolation feature which
2763 might cause Tor to open multiple rendezvous circuits for the same
2765 - Don't trigger an assertion failure when we mark a new client-side
2766 hidden-service introduction circuit for close during the process
2767 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
2770 o Minor bugfixes (log messages):
2771 - Correctly spell "connect" in a log message on failure to create a
2772 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
2774 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2775 Fixes bug 4856; bugfix on Tor 0.0.6.
2776 - Fix the log message describing how we work around discovering
2777 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2778 4837; bugfix on 0.2.2.9-alpha.
2779 - When logging about a disallowed .exit name, do not also call it
2780 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2782 o Minor bugfixes (build fixes):
2783 - During configure, detect when we're building with clang version
2784 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2785 CFLAGS. clang doesn't support them yet.
2786 - During configure, search for library containing cos function as
2787 libm lives in libcore on some platforms (BeOS/Haiku). Linking
2788 against libm was hard-coded before. Fixes the first part of bug
2789 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
2791 - Detect attempts to build Tor on (as yet hypothetical) versions
2792 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
2793 fix for bug 4533. Bugfix on 0.2.2.28-beta.
2794 - Preprocessor directives should not be put inside the arguments
2795 of a macro. This would break compilation with GCC releases prior
2796 to version 3.3. We would never recommend such an old GCC version,
2797 but it is apparently required for binary compatibility on some
2798 platforms (namely, certain builds of Haiku). Fixes the other part
2799 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
2802 o Minor bugfixes (other):
2803 - Older Linux kernels erroneously respond to strange nmap behavior
2804 by having accept() return successfully with a zero-length
2805 socket. When this happens, just close the connection. Previously,
2806 we would try harder to learn the remote address: but there was
2807 no such remote address to learn, and our method for trying to
2808 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2809 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2810 - Fix null-pointer access that could occur if TLS allocation failed.
2811 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
2812 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
2813 accidentally been reverted.
2814 - Fix our implementation of crypto_random_hostname() so it can't
2815 overflow on ridiculously large inputs. (No Tor version has ever
2816 provided this kind of bad inputs, but let's be correct in depth.)
2817 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2818 - Find more places in the code that should have been testing for
2819 invalid sockets using the SOCKET_OK macro. Required for a fix
2820 for bug 4533. Bugfix on 0.2.2.28-beta.
2821 - Fix an assertion failure when, while running with bufferevents, a
2822 connection finishes connecting after it is marked for close, but
2823 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
2824 - test_util_spawn_background_ok() hardcoded the expected value
2825 for ENOENT to 2. This isn't portable as error numbers are
2826 platform specific, and particularly the hurd has ENOENT at
2827 0x40000002. Construct expected string at runtime, using the correct
2828 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
2829 - Reject attempts to disable DisableDebuggerAttachment while Tor is
2830 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
2831 - Use an appropriate-width type for sockets in tor-fw-helper on
2832 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
2835 - When sending or relaying a RELAY_EARLY cell, we used to convert
2836 it to a RELAY cell if the connection was using the v1 link
2837 protocol. This was a workaround for older versions of Tor, which
2838 didn't handle RELAY_EARLY cells properly. Now that all supported
2839 versions can handle RELAY_EARLY cells, and now that we're enforcing
2840 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2841 remove this workaround. Addresses bug 4786.
2843 o Code simplifications and refactoring:
2844 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2845 own homebrewed ssl_state_to_string() replacement. Patch from
2846 Emile Snyder. Fixes bug 4653.
2847 - Use macros to indicate OpenSSL versions, so we don't need to worry
2848 about accidental hexadecimal bit shifts.
2849 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2851 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2852 - Use the smartlist_add_asprintf() alias more consistently.
2853 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2854 invalid value, rather than just -1.
2855 - Rename a handful of old identifiers, mostly related to crypto
2856 structures and crypto functions. By convention, our "create an
2857 object" functions are called "type_new()", our "free an object"
2858 functions are called "type_free()", and our types indicate that
2859 they are types only with a final "_t". But a handful of older
2860 types and functions broke these rules, with function names like
2861 "type_create" or "subsystem_op_type", or with type names like
2865 Changes in version 0.2.3.10-alpha - 2011-12-16
2866 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
2867 Tor's buffers code. Absolutely everybody should upgrade.
2869 The bug relied on an incorrect calculation when making data continuous
2870 in one of our IO buffers, if the first chunk of the buffer was
2871 misaligned by just the wrong amount. The miscalculation would allow an
2872 attacker to overflow a piece of heap-allocated memory. To mount this
2873 attack, the attacker would need to either open a SOCKS connection to
2874 Tor's SocksPort (usually restricted to localhost), or target a Tor
2875 instance configured to make its connections through a SOCKS proxy
2876 (which Tor does not do by default).
2878 Good security practice requires that all heap-overflow bugs should be
2879 presumed to be exploitable until proven otherwise, so we are treating
2880 this as a potential code execution attack. Please upgrade immediately!
2881 This bug does not affect bufferevents-based builds of Tor. Special
2882 thanks to "Vektor" for reporting this issue to us!
2884 This release also contains a few minor bugfixes for issues discovered
2888 - Fix a heap overflow bug that could occur when trying to pull
2889 data into the first chunk of a buffer, when that chunk had
2890 already had some data drained from it. Fixes CVE-2011-2778;
2891 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2894 - If we can't attach streams to a rendezvous circuit when we
2895 finish connecting to a hidden service, clear the rendezvous
2896 circuit's stream-isolation state and try to attach streams
2897 again. Previously, we cleared rendezvous circuits' isolation
2898 state either too early (if they were freshly built) or not at all
2899 (if they had been built earlier and were cannibalized). Bugfix on
2900 0.2.3.3-alpha; fixes bug 4655.
2901 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
2902 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
2903 - Fix an assertion failure when a relay with accounting enabled
2904 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
2907 - Update to the December 6 2011 Maxmind GeoLite Country database.
2910 Changes in version 0.2.2.35 - 2011-12-16
2911 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
2912 buffers code. Absolutely everybody should upgrade.
2914 The bug relied on an incorrect calculation when making data continuous
2915 in one of our IO buffers, if the first chunk of the buffer was
2916 misaligned by just the wrong amount. The miscalculation would allow an
2917 attacker to overflow a piece of heap-allocated memory. To mount this
2918 attack, the attacker would need to either open a SOCKS connection to
2919 Tor's SocksPort (usually restricted to localhost), or target a Tor
2920 instance configured to make its connections through a SOCKS proxy
2921 (which Tor does not do by default).
2923 Good security practice requires that all heap-overflow bugs should be
2924 presumed to be exploitable until proven otherwise, so we are treating
2925 this as a potential code execution attack. Please upgrade immediately!
2926 This bug does not affect bufferevents-based builds of Tor. Special
2927 thanks to "Vektor" for reporting this issue to us!
2929 Tor 0.2.2.35 also fixes several bugs in previous versions, including
2930 crash bugs for unusual configurations, and a long-term bug that
2931 would prevent Tor from starting on Windows machines with draconian
2934 With this release, we remind everyone that 0.2.0.x has reached its
2935 formal end-of-life. Those Tor versions have many known flaws, and
2936 nobody should be using them. You should upgrade -- ideally to the
2937 0.2.2.x series. If you're using a Linux or BSD and its packages are
2938 obsolete, stop using those packages and upgrade anyway.
2940 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
2941 longer receive support after some time in early 2012.
2944 - Fix a heap overflow bug that could occur when trying to pull
2945 data into the first chunk of a buffer, when that chunk had
2946 already had some data drained from it. Fixes CVE-2011-2778;
2947 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2948 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2949 that it doesn't attempt to allocate a socketpair. This could cause
2950 some problems on Windows systems with overzealous firewalls. Fix for
2951 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2953 - If we mark an OR connection for close based on a cell we process,
2954 don't process any further cells on it. We already avoid further
2955 reads on marked-for-close connections, but now we also discard the
2956 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2957 which was the first version where we might mark a connection for
2958 close based on processing a cell on it.
2959 - Correctly sanity-check that we don't underflow on a memory
2960 allocation (and then assert) for hidden service introduction
2961 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2962 bugfix on 0.2.1.5-alpha.
2963 - Fix a memory leak when we check whether a hidden service
2964 descriptor has any usable introduction points left. Fixes bug
2965 4424. Bugfix on 0.2.2.25-alpha.
2966 - Don't crash when we're running as a relay and don't have a GeoIP
2967 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
2968 we've had in the 0.2.3.x branch already.
2969 - When running as a client, do not print a misleading (and plain
2970 wrong) log message that we're collecting "directory request"
2971 statistics: clients don't collect statistics. Also don't create a
2972 useless (because empty) stats file in the stats/ directory. Fixes
2973 bug 4353; bugfix on 0.2.2.34.
2976 - Detect failure to initialize Libevent. This fix provides better
2977 detection for future instances of bug 4457.
2978 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2979 function. This was eating up hideously large amounts of time on some
2980 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2981 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2982 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2984 - Don't warn about unused log_mutex in log.c when building with
2985 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2986 0.1.0.6-rc which introduced --disable-threads.
2987 - When configuring, starting, or stopping an NT service, stop
2988 immediately after the service configuration attempt has succeeded
2989 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2990 - When sending a NETINFO cell, include the original address
2991 received for the other side, not its canonical address. Found
2992 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2993 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
2994 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2995 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2996 occurred when a client tried to fetch a descriptor for a bridge
2997 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2998 - Backport fixes for a pair of compilation warnings on Windows.
2999 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3000 - If we had ever tried to call tor_addr_to_str on an address of
3001 unknown type, we would have done a strdup on an uninitialized
3002 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3003 Reported by "troll_un".
3004 - Correctly detect and handle transient lookup failures from
3005 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3006 Reported by "troll_un".
3007 - Fix null-pointer access that could occur if TLS allocation failed.
3008 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3009 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3010 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3013 - Add two new config options for directory authorities:
3014 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3015 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3016 that is always sufficient to satisfy the bandwidth requirement for
3017 the Guard flag. Now it will be easier for researchers to simulate
3018 Tor networks with different values. Resolves ticket 4484.
3019 - When Tor ignores a hidden service specified in its configuration,
3020 include the hidden service's directory in the warning message.
3021 Previously, we would only tell the user that some hidden service
3022 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3023 - Update to the December 6 2011 Maxmind GeoLite Country database.
3025 o Packaging changes:
3026 - Make it easier to automate expert package builds on Windows,
3027 by removing an absolute path from makensis.exe command.
3030 Changes in version 0.2.1.32 - 2011-12-16
3031 Tor 0.2.1.32 backports important security and privacy fixes for
3032 oldstable. This release is intended only for package maintainers and
3033 others who cannot use the 0.2.2 stable series. All others should be
3034 using Tor 0.2.2.x or newer.
3036 The Tor 0.2.1.x series will reach formal end-of-life some time in
3037 early 2012; we will stop releasing patches for it then.
3039 o Major bugfixes (also included in 0.2.2.x):
3040 - Correctly sanity-check that we don't underflow on a memory
3041 allocation (and then assert) for hidden service introduction
3042 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3043 bugfix on 0.2.1.5-alpha.
3044 - Fix a heap overflow bug that could occur when trying to pull
3045 data into the first chunk of a buffer, when that chunk had
3046 already had some data drained from it. Fixes CVE-2011-2778;
3047 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3050 - Update to the December 6 2011 Maxmind GeoLite Country database.
3053 Changes in version 0.2.3.9-alpha - 2011-12-08
3054 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3055 a "DisableNetwork" security feature that bundles can use to avoid
3056 touching the network until bridges are configured, moves forward on
3057 the pluggable transport design, fixes a flaw in the hidden service
3058 design that unnecessarily prevented clients with wrong clocks from
3059 reaching hidden services, and fixes a wide variety of other issues.
3062 - Clients can now connect to private bridges over IPv6. Bridges
3063 still need at least one IPv4 address in order to connect to
3064 other relays. Note that we don't yet handle the case where the
3065 user has two bridge lines for the same bridge (one IPv4, one
3066 IPv6). Implements parts of proposal 186.
3067 - New "DisableNetwork" config option to prevent Tor from launching any
3068 connections or accepting any connections except on a control port.
3069 Bundles and controllers can set this option before letting Tor talk
3070 to the rest of the network, for example to prevent any connections
3071 to a non-bridge address. Packages like Orbot can also use this
3072 option to instruct Tor to save power when the network is off.
3073 - Clients and bridges can now be configured to use a separate
3074 "transport" proxy. This approach makes the censorship arms race
3075 easier by allowing bridges to use protocol obfuscation plugins. It
3076 implements the "managed proxy" part of proposal 180 (ticket 3472).
3077 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3078 implementation. It makes AES_CTR about 7% faster than our old one
3079 (which was about 10% faster than the one OpenSSL used to provide).
3080 Resolves ticket 4526.
3081 - Add a "tor2web mode" for clients that want to connect to hidden
3082 services non-anonymously (and possibly more quickly). As a safety
3083 measure to try to keep users from turning this on without knowing
3084 what they are doing, tor2web mode must be explicitly enabled at
3085 compile time, and a copy of Tor compiled to run in tor2web mode
3086 cannot be used as a normal Tor client. Implements feature 2553.
3087 - Add experimental support for running on Windows with IOCP and no
3088 kernel-space socket buffers. This feature is controlled by a new
3089 "UserspaceIOCPBuffers" config option (off by default), which has
3090 no effect unless Tor has been built with support for bufferevents,
3091 is running on Windows, and has enabled IOCP. This may, in the long
3092 run, help solve or mitigate bug 98.
3093 - Use a more secure consensus parameter voting algorithm. Now at
3094 least three directory authorities or a majority of them must
3095 vote on a given parameter before it will be included in the
3096 consensus. Implements proposal 178.
3099 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3100 They used to check that the timestamp was within 30 minutes
3101 of their system clock, so they could cap the size of their
3102 replay-detection cache, but that approach unnecessarily refused
3103 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3104 the v3 intro-point protocol (the first one which sent a timestamp
3105 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3106 - Only use the EVP interface when AES acceleration is enabled,
3107 to avoid a 5-7% performance regression. Resolves issue 4525;
3108 bugfix on 0.2.3.8-alpha.
3110 o Privacy/anonymity features (bridge detection):
3111 - Make bridge SSL certificates a bit more stealthy by using random
3112 serial numbers, in the same fashion as OpenSSL when generating
3113 self-signed certificates. Implements ticket 4584.
3114 - Introduce a new config option "DynamicDHGroups", enabled by
3115 default, which provides each bridge with a unique prime DH modulus
3116 to be used during SSL handshakes. This option attempts to help
3117 against censors who might use the Apache DH modulus as a static
3118 identifier for bridges. Addresses ticket 4548.
3120 o Minor features (new/different config options):
3121 - New configuration option "DisableDebuggerAttachment" (on by default)
3122 to prevent basic debugging attachment attempts by other processes.
3123 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3124 - Allow MapAddress directives to specify matches against super-domains,
3125 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3126 Implements issue 933.
3127 - Slightly change behavior of "list" options (that is, config
3128 options that can appear more than once) when they appear both in
3129 torrc and on the command line. Previously, the command-line options
3130 would be appended to the ones from torrc. Now, the command-line
3131 options override the torrc options entirely. This new behavior
3132 allows the user to override list options (like exit policies and
3133 ports to listen on) from the command line, rather than simply
3134 appending to the list.
3135 - You can get the old (appending) command-line behavior for "list"
3136 options by prefixing the option name with a "+".
3137 - You can remove all the values for a "list" option from the command
3138 line without adding any new ones by prefixing the option name
3140 - Add experimental support for a "defaults" torrc file to be parsed
3141 before the regular torrc. Torrc options override the defaults file's
3142 options in the same way that the command line overrides the torrc.
3143 The SAVECONF controller command saves only those options which
3144 differ between the current configuration and the defaults file. HUP
3145 reloads both files. (Note: This is an experimental feature; its
3146 behavior will probably be refined in future 0.2.3.x-alpha versions
3147 to better meet packagers' needs.) Implements task 4552.
3150 - Try to make the introductory warning message that Tor prints on
3151 startup more useful for actually finding help and information.
3152 Resolves ticket 2474.
3153 - Running "make version" now displays the version of Tor that
3154 we're about to build. Idea from katmagic; resolves issue 4400.
3155 - Expire old or over-used hidden service introduction points.
3156 Required by fix for bug 3460.
3157 - Move the replay-detection cache for the RSA-encrypted parts of
3158 INTRODUCE2 cells to the introduction point data structures.
3159 Previously, we would use one replay-detection cache per hidden
3160 service. Required by fix for bug 3460.
3161 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3162 public key replay-detection cache from 60 minutes to 5 minutes. This
3163 replay-detection cache is now used only to detect multiple
3164 INTRODUCE2 cells specifying the same rendezvous point, so we can
3165 avoid launching multiple simultaneous attempts to connect to it.
3167 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3168 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3169 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3171 - Fix a minor formatting issue in one of tor-gencert's error messages.
3173 - Prevent a false positive from the check-spaces script, by disabling
3174 the "whitespace between function name and (" check for functions
3176 - Fix a log message suggesting that people contact a non-existent
3177 email address. Fixes bug 3448.
3178 - Fix null-pointer access that could occur if TLS allocation failed.
3179 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3180 - Report a real bootstrap problem to the controller on router
3181 identity mismatch. Previously we just said "foo", which probably
3182 made a lot of sense at the time. Fixes bug 4169; bugfix on
3184 - If we had ever tried to call tor_addr_to_str() on an address of
3185 unknown type, we would have done a strdup() on an uninitialized
3186 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3187 Reported by "troll_un".
3188 - Correctly detect and handle transient lookup failures from
3189 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3190 Reported by "troll_un".
3191 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3192 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3193 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3194 bug 4532; found by "troll_un".
3196 o Minor bugfixes (on Tor 0.2.3.x):
3197 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3199 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3200 circuit for use as a hidden service client's rendezvous point.
3201 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3202 with help from wanoskarnet.
3203 - Restore behavior of overriding SocksPort, ORPort, and similar
3204 options from the command line. Bugfix on 0.2.3.3-alpha.
3207 - Properly handle the case where the build-tree is not the same
3208 as the source tree when generating src/common/common_sha1.i,
3209 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3210 bugfix on 0.2.0.1-alpha.
3212 o Code simplifications, cleanups, and refactorings:
3213 - Remove the pure attribute from all functions that used it
3214 previously. In many cases we assigned it incorrectly, because the
3215 functions might assert or call impure functions, and we don't have
3216 evidence that keeping the pure attribute is worthwhile. Implements
3217 changes suggested in ticket 4421.
3218 - Remove some dead code spotted by coverity. Fixes cid 432.
3219 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3222 Changes in version 0.2.3.8-alpha - 2011-11-22
3223 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3224 socketpair-related bug that has been bothering Windows users. It adds
3225 support to serve microdescriptors to controllers, so Vidalia's network
3226 map can resume listing relays (once Vidalia implements its side),
3227 and adds better support for hardware AES acceleration. Finally, it
3228 starts the process of adjusting the bandwidth cutoff for getting the
3229 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3230 that tiny relays harm performance more than they help network capacity.
3233 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3234 that it doesn't attempt to allocate a socketpair. This could cause
3235 some problems on Windows systems with overzealous firewalls. Fix for
3236 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3238 - Correctly sanity-check that we don't underflow on a memory
3239 allocation (and then assert) for hidden service introduction
3240 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3241 bugfix on 0.2.1.5-alpha.
3242 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3243 flag. In the past few years the average relay speed has picked
3244 up, and while the "top 7/8 of the network get the Fast flag" and
3245 "all relays with 20KB or more of capacity get the Fast flag" rules
3246 used to have the same result, now the top 7/8 of the network has
3247 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3248 - Fix a rare assertion failure when checking whether a v0 hidden
3249 service descriptor has any usable introduction points left, and
3250 we don't have enough information to build a circuit to the first
3251 intro point named in the descriptor. The HS client code in
3252 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3253 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3254 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3255 - Make bridge authorities not crash when they are asked for their own
3256 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3257 - When running as a client, do not print a misleading (and plain
3258 wrong) log message that we're collecting "directory request"
3259 statistics: clients don't collect statistics. Also don't create a
3260 useless (because empty) stats file in the stats/ directory. Fixes
3261 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3264 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3265 for a relay by identity digest or nickname. Previously,
3266 microdescriptors were only available by their own digests, so a
3267 controller would have to ask for and parse the whole microdescriptor
3268 consensus in order to look up a single relay's microdesc. Fixes
3269 bug 3832; bugfix on 0.2.3.1-alpha.
3270 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3271 operations can use hardware acceleration (if present). Resolves
3274 o Minor bugfixes (on 0.2.2.x and earlier):
3275 - Detect failure to initialize Libevent. This fix provides better
3276 detection for future instances of bug 4457.
3277 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3278 function. This was eating up hideously large amounts of time on some
3279 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3280 - Don't warn about unused log_mutex in log.c when building with
3281 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3282 0.1.0.6-rc which introduced --disable-threads.
3283 - Allow manual 'authenticate' commands to the controller interface
3284 from netcat (nc) as well as telnet. We were rejecting them because
3285 they didn't come with the expected whitespace at the end of the
3286 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3287 - Fix some (not actually triggerable) buffer size checks in usage of
3288 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3290 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3291 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3292 - When configuring, starting, or stopping an NT service, stop
3293 immediately after the service configuration attempt has succeeded
3294 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3295 - When sending a NETINFO cell, include the original address
3296 received for the other side, not its canonical address. Found
3297 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3298 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3299 can pick them up when the tests aren't disabled. Bugfix on
3300 0.2.2.4-alpha which introduced tinytest.
3301 - Fix a memory leak when we check whether a hidden service
3302 descriptor has any usable introduction points left. Fixes bug
3303 4424. Bugfix on 0.2.2.25-alpha.
3304 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3305 occurred when a client tried to fetch a descriptor for a bridge
3306 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3308 o Minor bugfixes (on 0.2.3.x):
3309 - Make util unit tests build correctly with MSVC. Bugfix on
3310 0.2.3.3-alpha. Patch by Gisle Vanem.
3311 - Successfully detect AUTH_CHALLENGE cells with no recognized
3312 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3314 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3315 it should still send a NETINFO cell to allow the connection to
3316 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3318 - Log less loudly when we get an invalid authentication certificate
3319 from a source other than a directory authority: it's not unusual
3320 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3322 - Tolerate servers with more clock skew in their authentication
3323 certificates than previously. Fixes bug 4371; bugfix on
3325 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3326 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3329 - Add two new config options for directory authorities:
3330 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3331 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3332 that is always sufficient to satisfy the bandwidth requirement for
3333 the Guard flag. Now it will be easier for researchers to simulate
3334 Tor networks with different values. Resolves ticket 4484.
3335 - When Tor ignores a hidden service specified in its configuration,
3336 include the hidden service's directory in the warning message.
3337 Previously, we would only tell the user that some hidden service
3338 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3339 - When we fail to initialize Libevent, retry with IOCP disabled so we
3340 don't need to turn on multi-threading support in Libevent, which in
3341 turn requires a working socketpair(). This is a workaround for bug
3342 4457, which affects Libevent versions from 2.0.1-alpha through
3344 - Detect when we try to build on a platform that doesn't define
3345 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3346 - Update to the November 1 2011 Maxmind GeoLite Country database.
3348 o Packaging changes:
3349 - Make it easier to automate expert package builds on Windows,
3350 by removing an absolute path from makensis.exe command.
3352 o Code simplifications and refactoring:
3353 - Remove some redundant #include directives throughout the code.
3354 Patch from Andrea Gelmini.
3355 - Unconditionally use OpenSSL's AES implementation instead of our
3356 old built-in one. OpenSSL's AES has been better for a while, and
3357 relatively few servers should still be on any version of OpenSSL
3358 that doesn't have good optimized assembly AES.
3359 - Use the name "CERTS" consistently to refer to the new cell type;
3360 we were calling it CERT in some places and CERTS in others.
3363 - Numerous new unit tests for functions in util.c and address.c by
3365 - The long-disabled benchmark tests are now split into their own
3366 ./src/test/bench binary.
3367 - The benchmark tests can now use more accurate timers than
3368 gettimeofday() when such timers are available.
3371 Changes in version 0.2.3.7-alpha - 2011-10-30
3372 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3373 the new v3 handshake. It also resolves yet another bridge address
3377 - If we mark an OR connection for close based on a cell we process,
3378 don't process any further cells on it. We already avoid further
3379 reads on marked-for-close connections, but now we also discard the
3380 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3381 which was the first version where we might mark a connection for
3382 close based on processing a cell on it.
3383 - Fix a double-free bug that would occur when we received an invalid
3384 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3385 bugfix on 0.2.3.6-alpha.
3386 - Bridges no longer include their address in NETINFO cells on outgoing
3387 OR connections, to allow them to blend in better with clients.
3388 Removes another avenue for enumerating bridges. Reported by
3389 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3390 cells were introduced.
3393 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3394 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3397 Changes in version 0.2.3.6-alpha - 2011-10-26
3398 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3399 anonymity vulnerability where an attacker can deanonymize Tor
3400 users. Everybody should upgrade.
3402 This release also features support for a new v3 connection handshake
3403 protocol, and fixes to make hidden service connections more robust.
3406 - Implement a new handshake protocol (v3) for authenticating Tors to
3407 each other over TLS. It should be more resistant to fingerprinting
3408 than previous protocols, and should require less TLS hacking for
3409 future Tor implementations. Implements proposal 176.
3410 - Allow variable-length padding cells to disguise the length of
3411 Tor's TLS records. Implements part of proposal 184.
3413 o Privacy/anonymity fixes (clients):
3414 - Clients and bridges no longer send TLS certificate chains on
3415 outgoing OR connections. Previously, each client or bridge would
3416 use the same cert chain for all outgoing OR connections until
3417 its IP address changes, which allowed any relay that the client
3418 or bridge contacted to determine which entry guards it is using.
3419 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3420 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3421 no longer considers that connection as suitable for satisfying a
3422 circuit EXTEND request. Now relays can protect clients from the
3423 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3424 - Directory authorities no longer assign the Guard flag to relays
3425 that haven't upgraded to the above "refuse EXTEND requests
3426 to client connections" fix. Now directory authorities can
3427 protect clients from the CVE-2011-2768 issue even if neither
3428 the clients nor the relays have upgraded yet. There's a new
3429 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3430 to let us transition smoothly, else tomorrow there would be no
3433 o Major bugfixes (hidden services):
3434 - Improve hidden service robustness: when an attempt to connect to
3435 a hidden service ends, be willing to refetch its hidden service
3436 descriptors from each of the HSDir relays responsible for them
3437 immediately. Previously, we would not consider refetching the
3438 service's descriptors from each HSDir for 15 minutes after the last
3439 fetch, which was inconvenient if the hidden service was not running
3440 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3441 - When one of a hidden service's introduction points appears to be
3442 unreachable, stop trying it. Previously, we would keep trying
3443 to build circuits to the introduction point until we lost the
3444 descriptor, usually because the user gave up and restarted Tor.
3445 Partly fixes bug 3825.
3446 - Don't launch a useless circuit after failing to use one of a
3447 hidden service's introduction points. Previously, we would
3448 launch a new introduction circuit, but not set the hidden service
3449 which that circuit was intended to connect to, so it would never
3450 actually be used. A different piece of code would then create a
3451 new introduction circuit correctly. Bug reported by katmagic and
3452 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3454 o Major bugfixes (other):
3455 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3456 that they initiated. Relays could distinguish incoming bridge
3457 connections from client connections, creating another avenue for
3458 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3459 Found by "frosty_un".
3460 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3461 tor gets started. This prevents a wrong average bandwidth
3462 estimate, which would cause relays to always start a new accounting
3463 interval at the earliest possible moment. Fixes bug 2003; bugfix
3464 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3465 immensely in tracking this bug down.
3466 - Fix a crash bug when changing node restrictions while a DNS lookup
3467 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3470 o Minor bugfixes (on 0.2.2.x and earlier):
3471 - When a hidden service turns an extra service-side introduction
3472 circuit into a general-purpose circuit, free the rend_data and
3473 intro_key fields first, so we won't leak memory if the circuit
3474 is cannibalized for use as another service-side introduction
3475 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3476 - Rephrase the log message emitted if the TestSocks check is
3477 successful. Patch from Fabian Keil; fixes bug 4094.
3478 - Bridges now skip DNS self-tests, to act a little more stealthily.
3479 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3480 bridges. Patch by "warms0x".
3481 - Remove a confusing dollar sign from the example fingerprint in the
3482 man page, and also make the example fingerprint a valid one. Fixes
3483 bug 4309; bugfix on 0.2.1.3-alpha.
3484 - Fix internal bug-checking logic that was supposed to catch
3485 failures in digest generation so that it will fail more robustly
3486 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3487 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3488 - Report any failure in init_keys() calls launched because our
3489 IP address has changed. Spotted by Coverity Scan. Bugfix on
3490 0.1.1.4-alpha; fixes CID 484.
3492 o Minor bugfixes (on 0.2.3.x):
3493 - Fix a bug in configure.in that kept it from building a configure
3494 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3495 bugfix on 0.2.3.1-alpha.
3496 - Don't warn users that they are exposing a client port to the
3497 Internet if they have specified an RFC1918 address. Previously,
3498 we would warn if the user had specified any non-loopback
3499 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3500 - Fix memory leaks in the failing cases of the new SocksPort and
3501 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3502 fixes coverity CIDs 485, 486, and 487.
3505 - When a hidden service's introduction point times out, consider
3506 trying it again during the next attempt to connect to the
3507 HS. Previously, we would not try it again unless a newly fetched
3508 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3509 - The next version of Windows will be called Windows 8, and it has
3510 a major version of 6, minor version of 2. Correctly identify that
3511 version instead of calling it "Very recent version". Resolves
3512 ticket 4153; reported by funkstar.
3513 - The Bridge Authority now writes statistics on how many bridge
3514 descriptors it gave out in total, and how many unique descriptors
3515 it gave out. It also lists how often the most and least commonly
3516 fetched descriptors were given out, as well as the median and
3517 25th/75th percentile. Implements tickets 4200 and 4294.
3518 - Update to the October 4 2011 Maxmind GeoLite Country database.
3520 o Code simplifications and refactoring:
3521 - Remove some old code to remember statistics about which descriptors
3522 we've served as a directory mirror. The feature wasn't used and
3523 is outdated now that microdescriptors are around.
3524 - Rename Tor functions that turn strings into addresses, so that
3525 "parse" indicates that no hostname resolution occurs, and
3526 "lookup" indicates that hostname resolution may occur. This
3527 should help prevent mistakes in the future. Fixes bug 3512.
3530 Changes in version 0.2.2.34 - 2011-10-26
3531 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3532 can deanonymize Tor users. Everybody should upgrade.
3534 The attack relies on four components: 1) Clients reuse their TLS cert
3535 when talking to different relays, so relays can recognize a user by
3536 the identity key in her cert. 2) An attacker who knows the client's
3537 identity key can probe each guard relay to see if that identity key
3538 is connected to that guard relay right now. 3) A variety of active
3539 attacks in the literature (starting from "Low-Cost Traffic Analysis
3540 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3541 discover the guard relays that a Tor user visiting the website is using.
3542 4) Clients typically pick three guards at random, so the set of guards
3543 for a given user could well be a unique fingerprint for her. This
3544 release fixes components #1 and #2, which is enough to block the attack;
3545 the other two remain as open research problems. Special thanks to
3546 "frosty_un" for reporting the issue to us!
3548 Clients should upgrade so they are no longer recognizable by the TLS
3549 certs they present. Relays should upgrade so they no longer allow a
3550 remote attacker to probe them to test whether unpatched clients are
3551 currently connected to them.
3553 This release also fixes several vulnerabilities that allow an attacker
3554 to enumerate bridge relays. Some bridge enumeration attacks still
3555 remain; see for example proposal 188.
3557 o Privacy/anonymity fixes (clients):
3558 - Clients and bridges no longer send TLS certificate chains on
3559 outgoing OR connections. Previously, each client or bridge would
3560 use the same cert chain for all outgoing OR connections until
3561 its IP address changes, which allowed any relay that the client
3562 or bridge contacted to determine which entry guards it is using.
3563 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3564 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3565 no longer considers that connection as suitable for satisfying a
3566 circuit EXTEND request. Now relays can protect clients from the
3567 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3568 - Directory authorities no longer assign the Guard flag to relays
3569 that haven't upgraded to the above "refuse EXTEND requests
3570 to client connections" fix. Now directory authorities can
3571 protect clients from the CVE-2011-2768 issue even if neither
3572 the clients nor the relays have upgraded yet. There's a new
3573 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3574 to let us transition smoothly, else tomorrow there would be no
3577 o Privacy/anonymity fixes (bridge enumeration):
3578 - Bridge relays now do their directory fetches inside Tor TLS
3579 connections, like all the other clients do, rather than connecting
3580 directly to the DirPort like public relays do. Removes another
3581 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3582 - Bridges relays now build circuits for themselves in a more similar
3583 way to how clients build them. Removes another avenue for
3584 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3585 when bridges were introduced.
3586 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3587 that they initiated. Relays could distinguish incoming bridge
3588 connections from client connections, creating another avenue for
3589 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3590 Found by "frosty_un".
3593 - Fix a crash bug when changing node restrictions while a DNS lookup
3594 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3596 - Don't launch a useless circuit after failing to use one of a
3597 hidden service's introduction points. Previously, we would
3598 launch a new introduction circuit, but not set the hidden service
3599 which that circuit was intended to connect to, so it would never
3600 actually be used. A different piece of code would then create a
3601 new introduction circuit correctly. Bug reported by katmagic and
3602 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3605 - Change an integer overflow check in the OpenBSD_Malloc code so
3606 that GCC is less likely to eliminate it as impossible. Patch
3607 from Mansour Moufid. Fixes bug 4059.
3608 - When a hidden service turns an extra service-side introduction
3609 circuit into a general-purpose circuit, free the rend_data and
3610 intro_key fields first, so we won't leak memory if the circuit
3611 is cannibalized for use as another service-side introduction
3612 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3613 - Bridges now skip DNS self-tests, to act a little more stealthily.
3614 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3615 bridges. Patch by "warms0x".
3616 - Fix internal bug-checking logic that was supposed to catch
3617 failures in digest generation so that it will fail more robustly
3618 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3619 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3620 - Report any failure in init_keys() calls launched because our
3621 IP address has changed. Spotted by Coverity Scan. Bugfix on
3622 0.1.1.4-alpha; fixes CID 484.
3624 o Minor bugfixes (log messages and documentation):
3625 - Remove a confusing dollar sign from the example fingerprint in the
3626 man page, and also make the example fingerprint a valid one. Fixes
3627 bug 4309; bugfix on 0.2.1.3-alpha.
3628 - The next version of Windows will be called Windows 8, and it has
3629 a major version of 6, minor version of 2. Correctly identify that
3630 version instead of calling it "Very recent version". Resolves
3631 ticket 4153; reported by funkstar.
3632 - Downgrade log messages about circuit timeout calibration from
3633 "notice" to "info": they don't require or suggest any human
3634 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3635 bugfix on 0.2.2.14-alpha.
3638 - Turn on directory request statistics by default and include them in
3639 extra-info descriptors. Don't break if we have no GeoIP database.
3640 Backported from 0.2.3.1-alpha; implements ticket 3951.
3641 - Update to the October 4 2011 Maxmind GeoLite Country database.
3644 Changes in version 0.2.1.31 - 2011-10-26
3645 Tor 0.2.1.31 backports important security and privacy fixes for
3646 oldstable. This release is intended only for package maintainers and
3647 others who cannot use the 0.2.2 stable series. All others should be
3648 using Tor 0.2.2.x or newer.
3650 o Security fixes (also included in 0.2.2.x):
3651 - Replace all potentially sensitive memory comparison operations
3652 with versions whose runtime does not depend on the data being
3653 compared. This will help resist a class of attacks where an
3654 adversary can use variations in timing information to learn
3655 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3656 implementation by Robert Ransom based partially on code by DJB.)
3657 - Fix an assert in parsing router descriptors containing IPv6
3658 addresses. This one took down the directory authorities when
3659 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3661 o Privacy/anonymity fixes (also included in 0.2.2.x):
3662 - Clients and bridges no longer send TLS certificate chains on
3663 outgoing OR connections. Previously, each client or bridge would
3664 use the same cert chain for all outgoing OR connections until
3665 its IP address changes, which allowed any relay that the client
3666 or bridge contacted to determine which entry guards it is using.
3667 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3668 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3669 no longer considers that connection as suitable for satisfying a
3670 circuit EXTEND request. Now relays can protect clients from the
3671 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3672 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3673 that they initiated. Relays could distinguish incoming bridge
3674 connections from client connections, creating another avenue for
3675 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3676 Found by "frosty_un".
3677 - When receiving a hidden service descriptor, check that it is for
3678 the hidden service we wanted. Previously, Tor would store any
3679 hidden service descriptors that a directory gave it, whether it
3680 wanted them or not. This wouldn't have let an attacker impersonate
3681 a hidden service, but it did let directories pre-seed a client
3682 with descriptors that it didn't want. Bugfix on 0.0.6.
3683 - Avoid linkability based on cached hidden service descriptors: forget
3684 all hidden service descriptors cached as a client when processing a
3685 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3686 - Make the bridge directory authority refuse to answer directory
3687 requests for "all" descriptors. It used to include bridge
3688 descriptors in its answer, which was a major information leak.
3689 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3690 - Don't attach new streams to old rendezvous circuits after SIGNAL
3691 NEWNYM. Previously, we would keep using an existing rendezvous
3692 circuit if it remained open (i.e. if it were kept open by a
3693 long-lived stream, or if a new stream were attached to it before
3694 Tor could notice that it was old and no longer in use). Bugfix on
3695 0.1.1.15-rc; fixes bug 3375.
3697 o Minor bugfixes (also included in 0.2.2.x):
3698 - When we restart our relay, we might get a successful connection
3699 from the outside before we've started our reachability tests,
3700 triggering a warning: "ORPort found reachable, but I have no
3701 routerinfo yet. Failing to inform controller of success." This
3702 bug was harmless unless Tor is running under a controller
3703 like Vidalia, in which case the controller would never get a
3704 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3706 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3707 enabled. Fixes bug 1526.
3708 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3709 anything since 0.2.1.16-rc.
3710 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3711 None of the cases where we did this before were wrong, but by making
3712 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3713 - Fix a rare crash bug that could occur when a client was configured
3714 with a large number of bridges. Fixes bug 2629; bugfix on
3715 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3716 - Correct the warning displayed when a rendezvous descriptor exceeds
3717 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3719 - Fix an uncommon assertion failure when running with DNSPort under
3720 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3721 - When warning about missing zlib development packages during compile,
3722 give the correct package names. Bugfix on 0.2.0.1-alpha.
3723 - Require that introduction point keys and onion keys have public
3724 exponent 65537. Bugfix on 0.2.0.10-alpha.
3725 - Do not crash when our configuration file becomes unreadable, for
3726 example due to a permissions change, between when we start up
3727 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3729 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3731 - Always NUL-terminate the sun_path field of a sockaddr_un before
3732 passing it to the kernel. (Not a security issue: kernels are
3733 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3734 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3735 - Don't stack-allocate the list of supplementary GIDs when we're
3736 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3737 could take up to 256K, which is way too much stack. Found by
3738 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3740 o Minor bugfixes (only in 0.2.1.x):
3741 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3742 rely on them. Bugfix on 0.2.1.30.
3743 - Use git revisions instead of svn revisions when generating our
3744 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3746 o Minor features (also included in 0.2.2.x):
3747 - Adjust the expiration time on our SSL session certificates to
3748 better match SSL certs seen in the wild. Resolves ticket 4014.
3749 - Allow nameservers with IPv6 address. Resolves bug 2574.
3750 - Update to the October 4 2011 Maxmind GeoLite Country database.
3753 Changes in version 0.2.3.5-alpha - 2011-09-28
3754 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
3755 bridge relays; fixes an assertion error that many users started hitting
3756 today; and adds the ability to refill token buckets more often than
3757 once per second, allowing significant performance improvements.
3760 - Bridge relays now do their directory fetches inside Tor TLS
3761 connections, like all the other clients do, rather than connecting
3762 directly to the DirPort like public relays do. Removes another
3763 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3764 - Bridges relays now build circuits for themselves in a more similar
3765 way to how clients build them. Removes another avenue for
3766 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3767 when bridges were introduced.
3770 - Fix an "Assertion md->held_by_node == 1 failed" error that could
3771 occur when the same microdescriptor was referenced by two node_t
3772 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
3774 o Major features (networking):
3775 - Add a new TokenBucketRefillInterval option to refill token buckets
3776 more frequently than once per second. This should improve network
3777 performance, alleviate queueing problems, and make traffic less
3778 bursty. Implements proposal 183; closes ticket 3630. Design by
3779 Florian Tschorsch and Björn Scheuermann; implementation by
3783 - Change an integer overflow check in the OpenBSD_Malloc code so
3784 that GCC is less likely to eliminate it as impossible. Patch
3785 from Mansour Moufid. Fixes bug 4059.
3787 o Minor bugfixes (usability):
3788 - Downgrade log messages about circuit timeout calibration from
3789 "notice" to "info": they don't require or suggest any human
3790 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3791 bugfix on 0.2.2.14-alpha.
3793 o Minor features (diagnostics):
3794 - When the system call to create a listener socket fails, log the
3795 error message explaining why. This may help diagnose bug 4027.
3798 Changes in version 0.2.3.4-alpha - 2011-09-13
3799 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
3800 tweak to Tor's TLS handshake that makes relays and bridges that run
3801 this new version reachable from Iran again. It also fixes a few new
3802 bugs in 0.2.3.x, and teaches relays to recognize when they're not
3803 listed in the network consensus and republish.
3805 o Major bugfixes (also part of 0.2.2.33):
3806 - Avoid an assertion failure when reloading a configuration with
3807 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3808 3923; bugfix on 0.2.2.25-alpha.
3810 o Minor features (security, also part of 0.2.2.33):
3811 - Check for replays of the public-key encrypted portion of an
3812 INTRODUCE1 cell, in addition to the current check for replays of
3813 the g^x value. This prevents a possible class of active attacks
3814 by an attacker who controls both an introduction point and a
3815 rendezvous point, and who uses the malleability of AES-CTR to
3816 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3817 that these attacks are infeasible (requiring the attacker to send
3818 on the order of zettabytes of altered cells in a short interval),
3819 but we'd rather block them off in case there are any classes of
3820 this attack that we missed. Reported by Willem Pinckaers.
3822 o Minor features (also part of 0.2.2.33):
3823 - Adjust the expiration time on our SSL session certificates to
3824 better match SSL certs seen in the wild. Resolves ticket 4014.
3825 - Change the default required uptime for a relay to be accepted as
3826 a HSDir (hidden service directory) from 24 hours to 25 hours.
3827 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3828 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3829 authorities to abstain from voting on assignment of the HSDir
3830 consensus flag. Related to bug 2649.
3831 - Update to the September 6 2011 Maxmind GeoLite Country database.
3833 o Minor bugfixes (also part of 0.2.2.33):
3834 - Demote the 'replay detected' log message emitted when a hidden
3835 service receives the same Diffie-Hellman public key in two different
3836 INTRODUCE2 cells to info level. A normal Tor client can cause that
3837 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3838 fixes part of bug 2442.
3839 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3840 level. There is nothing that a hidden service's operator can do
3841 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3843 - Clarify a log message specifying the characters permitted in
3844 HiddenServiceAuthorizeClient client names. Previously, the log
3845 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3846 given the impression that every ASCII character between "+" and "_"
3847 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3849 o Build fixes (also part of 0.2.2.33):
3850 - Clean up some code issues that prevented Tor from building on older
3851 BSDs. Fixes bug 3894; reported by "grarpamp".
3852 - Search for a platform-specific version of "ar" when cross-compiling.
3853 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3856 - Fix a bug where the SocksPort option (for example) would get
3857 ignored and replaced by the default if a SocksListenAddress
3858 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
3862 - Relays now try regenerating and uploading their descriptor more
3863 frequently if they are not listed in the consensus, or if the
3864 version of their descriptor listed in the consensus is too
3865 old. This fix should prevent situations where a server declines
3866 to re-publish itself because it has done so too recently, even
3867 though the authorities decided not to list its recent-enough
3868 descriptor. Fix for bug 3327.
3871 - Relays now include a reason for regenerating their descriptors
3872 in an HTTP header when uploading to the authorities. This will
3873 make it easier to debug descriptor-upload issues in the future.
3874 - When starting as root and then changing our UID via the User
3875 control option, and we have a ControlSocket configured, make sure
3876 that the ControlSocket is owned by the same account that Tor will
3877 run under. Implements ticket 3421; fix by Jérémy Bobbio.
3880 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
3881 utility function used in the control-port code). This shouldn't
3882 ever happen unless Tor is completely out of memory, but if it did
3883 happen and Tor somehow recovered from it, Tor could have sent a log
3884 message to a control port in the middle of a reply to a controller
3885 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
3886 - Make 'FetchUselessDescriptors' cause all descriptor types and
3887 all consensus types (including microdescriptors) to get fetched.
3888 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
3891 - Make a new "entry connection" struct as an internal subtype of "edge
3892 connection", to simplify the code and make exit connections smaller.
3895 Changes in version 0.2.2.33 - 2011-09-13
3896 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
3897 TLS handshake that makes relays and bridges that run this new version
3898 reachable from Iran again.
3901 - Avoid an assertion failure when reloading a configuration with
3902 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3903 3923; bugfix on 0.2.2.25-alpha.
3905 o Minor features (security):
3906 - Check for replays of the public-key encrypted portion of an
3907 INTRODUCE1 cell, in addition to the current check for replays of
3908 the g^x value. This prevents a possible class of active attacks
3909 by an attacker who controls both an introduction point and a
3910 rendezvous point, and who uses the malleability of AES-CTR to
3911 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3912 that these attacks are infeasible (requiring the attacker to send
3913 on the order of zettabytes of altered cells in a short interval),
3914 but we'd rather block them off in case there are any classes of
3915 this attack that we missed. Reported by Willem Pinckaers.
3918 - Adjust the expiration time on our SSL session certificates to
3919 better match SSL certs seen in the wild. Resolves ticket 4014.
3920 - Change the default required uptime for a relay to be accepted as
3921 a HSDir (hidden service directory) from 24 hours to 25 hours.
3922 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3923 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3924 authorities to abstain from voting on assignment of the HSDir
3925 consensus flag. Related to bug 2649.
3926 - Update to the September 6 2011 Maxmind GeoLite Country database.
3928 o Minor bugfixes (documentation and log messages):
3929 - Correct the man page to explain that HashedControlPassword and
3930 CookieAuthentication can both be set, in which case either method
3931 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3932 when we decided to allow these config options to both be set. Issue
3934 - Demote the 'replay detected' log message emitted when a hidden
3935 service receives the same Diffie-Hellman public key in two different
3936 INTRODUCE2 cells to info level. A normal Tor client can cause that
3937 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3938 fixes part of bug 2442.
3939 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3940 level. There is nothing that a hidden service's operator can do
3941 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3943 - Clarify a log message specifying the characters permitted in
3944 HiddenServiceAuthorizeClient client names. Previously, the log
3945 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3946 given the impression that every ASCII character between "+" and "_"
3947 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3950 - Provide a substitute implementation of lround() for MSVC, which
3951 apparently lacks it. Patch from Gisle Vanem.
3952 - Clean up some code issues that prevented Tor from building on older
3953 BSDs. Fixes bug 3894; reported by "grarpamp".
3954 - Search for a platform-specific version of "ar" when cross-compiling.
3955 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3958 Changes in version 0.2.3.3-alpha - 2011-09-01
3959 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
3960 security, and provides client-side support for the microdescriptor
3961 and optimistic data features introduced earlier in the 0.2.3.x
3962 series. It also includes numerous critical bugfixes in the (optional)
3963 bufferevent-based networking backend.
3965 o Major features (stream isolation):
3966 - You can now configure Tor so that streams from different
3967 applications are isolated on different circuits, to prevent an
3968 attacker who sees your streams as they leave an exit node from
3969 linking your sessions to one another. To do this, choose some way
3970 to distinguish the applications: have them connect to different
3971 SocksPorts, or have one of them use SOCKS4 while the other uses
3972 SOCKS5, or have them pass different authentication strings to the
3973 SOCKS proxy. Then, use the new SocksPort syntax to configure the
3974 degree of isolation you need. This implements Proposal 171.
3975 - There's a new syntax for specifying multiple client ports (such as
3976 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
3977 multiple *Port entries with full addr:port syntax on each.
3978 The old *ListenAddress format is still supported, but you can't
3979 mix it with the new *Port syntax.
3981 o Major features (other):
3982 - Enable microdescriptor fetching by default for clients. This allows
3983 clients to download a much smaller amount of directory information.
3984 To disable it (and go back to the old-style consensus and
3985 descriptors), set "UseMicrodescriptors 0" in your torrc file.
3986 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
3987 "PortForwarding" config option), now supports Windows.
3988 - When using an exit relay running 0.2.3.x, clients can now
3989 "optimistically" send data before the exit relay reports that
3990 the stream has opened. This saves a round trip when starting
3991 connections where the client speaks first (such as web browsing).
3992 This behavior is controlled by a consensus parameter (currently
3993 disabled). To turn it on or off manually, use the "OptimisticData"
3994 torrc option. Implements proposal 181; code by Ian Goldberg.
3996 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
3997 - When using IOCP on Windows, we need to enable Libevent windows
3999 - The IOCP backend now works even when the user has not specified
4000 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4001 Fixes part of bug 3752.
4002 - Correctly record the bytes we've read and written when using
4003 bufferevents, so that we can include them in our bandwidth history
4004 and advertised bandwidth. Fixes bug 3803.
4005 - Apply rate-limiting only at the bottom of a chain of filtering
4006 bufferevents. This prevents us from filling up internal read
4007 buffers and violating rate-limits when filtering bufferevents
4008 are enabled. Fixes part of bug 3804.
4009 - Add high-watermarks to the output buffers for filtered
4010 bufferevents. This prevents us from filling up internal write
4011 buffers and wasting CPU cycles when filtering bufferevents are
4012 enabled. Fixes part of bug 3804.
4013 - Correctly notice when data has been written from a bufferevent
4014 without flushing it completely. Fixes bug 3805.
4015 - Fix a bug where server-side tunneled bufferevent-based directory
4016 streams would get closed prematurely. Fixes bug 3814.
4017 - Fix a use-after-free error with per-connection rate-limiting
4018 buckets. Fixes bug 3888.
4020 o Major bugfixes (also part of 0.2.2.31-rc):
4021 - If we're configured to write our ControlPorts to disk, only write
4022 them after switching UID and creating the data directory. This way,
4023 we don't fail when starting up with a nonexistent DataDirectory
4024 and a ControlPortWriteToFile setting based on that directory. Fixes
4025 bug 3747; bugfix on Tor 0.2.2.26-beta.
4028 - Added a new CONF_CHANGED event so that controllers can be notified
4029 of any configuration changes made by other controllers, or by the
4030 user. Implements ticket 1692.
4031 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4032 leak when using bufferevents, and lets Libevent worry about how to
4033 best copy data out of a buffer.
4034 - Replace files in stats/ rather than appending to them. Now that we
4035 include statistics in extra-info descriptors, it makes no sense to
4036 keep old statistics forever. Implements ticket 2930.
4038 o Minor features (build compatibility):
4039 - Limited, experimental support for building with nmake and MSVC.
4040 - Provide a substitute implementation of lround() for MSVC, which
4041 apparently lacks it. Patch from Gisle Vanem.
4043 o Minor features (also part of 0.2.2.31-rc):
4044 - Update to the August 2 2011 Maxmind GeoLite Country database.
4046 o Minor bugfixes (on 0.2.3.x-alpha):
4047 - Fix a spurious warning when parsing SOCKS requests with
4048 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4049 - Get rid of a harmless warning that could happen on relays running
4050 with bufferevents. The warning was caused by someone doing an http
4051 request to a relay's orport. Also don't warn for a few related
4052 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4054 o Minor bugfixes (on 2.2.x and earlier):
4055 - Correct the man page to explain that HashedControlPassword and
4056 CookieAuthentication can both be set, in which case either method
4057 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4058 when we decided to allow these config options to both be set. Issue
4060 - The "--quiet" and "--hush" options now apply not only to Tor's
4061 behavior before logs are configured, but also to Tor's behavior in
4062 the absense of configured logs. Fixes bug 3550; bugfix on
4065 o Minor bugfixes (also part of 0.2.2.31-rc):
4066 - Write several files in text mode, on OSes that distinguish text
4067 mode from binary mode (namely, Windows). These files are:
4068 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4069 that collect those statistics; 'client_keys' and 'hostname' for
4070 hidden services that use authentication; and (in the tor-gencert
4071 utility) newly generated identity and signing keys. Previously,
4072 we wouldn't specify text mode or binary mode, leading to an
4073 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4074 the DirRecordUsageByCountry option which would have triggered
4075 the assertion failure was added), although this assertion failure
4076 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4077 - Selectively disable deprecation warnings on OS X because Lion
4078 started deprecating the shipped copy of openssl. Fixes bug 3643.
4079 - Remove an extra pair of quotation marks around the error
4080 message in control-port STATUS_GENERAL BUG events. Bugfix on
4081 0.1.2.6-alpha; fixes bug 3732.
4082 - When unable to format an address as a string, report its value
4083 as "???" rather than reusing the last formatted address. Bugfix
4086 o Code simplifications and refactoring:
4087 - Rewrite the listener-selection logic so that parsing which ports
4088 we want to listen on is now separate from binding to the ports
4092 - Building Tor with bufferevent support now requires Libevent
4093 2.0.13-stable or later. Previous versions of Libevent had bugs in
4094 SSL-related bufferevents and related issues that would make Tor
4095 work badly with bufferevents. Requiring 2.0.13-stable also allows
4096 Tor with bufferevents to take advantage of Libevent APIs
4097 introduced after 2.0.8-rc.
4100 Changes in version 0.2.2.32 - 2011-08-27
4101 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4102 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4103 a founder of the PETS community, a leader in our field, a mentor,
4104 and a friend. He left us with these words: "I had the possibility
4105 to contribute to this world that is not as it should be. I hope I
4106 could help in some areas to make the world a better place, and that
4107 I could also encourage other people to be engaged in improving the
4108 world. Please, stay engaged. This world needs you, your love, your
4109 initiative -- now I cannot be part of that anymore."
4111 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4112 ready. More than two years in the making, this release features improved
4113 client performance and hidden service reliability, better compatibility
4114 for Android, correct behavior for bridges that listen on more than
4115 one address, more extensible and flexible directory object handling,
4116 better reporting of network statistics, improved code security, and
4117 many many other features and bugfixes.
4120 Changes in version 0.2.2.31-rc - 2011-08-17
4121 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4122 for the Tor 0.2.2.x series.
4125 - Remove an extra pair of quotation marks around the error
4126 message in control-port STATUS_GENERAL BUG events. Bugfix on
4127 0.1.2.6-alpha; fixes bug 3732.
4128 - If we're configured to write our ControlPorts to disk, only write
4129 them after switching UID and creating the data directory. This way,
4130 we don't fail when starting up with a nonexistent DataDirectory
4131 and a ControlPortWriteToFile setting based on that directory. Fixes
4132 bug 3747; bugfix on Tor 0.2.2.26-beta.
4135 - Update to the August 2 2011 Maxmind GeoLite Country database.
4138 - Allow GETINFO fingerprint to return a fingerprint even when
4139 we have not yet built a router descriptor. Fixes bug 3577;
4140 bugfix on 0.2.0.1-alpha.
4141 - Write several files in text mode, on OSes that distinguish text
4142 mode from binary mode (namely, Windows). These files are:
4143 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4144 that collect those statistics; 'client_keys' and 'hostname' for
4145 hidden services that use authentication; and (in the tor-gencert
4146 utility) newly generated identity and signing keys. Previously,
4147 we wouldn't specify text mode or binary mode, leading to an
4148 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4149 the DirRecordUsageByCountry option which would have triggered
4150 the assertion failure was added), although this assertion failure
4151 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4152 - Selectively disable deprecation warnings on OS X because Lion
4153 started deprecating the shipped copy of openssl. Fixes bug 3643.
4154 - When unable to format an address as a string, report its value
4155 as "???" rather than reusing the last formatted address. Bugfix
4159 Changes in version 0.2.3.2-alpha - 2011-07-18
4160 Tor 0.2.3.2-alpha introduces two new experimental features:
4161 microdescriptors and pluggable transports. It also continues cleaning
4162 up a variety of recently introduced features.
4165 - Clients can now use microdescriptors instead of regular descriptors
4166 to build circuits. Microdescriptors are authority-generated
4167 summaries of regular descriptors' contents, designed to change
4168 very rarely (see proposal 158 for details). This feature is
4169 designed to save bandwidth, especially for clients on slow internet
4170 connections. It's off by default for now, since nearly no caches
4171 support it, but it will be on-by-default for clients in a future
4172 version. You can use the UseMicrodescriptors option to turn it on.
4173 - Tor clients using bridges can now be configured to use a separate
4174 'transport' proxy for each bridge. This approach helps to resist
4175 censorship by allowing bridges to use protocol obfuscation
4176 plugins. It implements part of proposal 180. Implements ticket 2841.
4177 - While we're trying to bootstrap, record how many TLS connections
4178 fail in each state, and report which states saw the most failures
4179 in response to any bootstrap failures. This feature may speed up
4180 diagnosis of censorship events. Implements ticket 3116.
4182 o Major bugfixes (on 0.2.3.1-alpha):
4183 - When configuring a large set of nodes in EntryNodes (as with
4184 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4185 random subset to be guards, and choose them in random
4186 order. Fixes bug 2798.
4187 - Tor could crash when remembering a consensus in a non-used consensus
4188 flavor without having a current consensus set. Fixes bug 3361.
4189 - Comparing an unknown address to a microdescriptor's shortened exit
4190 policy would always give a "rejected" result. Fixes bug 3599.
4191 - Using microdescriptors as a client no longer prevents Tor from
4192 uploading and downloading hidden service descriptors. Fixes
4196 - Allow nameservers with IPv6 address. Resolves bug 2574.
4197 - Accept attempts to include a password authenticator in the
4198 handshake, as supported by SOCKS5. This handles SOCKS clients that
4199 don't know how to omit a password when authenticating. Resolves
4201 - When configuring a large set of nodes in EntryNodes, and there are
4202 enough of them listed as Guard so that we don't need to consider
4203 the non-guard entries, prefer the ones listed with the Guard flag.
4204 - Check for and recover from inconsistency in the microdescriptor
4205 cache. This will make it harder for us to accidentally free a
4206 microdescriptor without removing it from the appropriate data
4207 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4208 - Log SSL state transitions at log level DEBUG, log domain
4209 HANDSHAKE. This can be useful for debugging censorship events.
4210 Implements ticket 3264.
4211 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4212 implements ticket 3439.
4214 o Minor bugfixes (on 0.2.3.1-alpha):
4215 - Do not free all general-purpose regular descriptors just
4216 because microdescriptor use is enabled. Fixes bug 3113.
4217 - Correctly link libevent_openssl when --enable-static-libevent
4218 is passed to configure. Fixes bug 3118.
4219 - Bridges should not complain during their heartbeat log messages that
4220 they are unlisted in the consensus: that's more or less the point
4221 of being a bridge. Fixes bug 3183.
4222 - Report a SIGNAL event to controllers when acting on a delayed
4223 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4224 event to the controller if we acted on a SIGNAL NEWNYM command
4225 immediately, and otherwise not report a SIGNAL event for the
4226 command at all. Fixes bug 3349.
4227 - Fix a crash when handling the SIGNAL controller command or
4228 reporting ERR-level status events with bufferevents enabled. Found
4229 by Robert Ransom. Fixes bug 3367.
4230 - Always ship the tor-fw-helper manpage in our release tarballs.
4231 Fixes bug 3389. Reported by Stephen Walker.
4232 - Fix a class of double-mark-for-close bugs when bufferevents
4233 are enabled. Fixes bug 3403.
4234 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4235 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4236 control-port command. Fixes part of bug 3465.
4237 - Prevent using negative indices during unit test runs when read_all()
4238 fails. Spotted by coverity.
4239 - Fix a rare memory leak when checking the nodelist without it being
4240 present. Found by coverity.
4241 - Only try to download a microdescriptor-flavored consensus from
4242 a directory cache that provides them.
4244 o Minor bugfixes (on 0.2.2.x and earlier):
4245 - Assert that hidden-service-related operations are not performed
4246 using single-hop circuits. Previously, Tor would assert that
4247 client-side streams are not attached to single-hop circuits,
4248 but not that other sensitive operations on the client and service
4249 side are not performed using single-hop circuits. Fixes bug 3332;
4251 - Don't publish a new relay descriptor when we reload our onion key,
4252 unless the onion key has actually changed. Fixes bug 3263 and
4253 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4254 - Allow GETINFO fingerprint to return a fingerprint even when
4255 we have not yet built a router descriptor. Fixes bug 3577;
4256 bugfix on 0.2.0.1-alpha.
4257 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4258 on 0.2.2.4-alpha; fixes bug 3427.
4260 o Code simplification and refactoring:
4261 - Use tor_sscanf() in place of scanf() in more places through the
4262 code. This makes us a little more locale-independent, and
4263 should help shut up code-analysis tools that can't tell
4264 a safe sscanf string from a dangerous one.
4265 - Use tt_assert(), not tor_assert(), for checking for test failures.
4266 This makes the unit tests more able to go on in the event that
4268 - Split connection_about_to_close() into separate functions for each
4272 - On Windows, we now define the _WIN32_WINNT macros only if they
4273 are not already defined. This lets the person building Tor decide,
4274 if they want, to require a later version of Windows.
4277 Changes in version 0.2.2.30-rc - 2011-07-07
4278 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4279 series. It fixes a few smaller bugs, but generally appears stable.
4280 Please test it and let us know whether it is!
4283 - Send a SUCCEEDED stream event to the controller when a reverse
4284 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4285 discovered by katmagic.
4286 - Always NUL-terminate the sun_path field of a sockaddr_un before
4287 passing it to the kernel. (Not a security issue: kernels are
4288 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4289 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4290 - Don't stack-allocate the list of supplementary GIDs when we're
4291 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4292 could take up to 256K, which is way too much stack. Found by
4293 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4294 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4295 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4296 fixes part of bug 3465.
4297 - Fix a memory leak when receiving a descriptor for a hidden
4298 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4302 - Update to the July 1 2011 Maxmind GeoLite Country database.
4305 Changes in version 0.2.2.29-beta - 2011-06-20
4306 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4307 have bridge lines in their torrc but don't want to use them; gets
4308 us closer to having the control socket feature working on Debian;
4309 and fixes a variety of smaller bugs.
4312 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4313 When we changed the default behavior to "use bridges if any
4314 are listed in the torrc", we surprised users who had bridges
4315 in their torrc files but who didn't actually want to use them.
4316 Partial resolution for bug 3354.
4319 - Don't attach new streams to old rendezvous circuits after SIGNAL
4320 NEWNYM. Previously, we would keep using an existing rendezvous
4321 circuit if it remained open (i.e. if it were kept open by a
4322 long-lived stream, or if a new stream were attached to it before
4323 Tor could notice that it was old and no longer in use). Bugfix on
4324 0.1.1.15-rc; fixes bug 3375.
4327 - Fix a bug when using ControlSocketsGroupWritable with User. The
4328 directory's group would be checked against the current group, not
4329 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4330 bugfix on 0.2.2.26-beta.
4331 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4332 expect it to emit a CRLF iff the format string ends with CRLF;
4333 it actually emitted a CRLF iff (a) the format string ended with
4334 CRLF or (b) the resulting string was over 1023 characters long or
4335 (c) the format string did not end with CRLF *and* the resulting
4336 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4337 fixes part of bug 3407.
4338 - Make send_control_event_impl()'s behaviour sane. Its callers
4339 expect it to always emit a CRLF at the end of the string; it
4340 might have emitted extra control characters as well. Bugfix on
4341 0.1.1.9-alpha; fixes another part of bug 3407.
4342 - Make crypto_rand_int() check the value of its input correctly.
4343 Previously, it accepted values up to UINT_MAX, but could return a
4344 negative number if given a value above INT_MAX+1. Found by George
4345 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4346 - Avoid a segfault when reading a malformed circuit build state
4347 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4349 - When asked about a DNS record type we don't support via a
4350 client DNSPort, reply with NOTIMPL rather than an empty
4351 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4352 - Fix a rare memory leak during stats writing. Found by coverity.
4355 - Update to the June 1 2011 Maxmind GeoLite Country database.
4357 o Code simplifications and refactoring:
4358 - Remove some dead code as indicated by coverity.
4359 - Remove a few dead assignments during router parsing. Found by
4361 - Add some forgotten return value checks during unit tests. Found
4363 - Don't use 1-bit wide signed bit fields. Found by coverity.
4366 Changes in version 0.2.2.28-beta - 2011-06-04
4367 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4368 fixed a big bug in whether relays stay in the consensus consistently,
4369 we moved closer to handling bridges and hidden services correctly,
4370 and we started the process of better handling the dreaded "my Vidalia
4371 died, and now my Tor demands a password when I try to reconnect to it"
4375 - Don't decide to make a new descriptor when receiving a HUP signal.
4376 This bug has caused a lot of 0.2.2.x relays to disappear from the
4377 consensus periodically. Fixes the most common case of triggering
4378 bug 1810; bugfix on 0.2.2.7-alpha.
4379 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4380 - Don't try to build descriptors if "ORPort auto" is set and we
4381 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4383 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4384 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4385 - Apply circuit timeouts to opened hidden-service-related circuits
4386 based on the correct start time. Previously, we would apply the
4387 circuit build timeout based on time since the circuit's creation;
4388 it was supposed to be applied based on time since the circuit
4389 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4390 - Use the same circuit timeout for client-side introduction
4391 circuits as for other four-hop circuits, rather than the timeout
4392 for single-hop directory-fetch circuits; the shorter timeout may
4393 have been appropriate with the static circuit build timeout in
4394 0.2.1.x and earlier, but caused many hidden service access attempts
4395 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4396 on 0.2.2.2-alpha; fixes another part of bug 1297.
4397 - In ticket 2511 we fixed a case where you could use an unconfigured
4398 bridge if you had configured it as a bridge the last time you ran
4399 Tor. Now fix another edge case: if you had configured it as a bridge
4400 but then switched to a different bridge via the controller, you
4401 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4405 - Add an __OwningControllerProcess configuration option and a
4406 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4407 that when it exits, Tor will shut down. Implements feature 3049.
4408 - If "UseBridges 1" is set and no bridges are configured, Tor will
4409 now refuse to build any circuits until some bridges are set.
4410 If "UseBridges auto" is set, Tor will use bridges if they are
4411 configured and we are not running as a server, but otherwise will
4412 make circuits as usual. The new default is "auto". Patch by anonym,
4413 so the Tails LiveCD can stop automatically revealing you as a Tor
4417 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4418 - Remove a trailing asterisk from "exit-policy/default" in the
4419 output of the control port command "GETINFO info/names". Bugfix
4421 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4423 - Warn when the user configures two HiddenServiceDir lines that point
4424 to the same directory. Bugfix on 0.0.6 (the version introducing
4425 HiddenServiceDir); fixes bug 3289.
4426 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4427 part of bug 2748; bugfix on 0.2.0.10-alpha.
4428 - Log malformed requests for rendezvous descriptors as protocol
4429 warnings, not warnings. Also, use a more informative log message
4430 in case someone sees it at log level warning without prior
4431 info-level messages. Fixes the other part of bug 2748; bugfix
4433 - Clear the table recording the time of the last request for each
4434 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4435 Previously, we would clear our HS descriptor cache on SIGNAL
4436 NEWNYM, but if we had previously retrieved a descriptor (or tried
4437 to) from every directory responsible for it, we would refuse to
4438 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4440 - Fix a log message that said "bits" while displaying a value in
4441 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4443 - When checking for 1024-bit keys, check for 1024 bits, not 128
4444 bytes. This allows Tor to correctly discard keys of length 1017
4445 through 1023. Bugfix on 0.0.9pre5.
4448 - Relays now log the reason for publishing a new relay descriptor,
4449 so we have a better chance of hunting down instances of bug 1810.
4450 Resolves ticket 3252.
4451 - Revise most log messages that refer to nodes by nickname to
4452 instead use the "$key=nickname at address" format. This should be
4453 more useful, especially since nicknames are less and less likely
4454 to be unique. Resolves ticket 3045.
4455 - Log (at info level) when purging pieces of hidden-service-client
4456 state because of SIGNAL NEWNYM.
4459 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4460 anything since 0.2.1.16-rc.
4463 Changes in version 0.2.2.27-beta - 2011-05-18
4464 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4465 release, and also adds a few more general bugfixes.
4468 - Fix a crash bug when changing bridges in a running Tor process.
4469 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4470 - When the controller configures a new bridge, don't wait 10 to 60
4471 seconds before trying to fetch its descriptor. Bugfix on
4472 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4475 - Require that onion keys have exponent 65537 in microdescriptors too.
4476 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4477 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4478 Changed the limit to 512 characters by removing base64 newlines.
4479 Fixes bug 2752. Fix by Michael Yakubovich.
4480 - When a client starts or stops using bridges, never use a circuit
4481 that was built before the configuration change. This behavior could
4482 put at risk a user who uses bridges to ensure that her traffic
4483 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4487 Changes in version 0.2.2.26-beta - 2011-05-17
4488 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4489 also introduces a new "socksport auto" approach that should make it
4490 easier to run multiple Tors on the same system, and does a lot of
4491 cleanup to get us closer to a release candidate.
4493 o Security/privacy fixes:
4494 - Replace all potentially sensitive memory comparison operations
4495 with versions whose runtime does not depend on the data being
4496 compared. This will help resist a class of attacks where an
4497 adversary can use variations in timing information to learn
4498 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4499 implementation by Robert Ransom based partially on code by DJB.)
4500 - When receiving a hidden service descriptor, check that it is for
4501 the hidden service we wanted. Previously, Tor would store any
4502 hidden service descriptors that a directory gave it, whether it
4503 wanted them or not. This wouldn't have let an attacker impersonate
4504 a hidden service, but it did let directories pre-seed a client
4505 with descriptors that it didn't want. Bugfix on 0.0.6.
4506 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4507 DNS cache entries, and virtual address mappings: that's what
4508 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4511 - The options SocksPort, ControlPort, and so on now all accept a
4512 value "auto" that opens a socket on an OS-selected port. A
4513 new ControlPortWriteToFile option tells Tor to write its
4514 actual control port or ports to a chosen file. If the option
4515 ControlPortFileGroupReadable is set, the file is created as
4516 group-readable. Now users can run two Tor clients on the same
4517 system without needing to manually mess with parameters. Resolves
4518 part of ticket 3076.
4519 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4520 help busy exit nodes avoid running out of useable ports just
4521 because all the ports have been used in the near past. Resolves
4525 - New "GETINFO net/listeners/(type)" controller command to return
4526 a list of addresses and ports that are bound for listeners for a
4527 given connection type. This is useful when the user has configured
4528 "SocksPort auto" and the controller needs to know which port got
4529 chosen. Resolves another part of ticket 3076.
4530 - Add a new ControlSocketsGroupWritable configuration option: when
4531 it is turned on, ControlSockets are group-writeable by the default
4532 group of the current user. Patch by Jérémy Bobbio; implements
4534 - Tor now refuses to create a ControlSocket in a directory that is
4535 world-readable (or group-readable if ControlSocketsGroupWritable
4536 is 0). This is necessary because some operating systems do not
4537 enforce permissions on an AF_UNIX sockets. Permissions on the
4538 directory holding the socket, however, seems to work everywhere.
4539 - Rate-limit a warning about failures to download v2 networkstatus
4540 documents. Resolves part of bug 1352.
4541 - Backport code from 0.2.3.x that allows directory authorities to
4542 clean their microdescriptor caches. Needed to resolve bug 2230.
4543 - When an HTTPS proxy reports "403 Forbidden", we now explain
4544 what it means rather than calling it an unexpected status code.
4545 Closes bug 2503. Patch from Michael Yakubovich.
4546 - Update to the May 1 2011 Maxmind GeoLite Country database.
4549 - Authorities now clean their microdesc cache periodically and when
4550 reading from disk initially, not only when adding new descriptors.
4551 This prevents a bug where we could lose microdescriptors. Bugfix
4552 on 0.2.2.6-alpha. Fixes bug 2230.
4553 - Do not crash when our configuration file becomes unreadable, for
4554 example due to a permissions change, between when we start up
4555 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4557 - Avoid a bug that would keep us from replacing a microdescriptor
4558 cache on Windows. (We would try to replace the file while still
4559 holding it open. That's fine on Unix, but Windows doesn't let us
4560 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4561 - Add missing explanations for the authority-related torrc options
4562 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4563 man page. Resolves issue 2379.
4564 - As an authority, do not upload our own vote or signature set to
4565 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4566 it would get flagged as a duplicate. Resolves bug 3026.
4567 - Accept hidden service descriptors if we think we might be a hidden
4568 service directory, regardless of what our consensus says. This
4569 helps robustness, since clients and hidden services can sometimes
4570 have a more up-to-date view of the network consensus than we do,
4571 and if they think that the directory authorities list us a HSDir,
4572 we might actually be one. Related to bug 2732; bugfix on
4574 - When a controller changes TrackHostExits, remove mappings for
4575 hosts that should no longer have their exits tracked. Bugfix on
4577 - When a controller changes VirtualAddrNetwork, remove any mappings
4578 for hosts that were automapped to the old network. Bugfix on
4580 - When a controller changes one of the AutomapHosts* options, remove
4581 any mappings for hosts that should no longer be automapped. Bugfix
4583 - Do not reset the bridge descriptor download status every time we
4584 re-parse our configuration or get a configuration change. Fixes
4585 bug 3019; bugfix on 0.2.0.3-alpha.
4587 o Minor bugfixes (code cleanup):
4588 - When loading the microdesc journal, remember its current size.
4589 In 0.2.2, this helps prevent the microdesc journal from growing
4590 without limit on authorities (who are the only ones to use it in
4591 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4592 Fix posted by "cypherpunks."
4593 - The microdesc journal is supposed to get rebuilt only if it is
4594 at least _half_ the length of the store, not _twice_ the length
4595 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4596 - Fix a potential null-pointer dereference while computing a
4597 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4599 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4600 cache without actually having any descriptors to cache. Bugfix on
4601 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4602 - If we fail to compute the identity digest of a v3 legacy keypair,
4603 warn, and don't use a buffer-full of junk instead. Bugfix on
4604 0.2.1.1-alpha; fixes bug 3106.
4605 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4606 where if the function had ever in the future been used to check
4607 for the presence of a too-large number, it would have given an
4608 incorrect result. (Fortunately, we only used it for 16-bit
4609 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4610 - Require that introduction point keys and onion handshake keys
4611 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4615 - Caches no longer download and serve v2 networkstatus documents
4616 unless FetchV2Networkstatus flag is set: these documents haven't
4617 haven't been used by clients or relays since 0.2.0.x. Resolves
4621 Changes in version 0.2.3.1-alpha - 2011-05-05
4622 Tor 0.2.3.1-alpha adds some new experimental features, including support
4623 for an improved network IO backend, IOCP networking on Windows,
4624 microdescriptor caching, "fast-start" support for streams, and automatic
4625 home router configuration. There are also numerous internal improvements
4626 to try to make the code easier for developers to work with.
4628 This is the first alpha release in a new series, so expect there to be
4629 bugs. Users who would rather test out a more stable branch should
4630 stay with 0.2.2.x for now.
4633 - Tor can now optionally build with the "bufferevents" buffered IO
4634 backend provided by Libevent 2. To use this feature, make sure you
4635 have the latest possible version of Libevent, and pass the
4636 --enable-bufferevents flag to configure when building Tor from
4637 source. This feature will make our networking code more flexible,
4638 let us stack layers on each other, and let us use more efficient
4639 zero-copy transports where available.
4640 - As an experimental feature, Tor can use IOCP for networking on Windows.
4641 Once this code is tuned and optimized, it promises much better
4642 performance than the select-based backend we've used in the past. To
4643 try this feature, you must build Tor with Libevent 2, configure Tor
4644 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4645 your torrc. There are known bugs here: only try this if you can help
4646 debug it as it breaks.
4647 - The EntryNodes option can now include country codes like {de} or IP
4648 addresses or network masks. Previously we had disallowed these options
4649 because we didn't have an efficient way to keep the list up to
4650 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4651 - Exit nodes now accept and queue data on not-yet-connected streams.
4652 Previously, the client wasn't allowed to send data until the stream was
4653 connected, which slowed down all connections. This change will enable
4654 clients to perform a "fast-start" on streams and send data without
4655 having to wait for a confirmation that the stream has opened. (Patch
4656 from Ian Goldberg; implements the server side of Proposal 174.)
4657 - Tor now has initial support for automatic port mapping on the many
4658 home routers that support NAT-PMP or UPnP. (Not yet supported on
4659 Windows). To build the support code, you'll need to have libnatpnp
4660 library and/or the libminiupnpc library, and you'll need to enable the
4661 feature specifically by passing "--enable-upnp" and/or
4662 "--enable-natpnp" to configure. To turn it on, use the new
4663 PortForwarding option.
4664 - Caches now download, cache, and serve multiple "flavors" of the
4665 consensus, including a flavor that describes microdescriptors.
4666 - Caches now download, cache, and serve microdescriptors -- small
4667 summaries of router descriptors that are authenticated by all of the
4668 directory authorities. Once enough caches are running this code,
4669 clients will be able to save significant amounts of directory bandwidth
4670 by downloading microdescriptors instead of router descriptors.
4673 - Make logging resolution configurable with a new LogTimeGranularity
4674 option, and change the default from 1 millisecond to 1 second.
4675 Implements enhancement 1668.
4676 - We log which torrc file we're using on startup. Implements ticket
4678 - Ordinarily, Tor does not count traffic from private addresses (like
4679 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4680 There is now a new option, CountPrivateBandwidth, to disable this
4681 behavior. Patch from Daniel Cagara.
4682 - New --enable-static-tor configure option for building Tor as
4683 statically as possible. Idea, general hackery and thoughts from
4684 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4686 - If you set the NumCPUs option to 0, Tor will now try to detect how
4687 many CPUs you have. This is the new default behavior.
4688 - Turn on directory request statistics by default and include them in
4689 extra-info descriptors. Don't break if we have no GeoIP database.
4690 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4691 bidirectional use of connections to disk every 24 hours.
4692 - Add a GeoIP file digest to the extra-info descriptor. Implements
4694 - The NodeFamily option -- which let you declare that you want to
4695 consider nodes to be part of a family whether they list themselves
4696 that way or not -- now allows IP address ranges and country codes.
4697 - Add a new 'Heartbeat' log message type to periodically log a message
4698 describing Tor's status at level Notice. This feature is meant for
4699 operators who log at notice, and want to make sure that their Tor
4700 server is still working. Implementation by George Kadianakis.
4702 o Minor bugfixes (on 0.2.2.25-alpha):
4703 - When loading the microdesc journal, remember its current size.
4704 In 0.2.2, this helps prevent the microdesc journal from growing
4705 without limit on authorities (who are the only ones to use it in
4706 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4707 Fix posted by "cypherpunks."
4708 - The microdesc journal is supposed to get rebuilt only if it is
4709 at least _half_ the length of the store, not _twice_ the length
4710 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4711 - If as an authority we fail to compute the identity digest of a v3
4712 legacy keypair, warn, and don't use a buffer-full of junk instead.
4713 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
4714 - Authorities now clean their microdesc cache periodically and when
4715 reading from disk initially, not only when adding new descriptors.
4716 This prevents a bug where we could lose microdescriptors. Bugfix
4719 o Minor features (controller):
4720 - Add a new SIGNAL event to the controller interface so that
4721 controllers can be notified when Tor handles a signal. Resolves
4722 issue 1955. Patch by John Brooks.
4723 - Add a new GETINFO option to get total bytes read and written. Patch
4724 from pipe, revised by atagar. Resolves ticket 2345.
4725 - Implement some GETINFO controller fields to provide information about
4726 the Tor process's pid, euid, username, and resource limits.
4729 - Our build system requires automake 1.6 or later to create the
4730 Makefile.in files. Previously, you could have used 1.4.
4731 This only affects developers and people building Tor from git;
4732 people who build Tor from the source distribution without changing
4733 the Makefile.am files should be fine.
4734 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
4735 so on. This is more robust against some of the failure modes
4736 associated with running the autotools pieces on their own.
4738 o Minor packaging issues:
4739 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
4740 already created. Patch from Andreas Stieger. Fixes bug 2573.
4742 o Code simplifications and refactoring:
4743 - A major revision to our internal node-selecting and listing logic.
4744 Tor already had at least two major ways to look at the question of
4745 "which Tor servers do we know about": a list of router descriptors,
4746 and a list of entries in the current consensus. With
4747 microdescriptors, we're adding a third. Having so many systems
4748 without an abstraction layer over them was hurting the codebase.
4749 Now, we have a new "node_t" abstraction that presents a consistent
4750 interface to a client's view of a Tor node, and holds (nearly) all
4751 of the mutable state formerly in routerinfo_t and routerstatus_t.
4752 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
4753 no longer link against Libevent: they never used it, but
4754 our library structure used to force them to link it.
4757 - Remove some old code to work around even older versions of Tor that
4758 used forked processes to handle DNS requests. Such versions of Tor
4759 are no longer in use as servers.
4761 o Documentation fixes:
4762 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
4763 - Add missing documentation for the authority-related torrc options
4764 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
4768 Changes in version 0.2.2.25-alpha - 2011-04-29
4769 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
4770 robust, routers no longer overreport their bandwidth, Win7 should crash
4771 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
4772 now prevents hidden service-related activity from being linkable. It
4773 provides more information to Vidalia so you can see if your bridge is
4774 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
4775 StrictNodes configuration options to make them more reliable, more
4776 understandable, and more regularly applied. If you use those options,
4777 please see the revised documentation for them in the manual page.
4780 - Relays were publishing grossly inflated bandwidth values because
4781 they were writing their state files wrong--now they write the
4782 correct value. Also, resume reading bandwidth history from the
4783 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
4784 - Improve hidden service robustness: When we find that we have
4785 extended a hidden service's introduction circuit to a relay not
4786 listed as an introduction point in the HS descriptor we currently
4787 have, retry with an introduction point from the current
4788 descriptor. Previously we would just give up. Fixes bugs 1024 and
4789 1930; bugfix on 0.2.0.10-alpha.
4790 - Clients now stop trying to use an exit node associated with a given
4791 destination by TrackHostExits if they fail to reach that exit node.
4792 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4793 - Fix crash bug on platforms where gmtime and localtime can return
4794 NULL. Windows 7 users were running into this one. Fixes part of bug
4795 2077. Bugfix on all versions of Tor. Found by boboper.
4797 o Security and stability fixes:
4798 - Don't double-free a parsable, but invalid, microdescriptor, even if
4799 it is followed in the blob we're parsing by an unparsable
4800 microdescriptor. Fixes an issue reported in a comment on bug 2954.
4801 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
4802 - If the Nickname configuration option isn't given, Tor would pick a
4803 nickname based on the local hostname as the nickname for a relay.
4804 Because nicknames are not very important in today's Tor and the
4805 "Unnamed" nickname has been implemented, this is now problematic
4806 behavior: It leaks information about the hostname without being
4807 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4808 introduced the Unnamed nickname. Reported by tagnaq.
4809 - Fix an uncommon assertion failure when running with DNSPort under
4810 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4811 - Avoid linkability based on cached hidden service descriptors: forget
4812 all hidden service descriptors cached as a client when processing a
4813 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4816 - Export GeoIP information on bridge usage to controllers even if we
4817 have not yet been running for 24 hours. Now Vidalia bridge operators
4818 can get more accurate and immediate feedback about their
4819 contributions to the network.
4821 o Major features and bugfixes (node selection):
4822 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4823 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
4824 options. Previously, we had been ambiguous in describing what
4825 counted as an "exit" node, and what operations exactly "StrictNodes
4826 0" would permit. This created confusion when people saw nodes built
4827 through unexpected circuits, and made it hard to tell real bugs from
4828 surprises. Now the intended behavior is:
4829 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4830 a node that delivers user traffic outside the Tor network.
4831 . "Entry", in the context of EntryNodes, means a node used as the
4832 first hop of a multihop circuit. It doesn't include direct
4833 connections to directory servers.
4834 . "ExcludeNodes" applies to all nodes.
4835 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4836 StrictNodes is set, Tor should avoid all nodes listed in
4837 ExcludeNodes, even when it will make user requests fail. When
4838 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4839 whenever it can, except when it must use an excluded node to
4840 perform self-tests, connect to a hidden service, provide a
4841 hidden service, fulfill a .exit request, upload directory
4842 information, or fetch directory information.
4843 Collectively, the changes to implement the behavior fix bug 1090.
4844 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4845 a node is listed in both, it's treated as excluded.
4846 - ExcludeNodes now applies to directory nodes -- as a preference if
4847 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4848 Don't exclude all the directory authorities and set StrictNodes to 1
4849 unless you really want your Tor to break.
4850 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4851 - ExcludeExitNodes now overrides .exit requests.
4852 - We don't use bridges listed in ExcludeNodes.
4853 - When StrictNodes is 1:
4854 . We now apply ExcludeNodes to hidden service introduction points
4855 and to rendezvous points selected by hidden service users. This
4856 can make your hidden service less reliable: use it with caution!
4857 . If we have used ExcludeNodes on ourself, do not try relay
4858 reachability self-tests.
4859 . If we have excluded all the directory authorities, we will not
4860 even try to upload our descriptor if we're a relay.
4861 . Do not honor .exit requests to an excluded node.
4862 - Remove a misfeature that caused us to ignore the Fast/Stable flags
4863 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
4864 - When the set of permitted nodes changes, we now remove any mappings
4865 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
4867 - We never cannibalize a circuit that had excluded nodes on it, even
4868 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
4869 - Revert a change where we would be laxer about attaching streams to
4870 circuits than when building the circuits. This was meant to prevent
4871 a set of bugs where streams were never attachable, but our improved
4872 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
4873 - Keep track of how many times we launch a new circuit to handle a
4874 given stream. Too many launches could indicate an inconsistency
4875 between our "launch a circuit to handle this stream" logic and our
4876 "attach this stream to one of the available circuits" logic.
4877 - Improve log messages related to excluded nodes.
4880 - Fix a spurious warning when moving from a short month to a long
4881 month on relays with month-based BandwidthAccounting. Bugfix on
4882 0.2.2.17-alpha; fixes bug 3020.
4883 - When a client finds that an origin circuit has run out of 16-bit
4884 stream IDs, we now mark it as unusable for new streams. Previously,
4885 we would try to close the entire circuit. Bugfix on 0.0.6.
4886 - Add a forgotten cast that caused a compile warning on OS X 10.6.
4887 Bugfix on 0.2.2.24-alpha.
4888 - Be more careful about reporting the correct error from a failed
4889 connect() system call. Under some circumstances, it was possible to
4890 look at an incorrect value for errno when sending the end reason.
4891 Bugfix on 0.1.0.1-rc.
4892 - Correctly handle an "impossible" overflow cases in connection byte
4893 counting, where we write or read more than 4GB on an edge connection
4894 in a single second. Bugfix on 0.1.2.8-beta.
4895 - Correct the warning displayed when a rendezvous descriptor exceeds
4896 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4898 - Clients and hidden services now use HSDir-flagged relays for hidden
4899 service descriptor downloads and uploads even if the relays have no
4900 DirPort set and the client has disabled TunnelDirConns. This will
4901 eventually allow us to give the HSDir flag to relays with no
4902 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
4903 - Downgrade "no current certificates known for authority" message from
4904 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
4905 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
4906 2917. Bugfix on 0.1.1.1-alpha.
4907 - Only limit the lengths of single HS descriptors, even when multiple
4908 HS descriptors are published to an HSDir relay in a single POST
4909 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
4910 - Write the current time into the LastWritten line in our state file,
4911 rather than the time from the previous write attempt. Also, stop
4912 trying to use a time of -1 in our log statements. Fixes bug 3039;
4913 bugfix on 0.2.2.14-alpha.
4914 - Be more consistent in our treatment of file system paths. "~" should
4915 get expanded to the user's home directory in the Log config option.
4916 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
4917 feature for the -f and --DataDirectory options.
4920 - Make sure every relay writes a state file at least every 12 hours.
4921 Previously, a relay could go for weeks without writing its state
4922 file, and on a crash could lose its bandwidth history, capacity
4923 estimates, client country statistics, and so on. Addresses bug 3012.
4924 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
4925 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
4926 clients are already deprecated because of security bugs.
4927 - Don't allow v0 hidden service authorities to act as clients.
4928 Required by fix for bug 3000.
4929 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
4930 by fix for bug 3000.
4931 - Ensure that no empty [dirreq-](read|write)-history lines are added
4932 to an extrainfo document. Implements ticket 2497.
4934 o Code simplification and refactoring:
4935 - Remove workaround code to handle directory responses from servers
4936 that had bug 539 (they would send HTTP status 503 responses _and_
4937 send a body too). Since only server versions before
4938 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
4939 keep the workaround in place.
4940 - Remove the old 'fuzzy time' logic. It was supposed to be used for
4941 handling calculations where we have a known amount of clock skew and
4942 an allowed amount of unknown skew. But we only used it in three
4943 places, and we never adjusted the known/unknown skew values. This is
4944 still something we might want to do someday, but if we do, we'll
4945 want to do it differently.
4946 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4947 None of the cases where we did this before were wrong, but by making
4948 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4949 - Use GetTempDir to find the proper temporary directory location on
4950 Windows when generating temporary files for the unit tests. Patch by
4954 Changes in version 0.2.2.24-alpha - 2011-04-08
4955 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
4956 prevented Tor clients from effectively using "multihomed" bridges,
4957 that is, bridges that listen on multiple ports or IP addresses so users
4958 can continue to use some of their addresses even if others get blocked.
4961 - Fix a bug where bridge users who configure the non-canonical
4962 address of a bridge automatically switch to its canonical
4963 address. If a bridge listens at more than one address, it should be
4964 able to advertise those addresses independently and any non-blocked
4965 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
4967 - If you configured Tor to use bridge A, and then quit and
4968 configured Tor to use bridge B instead, it would happily continue
4969 to use bridge A if it's still reachable. While this behavior is
4970 a feature if your goal is connectivity, in some scenarios it's a
4971 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
4972 - Directory authorities now use data collected from their own
4973 uptime observations when choosing whether to assign the HSDir flag
4974 to relays, instead of trusting the uptime value the relay reports in
4975 its descriptor. This change helps prevent an attack where a small
4976 set of nodes with frequently-changing identity keys can blackhole
4977 a hidden service. (Only authorities need upgrade; others will be
4978 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
4981 - When we restart our relay, we might get a successful connection
4982 from the outside before we've started our reachability tests,
4983 triggering a warning: "ORPort found reachable, but I have no
4984 routerinfo yet. Failing to inform controller of success." This
4985 bug was harmless unless Tor is running under a controller
4986 like Vidalia, in which case the controller would never get a
4987 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4989 - Make directory authorities more accurate at recording when
4990 relays that have failed several reachability tests became
4991 unreachable, so we can provide more accuracy at assigning Stable,
4992 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
4993 - Fix an issue that prevented static linking of libevent on
4994 some platforms (notably Linux). Fixes bug 2698; bugfix on
4995 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
4996 the --with-static-libevent configure option).
4997 - We now ask the other side of a stream (the client or the exit)
4998 for more data on that stream when the amount of queued data on
4999 that stream dips low enough. Previously, we wouldn't ask the
5000 other side for more data until either it sent us more data (which
5001 it wasn't supposed to do if it had exhausted its window!) or we
5002 had completely flushed all our queued data. This flow control fix
5003 should improve throughput. Fixes bug 2756; bugfix on the earliest
5004 released versions of Tor (svn commit r152).
5005 - Avoid a double-mark-for-free warning when failing to attach a
5006 transparent proxy connection. (We thought we had fixed this in
5007 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5008 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5009 bug) and 0.2.2.23-alpha (the incorrect fix).
5010 - When warning about missing zlib development packages during compile,
5011 give the correct package names. Bugfix on 0.2.0.1-alpha.
5014 - Directory authorities now log the source of a rejected POSTed v3
5016 - Make compilation with clang possible when using
5017 --enable-gcc-warnings by removing two warning options that clang
5018 hasn't implemented yet and by fixing a few warnings. Implements
5020 - When expiring circuits, use microsecond timers rather than
5021 one-second timers. This can avoid an unpleasant situation where a
5022 circuit is launched near the end of one second and expired right
5023 near the beginning of the next, and prevent fluctuations in circuit
5025 - Use computed circuit-build timeouts to decide when to launch
5026 parallel introduction circuits for hidden services. (Previously,
5027 we would retry after 15 seconds.)
5028 - Update to the April 1 2011 Maxmind GeoLite Country database.
5031 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5032 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5034 o Documentation changes:
5035 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5036 - Resolve all doxygen warnings except those for missing documentation.
5038 - Add doxygen documentation for more functions, fields, and types.
5041 Changes in version 0.2.2.23-alpha - 2011-03-08
5042 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5043 they restart they don't lose their bandwidth capacity estimate. This
5044 release also fixes a diverse set of user-facing bugs, ranging from
5045 relays overrunning their rate limiting to clients falsely warning about
5046 clock skew to bridge descriptor leaks by our bridge directory authority.
5049 - Stop sending a CLOCK_SKEW controller status event whenever
5050 we fetch directory information from a relay that has a wrong clock.
5051 Instead, only inform the controller when it's a trusted authority
5052 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5053 the rest of bug 1074.
5054 - Fix an assert in parsing router descriptors containing IPv6
5055 addresses. This one took down the directory authorities when
5056 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5057 - Make the bridge directory authority refuse to answer directory
5058 requests for "all" descriptors. It used to include bridge
5059 descriptors in its answer, which was a major information leak.
5060 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5061 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5062 Tor would ignore their RelayBandwidthBurst setting,
5063 potentially using more bandwidth than expected. Bugfix on
5064 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5065 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5066 hidserv" in her torrc. The 'hidserv' argument never controlled
5067 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5070 - Relays now save observed peak bandwidth throughput rates to their
5071 state file (along with total usage, which was already saved)
5072 so that they can determine their correct estimated bandwidth on
5073 restart. Resolves bug 1863, where Tor relays would reset their
5074 estimated bandwidth to 0 after restarting.
5075 - Directory authorities now take changes in router IP address and
5076 ORPort into account when determining router stability. Previously,
5077 if a router changed its IP or ORPort, the authorities would not
5078 treat it as having any downtime for the purposes of stability
5079 calculation, whereas clients would experience downtime since the
5080 change could take a while to propagate to them. Resolves issue 1035.
5081 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5082 Prevention (DEP) by default on Windows to make it harder for
5083 attackers to exploit vulnerabilities. Patch from John Brooks.
5085 o Minor bugfixes (on 0.2.1.x and earlier):
5086 - Fix a rare crash bug that could occur when a client was configured
5087 with a large number of bridges. Fixes bug 2629; bugfix on
5088 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5089 - Avoid a double mark-for-free warning when failing to attach a
5090 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5092 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5093 found by "cypherpunks". This bug was introduced before the first
5094 Tor release, in svn commit r110.
5095 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5096 don't mention them in the manpage. Fixes bug 2450; issue
5097 spotted by keb and G-Lo.
5098 - Fix a bug in bandwidth history state parsing that could have been
5099 triggered if a future version of Tor ever changed the timing
5100 granularity at which bandwidth history is measured. Bugfix on
5102 - When a relay decides that its DNS is too broken for it to serve
5103 as an exit server, it advertised itself as a non-exit, but
5104 continued to act as an exit. This could create accidental
5105 partitioning opportunities for users. Instead, if a relay is
5106 going to advertise reject *:* as its exit policy, it should
5107 really act with exit policy "reject *:*". Fixes bug 2366.
5108 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5109 - In the special case where you configure a public exit relay as your
5110 bridge, Tor would be willing to use that exit relay as the last
5111 hop in your circuit as well. Now we fail that circuit instead.
5112 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5113 - Fix a bug with our locking implementation on Windows that couldn't
5114 correctly detect when a file was already locked. Fixes bug 2504,
5115 bugfix on 0.2.1.6-alpha.
5116 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5117 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5119 - Set target port in get_interface_address6() correctly. Bugfix
5120 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5121 - Directory authorities are now more robust to hops back in time
5122 when calculating router stability. Previously, if a run of uptime
5123 or downtime appeared to be negative, the calculation could give
5124 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5126 - Fix an assert that got triggered when using the TestingTorNetwork
5127 configuration option and then issuing a GETINFO config-text control
5128 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5130 o Minor bugfixes (on 0.2.2.x):
5131 - Clients should not weight BadExit nodes as Exits in their node
5132 selection. Similarly, directory authorities should not count BadExit
5133 bandwidth as Exit bandwidth when computing bandwidth-weights.
5134 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5135 - Correctly clear our dir_read/dir_write history when there is an
5136 error parsing any bw history value from the state file. Bugfix on
5138 - Resolve a bug in verifying signatures of directory objects
5139 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5140 Fixes bug 2409. Found by "piebeer".
5141 - Bridge authorities no longer crash on SIGHUP when they try to
5142 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5146 - Log less aggressively about circuit timeout changes, and improve
5147 some other circuit timeout messages. Resolves bug 2004.
5148 - Log a little more clearly about the times at which we're no longer
5149 accepting new connections. Resolves bug 2181.
5150 - Reject attempts at the client side to open connections to private
5151 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5152 a randomly chosen exit node. Attempts to do so are always
5153 ill-defined, generally prevented by exit policies, and usually
5154 in error. This will also help to detect loops in transparent
5155 proxy configurations. You can disable this feature by setting
5156 "ClientRejectInternalAddresses 0" in your torrc.
5157 - Always treat failure to allocate an RSA key as an unrecoverable
5159 - Update to the March 1 2011 Maxmind GeoLite Country database.
5161 o Minor features (log subsystem):
5162 - Add documentation for configuring logging at different severities in
5163 different log domains. We've had this feature since 0.2.1.1-alpha,
5164 but for some reason it never made it into the manpage. Fixes
5166 - Make it simpler to specify "All log domains except for A and B".
5167 Previously you needed to say "[*,~A,~B]". Now you can just say
5169 - Add a "LogMessageDomains 1" option to include the domains of log
5170 messages along with the messages. Without this, there's no way
5171 to use log domains without reading the source or doing a lot
5174 o Packaging changes:
5175 - Stop shipping the Tor specs files and development proposal documents
5176 in the tarball. They are now in a separate git repository at
5177 git://git.torproject.org/torspec.git
5180 Changes in version 0.2.1.30 - 2011-02-23
5181 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5182 change is a slight tweak to Tor's TLS handshake that makes relays
5183 and bridges that run this new version reachable from Iran again.
5184 We don't expect this tweak will win the arms race long-term, but it
5185 buys us time until we roll out a better solution.
5188 - Stop sending a CLOCK_SKEW controller status event whenever
5189 we fetch directory information from a relay that has a wrong clock.
5190 Instead, only inform the controller when it's a trusted authority
5191 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5192 the rest of bug 1074.
5193 - Fix a bounds-checking error that could allow an attacker to
5194 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5196 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5197 Tor would ignore their RelayBandwidthBurst setting,
5198 potentially using more bandwidth than expected. Bugfix on
5199 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5200 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5201 hidserv" in her torrc. The 'hidserv' argument never controlled
5202 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5205 - Adjust our TLS Diffie-Hellman parameters to match those used by
5207 - Update to the February 1 2011 Maxmind GeoLite Country database.
5210 - Check for and reject overly long directory certificates and
5211 directory tokens before they have a chance to hit any assertions.
5212 Bugfix on 0.2.1.28. Found by "doorss".
5213 - Bring the logic that gathers routerinfos and assesses the
5214 acceptability of circuits into line. This prevents a Tor OP from
5215 getting locked in a cycle of choosing its local OR as an exit for a
5216 path (due to a .exit request) and then rejecting the circuit because
5217 its OR is not listed yet. It also prevents Tor clients from using an
5218 OR running in the same instance as an exit (due to a .exit request)
5219 if the OR does not meet the same requirements expected of an OR
5220 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5222 o Packaging changes:
5223 - Stop shipping the Tor specs files and development proposal documents
5224 in the tarball. They are now in a separate git repository at
5225 git://git.torproject.org/torspec.git
5226 - Do not include Git version tags as though they are SVN tags when
5227 generating a tarball from inside a repository that has switched
5228 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5231 Changes in version 0.2.2.22-alpha - 2011-01-25
5232 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5233 main other change is a slight tweak to Tor's TLS handshake that makes
5234 relays and bridges that run this new version reachable from Iran again.
5235 We don't expect this tweak will win the arms race long-term, but it
5236 will buy us a bit more time until we roll out a better solution.
5239 - Fix a bounds-checking error that could allow an attacker to
5240 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5242 - Don't assert when changing from bridge to relay or vice versa
5243 via the controller. The assert happened because we didn't properly
5244 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5245 bug 2433. Reported by bastik.
5248 - Adjust our TLS Diffie-Hellman parameters to match those used by
5250 - Provide a log message stating which geoip file we're parsing
5251 instead of just stating that we're parsing the geoip file.
5252 Implements ticket 2432.
5255 - Check for and reject overly long directory certificates and
5256 directory tokens before they have a chance to hit any assertions.
5257 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5260 Changes in version 0.2.2.21-alpha - 2011-01-15
5261 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5262 continues our recent code security audit work. The main fix resolves
5263 a remote heap overflow vulnerability that can allow remote code
5264 execution (CVE-2011-0427). Other fixes address a variety of assert
5265 and crash bugs, most of which we think are hard to exploit remotely.
5267 o Major bugfixes (security), also included in 0.2.1.29:
5268 - Fix a heap overflow bug where an adversary could cause heap
5269 corruption. This bug probably allows remote code execution
5270 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5272 - Prevent a denial-of-service attack by disallowing any
5273 zlib-compressed data whose compression factor is implausibly
5274 high. Fixes part of bug 2324; reported by "doorss".
5275 - Zero out a few more keys in memory before freeing them. Fixes
5276 bug 2384 and part of bug 2385. These key instances found by
5277 "cypherpunks", based on Andrew Case's report about being able
5278 to find sensitive data in Tor's memory space if you have enough
5279 permissions. Bugfix on 0.0.2pre9.
5281 o Major bugfixes (crashes), also included in 0.2.1.29:
5282 - Prevent calls to Libevent from inside Libevent log handlers.
5283 This had potential to cause a nasty set of crashes, especially
5284 if running Libevent with debug logging enabled, and running
5285 Tor with a controller watching for low-severity log messages.
5286 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5287 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5288 underflow errors there too. Fixes the other part of bug 2324.
5289 - Fix a bug where we would assert if we ever had a
5290 cached-descriptors.new file (or another file read directly into
5291 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5292 on 0.2.1.25. Found by doorss.
5293 - Fix some potential asserts and parsing issues with grossly
5294 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5297 o Minor bugfixes (other), also included in 0.2.1.29:
5298 - Fix a bug with handling misformed replies to reverse DNS lookup
5299 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5300 bug reported by doorss.
5301 - Fix compilation on mingw when a pthreads compatibility library
5302 has been installed. (We don't want to use it, so we shouldn't
5303 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5304 - Fix a bug where we would declare that we had run out of virtual
5305 addresses when the address space was only half-exhausted. Bugfix
5307 - Correctly handle the case where AutomapHostsOnResolve is set but
5308 no virtual addresses are available. Fixes bug 2328; bugfix on
5309 0.1.2.1-alpha. Bug found by doorss.
5310 - Correctly handle wrapping around when we run out of virtual
5311 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5313 o Minor features, also included in 0.2.1.29:
5314 - Update to the January 1 2011 Maxmind GeoLite Country database.
5315 - Introduce output size checks on all of our decryption functions.
5317 o Build changes, also included in 0.2.1.29:
5318 - Tor does not build packages correctly with Automake 1.6 and earlier;
5319 added a check to Makefile.am to make sure that we're building with
5320 Automake 1.7 or later.
5321 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5322 because we built it with a too-old version of automake. Thus that
5323 release broke ./configure --enable-openbsd-malloc, which is popular
5324 among really fast exit relays on Linux.
5326 o Major bugfixes, new in 0.2.2.21-alpha:
5327 - Prevent crash/heap corruption when the cbtnummodes consensus
5328 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5331 o Major features, new in 0.2.2.21-alpha:
5332 - Introduce minimum/maximum values that clients will believe
5333 from the consensus. Now we'll have a better chance to avoid crashes
5334 or worse when a consensus param has a weird value.
5336 o Minor features, new in 0.2.2.21-alpha:
5337 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5338 used on bridges, and it makes bridge scanning somewhat easier.
5339 - If writing the state file to disk fails, wait up to an hour before
5340 retrying again, rather than trying again each second. Fixes bug
5341 2346; bugfix on Tor 0.1.1.3-alpha.
5342 - Make Libevent log messages get delivered to controllers later,
5343 and not from inside the Libevent log handler. This prevents unsafe
5344 reentrant Libevent calls while still letting the log messages
5346 - Detect platforms that brokenly use a signed size_t, and refuse to
5347 build there. Found and analyzed by doorss and rransom.
5348 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5351 o Minor bugfixes, new in 0.2.2.21-alpha:
5352 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5353 than waiting forever for them to finish. Fixes bug 2330; bugfix
5354 on 0.2.0.16-alpha. Found by doorss.
5355 - Add assertions to check for overflow in arguments to
5356 base32_encode() and base32_decode(); fix a signed-unsigned
5357 comparison there too. These bugs are not actually reachable in Tor,
5358 but it's good to prevent future errors too. Found by doorss.
5359 - Correctly detect failures to create DNS requests when using Libevent
5360 versions before v2. (Before Libevent 2, we used our own evdns
5361 implementation. Its return values for Libevent's evdns_resolve_*()
5362 functions are not consistent with those from Libevent.) Fixes bug
5363 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5365 o Documentation, new in 0.2.2.21-alpha:
5366 - Document the default socks host and port (127.0.0.1:9050) for
5370 Changes in version 0.2.1.29 - 2011-01-15
5371 Tor 0.2.1.29 continues our recent code security audit work. The main
5372 fix resolves a remote heap overflow vulnerability that can allow remote
5373 code execution. Other fixes address a variety of assert and crash bugs,
5374 most of which we think are hard to exploit remotely.
5376 o Major bugfixes (security):
5377 - Fix a heap overflow bug where an adversary could cause heap
5378 corruption. This bug probably allows remote code execution
5379 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5381 - Prevent a denial-of-service attack by disallowing any
5382 zlib-compressed data whose compression factor is implausibly
5383 high. Fixes part of bug 2324; reported by "doorss".
5384 - Zero out a few more keys in memory before freeing them. Fixes
5385 bug 2384 and part of bug 2385. These key instances found by
5386 "cypherpunks", based on Andrew Case's report about being able
5387 to find sensitive data in Tor's memory space if you have enough
5388 permissions. Bugfix on 0.0.2pre9.
5390 o Major bugfixes (crashes):
5391 - Prevent calls to Libevent from inside Libevent log handlers.
5392 This had potential to cause a nasty set of crashes, especially
5393 if running Libevent with debug logging enabled, and running
5394 Tor with a controller watching for low-severity log messages.
5395 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5396 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5397 underflow errors there too. Fixes the other part of bug 2324.
5398 - Fix a bug where we would assert if we ever had a
5399 cached-descriptors.new file (or another file read directly into
5400 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5401 on 0.2.1.25. Found by doorss.
5402 - Fix some potential asserts and parsing issues with grossly
5403 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5406 o Minor bugfixes (other):
5407 - Fix a bug with handling misformed replies to reverse DNS lookup
5408 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5409 bug reported by doorss.
5410 - Fix compilation on mingw when a pthreads compatibility library
5411 has been installed. (We don't want to use it, so we shouldn't
5412 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5413 - Fix a bug where we would declare that we had run out of virtual
5414 addresses when the address space was only half-exhausted. Bugfix
5416 - Correctly handle the case where AutomapHostsOnResolve is set but
5417 no virtual addresses are available. Fixes bug 2328; bugfix on
5418 0.1.2.1-alpha. Bug found by doorss.
5419 - Correctly handle wrapping around to when we run out of virtual
5420 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5421 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5422 because we built it with a too-old version of automake. Thus that
5423 release broke ./configure --enable-openbsd-malloc, which is popular
5424 among really fast exit relays on Linux.
5427 - Update to the January 1 2011 Maxmind GeoLite Country database.
5428 - Introduce output size checks on all of our decryption functions.
5431 - Tor does not build packages correctly with Automake 1.6 and earlier;
5432 added a check to Makefile.am to make sure that we're building with
5433 Automake 1.7 or later.
5436 Changes in version 0.2.2.20-alpha - 2010-12-17
5437 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5438 exploitable bugs. We also fix a variety of other significant bugs,
5439 change the IP address for one of our directory authorities, and update
5440 the minimum version that Tor relays must run to join the network.
5443 - Fix a remotely exploitable bug that could be used to crash instances
5444 of Tor remotely by overflowing on the heap. Remote-code execution
5445 hasn't been confirmed, but can't be ruled out. Everyone should
5446 upgrade. Bugfix on the 0.1.1 series and later.
5447 - Fix a bug that could break accounting on 64-bit systems with large
5448 time_t values, making them hibernate for impossibly long intervals.
5449 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5450 - Fix a logic error in directory_fetches_from_authorities() that
5451 would cause all _non_-exits refusing single-hop-like circuits
5452 to fetch from authorities, when we wanted to have _exits_ fetch
5453 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5455 - Fix a stream fairness bug that would cause newer streams on a given
5456 circuit to get preference when reading bytes from the origin or
5457 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5458 introduced before the first Tor release, in svn revision r152.
5460 o Directory authority changes:
5461 - Change IP address and ports for gabelmoo (v3 directory authority).
5464 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5465 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5466 - Fix an off-by-one error in calculating some controller command
5467 argument lengths. Fortunately, this mistake is harmless since
5468 the controller code does redundant NUL termination too. Found by
5469 boboper. Bugfix on 0.1.1.1-alpha.
5470 - Do not dereference NULL if a bridge fails to build its
5471 extra-info descriptor. Found by an anonymous commenter on
5472 Trac. Bugfix on 0.2.2.19-alpha.
5475 - Update to the December 1 2010 Maxmind GeoLite Country database.
5476 - Directory authorities now reject relays running any versions of
5477 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5478 known bugs that keep RELAY_EARLY cells from working on rendezvous
5479 circuits. Followup to fix for bug 2081.
5480 - Directory authorities now reject relays running any version of Tor
5481 older than 0.2.0.26-rc. That version is the earliest that fetches
5482 current directory information correctly. Fixes bug 2156.
5483 - Report only the top 10 ports in exit-port stats in order not to
5484 exceed the maximum extra-info descriptor length of 50 KB. Implements
5488 Changes in version 0.2.1.28 - 2010-12-17
5489 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5490 exploitable bugs. We also took this opportunity to change the IP address
5491 for one of our directory authorities, and to update the geoip database
5495 - Fix a remotely exploitable bug that could be used to crash instances
5496 of Tor remotely by overflowing on the heap. Remote-code execution
5497 hasn't been confirmed, but can't be ruled out. Everyone should
5498 upgrade. Bugfix on the 0.1.1 series and later.
5500 o Directory authority changes:
5501 - Change IP address and ports for gabelmoo (v3 directory authority).
5504 - Update to the December 1 2010 Maxmind GeoLite Country database.
5507 Changes in version 0.2.1.27 - 2010-11-23
5508 Yet another OpenSSL security patch broke its compatibility with Tor:
5509 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5510 also took this opportunity to fix several crash bugs, integrate a new
5511 directory authority, and update the bundled GeoIP database.
5514 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5515 No longer set the tlsext_host_name extension on server SSL objects;
5516 but continue to set it on client SSL objects. Our goal in setting
5517 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5518 bugfix on 0.2.1.1-alpha.
5519 - Do not log messages to the controller while shrinking buffer
5520 freelists. Doing so would sometimes make the controller connection
5521 try to allocate a buffer chunk, which would mess up the internals
5522 of the freelist and cause an assertion failure. Fixes bug 1125;
5523 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5524 - Learn our external IP address when we're a relay or bridge, even if
5525 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5526 where we introduced bridge relays that don't need to publish to
5527 be useful. Fixes bug 2050.
5528 - Do even more to reject (and not just ignore) annotations on
5529 router descriptors received anywhere but from the cache. Previously
5530 we would ignore such annotations at first, but cache them to disk
5531 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5532 - When you're using bridges and your network goes away and your
5533 bridges get marked as down, recover when you attempt a new socks
5534 connection (if the network is back), rather than waiting up to an
5535 hour to try fetching new descriptors for your bridges. Bugfix on
5536 0.2.0.3-alpha; fixes bug 1981.
5539 - Move to the November 2010 Maxmind GeoLite country db (rather
5540 than the June 2009 ip-to-country GeoIP db) for our statistics that
5541 count how many users relays are seeing from each country. Now we'll
5542 have more accurate data, especially for many African countries.
5544 o New directory authorities:
5545 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5549 - Fix an assertion failure that could occur in directory caches or
5550 bridge users when using a very short voting interval on a testing
5551 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5553 - Enforce multiplicity rules when parsing annotations. Bugfix on
5554 0.2.0.8-alpha. Found by piebeer.
5555 - Allow handshaking OR connections to take a full KeepalivePeriod
5556 seconds to handshake. Previously, we would close them after
5557 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5558 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5560 - When building with --enable-gcc-warnings on OpenBSD, disable
5561 warnings in system headers. This makes --enable-gcc-warnings
5562 pass on OpenBSD 4.8.
5565 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5566 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5567 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5568 Servers can start sending this code when enough clients recognize
5569 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5570 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5571 Patch from mingw-san.
5574 - Remove the old debian/ directory from the main Tor distribution.
5575 The official Tor-for-debian git repository lives at the URL
5576 https://git.torproject.org/debian/tor.git
5577 - Stop shipping the old doc/website/ directory in the tarball. We
5578 changed the website format in late 2010, and what we shipped in
5579 0.2.1.26 really wasn't that useful anyway.
5582 Changes in version 0.2.2.19-alpha - 2010-11-22
5583 Yet another OpenSSL security patch broke its compatibility with Tor:
5584 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5587 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5588 No longer set the tlsext_host_name extension on server SSL objects;
5589 but continue to set it on client SSL objects. Our goal in setting
5590 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5591 bugfix on 0.2.1.1-alpha.
5594 - Try harder not to exceed the maximum length of 50 KB when writing
5595 statistics to extra-info descriptors. This bug was triggered by very
5596 fast relays reporting exit-port, entry, and dirreq statistics.
5597 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5598 - Publish a router descriptor even if generating an extra-info
5599 descriptor fails. Previously we would not publish a router
5600 descriptor without an extra-info descriptor; this can cause fast
5601 exit relays collecting exit-port statistics to drop from the
5602 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5605 Changes in version 0.2.2.18-alpha - 2010-11-16
5606 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5607 us lately, makes unpublished bridge relays able to detect their IP
5608 address, and fixes a wide variety of other bugs to get us much closer
5609 to a stable release.
5612 - Do even more to reject (and not just ignore) annotations on
5613 router descriptors received anywhere but from the cache. Previously
5614 we would ignore such annotations at first, but cache them to disk
5615 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5616 - Do not log messages to the controller while shrinking buffer
5617 freelists. Doing so would sometimes make the controller connection
5618 try to allocate a buffer chunk, which would mess up the internals
5619 of the freelist and cause an assertion failure. Fixes bug 1125;
5620 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5621 - Learn our external IP address when we're a relay or bridge, even if
5622 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5623 where we introduced bridge relays that don't need to publish to
5624 be useful. Fixes bug 2050.
5625 - Maintain separate TLS contexts and certificates for incoming and
5626 outgoing connections in bridge relays. Previously we would use the
5627 same TLS contexts and certs for incoming and outgoing connections.
5628 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5629 - Maintain separate identity keys for incoming and outgoing TLS
5630 contexts in bridge relays. Previously we would use the same
5631 identity keys for incoming and outgoing TLS contexts. Bugfix on
5632 0.2.0.3-alpha; addresses the other half of bug 988.
5633 - Avoid an assertion failure when we as an authority receive a
5634 duplicate upload of a router descriptor that we already have,
5635 but which we previously considered an obsolete descriptor.
5636 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5637 - Avoid a crash bug triggered by looking at a dangling pointer while
5638 setting the network status consensus. Found by Robert Ransom.
5639 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5640 - Fix a logic error where servers that _didn't_ act as exits would
5641 try to keep their server lists more aggressively up to date than
5642 exits, when it was supposed to be the other way around. Bugfix
5645 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5646 - When we're trying to guess whether we know our IP address as
5647 a relay, we would log various ways that we failed to guess
5648 our address, but never log that we ended up guessing it
5649 successfully. Now add a log line to help confused and anxious
5650 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5651 - Bring the logic that gathers routerinfos and assesses the
5652 acceptability of circuits into line. This prevents a Tor OP from
5653 getting locked in a cycle of choosing its local OR as an exit for a
5654 path (due to a .exit request) and then rejecting the circuit because
5655 its OR is not listed yet. It also prevents Tor clients from using an
5656 OR running in the same instance as an exit (due to a .exit request)
5657 if the OR does not meet the same requirements expected of an OR
5658 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5659 - Correctly describe errors that occur when generating a TLS object.
5660 Previously we would attribute them to a failure while generating a
5661 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5663 - Enforce multiplicity rules when parsing annotations. Bugfix on
5664 0.2.0.8-alpha. Found by piebeer.
5665 - Fix warnings that newer versions of autoconf produced during
5666 ./autogen.sh. These warnings appear to be harmless in our case,
5667 but they were extremely verbose. Fixes bug 2020.
5669 o Minor bugfixes (on Tor 0.2.2.x):
5670 - Enable protection of small arrays whenever we build with gcc
5671 hardening features, not only when also building with warnings
5672 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5675 - Make hidden services work better in private Tor networks by not
5676 requiring any uptime to join the hidden service descriptor
5677 DHT. Implements ticket 2088.
5678 - Rate-limit the "your application is giving Tor only an IP address"
5679 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5680 - When AllowSingleHopExits is set, print a warning to explain to the
5681 relay operator why most clients are avoiding her relay.
5682 - Update to the November 1 2010 Maxmind GeoLite Country database.
5684 o Code simplifications and refactoring:
5685 - When we fixed bug 1038 we had to put in a restriction not to send
5686 RELAY_EARLY cells on rend circuits. This was necessary as long
5687 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5688 active. Now remove this obsolete check. Resolves bug 2081.
5689 - Some options used different conventions for uppercasing of acronyms
5690 when comparing manpage and source. Fix those in favor of the
5691 manpage, as it makes sense to capitalize acronyms.
5692 - Remove the torrc.complete file. It hasn't been kept up to date
5693 and users will have better luck checking out the manpage.
5694 - Remove the obsolete "NoPublish" option; it has been flagged
5695 as obsolete and has produced a warning since 0.1.1.18-rc.
5696 - Remove everything related to building the expert bundle for OS X.
5697 It has confused many users, doesn't work right on OS X 10.6,
5698 and is hard to get rid of once installed. Resolves bug 1274.
5701 Changes in version 0.2.2.17-alpha - 2010-09-30
5702 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
5703 to use one-hop circuits (which can put the exit relays at higher risk,
5704 plus unbalance the network); fixes a big bug in bandwidth accounting
5705 for relays that want to limit their monthly bandwidth use; fixes a
5706 big pile of bugs in how clients tolerate temporary network failure;
5707 and makes our adaptive circuit build timeout feature (which improves
5708 client performance if your network is fast while not breaking things
5709 if your network is slow) better handle bad networks.
5712 - Exit relays now try harder to block exit attempts from unknown
5713 relays, to make it harder for people to use them as one-hop proxies
5714 a la tortunnel. Controlled by the refuseunknownexits consensus
5715 parameter (currently enabled), or you can override it on your
5716 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
5718 o Major bugfixes (0.2.1.x and earlier):
5719 - Fix a bug in bandwidth accounting that could make us use twice
5720 the intended bandwidth when our interval start changes due to
5721 daylight saving time. Now we tolerate skew in stored vs computed
5722 interval starts: if the start of the period changes by no more than
5723 50% of the period's duration, we remember bytes that we transferred
5724 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5725 - Always search the Windows system directory for system DLLs, and
5726 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5727 - When you're using bridges and your network goes away and your
5728 bridges get marked as down, recover when you attempt a new socks
5729 connection (if the network is back), rather than waiting up to an
5730 hour to try fetching new descriptors for your bridges. Bugfix on
5731 0.2.0.3-alpha; fixes bug 1981.
5733 o Major bugfixes (on 0.2.2.x):
5734 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
5736 - Fix a segfault that could happen when operating a bridge relay with
5737 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
5738 - The consensus bandwidth-weights (used by clients to choose fast
5739 relays) entered an unexpected edge case in September where
5740 Exits were much scarcer than Guards, resulting in bad weight
5741 recommendations. Now we compute them using new constraints that
5742 should succeed in all cases. Also alter directory authorities to
5743 not include the bandwidth-weights line if they fail to produce
5744 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
5745 - When weighting bridges during path selection, we used to trust
5746 the bandwidths they provided in their descriptor, only capping them
5747 at 10MB/s. This turned out to be problematic for two reasons:
5748 Bridges could claim to handle a lot more traffic then they
5749 actually would, thus making more clients pick them and have a
5750 pretty effective DoS attack. The other issue is that new bridges
5751 that might not have a good estimate for their bw capacity yet
5752 would not get used at all unless no other bridges are available
5753 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
5755 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
5756 - Ignore cannibalized circuits when recording circuit build times.
5757 This should provide for a minor performance improvement for hidden
5758 service users using 0.2.2.14-alpha, and should remove two spurious
5759 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
5760 - Simplify the logic that causes us to decide if the network is
5761 unavailable for purposes of recording circuit build times. If we
5762 receive no cells whatsoever for the entire duration of a circuit's
5763 full measured lifetime, the network is probably down. Also ignore
5764 one-hop directory fetching circuit timeouts when calculating our
5765 circuit build times. These changes should hopefully reduce the
5766 cases where we see ridiculous circuit build timeouts for people
5767 with spotty wireless connections. Fixes part of bug 1772; bugfix
5769 - Prevent the circuit build timeout from becoming larger than
5770 the maximum build time we have ever seen. Also, prevent the time
5771 period for measurement circuits from becoming larger than twice that
5772 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
5775 - When we run out of directory information such that we can't build
5776 circuits, but then get enough that we can build circuits, log when
5777 we actually construct a circuit, so the user has a better chance of
5778 knowing what's going on. Fixes bug 1362.
5779 - Be more generous with how much bandwidth we'd use up (with
5780 accounting enabled) before entering "soft hibernation". Previously,
5781 we'd refuse new connections and circuits once we'd used up 95% of
5782 our allotment. Now, we use up 95% of our allotment, AND make sure
5783 that we have no more than 500MB (or 3 hours of expected traffic,
5784 whichever is lower) remaining before we enter soft hibernation.
5785 - If we've configured EntryNodes and our network goes away and/or all
5786 our entrynodes get marked down, optimistically retry them all when
5787 a new socks application request appears. Fixes bug 1882.
5788 - Add some more defensive programming for architectures that can't
5789 handle unaligned integer accesses. We don't know of any actual bugs
5790 right now, but that's the best time to fix them. Fixes bug 1943.
5791 - Support line continuations in the torrc config file. If a line
5792 ends with a single backslash character, the newline is ignored, and
5793 the configuration value is treated as continuing on the next line.
5796 o Minor bugfixes (on 0.2.1.x and earlier):
5797 - For bandwidth accounting, calculate our expected bandwidth rate
5798 based on the time during which we were active and not in
5799 soft-hibernation during the last interval. Previously, we were
5800 also considering the time spent in soft-hibernation. If this
5801 was a long time, we would wind up underestimating our bandwidth
5802 by a lot, and skewing our wakeup time towards the start of the
5803 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
5805 o Minor bugfixes (on 0.2.2.x):
5806 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
5807 which were disabled by the circuit build timeout changes in
5808 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
5809 - Make sure we don't warn about missing bandwidth weights when
5810 choosing bridges or other relays not in the consensus. Bugfix on
5811 0.2.2.10-alpha; fixes bug 1805.
5812 - In our logs, do not double-report signatures from unrecognized
5813 authorities both as "from unknown authority" and "not
5814 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
5817 Changes in version 0.2.2.16-alpha - 2010-09-17
5818 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
5819 evident at exit relays), and also continues to resolve all the little
5820 bugs that have been filling up trac lately.
5822 o Major bugfixes (stream-level fairness):
5823 - When receiving a circuit-level SENDME for a blocked circuit, try
5824 to package cells fairly from all the streams that had previously
5825 been blocked on that circuit. Previously, we had started with the
5826 oldest stream, and allowed each stream to potentially exhaust
5827 the circuit's package window. This gave older streams on any
5828 given circuit priority over newer ones. Fixes bug 1937. Detected
5829 originally by Camilo Viecco. This bug was introduced before the
5830 first Tor release, in svn commit r152: it is the new winner of
5831 the longest-lived bug prize.
5832 - When the exit relay got a circuit-level sendme cell, it started
5833 reading on the exit streams, even if had 500 cells queued in the
5834 circuit queue already, so the circuit queue just grew and grew in
5835 some cases. We fix this by not re-enabling reading on receipt of a
5836 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
5837 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
5839 - Newly created streams were allowed to read cells onto circuits,
5840 even if the circuit's cell queue was blocked and waiting to drain.
5841 This created potential unfairness, as older streams would be
5842 blocked, but newer streams would gladly fill the queue completely.
5843 We add code to detect this situation and prevent any stream from
5844 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
5848 - Update to the September 1 2010 Maxmind GeoLite Country database.
5849 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
5850 not. This would lead to a cookie that is still not group readable.
5851 Closes bug 1843. Suggested by katmagic.
5852 - When logging a rate-limited warning, we now mention how many messages
5853 got suppressed since the last warning.
5854 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
5855 do individual connection-level rate limiting of clients. The torrc
5856 config options with the same names trump the consensus params, if
5857 both are present. Replaces the old "bwconnrate" and "bwconnburst"
5858 consensus params which were broken from 0.2.2.7-alpha through
5859 0.2.2.14-alpha. Closes bug 1947.
5860 - When a router changes IP address or port, authorities now launch
5861 a new reachability test for it. Implements ticket 1899.
5862 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
5863 2 no signature, 4 required" messages about consensus signatures
5864 easier to read, and make sure they get logged at the same severity
5865 as the messages explaining which keys are which. Fixes bug 1290.
5866 - Don't warn when we have a consensus that we can't verify because
5867 of missing certificates, unless those certificates are ones
5868 that we have been trying and failing to download. Fixes bug 1145.
5869 - If you configure your bridge with a known identity fingerprint,
5870 and the bridge authority is unreachable (as it is in at least
5871 one country now), fall back to directly requesting the descriptor
5872 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
5874 - When building with --enable-gcc-warnings on OpenBSD, disable
5875 warnings in system headers. This makes --enable-gcc-warnings
5876 pass on OpenBSD 4.8.
5878 o Minor bugfixes (on 0.2.1.x and earlier):
5879 - Authorities will now attempt to download consensuses if their
5880 own efforts to make a live consensus have failed. This change
5881 means authorities that restart will fetch a valid consensus, and
5882 it means authorities that didn't agree with the current consensus
5883 will still fetch and serve it if it has enough signatures. Bugfix
5884 on 0.2.0.9-alpha; fixes bug 1300.
5885 - Ensure DNS requests launched by "RESOLVE" commands from the
5886 controller respect the __LeaveStreamsUnattached setconf options. The
5887 same goes for requests launched via DNSPort or transparent
5888 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
5889 - Allow handshaking OR connections to take a full KeepalivePeriod
5890 seconds to handshake. Previously, we would close them after
5891 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5892 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5894 - Rate-limit "Failed to hand off onionskin" warnings.
5895 - Never relay a cell for a circuit we have already destroyed.
5896 Between marking a circuit as closeable and finally closing it,
5897 it may have been possible for a few queued cells to get relayed,
5898 even though they would have been immediately dropped by the next
5899 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
5900 - Never queue a cell for a circuit that's already been marked
5902 - Never vote for a server as "Running" if we have a descriptor for
5903 it claiming to be hibernating, and that descriptor was published
5904 more recently than our last contact with the server. Bugfix on
5905 0.2.0.3-alpha; fixes bug 911.
5906 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
5909 o Minor bugfixes (on 0.2.2.x):
5910 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
5911 down if a directory fetch fails and you've configured either
5912 bridges or EntryNodes. The intent was to mark the relay as down
5913 _unless_ you're using bridges or EntryNodes, since if you are
5914 then you could quickly run out of entry points.
5915 - Fix the Windows directory-listing code. A bug introduced in
5916 0.2.2.14-alpha could make Windows directory servers forget to load
5917 some of their cached v2 networkstatus files.
5918 - Really allow clients to use relays as bridges. Fixes bug 1776;
5919 bugfix on 0.2.2.15-alpha.
5920 - Demote a warn to info that happens when the CellStatistics option
5921 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
5922 Reported by Moritz Bartl.
5923 - On Windows, build correctly either with or without Unicode support.
5924 This is necessary so that Tor can support fringe platforms like
5925 Windows 98 (which has no Unicode), or Windows CE (which has no
5926 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
5929 - Add a unit test for cross-platform directory-listing code.
5932 Changes in version 0.2.2.15-alpha - 2010-08-18
5933 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
5934 fixes a variety of other bugs that were preventing performance
5935 experiments from moving forward, fixes several bothersome memory leaks,
5936 and generally closes a lot of smaller bugs that have been filling up
5940 - Stop assigning the HSDir flag to relays that disable their
5941 DirPort (and thus will refuse to answer directory requests). This
5942 fix should dramatically improve the reachability of hidden services:
5943 hidden services and hidden service clients pick six HSDir relays
5944 to store and retrieve the hidden service descriptor, and currently
5945 about half of the HSDir relays will refuse to work. Bugfix on
5946 0.2.0.10-alpha; fixes part of bug 1693.
5947 - The PerConnBWRate and Burst config options, along with the
5948 bwconnrate and bwconnburst consensus params, initialized each conn's
5949 token bucket values only when the connection is established. Now we
5950 update them if the config options change, and update them every time
5951 we get a new consensus. Otherwise we can encounter an ugly edge
5952 case where we initialize an OR conn to client-level bandwidth,
5953 but then later the relay joins the consensus and we leave it
5954 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
5955 - Fix a regression that caused Tor to rebind its ports if it receives
5956 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
5959 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
5960 should give us approximately 40-50% more Guard-flagged nodes,
5961 improving the anonymity the Tor network can provide and also
5962 decreasing the dropoff in throughput that relays experience when
5963 they first get the Guard flag.
5964 - Allow enabling or disabling the *Statistics config options while
5968 - Update to the August 1 2010 Maxmind GeoLite Country database.
5969 - Have the controller interface give a more useful message than
5970 "Internal Error" in response to failed GETINFO requests.
5971 - Warn when the same option is provided more than once in a torrc
5972 file, on the command line, or in a single SETCONF statement, and
5973 the option is one that only accepts a single line. Closes bug 1384.
5974 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5975 Patch from mingw-san.
5976 - Add support for the country code "{??}" in torrc options like
5977 ExcludeNodes, to indicate all routers of unknown country. Closes
5979 - Relays report the number of bytes spent on answering directory
5980 requests in extra-info descriptors similar to {read,write}-history.
5981 Implements enhancement 1790.
5983 o Minor bugfixes (on 0.2.1.x and earlier):
5984 - Complain if PublishServerDescriptor is given multiple arguments that
5985 include 0 or 1. This configuration will be rejected in the future.
5986 Bugfix on 0.2.0.1-alpha; closes bug 1107.
5987 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
5988 Bugfix on 0.2.0.13-alpha; closes bug 928.
5989 - Change "Application request when we're believed to be offline."
5990 notice to "Application request when we haven't used client
5991 functionality lately.", to clarify that it's not an error. Bugfix
5992 on 0.0.9.3; fixes bug 1222.
5993 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
5994 would return "551 Internal error" rather than "552 Unrecognized key
5995 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
5996 - Users can't configure a regular relay to be their bridge. It didn't
5997 work because when Tor fetched the bridge descriptor, it found
5998 that it already had it, and didn't realize that the purpose of the
5999 descriptor had changed. Now we replace routers with a purpose other
6000 than bridge with bridge descriptors when fetching them. Bugfix on
6001 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6002 refetch the descriptor with router purpose 'general', disabling
6004 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6005 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6006 on 0.2.0.10-alpha; fixes bug 1808.
6007 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6008 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6009 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6010 Servers can start sending this code when enough clients recognize
6011 it. Also update the spec to reflect this new reason. Bugfix on
6012 0.1.0.1-rc; fixes part of bug 1793.
6013 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6014 when we switch from being a public relay to a bridge. Otherwise
6015 there will still be clients that see the relay in their consensus,
6016 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6018 - Instead of giving an assertion failure on an internal mismatch
6019 on estimated freelist size, just log a BUG warning and try later.
6020 Mitigates but does not fix bug 1125.
6021 - Fix an assertion failure that could occur in caches or bridge users
6022 when using a very short voting interval on a testing network.
6023 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6025 o Minor bugfixes (on 0.2.2.x):
6026 - Alter directory authorities to always consider Exit-flagged nodes
6027 as potential Guard nodes in their votes. The actual decision to
6028 use Exits as Guards is done in the consensus bandwidth weights.
6029 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6030 - When the controller is reporting the purpose of circuits that
6031 didn't finish building before the circuit build timeout, it was
6032 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6033 - Our libevent version parsing code couldn't handle versions like
6034 1.4.14b-stable and incorrectly warned the user about using an
6035 old and broken version of libevent. Treat 1.4.14b-stable like
6036 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6038 - Don't use substitution references like $(VAR:MOD) when
6039 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6040 '$(:x)' to 'x' rather than the empty string. This bites us in
6041 doc/ when configured with --disable-asciidoc. Bugfix on
6042 0.2.2.9-alpha; fixes bug 1773.
6043 - Remove a spurious hidden service server-side log notice about
6044 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6046 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6048 - Correctly report written bytes on linked connections. Found while
6049 implementing 1790. Bugfix on 0.2.2.4-alpha.
6050 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6051 one in dirvote_add_signatures_to_pending_consensus(), and one every
6052 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6053 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6055 o Code simplifications and refactoring:
6056 - Take a first step towards making or.h smaller by splitting out
6057 function definitions for all source files in src/or/. Leave
6058 structures and defines in or.h for now.
6059 - Remove a bunch of unused function declarations as well as a block of
6060 #if 0'd code from the unit tests. Closes bug 1824.
6061 - New unit tests for exit-port history statistics; refactored exit
6062 statistics code to be more easily tested.
6063 - Remove the old debian/ directory from the main Tor distribution.
6064 The official Tor-for-debian git repository lives at the URL
6065 https://git.torproject.org/debian/tor.git
6068 Changes in version 0.2.2.14-alpha - 2010-07-12
6069 Tor 0.2.2.14-alpha greatly improves client-side handling of
6070 circuit build timeouts, which are used to estimate speed and improve
6071 performance. We also move to a much better GeoIP database, port Tor to
6072 Windows CE, introduce new compile flags that improve code security,
6073 add an eighth v3 directory authority, and address a lot of more
6077 - Tor directory authorities no longer crash when started with a
6078 cached-microdesc-consensus file in their data directory. Bugfix
6079 on 0.2.2.6-alpha; fixes bug 1532.
6080 - Treat an unset $HOME like an empty $HOME rather than triggering an
6081 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6082 - Ignore negative and large circuit build timeout values that can
6083 happen during a suspend or hibernate. These values caused various
6084 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6085 - Alter calculation of Pareto distribution parameter 'Xm' for
6086 Circuit Build Timeout learning to use the weighted average of the
6087 top N=3 modes (because we have three entry guards). Considering
6088 multiple modes should improve the timeout calculation in some cases,
6089 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6091 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6092 right censored distribution model. This approach improves over the
6093 synthetic timeout generation approach that was producing insanely
6094 high timeout values. Now we calculate build timeouts using truncated
6095 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6096 - Do not close circuits that are under construction when they reach
6097 the circuit build timeout. Instead, leave them building (but do not
6098 use them) for up until the time corresponding to the 95th percentile
6099 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6100 to provide better data for the new Pareto model. This percentile
6101 can be controlled by the consensus.
6104 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6105 June 2009 ip-to-country GeoIP db) for our statistics that count
6106 how many users relays are seeing from each country. Now we have
6107 more accurate data for many African countries.
6108 - Port Tor to build and run correctly on Windows CE systems, using
6109 the wcecompat library. Contributed by Valerio Lupi.
6110 - New "--enable-gcc-hardening" ./configure flag (off by default)
6111 to turn on gcc compile time hardening options. It ensures
6112 that signed ints have defined behavior (-fwrapv), enables
6113 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6114 with canaries (-fstack-protector-all), turns on ASLR protection if
6115 supported by the kernel (-fPIE, -pie), and adds additional security
6116 related warnings. Verified to work on Mac OS X and Debian Lenny.
6117 - New "--enable-linker-hardening" ./configure flag (off by default)
6118 to turn on ELF specific hardening features (relro, now). This does
6119 not work with Mac OS X or any other non-ELF binary format.
6121 o New directory authorities:
6122 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6126 - New config option "WarnUnsafeSocks 0" disables the warning that
6127 occurs whenever Tor receives a socks handshake using a version of
6128 the socks protocol that can only provide an IP address (rather
6129 than a hostname). Setups that do DNS locally over Tor are fine,
6130 and we shouldn't spam the logs in that case.
6131 - Convert the HACKING file to asciidoc, and add a few new sections
6132 to it, explaining how we use Git, how we make changelogs, and
6133 what should go in a patch.
6134 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6135 event, to give information on the current rate of circuit timeouts
6136 over our stored history.
6137 - Add ability to disable circuit build time learning via consensus
6138 parameter and via a LearnCircuitBuildTimeout config option. Also
6139 automatically disable circuit build time calculation if we are
6140 either a AuthoritativeDirectory, or if we fail to write our state
6141 file. Fixes bug 1296.
6142 - More gracefully handle corrupt state files, removing asserts
6143 in favor of saving a backup and resetting state.
6144 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6148 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6150 - When a2x fails, mention that the user could disable manpages instead
6151 of trying to fix their asciidoc installation.
6152 - Where available, use Libevent 2.0's periodic timers so that our
6153 once-per-second cleanup code gets called even more closely to
6154 once per second than it would otherwise. Fixes bug 943.
6155 - If you run a bridge that listens on multiple IP addresses, and
6156 some user configures a bridge address that uses a different IP
6157 address than your bridge writes in its router descriptor, and the
6158 user doesn't specify an identity key, their Tor would discard the
6159 descriptor because "it isn't one of our configured bridges", and
6160 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6161 Bugfix on 0.2.0.3-alpha.
6162 - If OpenSSL fails to make a duplicate of a private or public key, log
6163 an error message and try to exit cleanly. May help with debugging
6164 if bug 1209 ever remanifests.
6165 - Save a couple bytes in memory allocation every time we escape
6166 certain characters in a string. Patch from Florian Zumbiehl.
6167 - Make it explicit that we don't cannibalize one-hop circuits. This
6168 happens in the wild, but doesn't turn out to be a problem because
6169 we fortunately don't use those circuits. Many thanks to outofwords
6170 for the initial analysis and to swissknife who confirmed that
6171 two-hop circuits are actually created.
6172 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6173 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6174 - Eliminate a case where a circuit build time warning was displayed
6175 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6178 Changes in version 0.2.1.26 - 2010-05-02
6179 Tor 0.2.1.26 addresses the recent connection and memory overload
6180 problems we've been seeing on relays, especially relays with their
6181 DirPort open. If your relay has been crashing, or you turned it off
6182 because it used too many resources, give this release a try.
6184 This release also fixes yet another instance of broken OpenSSL libraries
6185 that was causing some relays to drop out of the consensus.
6188 - Teach relays to defend themselves from connection overload. Relays
6189 now close idle circuits early if it looks like they were intended
6190 for directory fetches. Relays are also more aggressive about closing
6191 TLS connections that have no circuits on them. Such circuits are
6192 unlikely to be re-used, and tens of thousands of them were piling
6193 up at the fast relays, causing the relays to run out of sockets
6194 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6195 their directory fetches over TLS).
6196 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6197 that claim to be earlier than 0.9.8m, but which have in reality
6198 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6199 behavior. Possible fix for some cases of bug 1346.
6200 - Directory mirrors were fetching relay descriptors only from v2
6201 directory authorities, rather than v3 authorities like they should.
6202 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6203 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6206 - Finally get rid of the deprecated and now harmful notion of "clique
6207 mode", where directory authorities maintain TLS connections to
6211 - In the util/threads test, no longer free the test_mutex before all
6212 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6213 - The master thread could starve the worker threads quite badly on
6214 certain systems, causing them to run only partially in the allowed
6215 window. This resulted in test failures. Now the master thread sleeps
6216 occasionally for a few microseconds while the two worker-threads
6217 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6220 Changes in version 0.2.2.13-alpha - 2010-04-24
6221 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6222 problems we've been seeing on relays, especially relays with their
6223 DirPort open. If your relay has been crashing, or you turned it off
6224 because it used too many resources, give this release a try.
6227 - Teach relays to defend themselves from connection overload. Relays
6228 now close idle circuits early if it looks like they were intended
6229 for directory fetches. Relays are also more aggressive about closing
6230 TLS connections that have no circuits on them. Such circuits are
6231 unlikely to be re-used, and tens of thousands of them were piling
6232 up at the fast relays, causing the relays to run out of sockets
6233 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6234 their directory fetches over TLS).
6237 - Finally get rid of the deprecated and now harmful notion of "clique
6238 mode", where directory authorities maintain TLS connections to
6240 - Directory authorities now do an immediate reachability check as soon
6241 as they hear about a new relay. This change should slightly reduce
6242 the time between setting up a relay and getting listed as running
6243 in the consensus. It should also improve the time between setting
6244 up a bridge and seeing use by bridge users.
6245 - Directory authorities no longer launch a TLS connection to every
6246 relay as they startup. Now that we have 2k+ descriptors cached,
6247 the resulting network hiccup is becoming a burden. Besides,
6248 authorities already avoid voting about Running for the first half
6249 hour of their uptime.
6252 Changes in version 0.2.2.12-alpha - 2010-04-20
6253 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6254 handle and vote on descriptors. It was causing relays to drop out of
6258 - Many relays have been falling out of the consensus lately because
6259 not enough authorities know about their descriptor for them to get
6260 a majority of votes. When we deprecated the v2 directory protocol,
6261 we got rid of the only way that v3 authorities can hear from each
6262 other about other descriptors. Now authorities examine every v3
6263 vote for new descriptors, and fetch them from that authority. Bugfix
6265 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6266 and a warning in or.h related to bandwidth_weight_rule_t that
6267 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6269 - Fix a segfault on relays when DirReqStatistics is enabled
6270 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6274 - Demote a confusing TLS warning that relay operators might get when
6275 someone tries to talk to their OrPort. It is neither the operator's
6276 fault nor can they do anything about it. Fixes bug 1364; bugfix
6280 Changes in version 0.2.2.11-alpha - 2010-04-15
6281 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6282 libraries that was causing some relays to drop out of the consensus.
6285 - Directory mirrors were fetching relay descriptors only from v2
6286 directory authorities, rather than v3 authorities like they should.
6287 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6288 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6289 - Fix a parsing error that made every possible value of
6290 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6291 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6292 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6293 about the option without breaking older ones.
6294 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6295 that claim to be earlier than 0.9.8m, but which have in reality
6296 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6297 behavior. Possible fix for some cases of bug 1346.
6300 - Experiment with a more aggressive approach to preventing clients
6301 from making one-hop exit streams. Exit relays who want to try it
6302 out can set "RefuseUnknownExits 1" in their torrc, and then look
6303 for "Attempt by %s to open a stream" log messages. Let us know
6305 - Add support for statically linking zlib by specifying
6306 --enable-static-zlib, to go with our support for statically linking
6307 openssl and libevent. Resolves bug 1358.
6310 - Fix a segfault that happens whenever a Tor client that is using
6311 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6313 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6314 out the first line. Fixes bug 1295.
6315 - When building the manpage from a tarball, we required asciidoc, but
6316 the asciidoc -> roff/html conversion was already done for the
6317 tarball. Make 'make' complain only when we need asciidoc (either
6318 because we're compiling directly from git, or because we altered
6319 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6320 - When none of the directory authorities vote on any params, Tor
6321 segfaulted when trying to make the consensus from the votes. We
6322 didn't trigger the bug in practice, because authorities do include
6323 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6326 - In the util/threads test, no longer free the test_mutex before all
6327 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6328 - The master thread could starve the worker threads quite badly on
6329 certain systems, causing them to run only partially in the allowed
6330 window. This resulted in test failures. Now the master thread sleeps
6331 occasionally for a few microseconds while the two worker-threads
6332 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6335 Changes in version 0.2.2.10-alpha - 2010-03-07
6336 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6337 could prevent relays from guessing their IP address correctly. It also
6338 starts the groundwork for another client-side performance boost, since
6339 currently we're not making efficient use of relays that have both the
6340 Guard flag and the Exit flag.
6343 - Fix a regression from our patch for bug 1244 that caused relays
6344 to guess their IP address incorrectly if they didn't set Address
6345 in their torrc and/or their address fails to resolve. Bugfix on
6346 0.2.2.9-alpha; fixes bug 1269.
6348 o Major features (performance):
6349 - Directory authorities now compute consensus weightings that instruct
6350 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6351 and no flag. Clients that use these weightings will distribute
6352 network load more evenly across these different relay types. The
6353 weightings are in the consensus so we can change them globally in
6354 the future. Extra thanks to "outofwords" for finding some nasty
6355 security bugs in the first implementation of this feature.
6357 o Minor features (performance):
6358 - Always perform router selections using weighted relay bandwidth,
6359 even if we don't need a high capacity circuit at the time. Non-fast
6360 circuits now only differ from fast ones in that they can use relays
6361 not marked with the Fast flag. This "feature" could turn out to
6362 be a horrible bug; we should investigate more before it goes into
6366 - Allow disabling building of the manpages. Skipping the manpage
6367 speeds up the build considerably.
6369 o Minor bugfixes (on 0.2.2.x):
6370 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6371 Bugfix on 0.2.2.9-alpha.
6372 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6373 config option. Bugfix on 0.2.2.7-alpha.
6374 - Ship the asciidoc-helper file in the tarball, so that people can
6375 build from source if they want to, and touching the .1.txt files
6376 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6378 o Minor bugfixes (on 0.2.1.x or earlier):
6379 - Fix a dereference-then-NULL-check sequence when publishing
6380 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6382 - Fix another dereference-then-NULL-check sequence. Bugfix on
6383 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6384 - Make sure we treat potentially not NUL-terminated strings correctly.
6385 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6387 o Code simplifications and refactoring:
6388 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6389 compliant. Based on a patch from Christian Kujau.
6390 - Don't use sed in asciidoc-helper anymore.
6391 - Make the build process fail if asciidoc cannot be found and
6392 building with asciidoc isn't disabled.
6395 Changes in version 0.2.2.9-alpha - 2010-02-22
6396 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6397 location of a directory authority, and cleans up a bunch of small bugs.
6399 o Directory authority changes:
6400 - Change IP address for dannenberg (v3 directory authority), and
6401 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6402 service directory authority) from the list.
6405 - Make Tor work again on the latest OS X: when deciding whether to
6406 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6407 version at run-time, not compile time. We need to do this because
6408 Apple doesn't update its dev-tools headers when it updates its
6409 libraries in a security patch.
6410 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6411 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6412 a memory leak when requesting a hidden service descriptor we've
6413 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6415 - Authorities could be tricked into giving out the Exit flag to relays
6416 that didn't allow exiting to any ports. This bug could screw
6417 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6418 1238. Bug discovered by Martin Kowalczyk.
6419 - When freeing a session key, zero it out completely. We only zeroed
6420 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6421 patched by ekir. Fixes bug 1254.
6424 - Fix static compilation by listing the openssl libraries in the right
6425 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6426 - Resume handling .exit hostnames in a special way: originally we
6427 stripped the .exit part and used the requested exit relay. In
6428 0.2.2.1-alpha we stopped treating them in any special way, meaning
6429 if you use a .exit address then Tor will pass it on to the exit
6430 relay. Now we reject the .exit stream outright, since that behavior
6431 might be more expected by the user. Found and diagnosed by Scott
6432 Bennett and Downie on or-talk.
6433 - Don't spam the controller with events when we have no file
6434 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6435 for log messages was already solved from bug 748.)
6436 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6438 - Make the DNSPort option work with libevent 2.x. Don't alter the
6439 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6440 - Emit a GUARD DROPPED controller event for a case we missed.
6441 - Make more fields in the controller protocol case-insensitive, since
6442 control-spec.txt said they were.
6443 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6444 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6445 - Fix a spec conformance issue: the network-status-version token
6446 must be the first token in a v3 consensus or vote. Discovered by
6447 parakeep. Bugfix on 0.2.0.3-alpha.
6449 o Code simplifications and refactoring:
6450 - Generate our manpage and HTML documentation using Asciidoc. This
6451 change should make it easier to maintain the documentation, and
6453 - Remove the --enable-iphone option. According to reports from Marco
6454 Bonetti, Tor builds fine without any special tweaking on recent
6455 iPhone SDK versions.
6456 - Removed some unnecessary files from the source distribution. The
6457 AUTHORS file has now been merged into the people page on the
6458 website. The roadmaps and design doc can now be found in the
6459 projects directory in svn.
6460 - Enabled various circuit build timeout constants to be controlled
6461 by consensus parameters. Also set better defaults for these
6462 parameters based on experimentation on broadband and simulated
6466 - The 'EXTENDCIRCUIT' control port command can now be used with
6467 a circ id of 0 and no path. This feature will cause Tor to build
6468 a new 'fast' general purpose circuit using its own path selection
6470 - Added a BUILDTIMEOUT_SET controller event to describe changes
6471 to the circuit build timeout.
6472 - Future-proof the controller protocol a bit by ignoring keyword
6473 arguments we do not recognize.
6474 - Expand homedirs passed to tor-checkkey. This should silence a
6475 coverity complaint about passing a user-supplied string into
6476 open() without checking it.
6479 Changes in version 0.2.1.25 - 2010-03-16
6480 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6481 prevent relays from guessing their IP address correctly. It also fixes
6482 several minor potential security bugs.
6485 - Fix a regression from our patch for bug 1244 that caused relays
6486 to guess their IP address incorrectly if they didn't set Address
6487 in their torrc and/or their address fails to resolve. Bugfix on
6488 0.2.1.23; fixes bug 1269.
6489 - When freeing a session key, zero it out completely. We only zeroed
6490 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6491 patched by ekir. Fixes bug 1254.
6494 - Fix a dereference-then-NULL-check sequence when publishing
6495 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6497 - Fix another dereference-then-NULL-check sequence. Bugfix on
6498 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6499 - Make sure we treat potentially not NUL-terminated strings correctly.
6500 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6504 Changes in version 0.2.1.24 - 2010-02-21
6505 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6509 - Work correctly out-of-the-box with even more vendor-patched versions
6510 of OpenSSL. In particular, make it so Debian and OS X don't need
6511 customized patches to run/build.
6514 Changes in version 0.2.1.23 - 2010-02-13
6515 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6516 again on the latest OS X, and updates the location of a directory
6519 o Major bugfixes (performance):
6520 - We were selecting our guards uniformly at random, and then weighting
6521 which of our guards we'd use uniformly at random. This imbalance
6522 meant that Tor clients were severely limited on throughput (and
6523 probably latency too) by the first hop in their circuit. Now we
6524 select guards weighted by currently advertised bandwidth. We also
6525 automatically discard guards picked using the old algorithm. Fixes
6526 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6529 - Make Tor work again on the latest OS X: when deciding whether to
6530 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6531 version at run-time, not compile time. We need to do this because
6532 Apple doesn't update its dev-tools headers when it updates its
6533 libraries in a security patch.
6534 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6535 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6536 a memory leak when requesting a hidden service descriptor we've
6537 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6540 o Directory authority changes:
6541 - Change IP address for dannenberg (v3 directory authority), and
6542 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6543 service directory authority) from the list.
6546 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6547 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6550 - Avoid a mad rush at the beginning of each month when each client
6551 rotates half of its guards. Instead we spread the rotation out
6552 throughout the month, but we still avoid leaving a precise timestamp
6553 in the state file about when we first picked the guard. Improves
6554 over the behavior introduced in 0.1.2.17.
6557 Changes in version 0.2.2.8-alpha - 2010-01-26
6558 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6559 causing bridge relays to disappear. If you're running a bridge,
6563 - Fix a memory corruption bug on bridges that occured during the
6564 inclusion of stats data in extra-info descriptors. Also fix the
6565 interface for geoip_get_bridge_stats* to prevent similar bugs in
6566 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6567 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6570 - Ignore OutboundBindAddress when connecting to localhost.
6571 Connections to localhost need to come _from_ localhost, or else
6572 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6576 Changes in version 0.2.2.7-alpha - 2010-01-19
6577 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6578 as laying the groundwork for further relay-side performance fixes. It
6579 also starts cleaning up client behavior with respect to the EntryNodes,
6580 ExitNodes, and StrictNodes config options.
6582 This release also rotates two directory authority keys, due to a
6583 security breach of some of the Torproject servers.
6585 o Directory authority changes:
6586 - Rotate keys (both v3 identity and relay identity) for moria1
6589 o Major features (performance):
6590 - We were selecting our guards uniformly at random, and then weighting
6591 which of our guards we'd use uniformly at random. This imbalance
6592 meant that Tor clients were severely limited on throughput (and
6593 probably latency too) by the first hop in their circuit. Now we
6594 select guards weighted by currently advertised bandwidth. We also
6595 automatically discard guards picked using the old algorithm. Fixes
6596 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6597 - When choosing which cells to relay first, relays can now favor
6598 circuits that have been quiet recently, to provide lower latency
6599 for low-volume circuits. By default, relays enable or disable this
6600 feature based on a setting in the consensus. You can override
6601 this default by using the new "CircuitPriorityHalflife" config
6602 option. Design and code by Ian Goldberg, Can Tang, and Chris
6604 - Add separate per-conn write limiting to go with the per-conn read
6605 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6606 but never per-conn write limits.
6607 - New consensus params "bwconnrate" and "bwconnburst" to let us
6608 rate-limit client connections as they enter the network. It's
6609 controlled in the consensus so we can turn it on and off for
6610 experiments. It's starting out off. Based on proposal 163.
6612 o Major features (relay selection options):
6613 - Switch to a StrictNodes config option, rather than the previous
6614 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6615 "StrictExcludeNodes" option.
6616 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6617 change during a config reload, mark and discard all our origin
6618 circuits. This fix should address edge cases where we change the
6619 config options and but then choose a circuit that we created before
6621 - If EntryNodes or ExitNodes are set, be more willing to use an
6622 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6624 - Make EntryNodes config option much more aggressive even when
6625 StrictNodes is not set. Before it would prepend your requested
6626 entrynodes to your list of guard nodes, but feel free to use others
6627 after that. Now it chooses only from your EntryNodes if any of
6628 those are available, and only falls back to others if a) they're
6629 all down and b) StrictNodes is not set.
6630 - Now we refresh your entry guards from EntryNodes at each consensus
6631 fetch -- rather than just at startup and then they slowly rot as
6632 the network changes.
6635 - Stop bridge directory authorities from answering dbg-stability.txt
6636 directory queries, which would let people fetch a list of all
6637 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6640 - Log a notice when we get a new control connection. Now it's easier
6641 for security-conscious users to recognize when a local application
6642 is knocking on their controller door. Suggested by bug 1196.
6643 - New config option "CircuitStreamTimeout" to override our internal
6644 timeout schedule for how many seconds until we detach a stream from
6645 a circuit and try a new circuit. If your network is particularly
6646 slow, you might want to set this to a number like 60.
6647 - New controller command "getinfo config-text". It returns the
6648 contents that Tor would write if you send it a SAVECONF command,
6649 so the controller can write the file to disk itself.
6650 - New options for SafeLogging to allow scrubbing only log messages
6651 generated while acting as a relay.
6652 - Ship the bridges spec file in the tarball too.
6653 - Avoid a mad rush at the beginning of each month when each client
6654 rotates half of its guards. Instead we spread the rotation out
6655 throughout the month, but we still avoid leaving a precise timestamp
6656 in the state file about when we first picked the guard. Improves
6657 over the behavior introduced in 0.1.2.17.
6659 o Minor bugfixes (compiling):
6660 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6661 hides it. Bugfix on 0.2.2.6-alpha.
6662 - Fix compilation on Solaris by removing support for the
6663 DisableAllSwap config option. Solaris doesn't have an rlimit for
6664 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6667 o Minor bugfixes (crashes):
6668 - Do not segfault when writing buffer stats when we haven't observed
6669 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6671 - If we're in the pathological case where there's no exit bandwidth
6672 but there is non-exit bandwidth, or no guard bandwidth but there
6673 is non-guard bandwidth, don't crash during path selection. Bugfix
6675 - Fix an impossible-to-actually-trigger buffer overflow in relay
6676 descriptor generation. Bugfix on 0.1.0.15.
6678 o Minor bugfixes (privacy):
6679 - Fix an instance where a Tor directory mirror might accidentally
6680 log the IP address of a misbehaving Tor client. Bugfix on
6682 - Don't list Windows capabilities in relay descriptors. We never made
6683 use of them, and maybe it's a bad idea to publish them. Bugfix
6686 o Minor bugfixes (other):
6687 - Resolve an edge case in path weighting that could make us misweight
6688 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6689 - Fix statistics on client numbers by country as seen by bridges that
6690 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
6691 intervals instead of variable 12-to-48-hour intervals.
6692 - After we free an internal connection structure, overwrite it
6693 with a different memory value than we use for overwriting a freed
6694 internal circuit structure. Should help with debugging. Suggested
6696 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6700 - Remove the HSAuthorityRecordStats option that version 0 hidden
6701 service authorities could have used to track statistics of overall
6702 hidden service usage.
6705 Changes in version 0.2.1.22 - 2010-01-19
6706 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6707 authorities -- it would tell you its whole history of bridge descriptors
6708 if you make the right directory request. This stable update also
6709 rotates two of the seven v3 directory authority keys and locations.
6711 o Directory authority changes:
6712 - Rotate keys (both v3 identity and relay identity) for moria1
6716 - Stop bridge directory authorities from answering dbg-stability.txt
6717 directory queries, which would let people fetch a list of all
6718 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6721 Changes in version 0.2.1.21 - 2009-12-21
6722 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6723 library. If you use Tor on Linux / Unix and you're getting SSL
6724 renegotiation errors, upgrading should help. We also recommend an
6725 upgrade if you're an exit relay.
6728 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6729 handshake from working unless we explicitly tell OpenSSL that we
6730 are using SSL renegotiation safely. We are, of course, but OpenSSL
6731 0.9.8l won't work unless we say we are.
6732 - Avoid crashing if the client is trying to upload many bytes and the
6733 circuit gets torn down at the same time, or if the flip side
6734 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6737 - Do not refuse to learn about authority certs and v2 networkstatus
6738 documents that are older than the latest consensus. This bug might
6739 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6740 Spotted and fixed by xmux.
6741 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
6742 trigger platform-specific option misparsing case found by Coverity
6744 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
6745 trigger assert. Fixes bug 1173.
6748 Changes in version 0.2.2.6-alpha - 2009-11-19
6749 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
6750 support for the new lower-footprint "microdescriptor" directory design,
6751 future-proofing our consensus format against new hash functions or
6752 other changes, and an Android port. It also makes Tor compatible with
6753 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
6756 - Directory authorities can now create, vote on, and serve multiple
6757 parallel formats of directory data as part of their voting process.
6758 Partially implements Proposal 162: "Publish the consensus in
6760 - Directory authorities can now agree on and publish small summaries
6761 of router information that clients can use in place of regular
6762 server descriptors. This transition will eventually allow clients
6763 to use far less bandwidth for downloading information about the
6764 network. Begins the implementation of Proposal 158: "Clients
6765 download consensus + microdescriptors".
6766 - The directory voting system is now extensible to use multiple hash
6767 algorithms for signatures and resource selection. Newer formats
6768 are signed with SHA256, with a possibility for moving to a better
6769 hash algorithm in the future.
6770 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
6771 current and future memory pages via mlockall(). On supported
6772 platforms (modern Linux and probably BSD but not Windows or OS X),
6773 this should effectively disable any and all attempts to page out
6774 memory. This option requires that you start your Tor as root --
6775 if you use DisableAllSwap, please consider using the User option
6776 to properly reduce the privileges of your Tor.
6777 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
6778 to help Tor build correctly for Android phones.
6781 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6782 handshake from working unless we explicitly tell OpenSSL that we
6783 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
6784 won't work unless we say we are.
6787 - Fix a crash bug when trying to initialize the evdns module in
6788 Libevent 2. Bugfix on 0.2.1.16-rc.
6789 - Stop logging at severity 'warn' when some other Tor client tries
6790 to establish a circuit with us using weak DH keys. It's a protocol
6791 violation, but that doesn't mean ordinary users need to hear about
6792 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6793 - Do not refuse to learn about authority certs and v2 networkstatus
6794 documents that are older than the latest consensus. This bug might
6795 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6796 Spotted and fixed by xmux.
6797 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
6798 - If all authorities restart at once right before a consensus vote,
6799 nobody will vote about "Running", and clients will get a consensus
6800 with no usable relays. Instead, authorities refuse to build a
6801 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
6802 - If your relay can't keep up with the number of incoming create
6803 cells, it would log one warning per failure into your logs. Limit
6804 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6805 - Bridges now use "reject *:*" as their default exit policy. Bugfix
6806 on 0.2.0.3-alpha; fixes bug 1113.
6807 - Fix a memory leak on directory authorities during voting that was
6808 introduced in 0.2.2.1-alpha. Found via valgrind.
6811 Changes in version 0.2.1.20 - 2009-10-15
6812 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
6813 services at once, prepares for more performance improvements, and
6814 fixes a bunch of smaller bugs.
6816 The Windows and OS X bundles also include a more recent Vidalia,
6817 and switch from Privoxy to Polipo.
6819 The OS X installers are now drag and drop. It's best to un-install
6820 Tor/Vidalia and then install this new bundle, rather than upgrade. If
6821 you want to upgrade, you'll need to update the paths for Tor and Polipo
6822 in the Vidalia Settings window.
6825 - Send circuit or stream sendme cells when our window has decreased
6826 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6827 by Karsten when testing the "reduce circuit window" performance
6828 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6829 before the release of Tor 0.0.0. This is the new winner of the
6831 - Fix a remotely triggerable memory leak when a consensus document
6832 contains more than one signature from the same voter. Bugfix on
6834 - Avoid segfault in rare cases when finishing an introduction circuit
6835 as a client and finding out that we don't have an introduction key
6836 for it. Fixes bug 1073. Reported by Aaron Swartz.
6839 - Tor now reads the "circwindow" parameter out of the consensus,
6840 and uses that value for its circuit package window rather than the
6841 default of 1000 cells. Begins the implementation of proposal 168.
6843 o New directory authorities:
6844 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6846 - Move moria1 and tonga to alternate IP addresses.
6849 - Fix a signed/unsigned compile warning in 0.2.1.19.
6850 - Fix possible segmentation fault on directory authorities. Bugfix on
6852 - Fix an extremely rare infinite recursion bug that could occur if
6853 we tried to log a message after shutting down the log subsystem.
6854 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6855 - Fix an obscure bug where hidden services on 64-bit big-endian
6856 systems might mis-read the timestamp in v3 introduce cells, and
6857 refuse to connect back to the client. Discovered by "rotor".
6858 Bugfix on 0.2.1.6-alpha.
6859 - We were triggering a CLOCK_SKEW controller status event whenever
6860 we connect via the v2 connection protocol to any relay that has
6861 a wrong clock. Instead, we should only inform the controller when
6862 it's a trusted authority that claims our clock is wrong. Bugfix
6863 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6864 - We were telling the controller about CHECKING_REACHABILITY and
6865 REACHABILITY_FAILED status events whenever we launch a testing
6866 circuit or notice that one has failed. Instead, only tell the
6867 controller when we want to inform the user of overall success or
6868 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6870 - Don't warn when we're using a circuit that ends with a node
6871 excluded in ExcludeExitNodes, but the circuit is not used to access
6872 the outside world. This should help fix bug 1090. Bugfix on
6874 - Work around a small memory leak in some versions of OpenSSL that
6875 stopped the memory used by the hostname TLS extension from being
6879 - Add a "getinfo status/accepted-server-descriptor" controller
6880 command, which is the recommended way for controllers to learn
6881 whether our server descriptor has been successfully received by at
6882 least on directory authority. Un-recommend good-server-descriptor
6883 getinfo and status events until we have a better design for them.
6886 Changes in version 0.2.2.5-alpha - 2009-10-11
6887 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
6890 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
6892 o Directory authorities:
6893 - Temporarily (just for this release) move dizum to an alternate
6897 Changes in version 0.2.2.4-alpha - 2009-10-10
6898 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
6899 introduces a new unit test framework, shifts directry authority
6900 addresses around to reduce the impact from recent blocking events,
6901 and fixes a few smaller bugs.
6904 - Fix several more asserts in the circuit_build_times code, for
6905 example one that causes Tor to fail to start once we have
6906 accumulated 5000 build times in the state file. Bugfixes on
6907 0.2.2.2-alpha; fixes bug 1108.
6909 o New directory authorities:
6910 - Move moria1 and Tonga to alternate IP addresses.
6913 - Log SSL state transitions at debug level during handshake, and
6914 include SSL states in error messages. This may help debug future
6915 SSL handshake issues.
6916 - Add a new "Handshake" log domain for activities that happen
6917 during the TLS handshake.
6918 - Revert to the "June 3 2009" ip-to-country file. The September one
6919 seems to have removed most US IP addresses.
6920 - Directory authorities now reject Tor relays with versions less than
6921 0.1.2.14. This step cuts out four relays from the current network,
6922 none of which are very big.
6925 - Fix a couple of smaller issues with gathering statistics. Bugfixes
6927 - Fix two memory leaks in the error case of
6928 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
6929 - Don't count one-hop circuits when we're estimating how long it
6930 takes circuits to build on average. Otherwise we'll set our circuit
6931 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
6932 - Directory authorities no longer change their opinion of, or vote on,
6933 whether a router is Running, unless they have themselves been
6934 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
6937 o Code simplifications and refactoring:
6938 - Revise our unit tests to use the "tinytest" framework, so we
6939 can run tests in their own processes, have smarter setup/teardown
6940 code, and so on. The unit test code has moved to its own
6941 subdirectory, and has been split into multiple modules.
6944 Changes in version 0.2.2.3-alpha - 2009-09-23
6945 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
6948 - Fix an overzealous assert in our new circuit build timeout code.
6949 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
6952 - If the networkstatus consensus tells us that we should use a
6953 negative circuit package window, ignore it. Otherwise we'll
6954 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
6957 Changes in version 0.2.2.2-alpha - 2009-09-21
6958 Tor 0.2.2.2-alpha introduces our latest performance improvement for
6959 clients: Tor tracks the average time it takes to build a circuit, and
6960 avoids using circuits that take too long to build. For fast connections,
6961 this feature can cut your expected latency in half. For slow or flaky
6962 connections, it could ruin your Tor experience. Let us know if it does!
6965 - Tor now tracks how long it takes to build client-side circuits
6966 over time, and adapts its timeout to local network performance.
6967 Since a circuit that takes a long time to build will also provide
6968 bad performance, we get significant latency improvements by
6969 discarding the slowest 20% of circuits. Specifically, Tor creates
6970 circuits more aggressively than usual until it has enough data
6971 points for a good timeout estimate. Implements proposal 151.
6972 We are especially looking for reports (good and bad) from users with
6973 both EDGE and broadband connections that can move from broadband
6974 to EDGE and find out if the build-time data in the .tor/state gets
6975 reset without loss of Tor usability. You should also see a notice
6976 log message telling you that Tor has reset its timeout.
6977 - Directory authorities can now vote on arbitary integer values as
6978 part of the consensus process. This is designed to help set
6979 network-wide parameters. Implements proposal 167.
6980 - Tor now reads the "circwindow" parameter out of the consensus,
6981 and uses that value for its circuit package window rather than the
6982 default of 1000 cells. Begins the implementation of proposal 168.
6985 - Fix a remotely triggerable memory leak when a consensus document
6986 contains more than one signature from the same voter. Bugfix on
6990 - Fix an extremely rare infinite recursion bug that could occur if
6991 we tried to log a message after shutting down the log subsystem.
6992 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6993 - Fix parsing for memory or time units given without a space between
6994 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
6995 - A networkstatus vote must contain exactly one signature. Spec
6996 conformance issue. Bugfix on 0.2.0.3-alpha.
6997 - Fix an obscure bug where hidden services on 64-bit big-endian
6998 systems might mis-read the timestamp in v3 introduce cells, and
6999 refuse to connect back to the client. Discovered by "rotor".
7000 Bugfix on 0.2.1.6-alpha.
7001 - We were triggering a CLOCK_SKEW controller status event whenever
7002 we connect via the v2 connection protocol to any relay that has
7003 a wrong clock. Instead, we should only inform the controller when
7004 it's a trusted authority that claims our clock is wrong. Bugfix
7005 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7006 - We were telling the controller about CHECKING_REACHABILITY and
7007 REACHABILITY_FAILED status events whenever we launch a testing
7008 circuit or notice that one has failed. Instead, only tell the
7009 controller when we want to inform the user of overall success or
7010 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7012 - Don't warn when we're using a circuit that ends with a node
7013 excluded in ExcludeExitNodes, but the circuit is not used to access
7014 the outside world. This should help fix bug 1090, but more problems
7015 remain. Bugfix on 0.2.1.6-alpha.
7016 - Work around a small memory leak in some versions of OpenSSL that
7017 stopped the memory used by the hostname TLS extension from being
7019 - Make our 'torify' script more portable; if we have only one of
7020 'torsocks' or 'tsocks' installed, don't complain to the user;
7021 and explain our warning about tsocks better.
7024 - Add a "getinfo status/accepted-server-descriptor" controller
7025 command, which is the recommended way for controllers to learn
7026 whether our server descriptor has been successfully received by at
7027 least on directory authority. Un-recommend good-server-descriptor
7028 getinfo and status events until we have a better design for them.
7029 - Update to the "September 4 2009" ip-to-country file.
7032 Changes in version 0.2.2.1-alpha - 2009-08-26
7033 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7034 Tor clients to bootstrap on networks where only port 80 is reachable,
7035 makes it more straightforward to support hardware crypto accelerators,
7036 and starts the groundwork for gathering stats safely at relays.
7039 - Start the process of disabling ".exit" address notation, since it
7040 can be used for a variety of esoteric application-level attacks
7041 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7044 o New directory authorities:
7045 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7049 - New AccelName and AccelDir options add support for dynamic OpenSSL
7050 hardware crypto acceleration engines.
7051 - Tor now supports tunneling all of its outgoing connections over
7052 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7053 configuration options. Code by Christopher Davis.
7056 - Send circuit or stream sendme cells when our window has decreased
7057 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7058 by Karsten when testing the "reduce circuit window" performance
7059 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7060 before the release of Tor 0.0.0. This is the new winner of the
7063 o New options for gathering stats safely:
7064 - Directory mirrors that set "DirReqStatistics 1" write statistics
7065 about directory requests to disk every 24 hours. As compared to the
7066 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7067 1) stats are written to disk exactly every 24 hours; 2) estimated
7068 shares of v2 and v3 requests are determined as mean values, not at
7069 the end of a measurement period; 3) unresolved requests are listed
7070 with country code '??'; 4) directories also measure download times.
7071 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7072 number of exit streams and transferred bytes per port to disk every
7074 - Relays that set "CellStatistics 1" write statistics on how long
7075 cells spend in their circuit queues to disk every 24 hours.
7076 - Entry nodes that set "EntryStatistics 1" write statistics on the
7077 rough number and origins of connecting clients to disk every 24
7079 - Relays that write any of the above statistics to disk and set
7080 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7081 their extra-info documents.
7084 - New --digests command-line switch to output the digests of the
7085 source files Tor was built with.
7086 - The "torify" script now uses torsocks where available.
7087 - The memarea code now uses a sentinel value at the end of each area
7088 to make sure nothing writes beyond the end of an area. This might
7089 help debug some conceivable causes of bug 930.
7090 - Time and memory units in the configuration file can now be set to
7091 fractional units. For example, "2.5 GB" is now a valid value for
7093 - Certain Tor clients (such as those behind check.torproject.org) may
7094 want to fetch the consensus in an extra early manner. To enable this
7095 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7096 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7097 as only certain clients who must have this information sooner should
7099 - Instead of adding the svn revision to the Tor version string, report
7100 the git commit (when we're building from a git checkout).
7103 - If any of the v3 certs we download are unparseable, we should
7104 actually notice the failure so we don't retry indefinitely. Bugfix
7105 on 0.2.0.x; reported by "rotator".
7106 - If the cached cert file is unparseable, warn but don't exit.
7107 - Fix possible segmentation fault on directory authorities. Bugfix on
7109 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7110 Might help diagnosing bug 1051.
7112 o Deprecated and removed features:
7113 - The controller no longer accepts the old obsolete "addr-mappings/"
7114 or "unregistered-servers-" GETINFO values.
7115 - Hidden services no longer publish version 0 descriptors, and clients
7116 do not request or use version 0 descriptors. However, the old hidden
7117 service authorities still accept and serve version 0 descriptors
7118 when contacted by older hidden services/clients.
7119 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7120 always on; using them is necessary for correct forward-compatible
7122 - Remove support for .noconnect style addresses. Nobody was using
7123 them, and they provided another avenue for detecting Tor users
7124 via application-level web tricks.
7126 o Packaging changes:
7127 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7128 installer bundles. See
7129 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7130 for details of what's new in Vidalia 0.2.3.
7131 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7132 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7133 configuration file, rather than the old Privoxy.
7134 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7135 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7136 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7137 better compatibility with OS X 10.6, aka Snow Leopard.
7138 - OS X Vidalia Bundle: The multi-package installer is now replaced
7139 by a simple drag and drop to the /Applications folder. This change
7140 occurred with the upgrade to Vidalia 0.2.3.
7143 Changes in version 0.2.1.19 - 2009-07-28
7144 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7145 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7148 - Make accessing hidden services on 0.2.1.x work right again.
7149 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7150 part of patch provided by "optimist".
7153 - When a relay/bridge is writing out its identity key fingerprint to
7154 the "fingerprint" file and to its logs, write it without spaces. Now
7155 it will look like the fingerprints in our bridges documentation,
7156 and confuse fewer users.
7159 - Relays no longer publish a new server descriptor if they change
7160 their MaxAdvertisedBandwidth config option but it doesn't end up
7161 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7162 fixes bug 1026. Patch from Sebastian.
7163 - Avoid leaking memory every time we get a create cell but we have
7164 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7165 fixes bug 1034. Reported by BarkerJr.
7168 Changes in version 0.2.1.18 - 2009-07-24
7169 Tor 0.2.1.18 lays the foundations for performance improvements,
7170 adds status events to help users diagnose bootstrap problems, adds
7171 optional authentication/authorization for hidden services, fixes a
7172 variety of potential anonymity problems, and includes a huge pile of
7173 other features and bug fixes.
7176 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7179 Changes in version 0.2.1.17-rc - 2009-07-07
7180 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7181 candidate for the 0.2.1.x series. It lays the groundwork for further
7182 client performance improvements, and also fixes a big bug with directory
7183 authorities that were causing them to assign Guard and Stable flags
7186 The Windows bundles also finally include the geoip database that we
7187 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7188 should actually install Torbutton rather than giving you a cryptic
7189 failure message (oops).
7192 - Clients now use the bandwidth values in the consensus, rather than
7193 the bandwidth values in each relay descriptor. This approach opens
7194 the door to more accurate bandwidth estimates once the directory
7195 authorities start doing active measurements. Implements more of
7199 - When Tor clients restart after 1-5 days, they discard all their
7200 cached descriptors as too old, but they still use the cached
7201 consensus document. This approach is good for robustness, but
7202 bad for performance: since they don't know any bandwidths, they
7203 end up choosing at random rather than weighting their choice by
7204 speed. Fixed by the above feature of putting bandwidths in the
7205 consensus. Bugfix on 0.2.0.x.
7206 - Directory authorities were neglecting to mark relays down in their
7207 internal histories if the relays fall off the routerlist without
7208 ever being found unreachable. So there were relays in the histories
7209 that haven't been seen for eight months, and are listed as being
7210 up for eight months. This wreaked havoc on the "median wfu"
7211 and "median mtbf" calculations, in turn making Guard and Stable
7212 flags very wrong, hurting network performance. Fixes bugs 696 and
7213 969. Bugfix on 0.2.0.6-alpha.
7216 - Serve the DirPortFrontPage page even when we have been approaching
7217 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7218 - The control port would close the connection before flushing long
7219 replies, such as the network consensus, if a QUIT command was issued
7220 before the reply had completed. Now, the control port flushes all
7221 pending replies before closing the connection. Also fixed a spurious
7222 warning when a QUIT command is issued after a malformed or rejected
7223 AUTHENTICATE command, but before the connection was closed. Patch
7224 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7225 - When we can't find an intro key for a v2 hidden service descriptor,
7226 fall back to the v0 hidden service descriptor and log a bug message.
7227 Workaround for bug 1024.
7228 - Fix a log message that did not respect the SafeLogging option.
7232 - If we're a relay and we change our IP address, be more verbose
7233 about the reason that made us change. Should help track down
7234 further bugs for relays on dynamic IP addresses.
7237 Changes in version 0.2.0.35 - 2009-06-24
7239 - Avoid crashing in the presence of certain malformed descriptors.
7240 Found by lark, and by automated fuzzing.
7241 - Fix an edge case where a malicious exit relay could convince a
7242 controller that the client's DNS question resolves to an internal IP
7243 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7246 - Finally fix the bug where dynamic-IP relays disappear when their
7247 IP address changes: directory mirrors were mistakenly telling
7248 them their old address if they asked via begin_dir, so they
7249 never got an accurate answer about their new address, so they
7250 just vanished after a day. For belt-and-suspenders, relays that
7251 don't set Address in their config now avoid using begin_dir for
7252 all direct connections. Should fix bugs 827, 883, and 900.
7253 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7254 that would occur on some exit nodes when DNS failures and timeouts
7255 occurred in certain patterns. Fix for bug 957.
7258 - When starting with a cache over a few days old, do not leak
7259 memory for the obsolete router descriptors in it. Bugfix on
7260 0.2.0.33; fixes bug 672.
7261 - Hidden service clients didn't use a cached service descriptor that
7262 was older than 15 minutes, but wouldn't fetch a new one either,
7263 because there was already one in the cache. Now, fetch a v2
7264 descriptor unless the same descriptor was added to the cache within
7265 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7268 Changes in version 0.2.1.16-rc - 2009-06-20
7269 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7270 a bunch of minor bugs.
7273 - Fix an edge case where a malicious exit relay could convince a
7274 controller that the client's DNS question resolves to an internal IP
7275 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7277 o Major performance improvements (on 0.2.0.x):
7278 - Disable and refactor some debugging checks that forced a linear scan
7279 over the whole server-side DNS cache. These accounted for over 50%
7280 of CPU time on a relatively busy exit node's gprof profile. Found
7282 - Disable some debugging checks that appeared in exit node profile
7286 - Update to the "June 3 2009" ip-to-country file.
7287 - Do not have tor-resolve automatically refuse all .onion addresses;
7288 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7290 o Minor bugfixes (on 0.2.0.x):
7291 - Log correct error messages for DNS-related network errors on
7293 - Fix a race condition that could cause crashes or memory corruption
7294 when running as a server with a controller listening for log
7296 - Avoid crashing when we have a policy specified in a DirPolicy or
7297 SocksPolicy or ReachableAddresses option with ports set on it,
7298 and we re-load the policy. May fix bug 996.
7299 - Hidden service clients didn't use a cached service descriptor that
7300 was older than 15 minutes, but wouldn't fetch a new one either,
7301 because there was already one in the cache. Now, fetch a v2
7302 descriptor unless the same descriptor was added to the cache within
7303 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7305 o Minor bugfixes (on 0.2.1.x):
7306 - Don't warn users about low port and hibernation mix when they
7307 provide a *ListenAddress directive to fix that. Bugfix on
7309 - When switching back and forth between bridge mode, do not start
7310 gathering GeoIP data until two hours have passed.
7311 - Do not complain that the user has requested an excluded node as
7312 an exit when the node is not really an exit. This could happen
7313 because the circuit was for testing, or an introduction point.
7317 Changes in version 0.2.1.15-rc - 2009-05-25
7318 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7319 series. It fixes a major bug on fast exit relays, as well as a variety
7322 o Major bugfixes (on 0.2.0.x):
7323 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7324 that would occur on some exit nodes when DNS failures and timeouts
7325 occurred in certain patterns. Fix for bug 957.
7327 o Minor bugfixes (on 0.2.0.x):
7328 - Actually return -1 in the error case for read_bandwidth_usage().
7329 Harmless bug, since we currently don't care about the return value
7330 anywhere. Bugfix on 0.2.0.9-alpha.
7331 - Provide a more useful log message if bug 977 (related to buffer
7332 freelists) ever reappears, and do not crash right away.
7333 - Fix an assertion failure on 64-bit platforms when we allocated
7334 memory right up to the end of a memarea, then realigned the memory
7335 one step beyond the end. Fixes a possible cause of bug 930.
7336 - Protect the count of open sockets with a mutex, so we can't
7337 corrupt it when two threads are closing or opening sockets at once.
7338 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7339 - Don't allow a bridge to publish its router descriptor to a
7340 non-bridge directory authority. Fixes part of bug 932.
7341 - When we change to or from being a bridge, reset our counts of
7342 client usage by country. Fixes bug 932.
7343 - Fix a bug that made stream bandwidth get misreported to the
7345 - Stop using malloc_usable_size() to use more area than we had
7346 actually allocated: it was safe, but made valgrind really unhappy.
7347 - Fix a memory leak when v3 directory authorities load their keys
7348 and cert from disk. Bugfix on 0.2.0.1-alpha.
7350 o Minor bugfixes (on 0.2.1.x):
7351 - Fix use of freed memory when deciding to mark a non-addable
7352 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7355 Changes in version 0.2.1.14-rc - 2009-04-12
7356 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7357 series. It begins fixing some major performance problems, and also
7358 finally addresses the bug that was causing relays on dynamic IP
7359 addresses to fall out of the directory.
7362 - Clients replace entry guards that were chosen more than a few months
7363 ago. This change should significantly improve client performance,
7364 especially once more people upgrade, since relays that have been
7365 a guard for a long time are currently overloaded.
7367 o Major bugfixes (on 0.2.0):
7368 - Finally fix the bug where dynamic-IP relays disappear when their
7369 IP address changes: directory mirrors were mistakenly telling
7370 them their old address if they asked via begin_dir, so they
7371 never got an accurate answer about their new address, so they
7372 just vanished after a day. For belt-and-suspenders, relays that
7373 don't set Address in their config now avoid using begin_dir for
7374 all direct connections. Should fix bugs 827, 883, and 900.
7375 - Relays were falling out of the networkstatus consensus for
7376 part of a day if they changed their local config but the
7377 authorities discarded their new descriptor as "not sufficiently
7378 different". Now directory authorities accept a descriptor as changed
7379 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7381 - Avoid crashing in the presence of certain malformed descriptors.
7382 Found by lark, and by automated fuzzing.
7385 - When generating circuit events with verbose nicknames for
7386 controllers, try harder to look up nicknames for routers on a
7387 circuit. (Previously, we would look in the router descriptors we had
7388 for nicknames, but not in the consensus.) Partial fix for bug 941.
7389 - If the bridge config line doesn't specify a port, assume 443.
7390 This makes bridge lines a bit smaller and easier for users to
7392 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7393 bytes (aka 20KB/s), to match our documentation. Also update
7394 directory authorities so they always assign the Fast flag to relays
7395 with 20KB/s of capacity. Now people running relays won't suddenly
7396 find themselves not seeing any use, if the network gets faster
7398 - Update to the "April 3 2009" ip-to-country file.
7401 - Avoid trying to print raw memory to the logs when we decide to
7402 give up on downloading a given relay descriptor. Bugfix on
7404 - In tor-resolve, when the Tor client to use is specified by
7405 <hostname>:<port>, actually use the specified port rather than
7406 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7407 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7408 - When starting with a cache over a few days old, do not leak
7409 memory for the obsolete router descriptors in it. Bugfix on
7411 - Avoid double-free on list of successfully uploaded hidden
7412 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7413 - Change memarea_strndup() implementation to work even when
7414 duplicating a string at the end of a page. This bug was
7415 harmless for now, but could have meant crashes later. Fix by
7416 lark. Bugfix on 0.2.1.1-alpha.
7417 - Limit uploaded directory documents to be 16M rather than 500K.
7418 The directory authorities were refusing v3 consensus votes from
7419 other authorities, since the votes are now 504K. Fixes bug 959;
7420 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7421 - Directory authorities should never send a 503 "busy" response to
7422 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7426 Changes in version 0.2.1.13-alpha - 2009-03-09
7427 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7428 cleanups. We're finally getting close to a release candidate.
7431 - Correctly update the list of which countries we exclude as
7432 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7433 lark. Bugfix on 0.2.1.6-alpha.
7435 o Minor bugfixes (on 0.2.0.x and earlier):
7436 - Automatically detect MacOSX versions earlier than 10.4.0, and
7437 disable kqueue from inside Tor when running with these versions.
7438 We previously did this from the startup script, but that was no
7439 help to people who didn't use the startup script. Resolves bug 863.
7440 - When we had picked an exit node for a connection, but marked it as
7441 "optional", and it turned out we had no onion key for the exit,
7442 stop wanting that exit and try again. This situation may not
7443 be possible now, but will probably become feasible with proposal
7444 158. Spotted by rovv. Fixes another case of bug 752.
7445 - Clients no longer cache certificates for authorities they do not
7446 recognize. Bugfix on 0.2.0.9-alpha.
7447 - When we can't transmit a DNS request due to a network error, retry
7448 it after a while, and eventually transmit a failing response to
7449 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7450 - If the controller claimed responsibility for a stream, but that
7451 stream never finished making its connection, it would live
7452 forever in circuit_wait state. Now we close it after SocksTimeout
7453 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7454 - Drop begin cells to a hidden service if they come from the middle
7455 of a circuit. Patch from lark.
7456 - When we erroneously receive two EXTEND cells for the same circuit
7457 ID on the same connection, drop the second. Patch from lark.
7458 - Fix a crash that occurs on exit nodes when a nameserver request
7459 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7460 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7462 - Do not assume that a stack-allocated character array will be
7463 64-bit aligned on platforms that demand that uint64_t access is
7464 aligned. Possible fix for bug 604.
7465 - Parse dates and IPv4 addresses in a locale- and libc-independent
7466 manner, to avoid platform-dependent behavior on malformed input.
7467 - Build correctly when configured to build outside the main source
7468 path. Patch from Michael Gold.
7469 - We were already rejecting relay begin cells with destination port
7470 of 0. Now also reject extend cells with destination port or address
7471 of 0. Suggested by lark.
7473 o Minor bugfixes (on 0.2.1.x):
7474 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7475 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7476 - If we're an exit node, scrub the IP address to which we are exiting
7477 in the logs. Bugfix on 0.2.1.8-alpha.
7480 - On Linux, use the prctl call to re-enable core dumps when the user
7482 - New controller event NEWCONSENSUS that lists the networkstatus
7483 lines for every recommended relay. Now controllers like Torflow
7484 can keep up-to-date on which relays they should be using.
7485 - Update to the "February 26 2009" ip-to-country file.
7488 Changes in version 0.2.0.34 - 2009-02-08
7489 Tor 0.2.0.34 features several more security-related fixes. You should
7490 upgrade, especially if you run an exit relay (remote crash) or a
7491 directory authority (remote infinite loop), or you're on an older
7492 (pre-XP) or not-recently-patched Windows (remote exploit).
7494 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7495 have many known flaws, and nobody should be using them. You should
7496 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7497 stop using those packages and upgrade anyway.
7500 - Fix an infinite-loop bug on handling corrupt votes under certain
7501 circumstances. Bugfix on 0.2.0.8-alpha.
7502 - Fix a temporary DoS vulnerability that could be performed by
7503 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7504 - Avoid a potential crash on exit nodes when processing malformed
7505 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7506 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7507 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7510 - Fix compilation on systems where time_t is a 64-bit integer.
7511 Patch from Matthias Drochner.
7512 - Don't consider expiring already-closed client connections. Fixes
7513 bug 893. Bugfix on 0.0.2pre20.
7516 Changes in version 0.2.1.12-alpha - 2009-02-08
7517 Tor 0.2.1.12-alpha features several more security-related fixes. You
7518 should upgrade, especially if you run an exit relay (remote crash) or
7519 a directory authority (remote infinite loop), or you're on an older
7520 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7521 includes a big pile of minor bugfixes and cleanups.
7524 - Fix an infinite-loop bug on handling corrupt votes under certain
7525 circumstances. Bugfix on 0.2.0.8-alpha.
7526 - Fix a temporary DoS vulnerability that could be performed by
7527 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7528 - Avoid a potential crash on exit nodes when processing malformed
7529 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7532 - Let controllers actually ask for the "clients_seen" event for
7533 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7534 reported by Matt Edman.
7535 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7537 - Fix a bug in address parsing that was preventing bridges or hidden
7538 service targets from being at IPv6 addresses.
7539 - Solve a bug that kept hardware crypto acceleration from getting
7540 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7542 - Remove a bash-ism from configure.in to build properly on non-Linux
7543 platforms. Bugfix on 0.2.1.1-alpha.
7544 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7545 headers. Bugfix on 0.2.0.10-alpha.
7546 - Don't consider expiring already-closed client connections. Fixes
7547 bug 893. Bugfix on 0.0.2pre20.
7548 - Fix another interesting corner-case of bug 891 spotted by rovv:
7549 Previously, if two hosts had different amounts of clock drift, and
7550 one of them created a new connection with just the wrong timing,
7551 the other might decide to deprecate the new connection erroneously.
7552 Bugfix on 0.1.1.13-alpha.
7553 - Resolve a very rare crash bug that could occur when the user forced
7554 a nameserver reconfiguration during the middle of a nameserver
7555 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7556 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7557 Bugfix on 0.2.1.7-alpha.
7558 - If we're using bridges and our network goes away, be more willing
7559 to forgive our bridges and try again when we get an application
7560 request. Bugfix on 0.2.0.x.
7563 - Support platforms where time_t is 64 bits long. (Congratulations,
7564 NetBSD!) Patch from Matthias Drochner.
7565 - Add a 'getinfo status/clients-seen' controller command, in case
7566 controllers want to hear clients_seen events but connect late.
7569 - Disable GCC's strict alias optimization by default, to avoid the
7570 likelihood of its introducing subtle bugs whenever our code violates
7571 the letter of C99's alias rules.
7574 Changes in version 0.2.0.33 - 2009-01-21
7575 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7576 useful to users. It also finally fixes a bug where a relay or client
7577 that's been off for many days would take a long time to bootstrap.
7579 This update also fixes an important security-related bug reported by
7580 Ilja van Sprundel. You should upgrade. (We'll send out more details
7581 about the bug once people have had some time to upgrade.)
7584 - Fix a heap-corruption bug that may be remotely triggerable on
7585 some platforms. Reported by Ilja van Sprundel.
7588 - When a stream at an exit relay is in state "resolving" or
7589 "connecting" and it receives an "end" relay cell, the exit relay
7590 would silently ignore the end cell and not close the stream. If
7591 the client never closes the circuit, then the exit relay never
7592 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7594 - When sending CREATED cells back for a given circuit, use a 64-bit
7595 connection ID to find the right connection, rather than an addr:port
7596 combination. Now that we can have multiple OR connections between
7597 the same ORs, it is no longer possible to use addr:port to uniquely
7598 identify a connection.
7599 - Bridge relays that had DirPort set to 0 would stop fetching
7600 descriptors shortly after startup, and then briefly resume
7601 after a new bandwidth test and/or after publishing a new bridge
7602 descriptor. Bridge users that try to bootstrap from them would
7603 get a recent networkstatus but would get descriptors from up to
7604 18 hours earlier, meaning most of the descriptors were obsolete
7605 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7606 - Prevent bridge relays from serving their 'extrainfo' document
7607 to anybody who asks, now that extrainfo docs include potentially
7608 sensitive aggregated client geoip summaries. Bugfix on
7610 - If the cached networkstatus consensus is more than five days old,
7611 discard it rather than trying to use it. In theory it could be
7612 useful because it lists alternate directory mirrors, but in practice
7613 it just means we spend many minutes trying directory mirrors that
7614 are long gone from the network. Also discard router descriptors as
7615 we load them if they are more than five days old, since the onion
7616 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7619 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7620 could make gcc generate non-functional binary search code. Bugfix
7622 - Build correctly on platforms without socklen_t.
7623 - Compile without warnings on solaris.
7624 - Avoid potential crash on internal error during signature collection.
7625 Fixes bug 864. Patch from rovv.
7626 - Correct handling of possible malformed authority signing key
7627 certificates with internal signature types. Fixes bug 880.
7628 Bugfix on 0.2.0.3-alpha.
7629 - Fix a hard-to-trigger resource leak when logging credential status.
7631 - When we can't initialize DNS because the network is down, do not
7632 automatically stop Tor from starting. Instead, we retry failed
7633 dns_init() every 10 minutes, and change the exit policy to reject
7634 *:* until one succeeds. Fixes bug 691.
7635 - Use 64 bits instead of 32 bits for connection identifiers used with
7636 the controller protocol, to greatly reduce risk of identifier reuse.
7637 - When we're choosing an exit node for a circuit, and we have
7638 no pending streams, choose a good general exit rather than one that
7639 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7640 - Fix another case of assuming, when a specific exit is requested,
7641 that we know more than the user about what hosts it allows.
7642 Fixes one case of bug 752. Patch from rovv.
7643 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7644 seconds. Warn the user if lower values are given in the
7645 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7646 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7647 user if lower values are given in the configuration. Bugfix on
7648 0.1.1.17-rc. Patch by Sebastian.
7649 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7650 the cache because we already had a v0 descriptor with the same ID.
7651 Bugfix on 0.2.0.18-alpha.
7652 - Fix a race condition when freeing keys shared between main thread
7653 and CPU workers that could result in a memory leak. Bugfix on
7654 0.1.0.1-rc. Fixes bug 889.
7655 - Send a valid END cell back when a client tries to connect to a
7656 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7657 840. Patch from rovv.
7658 - Check which hops rendezvous stream cells are associated with to
7659 prevent possible guess-the-streamid injection attacks from
7660 intermediate hops. Fixes another case of bug 446. Based on patch
7662 - If a broken client asks a non-exit router to connect somewhere,
7663 do not even do the DNS lookup before rejecting the connection.
7664 Fixes another case of bug 619. Patch from rovv.
7665 - When a relay gets a create cell it can't decrypt (e.g. because it's
7666 using the wrong onion key), we were dropping it and letting the
7667 client time out. Now actually answer with a destroy cell. Fixes
7668 bug 904. Bugfix on 0.0.2pre8.
7670 o Minor bugfixes (hidden services):
7671 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7672 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7675 - Report the case where all signatures in a detached set are rejected
7676 differently than the case where there is an error handling the
7678 - When we realize that another process has modified our cached
7679 descriptors, print out a more useful error message rather than
7680 triggering an assertion. Fixes bug 885. Patch from Karsten.
7681 - Implement the 0x20 hack to better resist DNS poisoning: set the
7682 case on outgoing DNS requests randomly, and reject responses that do
7683 not match the case correctly. This logic can be disabled with the
7684 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7685 of servers that do not reliably preserve case in replies. See
7686 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7688 - Check DNS replies for more matching fields to better resist DNS
7690 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7691 compress cells, which are basically all encrypted, compressed, or
7695 Changes in version 0.2.1.11-alpha - 2009-01-20
7696 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
7697 week it will take a long time to bootstrap again" bug. It also fixes
7698 an important security-related bug reported by Ilja van Sprundel. You
7699 should upgrade. (We'll send out more details about the bug once people
7700 have had some time to upgrade.)
7703 - Fix a heap-corruption bug that may be remotely triggerable on
7704 some platforms. Reported by Ilja van Sprundel.
7707 - Discard router descriptors as we load them if they are more than
7708 five days old. Otherwise if Tor is off for a long time and then
7709 starts with cached descriptors, it will try to use the onion
7710 keys in those obsolete descriptors when building circuits. Bugfix
7711 on 0.2.0.x. Fixes bug 887.
7714 - Try to make sure that the version of Libevent we're running with
7715 is binary-compatible with the one we built with. May address bug
7717 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
7718 for bug 905. Bugfix on 0.2.1.7-alpha.
7719 - Add a new --enable-local-appdata configuration switch to change
7720 the default location of the datadir on win32 from APPDATA to
7721 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7722 entirely. Patch from coderman.
7725 - Make outbound DNS packets respect the OutboundBindAddress setting.
7726 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7727 - When our circuit fails at the first hop (e.g. we get a destroy
7728 cell back), avoid using that OR connection anymore, and also
7729 tell all the one-hop directory requests waiting for it that they
7730 should fail. Bugfix on 0.2.1.3-alpha.
7731 - In the torify(1) manpage, mention that tsocks will leak your
7735 Changes in version 0.2.1.10-alpha - 2009-01-06
7736 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
7737 would make the bridge relay not so useful if it had DirPort set to 0,
7738 and one that could let an attacker learn a little bit of information
7739 about the bridge's users), and a bug that would cause your Tor relay
7740 to ignore a circuit create request it can't decrypt (rather than reply
7741 with an error). It also fixes a wide variety of other bugs.
7744 - If the cached networkstatus consensus is more than five days old,
7745 discard it rather than trying to use it. In theory it could
7746 be useful because it lists alternate directory mirrors, but in
7747 practice it just means we spend many minutes trying directory
7748 mirrors that are long gone from the network. Helps bug 887 a bit;
7750 - Bridge relays that had DirPort set to 0 would stop fetching
7751 descriptors shortly after startup, and then briefly resume
7752 after a new bandwidth test and/or after publishing a new bridge
7753 descriptor. Bridge users that try to bootstrap from them would
7754 get a recent networkstatus but would get descriptors from up to
7755 18 hours earlier, meaning most of the descriptors were obsolete
7756 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7757 - Prevent bridge relays from serving their 'extrainfo' document
7758 to anybody who asks, now that extrainfo docs include potentially
7759 sensitive aggregated client geoip summaries. Bugfix on
7763 - New controller event "clients_seen" to report a geoip-based summary
7764 of which countries we've seen clients from recently. Now controllers
7765 like Vidalia can show bridge operators that they're actually making
7767 - Build correctly against versions of OpenSSL 0.9.8 or later built
7768 without support for deprecated functions.
7769 - Update to the "December 19 2008" ip-to-country file.
7771 o Minor bugfixes (on 0.2.0.x):
7772 - Authorities now vote for the Stable flag for any router whose
7773 weighted MTBF is at least 5 days, regardless of the mean MTBF.
7774 - Do not remove routers as too old if we do not have any consensus
7775 document. Bugfix on 0.2.0.7-alpha.
7776 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7777 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7778 - When an exit relay resolves a stream address to a local IP address,
7779 do not just keep retrying that same exit relay over and
7780 over. Instead, just close the stream. Addresses bug 872. Bugfix
7781 on 0.2.0.32. Patch from rovv.
7782 - If a hidden service sends us an END cell, do not consider
7783 retrying the connection; just close it. Patch from rovv.
7784 - When we made bridge authorities stop serving bridge descriptors over
7785 unencrypted links, we also broke DirPort reachability testing for
7786 bridges. So bridges with a non-zero DirPort were printing spurious
7787 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
7788 - When a relay gets a create cell it can't decrypt (e.g. because it's
7789 using the wrong onion key), we were dropping it and letting the
7790 client time out. Now actually answer with a destroy cell. Fixes
7791 bug 904. Bugfix on 0.0.2pre8.
7792 - Squeeze 2-5% out of client performance (according to oprofile) by
7793 improving the implementation of some policy-manipulation functions.
7795 o Minor bugfixes (on 0.2.1.x):
7796 - Make get_interface_address() function work properly again; stop
7797 guessing the wrong parts of our address as our address.
7798 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
7799 send on that circuit. Otherwise we might violate the proposal-110
7800 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
7802 - When we're sending non-EXTEND cells to the first hop in a circuit,
7803 for example to use an encrypted directory connection, we don't need
7804 to use RELAY_EARLY cells: the first hop knows what kind of cell
7805 it is, and nobody else can even see the cell type. Conserving
7806 RELAY_EARLY cells makes it easier to cannibalize circuits like
7808 - Stop logging nameserver addresses in reverse order.
7809 - If we are retrying a directory download slowly over and over, do
7810 not automatically give up after the 254th failure. Bugfix on
7812 - Resume reporting accurate "stream end" reasons to the local control
7813 port. They were lost in the changes for Proposal 148. Bugfix on
7816 o Deprecated and removed features:
7817 - The old "tor --version --version" command, which would print out
7818 the subversion "Id" of most of the source files, is now removed. It
7819 turned out to be less useful than we'd expected, and harder to
7822 o Code simplifications and refactoring:
7823 - Change our header file guard macros to be less likely to conflict
7824 with system headers. Adam Langley noticed that we were conflicting
7825 with log.h on Android.
7826 - Tool-assisted documentation cleanup. Nearly every function or
7827 static variable in Tor should have its own documentation now.
7830 Changes in version 0.2.1.9-alpha - 2008-12-25
7831 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
7833 o New directory authorities:
7834 - gabelmoo (the authority run by Karsten Loesing) now has a new
7838 - Never use a connection with a mismatched address to extend a
7839 circuit, unless that connection is canonical. A canonical
7840 connection is one whose address is authenticated by the router's
7841 identity key, either in a NETINFO cell or in a router descriptor.
7842 - Avoid a possible memory corruption bug when receiving hidden service
7843 descriptors. Bugfix on 0.2.1.6-alpha.
7846 - Fix a logic error that would automatically reject all but the first
7847 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
7848 part of bug 813/868. Bug spotted by coderman.
7849 - When a stream at an exit relay is in state "resolving" or
7850 "connecting" and it receives an "end" relay cell, the exit relay
7851 would silently ignore the end cell and not close the stream. If
7852 the client never closes the circuit, then the exit relay never
7853 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
7855 - When we can't initialize DNS because the network is down, do not
7856 automatically stop Tor from starting. Instead, retry failed
7857 dns_init() every 10 minutes, and change the exit policy to reject
7858 *:* until one succeeds. Fixes bug 691.
7861 - Give a better error message when an overzealous init script says
7862 "sudo -u username tor --user username". Makes Bug 882 easier for
7864 - When a directory authority gives us a new guess for our IP address,
7865 log which authority we used. Hopefully this will help us debug
7866 the recent complaints about bad IP address guesses.
7867 - Detect svn revision properly when we're using git-svn.
7868 - Try not to open more than one descriptor-downloading connection
7869 to an authority at once. This should reduce load on directory
7870 authorities. Fixes bug 366.
7871 - Add cross-certification to newly generated certificates, so that
7872 a signing key is enough information to look up a certificate.
7873 Partial implementation of proposal 157.
7874 - Start serving certificates by <identity digest, signing key digest>
7875 pairs. Partial implementation of proposal 157.
7876 - Clients now never report any stream end reason except 'MISC'.
7877 Implements proposal 148.
7878 - On platforms with a maximum syslog string length, truncate syslog
7879 messages to that length ourselves, rather than relying on the
7880 system to do it for us.
7881 - Optimize out calls to time(NULL) that occur for every IO operation,
7882 or for every cell. On systems where time() is a slow syscall,
7883 this fix will be slightly helpful.
7884 - Exit servers can now answer resolve requests for ip6.arpa addresses.
7885 - When we download a descriptor that we then immediately (as
7886 a directory authority) reject, do not retry downloading it right
7887 away. Should save some bandwidth on authorities. Fix for bug
7888 888. Patch by Sebastian Hahn.
7889 - When a download gets us zero good descriptors, do not notify
7890 Tor that new directory information has arrived.
7891 - Avoid some nasty corner cases in the logic for marking connections
7892 as too old or obsolete or noncanonical for circuits. Partial
7895 o Minor features (controller):
7896 - New CONSENSUS_ARRIVED event to note when a new consensus has
7897 been fetched and validated.
7898 - When we realize that another process has modified our cached
7899 descriptors file, print out a more useful error message rather
7900 than triggering an assertion. Fixes bug 885. Patch from Karsten.
7901 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
7902 controllers to prevent SIGHUP from reloading the
7903 configuration. Fixes bug 856.
7906 - Resume using the correct "REASON=" stream when telling the
7907 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
7908 - When a canonical connection appears later in our internal list
7909 than a noncanonical one for a given OR ID, always use the
7910 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
7912 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7913 seconds. Warn the user if lower values are given in the
7914 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7915 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7916 user if lower values are given in the configuration. Bugfix on
7917 0.1.1.17-rc. Patch by Sebastian.
7918 - Fix a race condition when freeing keys shared between main thread
7919 and CPU workers that could result in a memory leak. Bugfix on
7920 0.1.0.1-rc. Fixes bug 889.
7922 o Minor bugfixes (hidden services):
7923 - Do not throw away existing introduction points on SIGHUP (bugfix on
7924 0.0.6pre1); also, do not stall hidden services because we're
7925 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
7926 by John Brooks. Patch by Karsten. Fixes bug 874.
7927 - Fix a memory leak when we decline to add a v2 rendezvous
7928 descriptor to the cache because we already had a v0 descriptor
7929 with the same ID. Bugfix on 0.2.0.18-alpha.
7931 o Deprecated and removed features:
7932 - RedirectExits has been removed. It was deprecated since
7934 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
7935 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
7936 - Cell pools are now always enabled; --disable-cell-pools is ignored.
7938 o Code simplifications and refactoring:
7939 - Rename the confusing or_is_obsolete field to the more appropriate
7940 is_bad_for_new_circs, and move it to or_connection_t where it
7942 - Move edge-only flags from connection_t to edge_connection_t: not
7943 only is this better coding, but on machines of plausible alignment,
7944 it should save 4-8 bytes per connection_t. "Every little bit helps."
7945 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
7946 for consistency; keep old option working for backward compatibility.
7947 - Simplify the code for finding connections to use for a circuit.
7950 Changes in version 0.2.1.8-alpha - 2008-12-08
7951 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
7952 builds better on unusual platforms like Solaris and old OS X, and
7953 fixes a variety of other issues.
7956 - New DirPortFrontPage option that takes an html file and publishes
7957 it as "/" on the DirPort. Now relay operators can provide a
7958 disclaimer without needing to set up a separate webserver. There's
7959 a sample disclaimer in contrib/tor-exit-notice.html.
7962 - When the client is choosing entry guards, now it selects at most
7963 one guard from a given relay family. Otherwise we could end up with
7964 all of our entry points into the network run by the same operator.
7965 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
7968 - Fix a DOS opportunity during the voting signature collection process
7969 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7970 - Fix a possible segfault when establishing an exit connection. Bugfix
7974 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
7976 - Made Tor a little less aggressive about deleting expired
7977 certificates. Partial fix for bug 854.
7978 - Stop doing unaligned memory access that generated bus errors on
7979 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
7980 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
7981 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
7982 - Make USR2 log-level switch take effect immediately. Bugfix on
7984 - If one win32 nameserver fails to get added, continue adding the
7985 rest, and don't automatically fail.
7986 - Use fcntl() for locking when flock() is not available. Should fix
7987 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
7988 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7989 could make gcc generate non-functional binary search code. Bugfix
7991 - Build correctly on platforms without socklen_t.
7992 - Avoid potential crash on internal error during signature collection.
7993 Fixes bug 864. Patch from rovv.
7994 - Do not use C's stdio library for writing to log files. This will
7995 improve logging performance by a minute amount, and will stop
7996 leaking fds when our disk is full. Fixes bug 861.
7997 - Stop erroneous use of O_APPEND in cases where we did not in fact
7998 want to re-seek to the end of a file before every last write().
7999 - Correct handling of possible malformed authority signing key
8000 certificates with internal signature types. Fixes bug 880. Bugfix
8002 - Fix a hard-to-trigger resource leak when logging credential status.
8006 - Directory mirrors no longer fetch the v1 directory or
8007 running-routers files. They are obsolete, and nobody asks for them
8008 anymore. This is the first step to making v1 authorities obsolete.
8010 o Minor features (controller):
8011 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8015 Changes in version 0.2.0.32 - 2008-11-20
8016 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8017 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8018 a smaller security flaw that might allow an attacker to access local
8019 services, further improves hidden service performance, and fixes a
8020 variety of other issues.
8023 - The "User" and "Group" config options did not clear the
8024 supplementary group entries for the Tor process. The "User" option
8025 is now more robust, and we now set the groups to the specified
8026 user's primary group. The "Group" option is now ignored. For more
8027 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8028 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8029 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8030 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8031 consistently obeyed: if an exit relay refuses a stream because its
8032 exit policy doesn't allow it, we would remember what IP address
8033 the relay said the destination address resolves to, even if it's
8034 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8037 - Fix a DOS opportunity during the voting signature collection process
8038 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8040 o Major bugfixes (hidden services):
8041 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8042 we were failing the whole hidden service request when the v0
8043 descriptor fetch fails, even if the v2 fetch is still pending and
8044 might succeed. Similarly, if the last v2 fetch fails, we were
8045 failing the whole hidden service request even if a v0 fetch is
8046 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8047 - When extending a circuit to a hidden service directory to upload a
8048 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8049 requests failed, because the router descriptor has not been
8050 downloaded yet. In these cases, do not attempt to upload the
8051 rendezvous descriptor, but wait until the router descriptor is
8052 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8053 descriptor from a hidden service directory for which the router
8054 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8058 - Fix several infrequent memory leaks spotted by Coverity.
8059 - When testing for libevent functions, set the LDFLAGS variable
8060 correctly. Found by Riastradh.
8061 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8062 bootstrapping with tunneled directory connections. Bugfix on
8063 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8064 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8065 and we know that server B rejects most-but-not all connections to
8066 port 80, we would previously reject the connection. Now, we assume
8067 the user knows what they were asking for. Fixes bug 752. Bugfix
8068 on 0.0.9rc5. Diagnosed by BarkerJr.
8069 - If we overrun our per-second write limits a little, count this as
8070 having used up our write allocation for the second, and choke
8071 outgoing directory writes. Previously, we had only counted this when
8072 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8073 Bugfix on 0.2.0.x (??).
8074 - Remove the old v2 directory authority 'lefkada' from the default
8075 list. It has been gone for many months.
8076 - Stop doing unaligned memory access that generated bus errors on
8077 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8078 - Make USR2 log-level switch take effect immediately. Bugfix on
8081 o Minor bugfixes (controller):
8082 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8083 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8086 Changes in version 0.2.1.7-alpha - 2008-11-08
8087 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8088 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8089 a smaller security flaw that might allow an attacker to access local
8090 services, adds better defense against DNS poisoning attacks on exit
8091 relays, further improves hidden service performance, and fixes a
8092 variety of other issues.
8095 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8096 consistently obeyed: if an exit relay refuses a stream because its
8097 exit policy doesn't allow it, we would remember what IP address
8098 the relay said the destination address resolves to, even if it's
8099 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8100 - The "User" and "Group" config options did not clear the
8101 supplementary group entries for the Tor process. The "User" option
8102 is now more robust, and we now set the groups to the specified
8103 user's primary group. The "Group" option is now ignored. For more
8104 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8105 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8106 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8107 - Do not use or believe expired v3 authority certificates. Patch
8108 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8111 - Now NodeFamily and MyFamily config options allow spaces in
8112 identity fingerprints, so it's easier to paste them in.
8113 Suggested by Lucky Green.
8114 - Implement the 0x20 hack to better resist DNS poisoning: set the
8115 case on outgoing DNS requests randomly, and reject responses that do
8116 not match the case correctly. This logic can be disabled with the
8117 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8118 of servers that do not reliably preserve case in replies. See
8119 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8121 - Preserve case in replies to DNSPort requests in order to support
8122 the 0x20 hack for resisting DNS poisoning attacks.
8124 o Hidden service performance improvements:
8125 - When the client launches an introduction circuit, retry with a
8126 new circuit after 30 seconds rather than 60 seconds.
8127 - Launch a second client-side introduction circuit in parallel
8128 after a delay of 15 seconds (based on work by Christian Wilms).
8129 - Hidden services start out building five intro circuits rather
8130 than three, and when the first three finish they publish a service
8131 descriptor using those. Now we publish our service descriptor much
8132 faster after restart.
8135 - Minor fix in the warning messages when you're having problems
8136 bootstrapping; also, be more forgiving of bootstrap problems when
8137 we're still making incremental progress on a given bootstrap phase.
8138 - When we're choosing an exit node for a circuit, and we have
8139 no pending streams, choose a good general exit rather than one that
8140 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8141 - Send a valid END cell back when a client tries to connect to a
8142 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8143 840. Patch from rovv.
8144 - If a broken client asks a non-exit router to connect somewhere,
8145 do not even do the DNS lookup before rejecting the connection.
8146 Fixes another case of bug 619. Patch from rovv.
8147 - Fix another case of assuming, when a specific exit is requested,
8148 that we know more than the user about what hosts it allows.
8149 Fixes another case of bug 752. Patch from rovv.
8150 - Check which hops rendezvous stream cells are associated with to
8151 prevent possible guess-the-streamid injection attacks from
8152 intermediate hops. Fixes another case of bug 446. Based on patch
8154 - Avoid using a negative right-shift when comparing 32-bit
8155 addresses. Possible fix for bug 845 and bug 811.
8156 - Make the assert_circuit_ok() function work correctly on circuits that
8157 have already been marked for close.
8158 - Fix read-off-the-end-of-string error in unit tests when decoding
8159 introduction points.
8160 - Fix uninitialized size field for memory area allocation: may improve
8161 memory performance during directory parsing.
8162 - Treat duplicate certificate fetches as failures, so that we do
8163 not try to re-fetch an expired certificate over and over and over.
8164 - Do not say we're fetching a certificate when we'll in fact skip it
8165 because of a pending download.
8168 Changes in version 0.2.1.6-alpha - 2008-09-30
8169 Tor 0.2.1.6-alpha further improves performance and robustness of
8170 hidden services, starts work on supporting per-country relay selection,
8171 and fixes a variety of smaller issues.
8174 - Implement proposal 121: make it possible to build hidden services
8175 that only certain clients are allowed to connect to. This is
8176 enforced at several points, so that unauthorized clients are unable
8177 to send INTRODUCE cells to the service, or even (depending on the
8178 type of authentication) to learn introduction points. This feature
8179 raises the bar for certain kinds of active attacks against hidden
8180 services. Code by Karsten Loesing.
8181 - Relays now store and serve v2 hidden service descriptors by default,
8182 i.e., the new default value for HidServDirectoryV2 is 1. This is
8183 the last step in proposal 114, which aims to make hidden service
8184 lookups more reliable.
8185 - Start work to allow node restrictions to include country codes. The
8186 syntax to exclude nodes in a country with country code XX is
8187 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8188 refinement to decide what config options should take priority if
8189 you ask to both use a particular node and exclude it.
8190 - Allow ExitNodes list to include IP ranges and country codes, just
8191 like the Exclude*Nodes lists. Patch from Robert Hogan.
8194 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8195 Tor to fail to start if you had it configured to use a bridge
8196 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8197 - When extending a circuit to a hidden service directory to upload a
8198 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8199 requests failed, because the router descriptor had not been
8200 downloaded yet. In these cases, we now wait until the router
8201 descriptor is downloaded, and then retry. Likewise, clients
8202 now skip over a hidden service directory if they don't yet have
8203 its router descriptor, rather than futilely requesting it and
8204 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8206 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8207 we were failing the whole hidden service request when the v0
8208 descriptor fetch fails, even if the v2 fetch is still pending and
8209 might succeed. Similarly, if the last v2 fetch fails, we were
8210 failing the whole hidden service request even if a v0 fetch is
8211 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8212 - DNS replies need to have names matching their requests, but
8213 these names should be in the questions section, not necessarily
8214 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8217 - Update to the "September 1 2008" ip-to-country file.
8218 - Allow ports 465 and 587 in the default exit policy again. We had
8219 rejected them in 0.1.0.15, because back in 2005 they were commonly
8220 misconfigured and ended up as spam targets. We hear they are better
8221 locked down these days.
8222 - Use a lockfile to make sure that two Tor processes are not
8223 simultaneously running with the same datadir.
8224 - Serve the latest v3 networkstatus consensus via the control
8225 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8226 - Better logging about stability/reliability calculations on directory
8228 - Drop the requirement to have an open dir port for storing and
8229 serving v2 hidden service descriptors.
8230 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8231 help debug WFU and MTBF calculations.
8232 - Implement most of Proposal 152: allow specialized servers to permit
8233 single-hop circuits, and clients to use those servers to build
8234 single-hop circuits when using a specialized controller. Patch
8235 from Josh Albrecht. Resolves feature request 768.
8236 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8237 people find host:port too confusing.
8238 - Make TrackHostExit mappings expire a while after their last use, not
8239 after their creation. Patch from Robert Hogan.
8240 - Provide circuit purposes along with circuit events to the controller.
8243 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8245 - Fixed some memory leaks -- some quite frequent, some almost
8246 impossible to trigger -- based on results from Coverity.
8247 - When testing for libevent functions, set the LDFLAGS variable
8248 correctly. Found by Riastradh.
8249 - Fix an assertion bug in parsing policy-related options; possible fix
8251 - Catch and report a few more bootstrapping failure cases when Tor
8252 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8253 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8254 bootstrapping with tunneled directory connections. Bugfix on
8255 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8256 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8257 and we know that server B rejects most-but-not all connections to
8258 port 80, we would previously reject the connection. Now, we assume
8259 the user knows what they were asking for. Fixes bug 752. Bugfix
8260 on 0.0.9rc5. Diagnosed by BarkerJr.
8261 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8262 service directories if they have no advertised dir port. Bugfix
8264 - If we overrun our per-second write limits a little, count this as
8265 having used up our write allocation for the second, and choke
8266 outgoing directory writes. Previously, we had only counted this when
8267 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8268 Bugfix on 0.2.0.x (??).
8269 - Avoid a "0 divided by 0" calculation when calculating router uptime
8270 at directory authorities. Bugfix on 0.2.0.8-alpha.
8271 - Make DNS resolved controller events into "CLOSED", not
8272 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8274 - Fix a bug where an unreachable relay would establish enough
8275 reachability testing circuits to do a bandwidth test -- if
8276 we already have a connection to the middle hop of the testing
8277 circuit, then it could establish the last hop by using the existing
8278 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8279 circuits no longer use entry guards in 0.2.1.3-alpha.
8280 - If we have correct permissions on $datadir, we complain to stdout
8281 and fail to start. But dangerous permissions on
8282 $datadir/cached-status/ would cause us to open a log and complain
8283 there. Now complain to stdout and fail to start in both cases. Fixes
8284 bug 820, reported by seeess.
8285 - Remove the old v2 directory authority 'lefkada' from the default
8286 list. It has been gone for many months.
8288 o Code simplifications and refactoring:
8289 - Revise the connection_new functions so that a more typesafe variant
8290 exists. This will work better with Coverity, and let us find any
8291 actual mistakes we're making here.
8292 - Refactor unit testing logic so that dmalloc can be used sensibly
8293 with unit tests to check for memory leaks.
8294 - Move all hidden-service related fields from connection and circuit
8295 structure to substructures: this way they won't eat so much memory.
8298 Changes in version 0.2.0.31 - 2008-09-03
8299 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8300 a big bug we're seeing where in rare cases traffic from one Tor stream
8301 gets mixed into another stream, and fixes a variety of smaller issues.
8304 - Make sure that two circuits can never exist on the same connection
8305 with the same circuit ID, even if one is marked for close. This
8306 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8307 - Relays now reject risky extend cells: if the extend cell includes
8308 a digest of all zeroes, or asks to extend back to the relay that
8309 sent the extend cell, tear down the circuit. Ideas suggested
8311 - If not enough of our entry guards are available so we add a new
8312 one, we might use the new one even if it overlapped with the
8313 current circuit's exit relay (or its family). Anonymity bugfix
8314 pointed out by rovv.
8317 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8318 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8319 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8320 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8321 - Pick size of default geoip filename string correctly on windows.
8322 Fixes bug 806. Bugfix on 0.2.0.30.
8323 - Make the autoconf script accept the obsolete --with-ssl-dir
8324 option as an alias for the actually-working --with-openssl-dir
8325 option. Fix the help documentation to recommend --with-openssl-dir.
8326 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8327 - When using the TransPort option on OpenBSD, and using the User
8328 option to change UID and drop privileges, make sure to open
8329 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8330 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8331 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8332 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8333 on the client side when connecting to a hidden service. Bugfix
8334 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8335 - When closing an application-side connection because its circuit is
8336 getting torn down, generate the stream event correctly. Bugfix on
8337 0.1.2.x. Anonymous patch.
8340 Changes in version 0.2.1.5-alpha - 2008-08-31
8341 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8342 in a lot of the infrastructure for adding authorization to hidden
8343 services, lays the groundwork for having clients read their load
8344 balancing information out of the networkstatus consensus rather than
8345 the individual router descriptors, addresses two potential anonymity
8346 issues, and fixes a variety of smaller issues.
8349 - Convert many internal address representations to optionally hold
8351 - Generate and accept IPv6 addresses in many protocol elements.
8352 - Make resolver code handle nameservers located at ipv6 addresses.
8353 - Begin implementation of proposal 121 ("Client authorization for
8354 hidden services"): configure hidden services with client
8355 authorization, publish descriptors for them, and configure
8356 authorization data for hidden services at clients. The next
8357 step is to actually access hidden services that perform client
8359 - More progress toward proposal 141: Network status consensus
8360 documents and votes now contain bandwidth information for each
8361 router and a summary of that router's exit policy. Eventually this
8362 will be used by clients so that they do not have to download every
8363 known descriptor before building circuits.
8365 o Major bugfixes (on 0.2.0.x and before):
8366 - When sending CREATED cells back for a given circuit, use a 64-bit
8367 connection ID to find the right connection, rather than an addr:port
8368 combination. Now that we can have multiple OR connections between
8369 the same ORs, it is no longer possible to use addr:port to uniquely
8370 identify a connection.
8371 - Relays now reject risky extend cells: if the extend cell includes
8372 a digest of all zeroes, or asks to extend back to the relay that
8373 sent the extend cell, tear down the circuit. Ideas suggested
8375 - If not enough of our entry guards are available so we add a new
8376 one, we might use the new one even if it overlapped with the
8377 current circuit's exit relay (or its family). Anonymity bugfix
8378 pointed out by rovv.
8381 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8382 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8383 - When using the TransPort option on OpenBSD, and using the User
8384 option to change UID and drop privileges, make sure to open /dev/pf
8385 before dropping privileges. Fixes bug 782. Patch from Christopher
8386 Davis. Bugfix on 0.1.2.1-alpha.
8387 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8388 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8389 - Add a missing safe_str() call for a debug log message.
8390 - Use 64 bits instead of 32 bits for connection identifiers used with
8391 the controller protocol, to greatly reduce risk of identifier reuse.
8392 - Make the autoconf script accept the obsolete --with-ssl-dir
8393 option as an alias for the actually-working --with-openssl-dir
8394 option. Fix the help documentation to recommend --with-openssl-dir.
8395 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8398 - Rate-limit too-many-sockets messages: when they happen, they happen
8399 a lot. Resolves bug 748.
8400 - Resist DNS poisoning a little better by making sure that names in
8401 answer sections match.
8402 - Print the SOCKS5 error message string as well as the error code
8403 when a tor-resolve request fails. Patch from Jacob.
8406 Changes in version 0.2.1.4-alpha - 2008-08-04
8407 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8410 - The address part of exit policies was not correctly written
8411 to router descriptors. This generated router descriptors that failed
8412 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8414 - Tor triggered a false assert when extending a circuit to a relay
8415 but we already have a connection open to that relay. Noticed by
8416 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8419 - Fix a hidden service logging bug: in some edge cases, the router
8420 descriptor of a previously picked introduction point becomes
8421 obsolete and we need to give up on it rather than continually
8422 complaining that it has become obsolete. Observed by xiando. Bugfix
8426 - Take out the TestVia config option, since it was a workaround for
8427 a bug that was fixed in Tor 0.1.1.21.
8430 Changes in version 0.2.1.3-alpha - 2008-08-03
8431 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8432 infinite-length circuit attacks (see proposal 110); fixes a bug that
8433 might cause exit relays to corrupt streams they send back; allows
8434 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8435 ExcludeExitNodes config options; and fixes a big pile of bugs.
8437 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8438 - Send a bootstrap problem "warn" event on the first problem if the
8439 reason is NO_ROUTE (that is, our network is down).
8442 - Implement most of proposal 110: The first K cells to be sent
8443 along a circuit are marked as special "early" cells; only K "early"
8444 cells will be allowed. Once this code is universal, we can block
8445 certain kinds of DOS attack by requiring that EXTEND commands must
8446 be sent using an "early" cell.
8449 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8450 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8451 on the client side when connecting to a hidden service. Bugfix
8452 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8453 - Ensure that two circuits can never exist on the same connection
8454 with the same circuit ID, even if one is marked for close. This
8455 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8458 - When relays do their initial bandwidth measurement, don't limit
8459 to just our entry guards for the test circuits. Otherwise we tend
8460 to have multiple test circuits going through a single entry guard,
8461 which makes our bandwidth test less accurate. Fixes part of bug 654;
8462 patch contributed by Josh Albrecht.
8463 - Add an ExcludeExitNodes option so users can list a set of nodes
8464 that should be be excluded from the exit node position, but
8465 allowed elsewhere. Implements proposal 151.
8466 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8467 ExcludeNodes and ExcludeExitNodes lists.
8468 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8469 be more efficient. Formerly it was quadratic in the number of
8470 servers; now it should be linear. Fixes bug 509.
8471 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8472 and n_conn_id_digest fields into a separate structure that's
8473 only needed when the circuit has not yet attached to an n_conn.
8476 - Change the contrib/tor.logrotate script so it makes the new
8477 logs as "_tor:_tor" rather than the default, which is generally
8478 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8479 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8480 warnings (occasionally), but it can also cause the compiler to
8481 eliminate error-checking code. Suggested by Peter Gutmann.
8482 - When a hidden service is giving up on an introduction point candidate
8483 that was not included in the last published rendezvous descriptor,
8484 don't reschedule publication of the next descriptor. Fixes bug 763.
8486 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8487 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8488 and nobody claims to be using them. Fixes bug 754. Bugfix on
8489 0.1.0.1-rc. Patch from Christian Wilms.
8490 - Fix a small alignment and memory-wasting bug on buffer chunks.
8493 o Minor bugfixes (controller):
8494 - When closing an application-side connection because its circuit
8495 is getting torn down, generate the stream event correctly.
8496 Bugfix on 0.1.2.x. Anonymous patch.
8499 - Remove all backward-compatibility code to support relays running
8500 versions of Tor so old that they no longer work at all on the
8504 Changes in version 0.2.0.30 - 2008-07-15
8506 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8507 warnings (occasionally), but it can also cause the compiler to
8508 eliminate error-checking code. Suggested by Peter Gutmann.
8511 Changes in version 0.2.0.29-rc - 2008-07-08
8512 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8513 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8516 - If you have more than one bridge but don't know their keys,
8517 you would only launch a request for the descriptor of the first one
8518 on your list. (Tor considered launching requests for the others, but
8519 found that it already had a connection on the way for $0000...0000
8520 so it didn't open another.) Bugfix on 0.2.0.x.
8521 - If you have more than one bridge but don't know their keys, and the
8522 connection to one of the bridges failed, you would cancel all
8523 pending bridge connections. (After all, they all have the same
8524 digest.) Bugfix on 0.2.0.x.
8525 - When a hidden service was trying to establish an introduction point,
8526 and Tor had built circuits preemptively for such purposes, we
8527 were ignoring all the preemptive circuits and launching a new one
8528 instead. Bugfix on 0.2.0.14-alpha.
8529 - When a hidden service was trying to establish an introduction point,
8530 and Tor *did* manage to reuse one of the preemptively built
8531 circuits, it didn't correctly remember which one it used,
8532 so it asked for another one soon after, until there were no
8533 more preemptive circuits, at which point it launched one from
8534 scratch. Bugfix on 0.0.9.x.
8535 - Make directory servers include the X-Your-Address-Is: http header in
8536 their responses even for begin_dir conns. Now clients who only
8537 ever use begin_dir connections still have a way to learn their IP
8538 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8541 - Fix a macro/CPP interaction that was confusing some compilers:
8542 some GCCs don't like #if/#endif pairs inside macro arguments.
8544 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8545 Fixes bug 704; fix from Steven Murdoch.
8546 - When opening /dev/null in finish_daemonize(), do not pass the
8547 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8548 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8549 - Correctly detect transparent proxy support on Linux hosts that
8550 require in.h to be included before netfilter_ipv4.h. Patch
8552 - Disallow session resumption attempts during the renegotiation
8553 stage of the v2 handshake protocol. Clients should never be trying
8554 session resumption at this point, but apparently some did, in
8555 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8556 found by Geoff Goodell.
8559 Changes in version 0.2.1.2-alpha - 2008-06-20
8560 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8561 make it easier to set up your own private Tor network; fixes several
8562 big bugs with using more than one bridge relay; fixes a big bug with
8563 offering hidden services quickly after Tor starts; and uses a better
8564 API for reporting potential bootstrapping problems to the controller.
8567 - New TestingTorNetwork config option to allow adjustment of
8568 previously constant values that, while reasonable, could slow
8569 bootstrapping. Implements proposal 135. Patch from Karsten.
8572 - If you have more than one bridge but don't know their digests,
8573 you would only learn a request for the descriptor of the first one
8574 on your list. (Tor considered launching requests for the others, but
8575 found that it already had a connection on the way for $0000...0000
8576 so it didn't open another.) Bugfix on 0.2.0.x.
8577 - If you have more than one bridge but don't know their digests,
8578 and the connection to one of the bridges failed, you would cancel
8579 all pending bridge connections. (After all, they all have the
8580 same digest.) Bugfix on 0.2.0.x.
8581 - When establishing a hidden service, introduction points that
8582 originate from cannibalized circuits are completely ignored and not
8583 included in rendezvous service descriptors. This might be another
8584 reason for delay in making a hidden service available. Bugfix
8585 from long ago (0.0.9.x?)
8588 - Allow OpenSSL to use dynamic locks if it wants.
8589 - When building a consensus, do not include routers that are down.
8590 This will cut down 30% to 40% on consensus size. Implements
8592 - In directory authorities' approved-routers files, allow
8593 fingerprints with or without space.
8594 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8595 controller can query our current bootstrap state in case it attaches
8596 partway through and wants to catch up.
8597 - Send an initial "Starting" bootstrap status event, so we have a
8598 state to start out in.
8601 - Asking for a conditional consensus at .../consensus/<fingerprints>
8602 would crash a dirserver if it did not already have a
8603 consensus. Bugfix on 0.2.1.1-alpha.
8604 - Clean up some macro/CPP interactions: some GCC versions don't like
8605 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8608 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8609 - Directory authorities shouldn't complain about bootstrapping
8610 problems just because they do a lot of reachability testing and
8611 some of the connection attempts fail.
8612 - Start sending "count" and "recommendation" key/value pairs in
8613 bootstrap problem status events, so the controller can hear about
8614 problems even before Tor decides they're worth reporting for sure.
8615 - If you're using bridges, generate "bootstrap problem" warnings
8616 as soon as you run out of working bridges, rather than waiting
8617 for ten failures -- which will never happen if you have less than
8619 - If we close our OR connection because there's been a circuit
8620 pending on it for too long, we were telling our bootstrap status
8621 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8624 Changes in version 0.2.1.1-alpha - 2008-06-13
8625 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8626 were making the Tor process bloat especially on Linux; makes our TLS
8627 handshake blend in better; sends "bootstrap phase" status events to
8628 the controller, so it can keep the user informed of progress (and
8629 problems) fetching directory information and establishing circuits;
8630 and adds a variety of smaller features.
8633 - More work on making our TLS handshake blend in: modify the list
8634 of ciphers advertised by OpenSSL in client mode to even more
8635 closely resemble a common web browser. We cheat a little so that
8636 we can advertise ciphers that the locally installed OpenSSL doesn't
8638 - Start sending "bootstrap phase" status events to the controller,
8639 so it can keep the user informed of progress fetching directory
8640 information and establishing circuits. Also inform the controller
8641 if we think we're stuck at a particular bootstrap phase. Implements
8643 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8644 cross-platform entropy collection again. We used to use it, then
8645 stopped using it because of a bug that could crash systems that
8646 called RAND_poll when they had a lot of fds open. It looks like the
8647 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8648 at startup, and to call RAND_poll() when we reseed later only if
8649 we have a non-buggy OpenSSL version.
8652 - When we choose to abandon a new entry guard because we think our
8653 older ones might be better, close any circuits pending on that
8654 new entry guard connection. This fix should make us recover much
8655 faster when our network is down and then comes back. Bugfix on
8656 0.1.2.8-beta; found by lodger.
8658 o Memory fixes and improvements:
8659 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8660 to avoid unused RAM in buffer chunks and memory pools.
8661 - Speed up parsing and cut down on memory fragmentation by using
8662 stack-style allocations for parsing directory objects. Previously,
8663 this accounted for over 40% of allocations from within Tor's code
8664 on a typical directory cache.
8665 - Use a Bloom filter rather than a digest-based set to track which
8666 descriptors we need to keep around when we're cleaning out old
8667 router descriptors. This speeds up the computation significantly,
8668 and may reduce fragmentation.
8669 - Reduce the default smartlist size from 32 to 16; it turns out that
8670 most smartlists hold around 8-12 elements tops.
8671 - Make dumpstats() log the fullness and size of openssl-internal
8673 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8674 patch to their OpenSSL, turn it on to save memory on servers. This
8675 patch will (with any luck) get included in a mainline distribution
8677 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8678 compress cells, which are basically all encrypted, compressed,
8682 - Stop reloading the router list from disk for no reason when we
8683 run out of reachable directory mirrors. Once upon a time reloading
8684 it would set the 'is_running' flag back to 1 for them. It hasn't
8685 done that for a long time.
8686 - In very rare situations new hidden service descriptors were
8687 published earlier than 30 seconds after the last change to the
8688 service. (We currently think that a hidden service descriptor
8689 that's been stable for 30 seconds is worth publishing.)
8692 - Allow separate log levels to be configured for different logging
8693 domains. For example, this allows one to log all notices, warnings,
8694 or errors, plus all memory management messages of level debug or
8695 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
8696 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8697 and stop using a warning that had become unfixably verbose under
8699 - New --hush command-line option similar to --quiet. While --quiet
8700 disables all logging to the console on startup, --hush limits the
8701 output to messages of warning and error severity.
8702 - Servers support a new URL scheme for consensus downloads that
8703 allows the client to specify which authorities are trusted.
8704 The server then only sends the consensus if the client will trust
8705 it. Otherwise a 404 error is sent back. Clients use this
8706 new scheme when the server supports it (meaning it's running
8707 0.2.1.1-alpha or later). Implements proposal 134.
8708 - New configure/torrc options (--enable-geoip-stats,
8709 DirRecordUsageByCountry) to record how many IPs we've served
8710 directory info to in each country code, how many status documents
8711 total we've sent to each country code, and what share of the total
8712 directory requests we should expect to see.
8713 - Use the TLS1 hostname extension to more closely resemble browser
8715 - Lots of new unit tests.
8716 - Add a macro to implement the common pattern of iterating through
8717 two parallel lists in lockstep.
8720 Changes in version 0.2.0.28-rc - 2008-06-13
8721 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
8722 performance bug, and fixes a bunch of smaller bugs.
8725 - Fix a bug where, when we were choosing the 'end stream reason' to
8726 put in our relay end cell that we send to the exit relay, Tor
8727 clients on Windows were sometimes sending the wrong 'reason'. The
8728 anonymity problem is that exit relays may be able to guess whether
8729 the client is running Windows, thus helping partition the anonymity
8730 set. Down the road we should stop sending reasons to exit relays,
8731 or otherwise prevent future versions of this bug.
8734 - While setting up a hidden service, some valid introduction circuits
8735 were overlooked and abandoned. This might be the reason for
8736 the long delay in making a hidden service available. Bugfix on
8740 - Update to the "June 9 2008" ip-to-country file.
8741 - Run 'make test' as part of 'make dist', so we stop releasing so
8742 many development snapshots that fail their unit tests.
8745 - When we're checking if we have enough dir info for each relay
8746 to begin establishing circuits, make sure that we actually have
8747 the descriptor listed in the consensus, not just any descriptor.
8749 - Bridge relays no longer print "xx=0" in their extrainfo document
8750 for every single country code in the geoip db. Bugfix on
8752 - Only warn when we fail to load the geoip file if we were planning to
8753 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
8754 - If we change our MaxAdvertisedBandwidth and then reload torrc,
8755 Tor won't realize it should publish a new relay descriptor. Fixes
8756 bug 688, reported by mfr. Bugfix on 0.1.2.x.
8757 - When we haven't had any application requests lately, don't bother
8758 logging that we have expired a bunch of descriptors. Bugfix
8760 - Make relay cells written on a connection count as non-padding when
8761 tracking how long a connection has been in use. Bugfix on
8762 0.2.0.1-alpha. Spotted by lodger.
8763 - Fix unit tests in 0.2.0.27-rc.
8764 - Fix compile on Windows.
8767 Changes in version 0.2.0.27-rc - 2008-06-03
8768 Tor 0.2.0.27-rc adds a few features we left out of the earlier
8769 release candidates. In particular, we now include an IP-to-country
8770 GeoIP database, so controllers can easily look up what country a
8771 given relay is in, and so bridge relays can give us some sanitized
8772 summaries about which countries are making use of bridges. (See proposal
8773 126-geoip-fetching.txt for details.)
8776 - Include an IP-to-country GeoIP file in the tarball, so bridge
8777 relays can report sanitized summaries of the usage they're seeing.
8780 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
8781 Robert Hogan. Fixes the first part of bug 681.
8782 - Make bridge authorities never serve extrainfo docs.
8783 - Add support to detect Libevent versions in the 1.4.x series
8785 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
8786 - Include a new contrib/tor-exit-notice.html file that exit relay
8787 operators can put on their website to help reduce abuse queries.
8790 - When tunneling an encrypted directory connection, and its first
8791 circuit fails, do not leave it unattached and ask the controller
8792 to deal. Fixes the second part of bug 681.
8793 - Make bridge authorities correctly expire old extrainfo documents
8797 Changes in version 0.2.0.26-rc - 2008-05-13
8798 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
8799 in Debian's OpenSSL packages. All users running any 0.2.0.x version
8800 should upgrade, whether they're running Debian or not.
8802 o Major security fixes:
8803 - Use new V3 directory authority keys on the tor26, gabelmoo, and
8804 moria1 V3 directory authorities. The old keys were generated with
8805 a vulnerable version of Debian's OpenSSL package, and must be
8806 considered compromised. Other authorities' keys were not generated
8807 with an affected version of OpenSSL.
8810 - List authority signatures as "unrecognized" based on DirServer
8811 lines, not on cert cache. Bugfix on 0.2.0.x.
8814 - Add a new V3AuthUseLegacyKey option to make it easier for
8815 authorities to change their identity keys if they have to.
8818 Changes in version 0.2.0.25-rc - 2008-04-23
8819 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
8822 - Remember to initialize threading before initializing logging.
8823 Otherwise, many BSD-family implementations will crash hard on
8824 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
8827 - Authorities correctly free policies on bad servers on
8828 exit. Fixes bug 672. Bugfix on 0.2.0.x.
8831 Changes in version 0.2.0.24-rc - 2008-04-22
8832 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
8833 v3 directory authority, makes relays with dynamic IP addresses and no
8834 DirPort notice more quickly when their IP address changes, fixes a few
8835 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
8837 o New directory authorities:
8838 - Take lefkada out of the list of v3 directory authorities, since
8839 it has been down for months.
8840 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
8844 - Detect address changes more quickly on non-directory mirror
8845 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
8847 o Minor features (security):
8848 - Reject requests for reverse-dns lookup of names that are in
8849 a private address space. Patch from lodger.
8850 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
8853 o Minor bugfixes (crashes):
8854 - Avoid a rare assert that can trigger when Tor doesn't have much
8855 directory information yet and it tries to fetch a v2 hidden
8856 service descriptor. Fixes bug 651, reported by nwf.
8857 - Initialize log mutex before initializing dmalloc. Otherwise,
8858 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
8859 - Use recursive pthread mutexes in order to avoid deadlock when
8860 logging debug-level messages to a controller. Bug spotted by nwf,
8861 bugfix on 0.2.0.16-alpha.
8863 o Minor bugfixes (resource management):
8864 - Keep address policies from leaking memory: start their refcount
8865 at 1, not 2. Bugfix on 0.2.0.16-alpha.
8866 - Free authority certificates on exit, so they don't look like memory
8867 leaks. Bugfix on 0.2.0.19-alpha.
8868 - Free static hashtables for policy maps and for TLS connections on
8869 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
8870 - Avoid allocating extra space when computing consensuses on 64-bit
8871 platforms. Bug spotted by aakova.
8873 o Minor bugfixes (misc):
8874 - Do not read the configuration file when we've only been told to
8875 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
8876 based on patch from Sebastian Hahn.
8877 - Exit relays that are used as a client can now reach themselves
8878 using the .exit notation, rather than just launching an infinite
8879 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
8880 - When attempting to open a logfile fails, tell us why.
8881 - Fix a dumb bug that was preventing us from knowing that we should
8882 preemptively build circuits to handle expected directory requests.
8883 Fixes bug 660. Bugfix on 0.1.2.x.
8884 - Warn less verbosely about clock skew from netinfo cells from
8885 untrusted sources. Fixes bug 663.
8886 - Make controller stream events for DNS requests more consistent,
8887 by adding "new stream" events for DNS requests, and removing
8888 spurious "stream closed" events" for cached reverse resolves.
8889 Patch from mwenge. Fixes bug 646.
8890 - Correctly notify one-hop connections when a circuit build has
8891 failed. Possible fix for bug 669. Found by lodger.
8894 Changes in version 0.2.0.23-rc - 2008-03-24
8895 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
8896 makes bootstrapping faster if the first directory mirror you contact
8897 is down. The bundles also include the new Vidalia 0.1.2 release.
8900 - When a tunneled directory request is made to a directory server
8901 that's down, notice after 30 seconds rather than 120 seconds. Also,
8902 fail any begindir streams that are pending on it, so they can
8903 retry elsewhere. This was causing multi-minute delays on bootstrap.
8906 Changes in version 0.2.0.22-rc - 2008-03-18
8907 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
8908 enables encrypted directory connections by default for non-relays, fixes
8909 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
8910 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
8913 - Enable encrypted directory connections by default for non-relays,
8914 so censor tools that block Tor directory connections based on their
8915 plaintext patterns will no longer work. This means Tor works in
8916 certain censored countries by default again.
8919 - Make sure servers always request certificates from clients during
8920 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
8921 - Do not enter a CPU-eating loop when a connection is closed in
8922 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
8923 diagnosed by lodger; bugfix on 0.2.0.20-rc.
8924 - Fix assertion failure that could occur when a blocked circuit
8925 became unblocked, and it had pending client DNS requests. Bugfix
8926 on 0.2.0.1-alpha. Fixes bug 632.
8928 o Minor bugfixes (on 0.1.2.x):
8929 - Generate "STATUS_SERVER" events rather than misspelled
8930 "STATUS_SEVER" events. Caught by mwenge.
8931 - When counting the number of bytes written on a TLS connection,
8932 look at the BIO actually used for writing to the network, not
8933 at the BIO used (sometimes) to buffer data for the network.
8934 Looking at different BIOs could result in write counts on the
8935 order of ULONG_MAX. Fixes bug 614.
8936 - On Windows, correctly detect errors when listing the contents of
8937 a directory. Fix from lodger.
8939 o Minor bugfixes (on 0.2.0.x):
8940 - Downgrade "sslv3 alert handshake failure" message to INFO.
8941 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
8942 left BandwidthRate and BandwidthBurst at the default, we would be
8943 silently limited by those defaults. Now raise them to match the
8944 RelayBandwidth* values.
8945 - Fix the SVK version detection logic to work correctly on a branch.
8946 - Make --enable-openbsd-malloc work correctly on Linux with alpha
8947 CPUs. Fixes bug 625.
8948 - Logging functions now check that the passed severity is sane.
8949 - Use proper log levels in the testsuite call of
8950 get_interface_address6().
8951 - When using a nonstandard malloc, do not use the platform values for
8952 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
8953 - Make the openbsd malloc code use 8k pages on alpha CPUs and
8955 - Detect mismatched page sizes when using --enable-openbsd-malloc.
8956 - Avoid double-marked-for-close warning when certain kinds of invalid
8957 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
8958 for bug 617. Bugfix on 0.2.0.1-alpha.
8959 - Make sure that the "NULL-means-reject *:*" convention is followed by
8960 all the policy manipulation functions, avoiding some possible crash
8961 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
8962 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
8963 actually works, and doesn't warn about every single reverse lookup.
8964 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
8967 - Only log guard node status when guard node status has changed.
8968 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
8969 make "INFO" 75% less verbose.
8972 Changes in version 0.2.0.21-rc - 2008-03-02
8973 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
8974 makes Tor work well with Vidalia again, fixes a rare assert bug,
8975 and fixes a pair of more minor bugs. The bundles also include Vidalia
8976 0.1.0 and Torbutton 1.1.16.
8979 - The control port should declare that it requires password auth
8980 when HashedControlSessionPassword is set too. Patch from Matt Edman;
8981 bugfix on 0.2.0.20-rc. Fixes bug 615.
8982 - Downgrade assert in connection_buckets_decrement() to a log message.
8983 This may help us solve bug 614, and in any case will make its
8984 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
8985 - We were sometimes miscounting the number of bytes read from the
8986 network, causing our rate limiting to not be followed exactly.
8987 Bugfix on 0.2.0.16-alpha. Reported by lodger.
8990 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
8991 OpenSSL versions should have been working fine. Diagnosis and patch
8992 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
8993 Bugfix on 0.2.0.20-rc.
8996 Changes in version 0.2.0.20-rc - 2008-02-24
8997 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
8998 makes more progress towards normalizing Tor's TLS handshake, makes
8999 hidden services work better again, helps relays bootstrap if they don't
9000 know their IP address, adds optional support for linking in openbsd's
9001 allocator or tcmalloc, allows really fast relays to scale past 15000
9002 sockets, and fixes a bunch of minor bugs reported by Veracode.
9005 - Enable the revised TLS handshake based on the one designed by
9006 Steven Murdoch in proposal 124, as revised in proposal 130. It
9007 includes version negotiation for OR connections as described in
9008 proposal 105. The new handshake is meant to be harder for censors
9009 to fingerprint, and it adds the ability to detect certain kinds of
9010 man-in-the-middle traffic analysis attacks. The version negotiation
9011 feature will allow us to improve Tor's link protocol more safely
9013 - Choose which bridge to use proportional to its advertised bandwidth,
9014 rather than uniformly at random. This should speed up Tor for
9015 bridge users. Also do this for people who set StrictEntryNodes.
9016 - When a TrackHostExits-chosen exit fails too many times in a row,
9017 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9020 - Resolved problems with (re-)fetching hidden service descriptors.
9021 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9023 - If we only ever used Tor for hidden service lookups or posts, we
9024 would stop building circuits and start refusing connections after
9025 24 hours, since we falsely believed that Tor was dormant. Reported
9026 by nwf; bugfix on 0.1.2.x.
9027 - Servers that don't know their own IP address should go to the
9028 authorities for their first directory fetch, even if their DirPort
9029 is off or if they don't know they're reachable yet. This will help
9030 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9031 - When counting the number of open sockets, count not only the number
9032 of sockets we have received from the socket() call, but also
9033 the number we've gotten from accept() and socketpair(). This bug
9034 made us fail to count all sockets that we were using for incoming
9035 connections. Bugfix on 0.2.0.x.
9036 - Fix code used to find strings within buffers, when those strings
9037 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9038 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9039 - Add a new __HashedControlSessionPassword option for controllers
9040 to use for one-off session password hashes that shouldn't get
9041 saved to disk by SAVECONF --- Vidalia users were accumulating a
9042 pile of HashedControlPassword lines in their torrc files, one for
9043 each time they had restarted Tor and then clicked Save. Make Tor
9044 automatically convert "HashedControlPassword" to this new option but
9045 only when it's given on the command line. Partial fix for bug 586.
9047 o Minor features (performance):
9048 - Tune parameters for cell pool allocation to minimize amount of
9050 - Add OpenBSD malloc code from phk as an optional malloc
9051 replacement on Linux: some glibc libraries do very poorly
9052 with Tor's memory allocation patterns. Pass
9053 --enable-openbsd-malloc to get the replacement malloc code.
9054 - Add a --with-tcmalloc option to the configure script to link
9055 against tcmalloc (if present). Does not yet search for
9056 non-system include paths.
9057 - Stop imposing an arbitrary maximum on the number of file descriptors
9058 used for busy servers. Bug reported by Olaf Selke; patch from
9061 o Minor features (other):
9062 - When SafeLogging is disabled, log addresses along with all TLS
9064 - When building with --enable-gcc-warnings, check for whether Apple's
9065 warning "-Wshorten-64-to-32" is available.
9066 - Add a --passphrase-fd argument to the tor-gencert command for
9069 o Minor bugfixes (memory leaks and code problems):
9070 - We were leaking a file descriptor if Tor started with a zero-length
9071 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9072 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9074 - We were comparing the raw BridgePassword entry with a base64'ed
9075 version of it, when handling a "/tor/networkstatus-bridges"
9076 directory request. Now compare correctly. Noticed by Veracode.
9077 - Recover from bad tracked-since value in MTBF-history file.
9079 - Alter the code that tries to recover from unhandled write
9080 errors, to not try to flush onto a socket that's given us
9081 unhandled errors. Bugfix on 0.1.2.x.
9082 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9083 tup. Bugfix on 0.2.0.3-alpha.
9085 o Minor bugfixes (other):
9086 - If we have an extra-info document for our server, always make
9087 it available on the control port, even if we haven't gotten
9088 a copy of it from an authority yet. Patch from mwenge.
9089 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9090 - Directory mirrors no longer include a guess at the client's IP
9091 address if the connection appears to be coming from the same /24
9092 network; it was producing too many wrong guesses.
9093 - Make the new hidden service code respect the SafeLogging setting.
9094 Bugfix on 0.2.0.x. Patch from Karsten.
9095 - When starting as an authority, do not overwrite all certificates
9096 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9097 - If we're trying to flush the last bytes on a connection (for
9098 example, when answering a directory request), reset the
9099 time-to-give-up timeout every time we manage to write something
9100 on the socket. Bugfix on 0.1.2.x.
9101 - Change the behavior of "getinfo status/good-server-descriptor"
9102 so it doesn't return failure when any authority disappears.
9103 - Even though the man page said that "TrackHostExits ." should
9104 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9105 - Report TLS "zero return" case as a "clean close" and "IO error"
9106 as a "close". Stop calling closes "unexpected closes": existing
9107 Tors don't use SSL_close(), so having a connection close without
9108 the TLS shutdown handshake is hardly unexpected.
9109 - Send NAMESERVER_STATUS messages for a single failed nameserver
9112 o Code simplifications and refactoring:
9113 - Remove the tor_strpartition function: its logic was confused,
9114 and it was only used for one thing that could be implemented far
9118 Changes in version 0.2.0.19-alpha - 2008-02-09
9119 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9120 handshake, makes path selection for relays more secure and IP address
9121 guessing more robust, and generally fixes a lot of bugs in preparation
9122 for calling the 0.2.0 branch stable.
9125 - Do not include recognizeable strings in the commonname part of
9126 Tor's x509 certificates.
9129 - If we're a relay, avoid picking ourselves as an introduction point,
9130 a rendezvous point, or as the final hop for internal circuits. Bug
9131 reported by taranis and lodger. Bugfix on 0.1.2.x.
9132 - Patch from "Andrew S. Lists" to catch when we contact a directory
9133 mirror at IP address X and he says we look like we're coming from
9134 IP address X. Bugfix on 0.1.2.x.
9136 o Minor features (security):
9137 - Be more paranoid about overwriting sensitive memory on free(),
9138 as a defensive programming tactic to ensure forward secrecy.
9140 o Minor features (directory authority):
9141 - Actually validate the options passed to AuthDirReject,
9142 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9143 - Reject router descriptors with out-of-range bandwidthcapacity or
9144 bandwidthburst values.
9146 o Minor features (controller):
9147 - Reject controller commands over 1MB in length. This keeps rogue
9148 processes from running us out of memory.
9150 o Minor features (misc):
9151 - Give more descriptive well-formedness errors for out-of-range
9152 hidden service descriptor/protocol versions.
9153 - Make memory debugging information describe more about history
9154 of cell allocation, so we can help reduce our memory use.
9156 o Deprecated features (controller):
9157 - The status/version/num-versioning and status/version/num-concurring
9158 GETINFO options are no longer useful in the v3 directory protocol:
9159 treat them as deprecated, and warn when they're used.
9162 - When our consensus networkstatus has been expired for a while, stop
9163 being willing to build circuits using it. Fixes bug 401. Bugfix
9165 - Directory caches now fetch certificates from all authorities
9166 listed in a networkstatus consensus, even when they do not
9167 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9168 - When connecting to a bridge without specifying its key, insert
9169 the connection into the identity-to-connection map as soon as
9170 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9171 - Detect versions of OS X where malloc_good_size() is present in the
9172 library but never actually declared. Resolves bug 587. Bugfix
9174 - Stop incorrectly truncating zlib responses to directory authority
9175 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9176 - Stop recommending that every server operator send mail to tor-ops.
9177 Resolves bug 597. Bugfix on 0.1.2.x.
9178 - Don't trigger an assert if we start a directory authority with a
9179 private IP address (like 127.0.0.1).
9180 - Avoid possible failures when generating a directory with routers
9181 with over-long versions strings, or too many flags set. Bugfix
9183 - If an attempt to launch a DNS resolve request over the control
9184 port fails because we have overrun the limit on the number of
9185 connections, tell the controller that the request has failed.
9186 - Avoid using too little bandwidth when our clock skips a few
9187 seconds. Bugfix on 0.1.2.x.
9188 - Fix shell error when warning about missing packages in configure
9189 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9190 - Do not become confused when receiving a spurious VERSIONS-like
9191 cell from a confused v1 client. Bugfix on 0.2.0.x.
9192 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9193 introduction points for a hidden service have failed. Patch from
9194 Karsten Loesing. Bugfix on 0.2.0.x.
9196 o Code simplifications and refactoring:
9197 - Remove some needless generality from cpuworker code, for improved
9199 - Stop overloading the circuit_t.onionskin field for both "onionskin
9200 from a CREATE cell that we are waiting for a cpuworker to be
9201 assigned" and "onionskin from an EXTEND cell that we are going to
9202 send to an OR as soon as we are connected". Might help with bug 600.
9203 - Add an in-place version of aes_crypt() so that we can avoid doing a
9204 needless memcpy() call on each cell payload.
9207 Changes in version 0.2.0.18-alpha - 2008-01-25
9208 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9209 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9210 that can warn or reject connections to ports generally associated with
9211 vulnerable-plaintext protocols.
9213 o New directory authorities:
9214 - Set up dannenberg (run by CCC) as the sixth v3 directory
9218 - Fix a major memory leak when attempting to use the v2 TLS
9219 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9220 - We accidentally enabled the under-development v2 TLS handshake
9221 code, which was causing log entries like "TLS error while
9222 renegotiating handshake". Disable it again. Resolves bug 590.
9223 - We were computing the wrong Content-Length: header for directory
9224 responses that need to be compressed on the fly, causing clients
9225 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9229 - Avoid going directly to the directory authorities even if you're a
9230 relay, if you haven't found yourself reachable yet or if you've
9231 decided not to advertise your dirport yet. Addresses bug 556.
9232 - If we've gone 12 hours since our last bandwidth check, and we
9233 estimate we have less than 50KB bandwidth capacity but we could
9234 handle more, do another bandwidth test.
9235 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9236 Tor can warn and/or refuse connections to ports commonly used with
9237 vulnerable-plaintext protocols. Currently we warn on ports 23,
9238 109, 110, and 143, but we don't reject any.
9241 - When we setconf ClientOnly to 1, close any current OR and Dir
9242 listeners. Reported by mwenge.
9243 - When we get a consensus that's been signed by more people than
9244 we expect, don't log about it; it's not a big deal. Reported
9248 - Don't answer "/tor/networkstatus-bridges" directory requests if
9249 the request isn't encrypted.
9250 - Make "ClientOnly 1" config option disable directory ports too.
9251 - Patches from Karsten Loesing to make v2 hidden services more
9252 robust: work even when there aren't enough HSDir relays available;
9253 retry when a v2 rend desc fetch fails; but don't retry if we
9254 already have a usable v0 rend desc.
9257 Changes in version 0.2.0.17-alpha - 2008-01-17
9258 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9261 - Make the tor-gencert man page get included correctly in the tarball.
9264 Changes in version 0.2.0.16-alpha - 2008-01-17
9265 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9266 Loesing, and generally cleans up a lot of features and minor bugs.
9268 o New directory authorities:
9269 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9272 o Major performance improvements:
9273 - Switch our old ring buffer implementation for one more like that
9274 used by free Unix kernels. The wasted space in a buffer with 1mb
9275 of data will now be more like 8k than 1mb. The new implementation
9276 also avoids realloc();realloc(); patterns that can contribute to
9277 memory fragmentation.
9280 - Configuration files now accept C-style strings as values. This
9281 helps encode characters not allowed in the current configuration
9282 file format, such as newline or #. Addresses bug 557.
9283 - Although we fixed bug 539 (where servers would send HTTP status 503
9284 responses _and_ send a body too), there are still servers out
9285 there that haven't upgraded. Therefore, make clients parse such
9286 bodies when they receive them.
9287 - When we're not serving v2 directory information, there is no reason
9288 to actually keep any around. Remove the obsolete files and directory
9289 on startup if they are very old and we aren't going to serve them.
9291 o Minor performance improvements:
9292 - Reference-count and share copies of address policy entries; only 5%
9293 of them were actually distinct.
9294 - Never walk through the list of logs if we know that no log is
9295 interested in a given message.
9298 - When an authority has not signed a consensus, do not try to
9299 download a nonexistent "certificate with key 00000000". Bugfix
9300 on 0.2.0.x. Fixes bug 569.
9301 - Fix a rare assert error when we're closing one of our threads:
9302 use a mutex to protect the list of logs, so we never write to the
9303 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9304 bug 575, which is kind of the revenge of bug 222.
9305 - Patch from Karsten Loesing to complain less at both the client
9306 and the relay when a relay used to have the HSDir flag but doesn't
9307 anymore, and we try to upload a hidden service descriptor.
9308 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9310 - Do not try to download missing certificates until we have tried
9311 to check our fallback consensus. Fixes bug 583.
9312 - Make bridges round reported GeoIP stats info up to the nearest
9313 estimate, not down. Now we can distinguish between "0 people from
9314 this country" and "1 person from this country".
9315 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9316 - Avoid possible segfault if key generation fails in
9317 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9318 - Avoid segfault in the case where a badly behaved v2 versioning
9319 directory sends a signed networkstatus with missing client-versions.
9321 - Avoid segfaults on certain complex invocations of
9322 router_get_by_hexdigest(). Bugfix on 0.1.2.
9323 - Correct bad index on array access in parse_http_time(). Bugfix
9325 - Fix possible bug in vote generation when server versions are present
9326 but client versions are not.
9327 - Fix rare bug on REDIRECTSTREAM control command when called with no
9328 port set: it could erroneously report an error when none had
9330 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9331 compressing large objects and find ourselves with more than 4k
9332 left over. Bugfix on 0.2.0.
9333 - Fix a small memory leak when setting up a hidden service.
9334 - Fix a few memory leaks that could in theory happen under bizarre
9336 - Fix an assert if we post a general-purpose descriptor via the
9337 control port but that descriptor isn't mentioned in our current
9338 network consensus. Bug reported by Jon McLachlan; bugfix on
9341 o Minor features (controller):
9342 - Get NS events working again. Patch from tup.
9343 - The GETCONF command now escapes and quotes configuration values
9344 that don't otherwise fit into the torrc file.
9345 - The SETCONF command now handles quoted values correctly.
9347 o Minor features (directory authorities):
9348 - New configuration options to override default maximum number of
9349 servers allowed on a single IP address. This is important for
9350 running a test network on a single host.
9351 - Actually implement the -s option to tor-gencert.
9352 - Add a manual page for tor-gencert.
9354 o Minor features (bridges):
9355 - Bridge authorities no longer serve bridge descriptors over
9356 unencrypted connections.
9358 o Minor features (other):
9359 - Add hidden services and DNSPorts to the list of things that make
9360 Tor accept that it has running ports. Change starting Tor with no
9361 ports from a fatal error to a warning; we might change it back if
9362 this turns out to confuse anybody. Fixes bug 579.
9365 Changes in version 0.1.2.19 - 2008-01-17
9366 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9367 exit policy a little bit more conservative so it's safer to run an
9368 exit relay on a home system, and fixes a variety of smaller issues.
9371 - Exit policies now reject connections that are addressed to a
9372 relay's public (external) IP address too, unless
9373 ExitPolicyRejectPrivate is turned off. We do this because too
9374 many relays are running nearby to services that trust them based
9378 - When the clock jumps forward a lot, do not allow the bandwidth
9379 buckets to become negative. Fixes bug 544.
9380 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9381 on every successful resolve. Reported by Mike Perry.
9382 - Purge old entries from the "rephist" database and the hidden
9383 service descriptor database even when DirPort is zero.
9384 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9385 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9386 crashing or mis-answering these requests.
9387 - When we decide to send a 503 response to a request for servers, do
9388 not then also send the server descriptors: this defeats the whole
9389 purpose. Fixes bug 539.
9392 - Changing the ExitPolicyRejectPrivate setting should cause us to
9393 rebuild our server descriptor.
9394 - Fix handling of hex nicknames when answering controller requests for
9395 networkstatus by name, or when deciding whether to warn about
9396 unknown routers in a config option. (Patch from mwenge.)
9397 - Fix a couple of hard-to-trigger autoconf problems that could result
9398 in really weird results on platforms whose sys/types.h files define
9399 nonstandard integer types.
9400 - Don't try to create the datadir when running --verify-config or
9401 --hash-password. Resolves bug 540.
9402 - If we were having problems getting a particular descriptor from the
9403 directory caches, and then we learned about a new descriptor for
9404 that router, we weren't resetting our failure count. Reported
9406 - Although we fixed bug 539 (where servers would send HTTP status 503
9407 responses _and_ send a body too), there are still servers out there
9408 that haven't upgraded. Therefore, make clients parse such bodies
9409 when they receive them.
9410 - Run correctly on systems where rlim_t is larger than unsigned long.
9411 This includes some 64-bit systems.
9412 - Run correctly on platforms (like some versions of OS X 10.5) where
9413 the real limit for number of open files is OPEN_FILES, not rlim_max
9414 from getrlimit(RLIMIT_NOFILES).
9415 - Avoid a spurious free on base64 failure.
9416 - Avoid segfaults on certain complex invocations of
9417 router_get_by_hexdigest().
9418 - Fix rare bug on REDIRECTSTREAM control command when called with no
9419 port set: it could erroneously report an error when none had
9423 Changes in version 0.2.0.15-alpha - 2007-12-25
9424 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9425 features added in 0.2.0.13-alpha.
9428 - Fix several remotely triggerable asserts based on DirPort requests
9429 for a v2 or v3 networkstatus object before we were prepared. This
9430 was particularly bad for 0.2.0.13 and later bridge relays, who
9431 would never have a v2 networkstatus and would thus always crash
9432 when used. Bugfixes on 0.2.0.x.
9433 - Estimate the v3 networkstatus size more accurately, rather than
9434 estimating it at zero bytes and giving it artificially high priority
9435 compared to other directory requests. Bugfix on 0.2.0.x.
9438 - Fix configure.in logic for cross-compilation.
9439 - When we load a bridge descriptor from the cache, and it was
9440 previously unreachable, mark it as retriable so we won't just
9441 ignore it. Also, try fetching a new copy immediately. Bugfixes
9443 - The bridge GeoIP stats were counting other relays, for example
9444 self-reachability and authority-reachability tests.
9447 - Support compilation to target iPhone; patch from cjacker huang.
9448 To build for iPhone, pass the --enable-iphone option to configure.
9451 Changes in version 0.2.0.14-alpha - 2007-12-23
9453 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9454 without a datadirectory from a previous Tor install. Reported
9456 - Fix a crash when we fetch a descriptor that turns out to be
9457 unexpected (it used to be in our networkstatus when we started
9458 fetching it, but it isn't in our current networkstatus), and we
9459 aren't using bridges. Bugfix on 0.2.0.x.
9460 - Fix a crash when accessing hidden services: it would work the first
9461 time you use a given introduction point for your service, but
9462 on subsequent requests we'd be using garbage memory. Fixed by
9463 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9464 - Fix a crash when we load a bridge descriptor from disk but we don't
9465 currently have a Bridge line for it in our torrc. Bugfix on
9469 - If bridge authorities set BridgePassword, they will serve a
9470 snapshot of known bridge routerstatuses from their DirPort to
9471 anybody who knows that password. Unset by default.
9474 - Make the unit tests build again.
9475 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9476 - Make PublishServerDescriptor default to 1, so the default doesn't
9477 have to change as we invent new directory protocol versions.
9478 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9479 be included unless sys/time.h is already included. Fixes
9480 bug 553. Bugfix on 0.2.0.x.
9481 - If we receive a general-purpose descriptor and then receive an
9482 identical bridge-purpose descriptor soon after, don't discard
9483 the next one as a duplicate.
9486 - If BridgeRelay is set to 1, then the default for
9487 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9488 - If the user sets RelayBandwidthRate but doesn't set
9489 RelayBandwidthBurst, then make them equal rather than erroring out.
9492 Changes in version 0.2.0.13-alpha - 2007-12-21
9493 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9494 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9497 o New directory authorities:
9498 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9502 - Only update guard status (usable / not usable) once we have
9503 enough directory information. This was causing us to always pick
9504 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9505 causing us to discard all our guards on startup if we hadn't been
9506 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9507 - Purge old entries from the "rephist" database and the hidden
9508 service descriptor databases even when DirPort is zero. Bugfix
9510 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9511 after opening a circuit -- even a relayed circuit. Bugfix on
9513 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9514 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9515 crashing or mis-answering these types of requests.
9516 - Relays were publishing their server descriptor to v1 and v2
9517 directory authorities, but they didn't try publishing to v3-only
9518 authorities. Fix this; and also stop publishing to v1 authorities.
9520 - When we were reading router descriptors from cache, we were ignoring
9521 the annotations -- so for example we were reading in bridge-purpose
9522 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9523 - When we decided to send a 503 response to a request for servers, we
9524 were then also sending the server descriptors: this defeats the
9525 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9528 - Bridge relays now behave like clients with respect to time
9529 intervals for downloading new consensus documents -- otherwise they
9530 stand out. Bridge users now wait until the end of the interval,
9531 so their bridge relay will be sure to have a new consensus document.
9532 - Three new config options (AlternateDirAuthority,
9533 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9534 user selectively replace the default directory authorities by type,
9535 rather than the all-or-nothing replacement that DirServer offers.
9536 - Tor can now be configured to read a GeoIP file from disk in one
9537 of two formats. This can be used by controllers to map IP addresses
9538 to countries. Eventually, it may support exit-by-country.
9539 - When possible, bridge relays remember which countries users
9540 are coming from, and report aggregate information in their
9541 extra-info documents, so that the bridge authorities can learn
9542 where Tor is blocked.
9543 - Bridge directory authorities now do reachability testing on the
9544 bridges they know. They provide router status summaries to the
9545 controller via "getinfo ns/purpose/bridge", and also dump summaries
9546 to a file periodically.
9547 - Stop fetching directory info so aggressively if your DirPort is
9548 on but your ORPort is off; stop fetching v2 dir info entirely.
9549 You can override these choices with the new FetchDirInfoEarly
9553 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9554 consensus documents when there are too many relays at a single
9555 IP address. Now clear it in v2 network status documents too, and
9556 also clear it in routerinfo_t when the relay is no longer listed
9557 in the relevant networkstatus document.
9558 - Don't crash if we get an unexpected value for the
9559 PublishServerDescriptor config option. Reported by Matt Edman;
9560 bugfix on 0.2.0.9-alpha.
9561 - Our new v2 hidden service descriptor format allows descriptors
9562 that have no introduction points. But Tor crashed when we tried
9563 to build a descriptor with no intro points (and it would have
9564 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9566 - Fix building with dmalloc 5.5.2 with glibc.
9567 - Reject uploaded descriptors and extrainfo documents if they're
9568 huge. Otherwise we'll cache them all over the network and it'll
9569 clog everything up. Reported by Aljosha Judmayer.
9570 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9571 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9572 - When the DANGEROUS_VERSION controller status event told us we're
9573 running an obsolete version, it used the string "OLD" to describe
9574 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9575 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9576 - If we can't expand our list of entry guards (e.g. because we're
9577 using bridges or we have StrictEntryNodes set), don't mark relays
9578 down when they fail a directory request. Otherwise we're too quick
9579 to mark all our entry points down. Bugfix on 0.1.2.x.
9580 - Fix handling of hex nicknames when answering controller requests for
9581 networkstatus by name, or when deciding whether to warn about unknown
9582 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9583 - Fix a couple of hard-to-trigger autoconf problems that could result
9584 in really weird results on platforms whose sys/types.h files define
9585 nonstandard integer types. Bugfix on 0.1.2.x.
9586 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9587 - Don't crash on name lookup when we have no current consensus. Fixes
9588 bug 538; bugfix on 0.2.0.x.
9589 - Only Tors that want to mirror the v2 directory info should
9590 create the "cached-status" directory in their datadir. (All Tors
9591 used to create it.) Bugfix on 0.2.0.9-alpha.
9592 - Directory authorities should only automatically download Extra Info
9593 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9596 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9597 consumers. (We already do this on HUP.)
9598 - Authorities and caches fetch the v2 networkstatus documents
9599 less often, now that v3 is encouraged.
9600 - Add a new config option BridgeRelay that specifies you want to
9601 be a bridge relay. Right now the only difference is that it makes
9602 you answer begin_dir requests, and it makes you cache dir info,
9603 even if your DirPort isn't on.
9604 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9605 ask about source, timestamp of arrival, purpose, etc. We need
9606 something like this to help Vidalia not do GeoIP lookups on bridge
9608 - Allow multiple HashedControlPassword config lines, to support
9609 multiple controller passwords.
9610 - Authorities now decide whether they're authoritative for a given
9611 router based on the router's purpose.
9612 - New config options AuthDirBadDir and AuthDirListBadDirs for
9613 authorities to mark certain relays as "bad directories" in the
9614 networkstatus documents. Also supports the "!baddir" directive in
9615 the approved-routers file.
9618 Changes in version 0.2.0.12-alpha - 2007-11-16
9619 This twelfth development snapshot fixes some more build problems as
9620 well as a few minor bugs.
9623 - Make it build on OpenBSD again. Patch from tup.
9624 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9625 package-building for Red Hat, OS X, etc.
9627 o Minor bugfixes (on 0.1.2.x):
9628 - Changing the ExitPolicyRejectPrivate setting should cause us to
9629 rebuild our server descriptor.
9631 o Minor bugfixes (on 0.2.0.x):
9632 - When we're lacking a consensus, don't try to perform rendezvous
9633 operations. Reported by Karsten Loesing.
9634 - Fix a small memory leak whenever we decide against using a
9635 newly picked entry guard. Reported by Mike Perry.
9636 - When authorities detected more than two relays running on the same
9637 IP address, they were clearing all the status flags but forgetting
9638 to clear the "hsdir" flag. So clients were being told that a
9639 given relay was the right choice for a v2 hsdir lookup, yet they
9640 never had its descriptor because it was marked as 'not running'
9642 - If we're trying to fetch a bridge descriptor and there's no way
9643 the bridge authority could help us (for example, we don't know
9644 a digest, or there is no bridge authority), don't be so eager to
9645 fall back to asking the bridge authority.
9646 - If we're using bridges or have strictentrynodes set, and our
9647 chosen exit is in the same family as all our bridges/entry guards,
9648 then be flexible about families.
9651 - When we negotiate a v2 link-layer connection (not yet implemented),
9652 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9653 negotiated a v1 connection for their next step. Initial code for
9657 Changes in version 0.2.0.11-alpha - 2007-11-12
9658 This eleventh development snapshot fixes some build problems with
9659 the previous snapshot. It also includes a more secure-by-default exit
9660 policy for relays, fixes an enormous memory leak for exit relays, and
9661 fixes another bug where servers were falling out of the directory list.
9664 - Exit policies now reject connections that are addressed to a
9665 relay's public (external) IP address too, unless
9666 ExitPolicyRejectPrivate is turned off. We do this because too
9667 many relays are running nearby to services that trust them based
9668 on network address. Bugfix on 0.1.2.x.
9671 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9672 on every successful resolve. Reported by Mike Perry; bugfix
9674 - On authorities, never downgrade to old router descriptors simply
9675 because they're listed in the consensus. This created a catch-22
9676 where we wouldn't list a new descriptor because there was an
9677 old one in the consensus, and we couldn't get the new one in the
9678 consensus because we wouldn't list it. Possible fix for bug 548.
9679 Also, this might cause bug 543 to appear on authorities; if so,
9680 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
9682 o Packaging fixes on 0.2.0.10-alpha:
9683 - We were including instructions about what to do with the
9684 src/config/fallback-consensus file, but we weren't actually
9685 including it in the tarball. Disable all of that for now.
9688 - Allow people to say PreferTunnelledDirConns rather than
9689 PreferTunneledDirConns, for those alternate-spellers out there.
9692 - Don't reevaluate all the information from our consensus document
9693 just because we've downloaded a v2 networkstatus that we intend
9694 to cache. Fixes bug 545; bugfix on 0.2.0.x.
9697 Changes in version 0.2.0.10-alpha - 2007-11-10
9698 This tenth development snapshot adds a third v3 directory authority
9699 run by Mike Perry, adds most of Karsten Loesing's new hidden service
9700 descriptor format, fixes a bad crash bug and new bridge bugs introduced
9701 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
9702 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
9703 addresses many more minor issues.
9705 o New directory authorities:
9706 - Set up ides (run by Mike Perry) as the third v3 directory authority.
9709 - Allow tunnelled directory connections to ask for an encrypted
9710 "begin_dir" connection or an anonymized "uses a full Tor circuit"
9711 connection independently. Now we can make anonymized begin_dir
9712 connections for (e.g.) more secure hidden service posting and
9714 - More progress on proposal 114: code from Karsten Loesing to
9715 implement new hidden service descriptor format.
9716 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
9717 accommodate the growing number of servers that use the default
9718 and are reaching it.
9719 - Directory authorities use a new formula for selecting which nodes
9720 to advertise as Guards: they must be in the top 7/8 in terms of
9721 how long we have known about them, and above the median of those
9722 nodes in terms of weighted fractional uptime.
9723 - Make "not enough dir info yet" warnings describe *why* Tor feels
9724 it doesn't have enough directory info yet.
9727 - Stop servers from crashing if they set a Family option (or
9728 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
9730 - Make bridge users work again -- the move to v3 directories in
9731 0.2.0.9-alpha had introduced a number of bugs that made bridges
9732 no longer work for clients.
9733 - When the clock jumps forward a lot, do not allow the bandwidth
9734 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
9736 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
9737 - When the consensus lists a router descriptor that we previously were
9738 mirroring, but that we considered non-canonical, reload the
9739 descriptor as canonical. This fixes bug 543 where Tor servers
9740 would start complaining after a few days that they don't have
9741 enough directory information to build a circuit.
9742 - Consider replacing the current consensus when certificates arrive
9743 that make the pending consensus valid. Previously, we were only
9744 considering replacement when the new certs _didn't_ help.
9745 - Fix an assert error on startup if we didn't already have the
9746 consensus and certs cached in our datadirectory: we were caching
9747 the consensus in consensus_waiting_for_certs but then free'ing it
9749 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
9750 Request) if we need more v3 certs but we've already got pending
9751 requests for all of them.
9752 - Correctly back off from failing certificate downloads. Fixes
9754 - Authorities don't vote on the Running flag if they have been running
9755 for less than 30 minutes themselves. Fixes bug 547, where a newly
9756 started authority would vote that everyone was down.
9759 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
9760 it, it had no AES, and it hasn't seen any security patches since
9764 - Clients now hold circuitless TLS connections open for 1.5 times
9765 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
9766 rebuild a new circuit over them within that timeframe. Previously,
9767 they held them open only for KeepalivePeriod (5 minutes).
9768 - Use "If-Modified-Since" to avoid retrieving consensus
9769 networkstatuses that we already have.
9770 - When we have no consensus, check FallbackNetworkstatusFile (defaults
9771 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
9772 we start knowing some directory caches.
9773 - When we receive a consensus from the future, warn about skew.
9774 - Improve skew reporting: try to give the user a better log message
9775 about how skewed they are, and how much this matters.
9776 - When we have a certificate for an authority, believe that
9777 certificate's claims about the authority's IP address.
9778 - New --quiet command-line option to suppress the default console log.
9779 Good in combination with --hash-password.
9780 - Authorities send back an X-Descriptor-Not-New header in response to
9781 an accepted-but-discarded descriptor upload. Partially implements
9783 - Make the log message for "tls error. breaking." more useful.
9784 - Better log messages about certificate downloads, to attempt to
9785 track down the second incarnation of bug 546.
9787 o Minor features (bridges):
9788 - If bridge users set UpdateBridgesFromAuthority, but the digest
9789 they ask for is a 404 from the bridge authority, they now fall
9790 back to trying the bridge directly.
9791 - Bridges now use begin_dir to publish their server descriptor to
9792 the bridge authority, even when they haven't set TunnelDirConns.
9794 o Minor features (controller):
9795 - When reporting clock skew, and we know that the clock is _at least
9796 as skewed_ as some value, but we don't know the actual value,
9797 report the value as a "minimum skew."
9800 - Update linux-tor-prio.sh script to allow QoS based on the uid of
9801 the Tor process. Patch from Marco Bonetti with tweaks from Mike
9805 - Refuse to start if both ORPort and UseBridges are set. Bugfix
9806 on 0.2.0.x, suggested by Matt Edman.
9807 - Don't stop fetching descriptors when FetchUselessDescriptors is
9808 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
9809 reported by tup and ioerror.
9810 - Better log message on vote from unknown authority.
9811 - Don't log "Launching 0 request for 0 router" message.
9813 o Minor bugfixes (memory leaks):
9814 - Stop leaking memory every time we parse a v3 certificate. Bugfix
9816 - Stop leaking memory every time we load a v3 certificate. Bugfix
9817 on 0.2.0.1-alpha. Fixes bug 536.
9818 - Stop leaking a cached networkstatus on exit. Bugfix on
9820 - Stop leaking voter information every time we free a consensus.
9821 Bugfix on 0.2.0.3-alpha.
9822 - Stop leaking signed data every time we check a voter signature.
9823 Bugfix on 0.2.0.3-alpha.
9824 - Stop leaking a signature every time we fail to parse a consensus or
9825 a vote. Bugfix on 0.2.0.3-alpha.
9826 - Stop leaking v2_download_status_map on shutdown. Bugfix on
9828 - Stop leaking conn->nickname every time we make a connection to a
9829 Tor relay without knowing its expected identity digest (e.g. when
9830 using bridges). Bugfix on 0.2.0.3-alpha.
9832 - Minor bugfixes (portability):
9833 - Run correctly on platforms where rlim_t is larger than unsigned
9834 long, and/or where the real limit for number of open files is
9835 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
9836 particular, these may be needed for OS X 10.5.
9839 Changes in version 0.1.2.18 - 2007-10-28
9840 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
9841 hidden service introduction that were causing huge delays, and a big
9842 bug that was causing some servers to disappear from the network status
9843 lists for a few hours each day.
9845 o Major bugfixes (crashes):
9846 - If a connection is shut down abruptly because of something that
9847 happened inside connection_flushed_some(), do not call
9848 connection_finished_flushing(). Should fix bug 451:
9849 "connection_stop_writing: Assertion conn->write_event failed"
9850 Bugfix on 0.1.2.7-alpha.
9851 - Fix possible segfaults in functions called from
9852 rend_process_relay_cell().
9854 o Major bugfixes (hidden services):
9855 - Hidden services were choosing introduction points uniquely by
9856 hexdigest, but when constructing the hidden service descriptor
9857 they merely wrote the (potentially ambiguous) nickname.
9858 - Clients now use the v2 intro format for hidden service
9859 connections: they specify their chosen rendezvous point by identity
9860 digest rather than by (potentially ambiguous) nickname. These
9861 changes could speed up hidden service connections dramatically.
9863 o Major bugfixes (other):
9864 - Stop publishing a new server descriptor just because we get a
9865 HUP signal. This led (in a roundabout way) to some servers getting
9866 dropped from the networkstatus lists for a few hours each day.
9867 - When looking for a circuit to cannibalize, consider family as well
9868 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9869 circuit cannibalization).
9870 - When a router wasn't listed in a new networkstatus, we were leaving
9871 the flags for that router alone -- meaning it remained Named,
9872 Running, etc -- even though absence from the networkstatus means
9873 that it shouldn't be considered to exist at all anymore. Now we
9874 clear all the flags for routers that fall out of the networkstatus
9875 consensus. Fixes bug 529.
9878 - Don't try to access (or alter) the state file when running
9879 --list-fingerprint or --verify-config or --hash-password. Resolves
9881 - When generating information telling us how to extend to a given
9882 router, do not try to include the nickname if it is
9883 absent. Resolves bug 467.
9884 - Fix a user-triggerable segfault in expand_filename(). (There isn't
9885 a way to trigger this remotely.)
9886 - When sending a status event to the controller telling it that an
9887 OR address is reachable, set the port correctly. (Previously we
9888 were reporting the dir port.)
9889 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9890 command. Bugfix on 0.1.2.17.
9891 - When loading bandwidth history, do not believe any information in
9892 the future. Fixes bug 434.
9893 - When loading entry guard information, do not believe any information
9895 - When we have our clock set far in the future and generate an
9896 onion key, then re-set our clock to be correct, we should not stop
9897 the onion key from getting rotated.
9898 - On some platforms, accept() can return a broken address. Detect
9899 this more quietly, and deal accordingly. Fixes bug 483.
9900 - It's not actually an error to find a non-pending entry in the DNS
9901 cache when canceling a pending resolve. Don't log unless stuff
9902 is fishy. Resolves bug 463.
9903 - Don't reset trusted dir server list when we set a configuration
9904 option. Patch from Robert Hogan.
9905 - Don't try to create the datadir when running --verify-config or
9906 --hash-password. Resolves bug 540.
9909 Changes in version 0.2.0.9-alpha - 2007-10-24
9910 This ninth development snapshot switches clients to the new v3 directory
9911 system; allows servers to be listed in the network status even when they
9912 have the same nickname as a registered server; and fixes many other
9913 bugs including a big one that was causing some servers to disappear
9914 from the network status lists for a few hours each day.
9916 o Major features (directory system):
9917 - Clients now download v3 consensus networkstatus documents instead
9918 of v2 networkstatus documents. Clients and caches now base their
9919 opinions about routers on these consensus documents. Clients only
9920 download router descriptors listed in the consensus.
9921 - Authorities now list servers who have the same nickname as
9922 a different named server, but list them with a new flag,
9923 "Unnamed". Now we can list servers that happen to pick the same
9924 nickname as a server that registered two years ago and then
9925 disappeared. Partially implements proposal 122.
9926 - If the consensus lists a router as "Unnamed", the name is assigned
9927 to a different router: do not identify the router by that name.
9928 Partially implements proposal 122.
9929 - Authorities can now come to a consensus on which method to use to
9930 compute the consensus. This gives us forward compatibility.
9933 - Stop publishing a new server descriptor just because we HUP or
9934 when we find our DirPort to be reachable but won't actually publish
9935 it. New descriptors without any real changes are dropped by the
9936 authorities, and can screw up our "publish every 18 hours" schedule.
9938 - When a router wasn't listed in a new networkstatus, we were leaving
9939 the flags for that router alone -- meaning it remained Named,
9940 Running, etc -- even though absence from the networkstatus means
9941 that it shouldn't be considered to exist at all anymore. Now we
9942 clear all the flags for routers that fall out of the networkstatus
9943 consensus. Fixes bug 529; bugfix on 0.1.2.x.
9944 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
9945 extrainfo documents and then discard them immediately for not
9946 matching the latest router. Bugfix on 0.2.0.1-alpha.
9948 o Minor features (v3 directory protocol):
9949 - Allow tor-gencert to generate a new certificate without replacing
9951 - Allow certificates to include an address.
9952 - When we change our directory-cache settings, reschedule all voting
9953 and download operations.
9954 - Reattempt certificate downloads immediately on failure, as long as
9955 we haven't failed a threshold number of times yet.
9956 - Delay retrying consensus downloads while we're downloading
9957 certificates to verify the one we just got. Also, count getting a
9958 consensus that we already have (or one that isn't valid) as a failure,
9959 and count failing to get the certificates after 20 minutes as a
9961 - Build circuits and download descriptors even if our consensus is a
9962 little expired. (This feature will go away once authorities are
9965 o Minor features (router descriptor cache):
9966 - If we find a cached-routers file that's been sitting around for more
9967 than 28 days unmodified, then most likely it's a leftover from
9968 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
9970 - When we (as a cache) download a descriptor because it was listed
9971 in a consensus, remember when the consensus was supposed to expire,
9972 and don't expire the descriptor until then.
9974 o Minor features (performance):
9975 - Call routerlist_remove_old_routers() much less often. This should
9976 speed startup, especially on directory caches.
9977 - Don't try to launch new descriptor downloads quite so often when we
9978 already have enough directory information to build circuits.
9979 - Base64 decoding was actually showing up on our profile when parsing
9980 the initial descriptor file; switch to an in-process all-at-once
9981 implementation that's about 3.5x times faster than calling out to
9984 o Minor features (compilation):
9985 - Detect non-ASCII platforms (if any still exist) and refuse to
9986 build there: some of our code assumes that 'A' is 65 and so on.
9988 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
9989 - Make the "next period" votes into "current period" votes immediately
9990 after publishing the consensus; avoid a heisenbug that made them
9991 stick around indefinitely.
9992 - When we discard a vote as a duplicate, do not report this as
9994 - Treat missing v3 keys or certificates as an error when running as a
9995 v3 directory authority.
9996 - When we're configured to be a v3 authority, but we're only listed
9997 as a non-v3 authority in our DirServer line for ourself, correct
9999 - If an authority doesn't have a qualified hostname, just put
10000 its address in the vote. This fixes the problem where we referred to
10001 "moria on moria:9031."
10002 - Distinguish between detached signatures for the wrong period, and
10003 detached signatures for a divergent vote.
10004 - Fix a small memory leak when computing a consensus.
10005 - When there's no concensus, we were forming a vote every 30
10006 minutes, but writing the "valid-after" line in our vote based
10007 on our configured V3AuthVotingInterval: so unless the intervals
10008 matched up, we immediately rejected our own vote because it didn't
10009 start at the voting interval that caused us to construct a vote.
10011 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10012 - Delete unverified-consensus when the real consensus is set.
10013 - Consider retrying a consensus networkstatus fetch immediately
10014 after one fails: don't wait 60 seconds to notice.
10015 - When fetching a consensus as a cache, wait until a newer consensus
10016 should exist before trying to replace the current one.
10017 - Use a more forgiving schedule for retrying failed consensus
10018 downloads than for other types.
10020 o Minor bugfixes (other directory issues):
10021 - Correct the implementation of "download votes by digest." Bugfix on
10023 - Authorities no longer send back "400 you're unreachable please fix
10024 it" errors to Tor servers that aren't online all the time. We're
10025 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10027 o Minor bugfixes (controller):
10028 - Don't reset trusted dir server list when we set a configuration
10029 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10030 - Respond to INT and TERM SIGNAL commands before we execute the
10031 signal, in case the signal shuts us down. We had a patch in
10032 0.1.2.1-alpha that tried to do this by queueing the response on
10033 the connection's buffer before shutting down, but that really
10034 isn't the same thing at all. Bug located by Matt Edman.
10036 o Minor bugfixes (misc):
10037 - Correctly check for bad options to the "PublishServerDescriptor"
10038 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10039 - Stop leaking memory on failing case of base32_decode, and make
10040 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10041 - Don't try to download extrainfo documents when we're trying to
10042 fetch enough directory info to build a circuit: having enough
10043 info should get priority. Bugfix on 0.2.0.x.
10044 - Don't complain that "your server has not managed to confirm that its
10045 ports are reachable" if we haven't been able to build any circuits
10046 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10048 - Detect the reason for failing to mmap a descriptor file we just
10049 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10052 o Code simplifications and refactoring:
10053 - Remove support for the old bw_accounting file: we've been storing
10054 bandwidth accounting information in the state file since
10055 0.1.2.5-alpha. This may result in bandwidth accounting errors
10056 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10057 downgrade to 0.1.1.x or earlier.
10058 - New convenience code to locate a file within the DataDirectory.
10059 - Move non-authority functionality out of dirvote.c.
10060 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10061 so that they all take the same named flags.
10064 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10065 Unix users an easy way to script their Tor process (e.g. by
10066 adjusting bandwidth based on the time of the day).
10069 Changes in version 0.2.0.8-alpha - 2007-10-12
10070 This eighth development snapshot fixes a crash bug that's been bothering
10071 us since February 2007, lets bridge authorities store a list of bridge
10072 descriptors they've seen, gets v3 directory voting closer to working,
10073 starts caching v3 directory consensus documents on directory mirrors,
10074 and fixes a variety of smaller issues including some minor memory leaks.
10076 o Major features (router descriptor cache):
10077 - Store routers in a file called cached-descriptors instead of in
10078 cached-routers. Initialize cached-descriptors from cached-routers
10079 if the old format is around. The new format allows us to store
10080 annotations along with descriptors.
10081 - Use annotations to record the time we received each descriptor, its
10082 source, and its purpose.
10083 - Disable the SETROUTERPURPOSE controller command: it is now
10085 - Controllers should now specify cache=no or cache=yes when using
10086 the +POSTDESCRIPTOR command.
10087 - Bridge authorities now write bridge descriptors to disk, meaning
10088 we can export them to other programs and begin distributing them
10091 o Major features (directory authorities):
10092 - When a v3 authority is missing votes or signatures, it now tries
10094 - Directory authorities track weighted fractional uptime as well as
10095 weighted mean-time-between failures. WFU is suitable for deciding
10096 whether a node is "usually up", while MTBF is suitable for deciding
10097 whether a node is "likely to stay up." We need both, because
10098 "usually up" is a good requirement for guards, while "likely to
10099 stay up" is a good requirement for long-lived connections.
10101 o Major features (v3 directory system):
10102 - Caches now download v3 network status documents as needed,
10103 and download the descriptors listed in them.
10104 - All hosts now attempt to download and keep fresh v3 authority
10105 certificates, and re-attempt after failures.
10106 - More internal-consistency checks for vote parsing.
10108 o Major bugfixes (crashes):
10109 - If a connection is shut down abruptly because of something that
10110 happened inside connection_flushed_some(), do not call
10111 connection_finished_flushing(). Should fix bug 451. Bugfix on
10114 o Major bugfixes (performance):
10115 - Fix really bad O(n^2) performance when parsing a long list of
10116 routers: Instead of searching the entire list for an "extra-info "
10117 string which usually wasn't there, once for every routerinfo
10118 we read, just scan lines forward until we find one we like.
10120 - When we add data to a write buffer in response to the data on that
10121 write buffer getting low because of a flush, do not consider the
10122 newly added data as a candidate for immediate flushing, but rather
10123 make it wait until the next round of writing. Otherwise, we flush
10124 and refill recursively, and a single greedy TLS connection can
10125 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10127 o Minor features (v3 authority system):
10128 - Add more ways for tools to download the votes that lead to the
10130 - Send a 503 when low on bandwidth and a vote, consensus, or
10131 certificate is requested.
10132 - If-modified-since is now implemented properly for all kinds of
10133 certificate requests.
10135 o Minor bugfixes (network statuses):
10136 - Tweak the implementation of proposal 109 slightly: allow at most
10137 two Tor servers on the same IP address, except if it's the location
10138 of a directory authority, in which case allow five. Bugfix on
10141 o Minor bugfixes (controller):
10142 - When sending a status event to the controller telling it that an
10143 OR address is reachable, set the port correctly. (Previously we
10144 were reporting the dir port.) Bugfix on 0.1.2.x.
10146 o Minor bugfixes (v3 directory system):
10147 - Fix logic to look up a cert by its signing key digest. Bugfix on
10149 - Only change the reply to a vote to "OK" if it's not already
10150 set. This gets rid of annoying "400 OK" log messages, which may
10151 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10152 - When we get a valid consensus, recompute the voting schedule.
10153 - Base the valid-after time of a vote on the consensus voting
10154 schedule, not on our preferred schedule.
10155 - Make the return values and messages from signature uploads and
10156 downloads more sensible.
10157 - Fix a memory leak when serving votes and consensus documents, and
10158 another when serving certificates.
10160 o Minor bugfixes (performance):
10161 - Use a slightly simpler string hashing algorithm (copying Python's
10162 instead of Java's) and optimize our digest hashing algorithm to take
10163 advantage of 64-bit platforms and to remove some possibly-costly
10165 - Fix a minor memory leak whenever we parse guards from our state
10166 file. Bugfix on 0.2.0.7-alpha.
10167 - Fix a minor memory leak whenever we write out a file. Bugfix on
10169 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10170 command. Bugfix on 0.2.0.5-alpha.
10172 o Minor bugfixes (portability):
10173 - On some platforms, accept() can return a broken address. Detect
10174 this more quietly, and deal accordingly. Fixes bug 483.
10175 - Stop calling tor_strlower() on uninitialized memory in some cases.
10176 Bugfix in 0.2.0.7-alpha.
10178 o Minor bugfixes (usability):
10179 - Treat some 403 responses from directory servers as INFO rather than
10180 WARN-severity events.
10181 - It's not actually an error to find a non-pending entry in the DNS
10182 cache when canceling a pending resolve. Don't log unless stuff is
10183 fishy. Resolves bug 463.
10185 o Minor bugfixes (anonymity):
10186 - Never report that we've used more bandwidth than we're willing to
10187 relay: it leaks how much non-relay traffic we're using. Resolves
10189 - When looking for a circuit to cannibalize, consider family as well
10190 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10191 circuit cannibalization).
10193 o Code simplifications and refactoring:
10194 - Make a bunch of functions static. Remove some dead code.
10195 - Pull out about a third of the really big routerlist.c; put it in a
10196 new module, networkstatus.c.
10197 - Merge the extra fields in local_routerstatus_t back into
10198 routerstatus_t: we used to need one routerstatus_t for each
10199 authority's opinion, plus a local_routerstatus_t for the locally
10200 computed consensus opinion. To save space, we put the locally
10201 modified fields into local_routerstatus_t, and only the common
10202 stuff into routerstatus_t. But once v3 directories are in use,
10203 clients and caches will no longer need to hold authority opinions;
10204 thus, the rationale for keeping the types separate is now gone.
10205 - Make the code used to reschedule and reattempt downloads more
10207 - Turn all 'Are we a directory server/mirror?' logic into a call to
10209 - Remove the code to generate the oldest (v1) directory format.
10210 The code has been disabled since 0.2.0.5-alpha.
10213 Changes in version 0.2.0.7-alpha - 2007-09-21
10214 This seventh development snapshot makes bridges work again, makes bridge
10215 authorities work for the first time, fixes two huge performance flaws
10216 in hidden services, and fixes a variety of minor issues.
10218 o New directory authorities:
10219 - Set up moria1 and tor26 as the first v3 directory authorities. See
10220 doc/spec/dir-spec.txt for details on the new directory design.
10222 o Major bugfixes (crashes):
10223 - Fix possible segfaults in functions called from
10224 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10226 o Major bugfixes (bridges):
10227 - Fix a bug that made servers send a "404 Not found" in response to
10228 attempts to fetch their server descriptor. This caused Tor servers
10229 to take many minutes to establish reachability for their DirPort,
10230 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10231 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10232 users configure that and specify a bridge with an identity
10233 fingerprint, now they will lookup the bridge descriptor at the
10234 default bridge authority via a one-hop tunnel, but once circuits
10235 are established they will switch to a three-hop tunnel for later
10236 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10238 o Major bugfixes (hidden services):
10239 - Hidden services were choosing introduction points uniquely by
10240 hexdigest, but when constructing the hidden service descriptor
10241 they merely wrote the (potentially ambiguous) nickname.
10242 - Clients now use the v2 intro format for hidden service
10243 connections: they specify their chosen rendezvous point by identity
10244 digest rather than by (potentially ambiguous) nickname. Both
10245 are bugfixes on 0.1.2.x, and they could speed up hidden service
10246 connections dramatically. Thanks to Karsten Loesing.
10248 o Minor features (security):
10249 - As a client, do not believe any server that tells us that an
10250 address maps to an internal address space.
10251 - Make it possible to enable HashedControlPassword and
10252 CookieAuthentication at the same time.
10254 o Minor features (guard nodes):
10255 - Tag every guard node in our state file with the version that
10256 we believe added it, or with our own version if we add it. This way,
10257 if a user temporarily runs an old version of Tor and then switches
10258 back to a new one, she doesn't automatically lose her guards.
10260 o Minor features (speed):
10261 - When implementing AES counter mode, update only the portions of the
10262 counter buffer that need to change, and don't keep separate
10263 network-order and host-order counters when they are the same (i.e.,
10264 on big-endian hosts.)
10266 o Minor features (controller):
10267 - Accept LF instead of CRLF on controller, since some software has a
10268 hard time generating real Internet newlines.
10269 - Add GETINFO values for the server status events
10270 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10273 o Removed features:
10274 - Routers no longer include bandwidth-history lines in their
10275 descriptors; this information is already available in extra-info
10276 documents, and including it in router descriptors took up 60%
10277 (!) of compressed router descriptor downloads. Completes
10278 implementation of proposal 104.
10279 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10280 and TorControl.py, as they use the old v0 controller protocol,
10281 and are obsoleted by TorFlow anyway.
10282 - Drop support for v1 rendezvous descriptors, since we never used
10283 them anyway, and the code has probably rotted by now. Based on
10284 patch from Karsten Loesing.
10285 - On OSX, stop warning the user that kqueue support in libevent is
10286 "experimental", since it seems to have worked fine for ages.
10289 - When generating information telling us how to extend to a given
10290 router, do not try to include the nickname if it is absent. Fixes
10291 bug 467. Bugfix on 0.2.0.3-alpha.
10292 - Fix a user-triggerable (but not remotely-triggerable) segfault
10293 in expand_filename(). Bugfix on 0.1.2.x.
10294 - Fix a memory leak when freeing incomplete requests from DNSPort.
10295 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10296 - Don't try to access (or alter) the state file when running
10297 --list-fingerprint or --verify-config or --hash-password. (Resolves
10298 bug 499.) Bugfix on 0.1.2.x.
10299 - Servers used to decline to publish their DirPort if their
10300 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10301 were below a threshold. Now they only look at BandwidthRate and
10302 RelayBandwidthRate. Bugfix on 0.1.2.x.
10303 - Remove an optimization in the AES counter-mode code that assumed
10304 that the counter never exceeded 2^68. When the counter can be set
10305 arbitrarily as an IV (as it is by Karsten's new hidden services
10306 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10307 - Resume listing "AUTHORITY" flag for authorities in network status.
10308 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10310 o Code simplifications and refactoring:
10311 - Revamp file-writing logic so we don't need to have the entire
10312 contents of a file in memory at once before we write to disk. Tor,
10314 - Turn "descriptor store" into a full-fledged type.
10315 - Move all NT services code into a separate source file.
10316 - Unify all code that computes medians, percentile elements, etc.
10317 - Get rid of a needless malloc when parsing address policies.
10320 Changes in version 0.1.2.17 - 2007-08-30
10321 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10322 X bundles. Vidalia 0.0.14 makes authentication required for the
10323 ControlPort in the default configuration, which addresses important
10324 security risks. Everybody who uses Vidalia (or another controller)
10327 In addition, this Tor update fixes major load balancing problems with
10328 path selection, which should speed things up a lot once many people
10331 o Major bugfixes (security):
10332 - We removed support for the old (v0) control protocol. It has been
10333 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10334 become more of a headache than it's worth.
10336 o Major bugfixes (load balancing):
10337 - When choosing nodes for non-guard positions, weight guards
10338 proportionally less, since they already have enough load. Patch
10340 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10341 will allow fast Tor servers to get more attention.
10342 - When we're upgrading from an old Tor version, forget our current
10343 guards and pick new ones according to the new weightings. These
10344 three load balancing patches could raise effective network capacity
10345 by a factor of four. Thanks to Mike Perry for measurements.
10347 o Major bugfixes (stream expiration):
10348 - Expire not-yet-successful application streams in all cases if
10349 they've been around longer than SocksTimeout. Right now there are
10350 some cases where the stream will live forever, demanding a new
10351 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10353 o Minor features (controller):
10354 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10355 is valid before any authentication has been received. It tells
10356 a controller what kind of authentication is expected, and what
10357 protocol is spoken. Implements proposal 119.
10359 o Minor bugfixes (performance):
10360 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10361 greatly speeding up loading cached-routers from disk on startup.
10362 - Disable sentinel-based debugging for buffer code: we squashed all
10363 the bugs that this was supposed to detect a long time ago, and now
10364 its only effect is to change our buffer sizes from nice powers of
10365 two (which platform mallocs tend to like) to values slightly over
10366 powers of two (which make some platform mallocs sad).
10368 o Minor bugfixes (misc):
10369 - If exit bandwidth ever exceeds one third of total bandwidth, then
10370 use the correct formula to weight exit nodes when choosing paths.
10371 Based on patch from Mike Perry.
10372 - Choose perfectly fairly among routers when choosing by bandwidth and
10373 weighting by fraction of bandwidth provided by exits. Previously, we
10374 would choose with only approximate fairness, and correct ourselves
10375 if we ran off the end of the list.
10376 - If we require CookieAuthentication but we fail to write the
10377 cookie file, we would warn but not exit, and end up in a state
10378 where no controller could authenticate. Now we exit.
10379 - If we require CookieAuthentication, stop generating a new cookie
10380 every time we change any piece of our config.
10381 - Refuse to start with certain directory authority keys, and
10382 encourage people using them to stop.
10383 - Terminate multi-line control events properly. Original patch
10385 - Fix a minor memory leak when we fail to find enough suitable
10386 servers to choose a circuit.
10387 - Stop leaking part of the descriptor when we run into a particularly
10388 unparseable piece of it.
10391 Changes in version 0.2.0.6-alpha - 2007-08-26
10392 This sixth development snapshot features a new Vidalia version in the
10393 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10394 the ControlPort in the default configuration, which addresses important
10397 In addition, this snapshot fixes major load balancing problems
10398 with path selection, which should speed things up a lot once many
10399 people have upgraded. The directory authorities also use a new
10400 mean-time-between-failure approach to tracking which servers are stable,
10401 rather than just looking at the most recent uptime.
10403 o New directory authorities:
10404 - Set up Tonga as the default bridge directory authority.
10407 - Directory authorities now track servers by weighted
10408 mean-times-between-failures. When we have 4 or more days of data,
10409 use measured MTBF rather than declared uptime to decide whether
10410 to call a router Stable. Implements proposal 108.
10412 o Major bugfixes (load balancing):
10413 - When choosing nodes for non-guard positions, weight guards
10414 proportionally less, since they already have enough load. Patch
10416 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10417 will allow fast Tor servers to get more attention.
10418 - When we're upgrading from an old Tor version, forget our current
10419 guards and pick new ones according to the new weightings. These
10420 three load balancing patches could raise effective network capacity
10421 by a factor of four. Thanks to Mike Perry for measurements.
10423 o Major bugfixes (descriptor parsing):
10424 - Handle unexpected whitespace better in malformed descriptors. Bug
10425 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10428 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10429 GETINFO for Torstat to use until it can switch to using extrainfos.
10430 - Optionally (if built with -DEXPORTMALLINFO) export the output
10431 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10435 - Do not intermix bridge routers with controller-added
10436 routers. (Bugfix on 0.2.0.x)
10437 - Do not fail with an assert when accept() returns an unexpected
10438 address family. Addresses but does not wholly fix bug 483. (Bugfix
10440 - Let directory authorities startup even when they can't generate
10441 a descriptor immediately, e.g. because they don't know their
10443 - Stop putting the authentication cookie in a file called "0"
10444 in your working directory if you don't specify anything for the
10445 new CookieAuthFile option. Reported by Matt Edman.
10446 - Make it possible to read the PROTOCOLINFO response in a way that
10447 conforms to our control-spec. Reported by Matt Edman.
10448 - Fix a minor memory leak when we fail to find enough suitable
10449 servers to choose a circuit. Bugfix on 0.1.2.x.
10450 - Stop leaking part of the descriptor when we run into a particularly
10451 unparseable piece of it. Bugfix on 0.1.2.x.
10452 - Unmap the extrainfo cache file on exit.
10455 Changes in version 0.2.0.5-alpha - 2007-08-19
10456 This fifth development snapshot fixes compilation on Windows again;
10457 fixes an obnoxious client-side bug that slowed things down and put
10458 extra load on the network; gets us closer to using the v3 directory
10459 voting scheme; makes it easier for Tor controllers to use cookie-based
10460 authentication; and fixes a variety of other bugs.
10462 o Removed features:
10463 - Version 1 directories are no longer generated in full. Instead,
10464 authorities generate and serve "stub" v1 directories that list
10465 no servers. This will stop Tor versions 0.1.0.x and earlier from
10466 working, but (for security reasons) nobody should be running those
10469 o Major bugfixes (compilation, 0.2.0.x):
10470 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10471 - Try to fix MSVC compilation: build correctly on platforms that do
10472 not define s6_addr16 or s6_addr32.
10473 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10476 o Major bugfixes (stream expiration):
10477 - Expire not-yet-successful application streams in all cases if
10478 they've been around longer than SocksTimeout. Right now there are
10479 some cases where the stream will live forever, demanding a new
10480 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10481 reported by lodger.
10483 o Minor features (directory servers):
10484 - When somebody requests a list of statuses or servers, and we have
10485 none of those, return a 404 rather than an empty 200.
10487 o Minor features (directory voting):
10488 - Store v3 consensus status consensuses on disk, and reload them
10491 o Minor features (security):
10492 - Warn about unsafe ControlPort configurations.
10493 - Refuse to start with certain directory authority keys, and
10494 encourage people using them to stop.
10496 o Minor features (controller):
10497 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10498 is valid before any authentication has been received. It tells
10499 a controller what kind of authentication is expected, and what
10500 protocol is spoken. Implements proposal 119.
10501 - New config option CookieAuthFile to choose a new location for the
10502 cookie authentication file, and config option
10503 CookieAuthFileGroupReadable to make it group-readable.
10505 o Minor features (unit testing):
10506 - Add command-line arguments to unit-test executable so that we can
10507 invoke any chosen test from the command line rather than having
10508 to run the whole test suite at once; and so that we can turn on
10509 logging for the unit tests.
10511 o Minor bugfixes (on 0.1.2.x):
10512 - If we require CookieAuthentication but we fail to write the
10513 cookie file, we would warn but not exit, and end up in a state
10514 where no controller could authenticate. Now we exit.
10515 - If we require CookieAuthentication, stop generating a new cookie
10516 every time we change any piece of our config.
10517 - When loading bandwidth history, do not believe any information in
10518 the future. Fixes bug 434.
10519 - When loading entry guard information, do not believe any information
10521 - When we have our clock set far in the future and generate an
10522 onion key, then re-set our clock to be correct, we should not stop
10523 the onion key from getting rotated.
10524 - Clean up torrc sample config file.
10525 - Do not automatically run configure from autogen.sh. This
10526 non-standard behavior tended to annoy people who have built other
10529 o Minor bugfixes (on 0.2.0.x):
10530 - Fix a bug with AutomapHostsOnResolve that would always cause
10531 the second request to fail. Bug reported by Kate. Bugfix on
10533 - Fix a bug in ADDRMAP controller replies that would sometimes
10534 try to print a NULL. Patch from tup.
10535 - Read v3 directory authority keys from the right location.
10536 - Numerous bugfixes to directory voting code.
10539 Changes in version 0.1.2.16 - 2007-08-01
10540 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10541 remote attacker in certain situations to rewrite the user's torrc
10542 configuration file. This can completely compromise anonymity of users
10543 in most configurations, including those running the Vidalia bundles,
10544 TorK, etc. Or worse.
10546 o Major security fixes:
10547 - Close immediately after missing authentication on control port;
10548 do not allow multiple authentication attempts.
10551 Changes in version 0.2.0.4-alpha - 2007-08-01
10552 This fourth development snapshot fixes a critical security vulnerability
10553 for most users, specifically those running Vidalia, TorK, etc. Everybody
10554 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10556 o Major security fixes:
10557 - Close immediately after missing authentication on control port;
10558 do not allow multiple authentication attempts.
10560 o Major bugfixes (compilation):
10561 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10564 o Minor features (performance):
10565 - Be even more aggressive about releasing RAM from small
10566 empty buffers. Thanks to our free-list code, this shouldn't be too
10567 performance-intensive.
10568 - Disable sentinel-based debugging for buffer code: we squashed all
10569 the bugs that this was supposed to detect a long time ago, and
10570 now its only effect is to change our buffer sizes from nice
10571 powers of two (which platform mallocs tend to like) to values
10572 slightly over powers of two (which make some platform mallocs sad).
10573 - Log malloc statistics from mallinfo() on platforms where it
10577 Changes in version 0.2.0.3-alpha - 2007-07-29
10578 This third development snapshot introduces new experimental
10579 blocking-resistance features and a preliminary version of the v3
10580 directory voting design, and includes many other smaller features
10584 - The first pieces of our "bridge" design for blocking-resistance
10585 are implemented. People can run bridge directory authorities;
10586 people can run bridges; and people can configure their Tor clients
10587 with a set of bridges to use as the first hop into the Tor network.
10588 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10590 - Create listener connections before we setuid to the configured
10591 User and Group. Now non-Windows users can choose port values
10592 under 1024, start Tor as root, and have Tor bind those ports
10593 before it changes to another UID. (Windows users could already
10595 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10596 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10597 on "vserver" accounts. (Patch from coderman.)
10598 - Be even more aggressive about separating local traffic from relayed
10599 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10601 o Major features (experimental):
10602 - First cut of code for "v3 dir voting": directory authorities will
10603 vote on a common network status document rather than each publishing
10604 their own opinion. This code needs more testing and more corner-case
10605 handling before it's ready for use.
10608 - Directory authorities now call routers Fast if their bandwidth is
10609 at least 100KB/s, and consider their bandwidth adequate to be a
10610 Guard if it is at least 250KB/s, no matter the medians. This fix
10611 complements proposal 107. [Bugfix on 0.1.2.x]
10612 - Directory authorities now never mark more than 3 servers per IP as
10613 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10615 - Minor change to organizationName and commonName generation
10616 procedures in TLS certificates during Tor handshakes, to invalidate
10617 some earlier censorware approaches. This is not a long-term
10618 solution, but applying it will give us a bit of time to look into
10619 the epidemiology of countermeasures as they spread.
10621 o Major bugfixes (directory):
10622 - Rewrite directory tokenization code to never run off the end of
10623 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10625 o Minor features (controller):
10626 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10627 match requests to applications. (Patch from Robert Hogan.)
10628 - Report address and port correctly on connections to DNSPort. (Patch
10629 from Robert Hogan.)
10630 - Add a RESOLVE command to launch hostname lookups. (Original patch
10631 from Robert Hogan.)
10632 - Add GETINFO status/enough-dir-info to let controllers tell whether
10633 Tor has downloaded sufficient directory information. (Patch
10635 - You can now use the ControlSocket option to tell Tor to listen for
10636 controller connections on Unix domain sockets on systems that
10637 support them. (Patch from Peter Palfrader.)
10638 - STREAM NEW events are generated for DNSPort requests and for
10639 tunneled directory connections. (Patch from Robert Hogan.)
10640 - New "GETINFO address-mappings/*" command to get address mappings
10641 with expiry information. "addr-mappings/*" is now deprecated.
10644 o Minor features (misc):
10645 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10647 - The tor-gencert tool for v3 directory authorities now creates all
10648 files as readable to the file creator only, and write-protects
10649 the authority identity key.
10650 - When dumping memory usage, list bytes used in buffer memory
10652 - When running with dmalloc, dump more stats on hup and on exit.
10653 - Directory authorities now fail quickly and (relatively) harmlessly
10654 if they generate a network status document that is somehow
10657 o Traffic load balancing improvements:
10658 - If exit bandwidth ever exceeds one third of total bandwidth, then
10659 use the correct formula to weight exit nodes when choosing paths.
10660 (Based on patch from Mike Perry.)
10661 - Choose perfectly fairly among routers when choosing by bandwidth and
10662 weighting by fraction of bandwidth provided by exits. Previously, we
10663 would choose with only approximate fairness, and correct ourselves
10664 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10666 o Performance improvements:
10667 - Be more aggressive with freeing buffer RAM or putting it on the
10669 - Use Critical Sections rather than Mutexes for synchronizing threads
10670 on win32; Mutexes are heavier-weight, and designed for synchronizing
10673 o Deprecated and removed features:
10674 - RedirectExits is now deprecated.
10675 - Stop allowing address masks that do not correspond to bit prefixes.
10676 We have warned about these for a really long time; now it's time
10677 to reject them. (Patch from croup.)
10679 o Minor bugfixes (directory):
10680 - Fix another crash bug related to extra-info caching. (Bug found by
10681 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
10682 - Directories no longer return a "304 not modified" when they don't
10683 have the networkstatus the client asked for. Also fix a memory
10684 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
10685 - We had accidentally labelled 0.1.2.x directory servers as not
10686 suitable for begin_dir requests, and had labelled no directory
10687 servers as suitable for uploading extra-info documents. [Bugfix
10690 o Minor bugfixes (dns):
10691 - Fix a crash when DNSPort is set more than once. (Patch from Robert
10692 Hogan.) [Bugfix on 0.2.0.2-alpha]
10693 - Add DNSPort connections to the global connection list, so that we
10694 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
10696 - Fix a dangling reference that could lead to a crash when DNSPort is
10697 changed or closed (Patch from Robert Hogan.) [Bugfix on
10700 o Minor bugfixes (controller):
10701 - Provide DNS expiry times in GMT, not in local time. For backward
10702 compatibility, ADDRMAP events only provide GMT expiry in an extended
10703 field. "GETINFO address-mappings" always does the right thing.
10704 - Use CRLF line endings properly in NS events.
10705 - Terminate multi-line control events properly. (Original patch
10706 from tup.) [Bugfix on 0.1.2.x-alpha]
10707 - Do not include spaces in SOURCE_ADDR fields in STREAM
10708 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
10711 Changes in version 0.1.2.15 - 2007-07-17
10712 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
10713 problems, fixes compilation on BSD, and fixes a variety of other
10714 bugs. Everybody should upgrade.
10716 o Major bugfixes (compilation):
10717 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
10719 o Major bugfixes (crashes):
10720 - Try even harder not to dereference the first character after
10721 an mmap(). Reported by lodger.
10722 - Fix a crash bug in directory authorities when we re-number the
10723 routerlist while inserting a new router.
10724 - When the cached-routers file is an even multiple of the page size,
10725 don't run off the end and crash. (Fixes bug 455; based on idea
10727 - Fix eventdns.c behavior on Solaris: It is critical to include
10728 orconfig.h _before_ sys/types.h, so that we can get the expected
10729 definition of _FILE_OFFSET_BITS.
10731 o Major bugfixes (security):
10732 - Fix a possible buffer overrun when using BSD natd support. Bug
10734 - When sending destroy cells from a circuit's origin, don't include
10735 the reason for tearing down the circuit. The spec says we didn't,
10736 and now we actually don't. Reported by lodger.
10737 - Keep streamids from different exits on a circuit separate. This
10738 bug may have allowed other routers on a given circuit to inject
10739 cells into streams. Reported by lodger; fixes bug 446.
10740 - If there's a never-before-connected-to guard node in our list,
10741 never choose any guards past it. This way we don't expand our
10742 guard list unless we need to.
10744 o Minor bugfixes (guard nodes):
10745 - Weight guard selection by bandwidth, so that low-bandwidth nodes
10746 don't get overused as guards.
10748 o Minor bugfixes (directory):
10749 - Correctly count the number of authorities that recommend each
10750 version. Previously, we were under-counting by 1.
10751 - Fix a potential crash bug when we load many server descriptors at
10752 once and some of them make others of them obsolete. Fixes bug 458.
10754 o Minor bugfixes (hidden services):
10755 - Stop tearing down the whole circuit when the user asks for a
10756 connection to a port that the hidden service didn't configure.
10759 o Minor bugfixes (misc):
10760 - On Windows, we were preventing other processes from reading
10761 cached-routers while Tor was running. Reported by janbar.
10762 - Fix a possible (but very unlikely) bug in picking routers by
10763 bandwidth. Add a log message to confirm that it is in fact
10764 unlikely. Patch from lodger.
10765 - Backport a couple of memory leak fixes.
10766 - Backport miscellaneous cosmetic bugfixes.
10769 Changes in version 0.2.0.2-alpha - 2007-06-02
10770 o Major bugfixes on 0.2.0.1-alpha:
10771 - Fix an assertion failure related to servers without extra-info digests.
10772 Resolves bugs 441 and 442.
10774 o Minor features (directory):
10775 - Support "If-Modified-Since" when answering HTTP requests for
10776 directories, running-routers documents, and network-status documents.
10777 (There's no need to support it for router descriptors, since those
10778 are downloaded by descriptor digest.)
10780 o Minor build issues:
10781 - Clear up some MIPSPro compiler warnings.
10782 - When building from a tarball on a machine that happens to have SVK
10783 installed, report the micro-revision as whatever version existed
10784 in the tarball, not as "x".
10787 Changes in version 0.2.0.1-alpha - 2007-06-01
10788 This early development snapshot provides new features for people running
10789 Tor as both a client and a server (check out the new RelayBandwidth
10790 config options); lets Tor run as a DNS proxy; and generally moves us
10791 forward on a lot of fronts.
10793 o Major features, server usability:
10794 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10795 a separate set of token buckets for relayed traffic. Right now
10796 relayed traffic is defined as answers to directory requests, and
10797 OR connections that don't have any local circuits on them.
10799 o Major features, client usability:
10800 - A client-side DNS proxy feature to replace the need for
10801 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10802 for DNS requests on port 9999, use the Tor network to resolve them
10803 anonymously, and send the reply back like a regular DNS server.
10804 The code still only implements a subset of DNS.
10805 - Make PreferTunneledDirConns and TunnelDirConns work even when
10806 we have no cached directory info. This means Tor clients can now
10807 do all of their connections protected by TLS.
10809 o Major features, performance and efficiency:
10810 - Directory authorities accept and serve "extra info" documents for
10811 routers. These documents contain fields from router descriptors
10812 that aren't usually needed, and that use a lot of excess
10813 bandwidth. Once these fields are removed from router descriptors,
10814 the bandwidth savings should be about 60%. [Partially implements
10816 - Servers upload extra-info documents to any authority that accepts
10817 them. Authorities (and caches that have been configured to download
10818 extra-info documents) download them as needed. [Partially implements
10820 - Change the way that Tor buffers data that it is waiting to write.
10821 Instead of queueing data cells in an enormous ring buffer for each
10822 client->OR or OR->OR connection, we now queue cells on a separate
10823 queue for each circuit. This lets us use less slack memory, and
10824 will eventually let us be smarter about prioritizing different kinds
10826 - Use memory pools to allocate cells with better speed and memory
10827 efficiency, especially on platforms where malloc() is inefficient.
10828 - Stop reading on edge connections when their corresponding circuit
10829 buffers are full; start again as the circuits empty out.
10831 o Major features, other:
10832 - Add an HSAuthorityRecordStats option that hidden service authorities
10833 can use to track statistics of overall hidden service usage without
10834 logging information that would be very useful to an attacker.
10835 - Start work implementing multi-level keys for directory authorities:
10836 Add a standalone tool to generate key certificates. (Proposal 103.)
10839 - Directory authorities now call routers Stable if they have an
10840 uptime of at least 30 days, even if that's not the median uptime
10841 in the network. Implements proposal 107, suggested by Kevin Bauer
10844 o Minor fixes (resource management):
10845 - Count the number of open sockets separately from the number
10846 of active connection_t objects. This will let us avoid underusing
10847 our allocated connection limit.
10848 - We no longer use socket pairs to link an edge connection to an
10849 anonymous directory connection or a DirPort test connection.
10850 Instead, we track the link internally and transfer the data
10851 in-process. This saves two sockets per "linked" connection (at the
10852 client and at the server), and avoids the nasty Windows socketpair()
10854 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10855 for every single inactive connection_t. Free items from the
10856 4k/16k-buffer free lists when they haven't been used for a while.
10858 o Minor features (build):
10859 - Make autoconf search for libevent, openssl, and zlib consistently.
10860 - Update deprecated macros in configure.in.
10861 - When warning about missing headers, tell the user to let us
10862 know if the compile succeeds anyway, so we can downgrade the
10864 - Include the current subversion revision as part of the version
10865 string: either fetch it directly if we're in an SVN checkout, do
10866 some magic to guess it if we're in an SVK checkout, or use
10867 the last-detected version if we're building from a .tar.gz.
10868 Use this version consistently in log messages.
10870 o Minor features (logging):
10871 - Always prepend "Bug: " to any log message about a bug.
10872 - Put a platform string (e.g. "Linux i686") in the startup log
10873 message, so when people paste just their logs, we know if it's
10874 OpenBSD or Windows or what.
10875 - When logging memory usage, break down memory used in buffers by
10878 o Minor features (directory system):
10879 - New config option V2AuthoritativeDirectory that all directory
10880 authorities should set. This will let future authorities choose
10881 not to serve V2 directory information.
10882 - Directory authorities allow multiple router descriptors and/or extra
10883 info documents to be uploaded in a single go. This will make
10884 implementing proposal 104 simpler.
10886 o Minor features (controller):
10887 - Add a new config option __DisablePredictedCircuits designed for
10888 use by the controller, when we don't want Tor to build any circuits
10890 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
10891 so we can exit from the middle of the circuit.
10892 - Implement "getinfo status/circuit-established".
10893 - Implement "getinfo status/version/..." so a controller can tell
10894 whether the current version is recommended, and whether any versions
10895 are good, and how many authorities agree. (Patch from shibz.)
10897 o Minor features (hidden services):
10898 - Allow multiple HiddenServicePort directives with the same virtual
10899 port; when they occur, the user is sent round-robin to one
10900 of the target ports chosen at random. Partially fixes bug 393 by
10901 adding limited ad-hoc round-robining.
10903 o Minor features (other):
10905 - Add a new AutomapHostsOnResolve option: when it is enabled, any
10906 resolve request for hosts matching a given pattern causes Tor to
10907 generate an internal virtual address mapping for that host. This
10908 allows DNSPort to work sensibly with hidden service users. By
10909 default, .exit and .onion addresses are remapped; the list of
10910 patterns can be reconfigured with AutomapHostsSuffixes.
10911 - Add an "-F" option to tor-resolve to force a resolve for a .onion
10912 address. Thanks to the AutomapHostsOnResolve option, this is no
10913 longer a completely silly thing to do.
10914 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
10915 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
10916 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
10917 minus 1 byte: the actual maximum declared bandwidth.
10919 o Removed features:
10920 - Removed support for the old binary "version 0" controller protocol.
10921 This has been deprecated since 0.1.1, and warnings have been issued
10922 since 0.1.2. When we encounter a v0 control message, we now send
10923 back an error and close the connection.
10924 - Remove the old "dns worker" server DNS code: it hasn't been default
10925 since 0.1.2.2-alpha, and all the servers seem to be using the new
10928 o Minor bugfixes (portability):
10929 - Even though Windows is equally happy with / and \ as path separators,
10930 try to use \ consistently on Windows and / consistently on Unix: it
10931 makes the log messages nicer.
10932 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
10933 - Read resolv.conf files correctly on platforms where read() returns
10934 partial results on small file reads.
10936 o Minor bugfixes (directory):
10937 - Correctly enforce that elements of directory objects do not appear
10938 more often than they are allowed to appear.
10939 - When we are reporting the DirServer line we just parsed, we were
10940 logging the second stanza of the key fingerprint, not the first.
10942 o Minor bugfixes (logging):
10943 - When we hit an EOF on a log (probably because we're shutting down),
10944 don't try to remove the log from the list: just mark it as
10945 unusable. (Bulletproofs against bug 222.)
10947 o Minor bugfixes (other):
10948 - In the exitlist script, only consider the most recently published
10949 server descriptor for each server. Also, when the user requests
10950 a list of servers that _reject_ connections to a given address,
10951 explicitly exclude the IPs that also have servers that accept
10952 connections to that address. (Resolves bug 405.)
10953 - Stop allowing hibernating servers to be "stable" or "fast".
10954 - On Windows, we were preventing other processes from reading
10955 cached-routers while Tor was running. (Reported by janbar)
10956 - Make the NodeFamilies config option work. (Reported by
10957 lodger -- it has never actually worked, even though we added it
10959 - Check return values from pthread_mutex functions.
10960 - Don't save non-general-purpose router descriptors to the disk cache,
10961 because we have no way of remembering what their purpose was when
10963 - Add even more asserts to hunt down bug 417.
10964 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
10965 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
10966 Add a log message to confirm that it is in fact unlikely.
10968 o Minor bugfixes (controller):
10969 - Make 'getinfo fingerprint' return a 551 error if we're not a
10970 server, so we match what the control spec claims we do. Reported
10972 - Fix a typo in an error message when extendcircuit fails that
10973 caused us to not follow the \r\n-based delimiter protocol. Reported
10976 o Code simplifications and refactoring:
10977 - Stop passing around circuit_t and crypt_path_t pointers that are
10978 implicit in other procedure arguments.
10979 - Drop the old code to choke directory connections when the
10980 corresponding OR connections got full: thanks to the cell queue
10981 feature, OR conns don't get full any more.
10982 - Make dns_resolve() handle attaching connections to circuits
10983 properly, so the caller doesn't have to.
10984 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
10985 - Keep the connection array as a dynamic smartlist_t, rather than as
10986 a fixed-sized array. This is important, as the number of connections
10987 is becoming increasingly decoupled from the number of sockets.
10990 Changes in version 0.1.2.14 - 2007-05-25
10991 Tor 0.1.2.14 changes the addresses of two directory authorities (this
10992 change especially affects those who serve or use hidden services),
10993 and fixes several other crash- and security-related bugs.
10995 o Directory authority changes:
10996 - Two directory authorities (moria1 and moria2) just moved to new
10997 IP addresses. This change will particularly affect those who serve
10998 or use hidden services.
11000 o Major bugfixes (crashes):
11001 - If a directory server runs out of space in the connection table
11002 as it's processing a begin_dir request, it will free the exit stream
11003 but leave it attached to the circuit, leading to unpredictable
11004 behavior. (Reported by seeess, fixes bug 425.)
11005 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11006 to corrupt memory under some really unlikely scenarios.
11007 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11008 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11011 o Major bugfixes (security):
11012 - When choosing an entry guard for a circuit, avoid using guards
11013 that are in the same family as the chosen exit -- not just guards
11014 that are exactly the chosen exit. (Reported by lodger.)
11016 o Major bugfixes (resource management):
11017 - If a directory authority is down, skip it when deciding where to get
11018 networkstatus objects or descriptors. Otherwise we keep asking
11019 every 10 seconds forever. Fixes bug 384.
11020 - Count it as a failure if we fetch a valid network-status but we
11021 don't want to keep it. Otherwise we'll keep fetching it and keep
11022 not wanting to keep it. Fixes part of bug 422.
11023 - If all of our dirservers have given us bad or no networkstatuses
11024 lately, then stop hammering them once per minute even when we
11025 think they're failed. Fixes another part of bug 422.
11028 - Actually set the purpose correctly for descriptors inserted with
11029 purpose=controller.
11030 - When we have k non-v2 authorities in our DirServer config,
11031 we ignored the last k authorities in the list when updating our
11033 - Correctly back-off from requesting router descriptors that we are
11034 having a hard time downloading.
11035 - Read resolv.conf files correctly on platforms where read() returns
11036 partial results on small file reads.
11037 - Don't rebuild the entire router store every time we get 32K of
11038 routers: rebuild it when the journal gets very large, or when
11039 the gaps in the store get very large.
11042 - When routers publish SVN revisions in their router descriptors,
11043 authorities now include those versions correctly in networkstatus
11045 - Warn when using a version of libevent before 1.3b to run a server on
11046 OSX or BSD: these versions interact badly with userspace threads.
11049 Changes in version 0.1.2.13 - 2007-04-24
11050 This release features some major anonymity fixes, such as safer path
11051 selection; better client performance; faster bootstrapping, better
11052 address detection, and better DNS support for servers; write limiting as
11053 well as read limiting to make servers easier to run; and a huge pile of
11054 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11056 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11057 of the Freenode IRC network, remembering his patience and vision for
11058 free speech on the Internet.
11061 - Fix a memory leak when we ask for "all" networkstatuses and we
11062 get one we don't recognize.
11063 - Add more asserts to hunt down bug 417.
11064 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11067 Changes in version 0.1.2.12-rc - 2007-03-16
11069 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11070 directory information requested inside Tor connections (i.e. via
11071 begin_dir cells). It only triggered when the same connection was
11072 serving other data at the same time. Reported by seeess.
11075 - When creating a circuit via the controller, send a 'launched'
11076 event when we're done, so we follow the spec better.
11079 Changes in version 0.1.2.11-rc - 2007-03-15
11080 o Minor bugfixes (controller), reported by daejees:
11081 - Correct the control spec to match how the code actually responds
11082 to 'getinfo addr-mappings/*'.
11083 - The control spec described a GUARDS event, but the code
11084 implemented a GUARD event. Standardize on GUARD, but let people
11085 ask for GUARDS too.
11088 Changes in version 0.1.2.10-rc - 2007-03-07
11089 o Major bugfixes (Windows):
11090 - Do not load the NT services library functions (which may not exist)
11091 just to detect if we're a service trying to shut down. Now we run
11092 on Win98 and friends again.
11094 o Minor bugfixes (other):
11095 - Clarify a couple of log messages.
11096 - Fix a misleading socks5 error number.
11099 Changes in version 0.1.2.9-rc - 2007-03-02
11100 o Major bugfixes (Windows):
11101 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11102 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11103 int configuration values: the high-order 32 bits would get
11104 truncated. In particular, we were being bitten by the default
11105 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11106 and maybe also bug 397.)
11108 o Minor bugfixes (performance):
11109 - Use OpenSSL's AES implementation on platforms where it's faster.
11110 This could save us as much as 10% CPU usage.
11112 o Minor bugfixes (server):
11113 - Do not rotate onion key immediately after setting it for the first
11116 o Minor bugfixes (directory authorities):
11117 - Stop calling servers that have been hibernating for a long time
11118 "stable". Also, stop letting hibernating or obsolete servers affect
11119 uptime and bandwidth cutoffs.
11120 - Stop listing hibernating servers in the v1 directory.
11122 o Minor bugfixes (hidden services):
11123 - Upload hidden service descriptors slightly less often, to reduce
11124 load on authorities.
11126 o Minor bugfixes (other):
11127 - Fix an assert that could trigger if a controller quickly set then
11128 cleared EntryNodes. Bug found by Udo van den Heuvel.
11129 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11131 - Fix a potential race condition in the rpm installer. Found by
11133 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11134 of 2 as indicating that the server is completely bad; it sometimes
11135 means that the server is just bad for the request in question. (may fix
11136 the last of bug 326.)
11137 - Disable encrypted directory connections when we don't have a server
11138 descriptor for the destination. We'll get this working again in
11142 Changes in version 0.1.2.8-beta - 2007-02-26
11143 o Major bugfixes (crashes):
11144 - Stop crashing when the controller asks us to resetconf more than
11145 one config option at once. (Vidalia 0.0.11 does this.)
11146 - Fix a crash that happened on Win98 when we're given command-line
11147 arguments: don't try to load NT service functions from advapi32.dll
11148 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11150 - Fix a longstanding obscure crash bug that could occur when
11151 we run out of DNS worker processes. (Resolves bug 390.)
11153 o Major bugfixes (hidden services):
11154 - Correctly detect whether hidden service descriptor downloads are
11155 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11157 o Major bugfixes (accounting):
11158 - When we start during an accounting interval before it's time to wake
11159 up, remember to wake up at the correct time. (May fix bug 342.)
11161 o Minor bugfixes (controller):
11162 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11163 clear the corresponding on_circuit variable, and remember later
11164 that we don't need to send a redundant CLOSED event. Resolves part
11166 - Report events where a resolve succeeded or where we got a socks
11167 protocol error correctly, rather than calling both of them
11169 - Change reported stream target addresses to IP consistently when
11170 we finally get the IP from an exit node.
11171 - Send log messages to the controller even if they happen to be very
11174 o Minor bugfixes (other):
11175 - Display correct results when reporting which versions are
11176 recommended, and how recommended they are. (Resolves bug 383.)
11177 - Improve our estimates for directory bandwidth to be less random:
11178 guess that an unrecognized directory will have the average bandwidth
11179 from all known directories, not that it will have the average
11180 bandwidth from those directories earlier than it on the list.
11181 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11182 and hup, stop triggering an assert based on an empty onion_key.
11183 - On platforms with no working mmap() equivalent, don't warn the
11184 user when cached-routers doesn't exist.
11185 - Warn the user when mmap() [or its equivalent] fails for some reason
11186 other than file-not-found.
11187 - Don't warn the user when cached-routers.new doesn't exist: that's
11188 perfectly fine when starting up for the first time.
11189 - When EntryNodes are configured, rebuild the guard list to contain,
11190 in order: the EntryNodes that were guards before; the rest of the
11191 EntryNodes; the nodes that were guards before.
11192 - Mask out all signals in sub-threads; only the libevent signal
11193 handler should be processing them. This should prevent some crashes
11194 on some machines using pthreads. (Patch from coderman.)
11195 - Fix switched arguments on memset in the implementation of
11196 tor_munmap() for systems with no mmap() call.
11197 - When Tor receives a router descriptor that it asked for, but
11198 no longer wants (because it has received fresh networkstatuses
11199 in the meantime), do not warn the user. Cache the descriptor if
11200 we're a cache; drop it if we aren't.
11201 - Make earlier entry guards _really_ get retried when the network
11203 - On a malformed DNS reply, always give an error to the corresponding
11205 - Build with recent libevents on platforms that do not define the
11206 nonstandard types "u_int8_t" and friends.
11208 o Minor features (controller):
11209 - Warn the user when an application uses the obsolete binary v0
11210 control protocol. We're planning to remove support for it during
11211 the next development series, so it's good to give people some
11213 - Add STREAM_BW events to report per-entry-stream bandwidth
11214 use. (Patch from Robert Hogan.)
11215 - Rate-limit SIGNEWNYM signals in response to controllers that
11216 impolitely generate them for every single stream. (Patch from
11217 mwenge; closes bug 394.)
11218 - Make REMAP stream events have a SOURCE (cache or exit), and
11219 make them generated in every case where we get a successful
11220 connected or resolved cell.
11222 o Minor bugfixes (performance):
11223 - Call router_have_min_dir_info half as often. (This is showing up in
11224 some profiles, but not others.)
11225 - When using GCC, make log_debug never get called at all, and its
11226 arguments never get evaluated, when no debug logs are configured.
11227 (This is showing up in some profiles, but not others.)
11230 - Remove some never-implemented options. Mark PathlenCoinWeight as
11232 - Implement proposal 106: Stop requiring clients to have well-formed
11233 certificates; stop checking nicknames in certificates. (Clients
11234 have certificates so that they can look like Tor servers, but in
11235 the future we might want to allow them to look like regular TLS
11236 clients instead. Nicknames in certificates serve no purpose other
11237 than making our protocol easier to recognize on the wire.)
11238 - Revise messages on handshake failure again to be even more clear about
11239 which are incoming connections and which are outgoing.
11240 - Discard any v1 directory info that's over 1 month old (for
11241 directories) or over 1 week old (for running-routers lists).
11242 - Do not warn when individual nodes in the configuration's EntryNodes,
11243 ExitNodes, etc are down: warn only when all possible nodes
11244 are down. (Fixes bug 348.)
11245 - Always remove expired routers and networkstatus docs before checking
11246 whether we have enough information to build circuits. (Fixes
11248 - Put a lower-bound on MaxAdvertisedBandwidth.
11251 Changes in version 0.1.2.7-alpha - 2007-02-06
11252 o Major bugfixes (rate limiting):
11253 - Servers decline directory requests much more aggressively when
11254 they're low on bandwidth. Otherwise they end up queueing more and
11255 more directory responses, which can't be good for latency.
11256 - But never refuse directory requests from local addresses.
11257 - Fix a memory leak when sending a 503 response for a networkstatus
11259 - Be willing to read or write on local connections (e.g. controller
11260 connections) even when the global rate limiting buckets are empty.
11261 - If our system clock jumps back in time, don't publish a negative
11262 uptime in the descriptor. Also, don't let the global rate limiting
11263 buckets go absurdly negative.
11264 - Flush local controller connection buffers periodically as we're
11265 writing to them, so we avoid queueing 4+ megabytes of data before
11268 o Major bugfixes (NT services):
11269 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11270 command-line flag so that admins can override the default by saying
11271 "tor --service install --user "SomeUser"". This will not affect
11272 existing installed services. Also, warn the user that the service
11273 will look for its configuration file in the service user's
11274 %appdata% directory. (We can't do the 'hardwire the user's appdata
11275 directory' trick any more, since we may not have read access to that
11278 o Major bugfixes (other):
11279 - Previously, we would cache up to 16 old networkstatus documents
11280 indefinitely, if they came from nontrusted authorities. Now we
11281 discard them if they are more than 10 days old.
11282 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11284 - Detect and reject malformed DNS responses containing circular
11286 - If exits are rare enough that we're not marking exits as guards,
11287 ignore exit bandwidth when we're deciding the required bandwidth
11289 - When we're handling a directory connection tunneled over Tor,
11290 don't fill up internal memory buffers with all the data we want
11291 to tunnel; instead, only add it if the OR connection that will
11292 eventually receive it has some room for it. (This can lead to
11293 slowdowns in tunneled dir connections; a better solution will have
11294 to wait for 0.2.0.)
11296 o Minor bugfixes (dns):
11297 - Add some defensive programming to eventdns.c in an attempt to catch
11298 possible memory-stomping bugs.
11299 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11300 an incorrect number of bytes. (Previously, we would ignore the
11302 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11303 in the correct order, and doesn't crash.
11304 - Free memory held in recently-completed DNS lookup attempts on exit.
11305 This was not a memory leak, but may have been hiding memory leaks.
11306 - Handle TTL values correctly on reverse DNS lookups.
11307 - Treat failure to parse resolv.conf as an error.
11309 o Minor bugfixes (other):
11310 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11311 - When computing clock skew from directory HTTP headers, consider what
11312 time it was when we finished asking for the directory, not what
11314 - Expire socks connections if they spend too long waiting for the
11315 handshake to finish. Previously we would let them sit around for
11316 days, if the connecting application didn't close them either.
11317 - And if the socks handshake hasn't started, don't send a
11318 "DNS resolve socks failed" handshake reply; just close it.
11319 - Stop using C functions that OpenBSD's linker doesn't like.
11320 - Don't launch requests for descriptors unless we have networkstatuses
11321 from at least half of the authorities. This delays the first
11322 download slightly under pathological circumstances, but can prevent
11323 us from downloading a bunch of descriptors we don't need.
11324 - Do not log IPs with TLS failures for incoming TLS
11325 connections. (Fixes bug 382.)
11326 - If the user asks to use invalid exit nodes, be willing to use
11328 - Stop using the reserved ac_cv namespace in our configure script.
11329 - Call stat() slightly less often; use fstat() when possible.
11330 - Refactor the way we handle pending circuits when an OR connection
11331 completes or fails, in an attempt to fix a rare crash bug.
11332 - Only rewrite a conn's address based on X-Forwarded-For: headers
11333 if it's a parseable public IP address; and stop adding extra quotes
11334 to the resulting address.
11337 - Weight directory requests by advertised bandwidth. Now we can
11338 let servers enable write limiting but still allow most clients to
11339 succeed at their directory requests. (We still ignore weights when
11340 choosing a directory authority; I hope this is a feature.)
11343 - Create a new file ReleaseNotes which was the old ChangeLog. The
11344 new ChangeLog file now includes the summaries for all development
11346 - Check for addresses with invalid characters at the exit as well
11347 as at the client, and warn less verbosely when they fail. You can
11348 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11349 - Adapt a patch from goodell to let the contrib/exitlist script
11350 take arguments rather than require direct editing.
11351 - Inform the server operator when we decide not to advertise a
11352 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11353 was confusing Zax, so now we're hopefully more helpful.
11354 - Bring us one step closer to being able to establish an encrypted
11355 directory tunnel without knowing a descriptor first. Still not
11356 ready yet. As part of the change, now assume we can use a
11357 create_fast cell if we don't know anything about a router.
11358 - Allow exit nodes to use nameservers running on ports other than 53.
11359 - Servers now cache reverse DNS replies.
11360 - Add an --ignore-missing-torrc command-line option so that we can
11361 get the "use sensible defaults if the configuration file doesn't
11362 exist" behavior even when specifying a torrc location on the command
11365 o Minor features (controller):
11366 - Track reasons for OR connection failure; make these reasons
11367 available via the controller interface. (Patch from Mike Perry.)
11368 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11369 can learn when clients are sending malformed hostnames to Tor.
11370 - Clean up documentation for controller status events.
11371 - Add a REMAP status to stream events to note that a stream's
11372 address has changed because of a cached address or a MapAddress
11376 Changes in version 0.1.2.6-alpha - 2007-01-09
11378 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11379 connection handles more than 4 gigs in either direction, we crash.
11380 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11381 advertised exit node, somebody might try to exit from us when
11382 we're bootstrapping and before we've built our descriptor yet.
11383 Refuse the connection rather than crashing.
11386 - Warn if we (as a server) find that we've resolved an address that we
11387 weren't planning to resolve.
11388 - Warn that using select() on any libevent version before 1.1 will be
11389 unnecessarily slow (even for select()).
11390 - Flush ERR-level controller status events just like we currently
11391 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11392 the controller from learning about current events.
11394 o Minor features (more controller status events):
11395 - Implement EXTERNAL_ADDRESS server status event so controllers can
11396 learn when our address changes.
11397 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11398 can learn when directories reject our descriptor.
11399 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11400 can learn when a client application is speaking a non-socks protocol
11402 - Implement DANGEROUS_SOCKS client status event so controllers
11403 can learn when a client application is leaking DNS addresses.
11404 - Implement BUG general status event so controllers can learn when
11405 Tor is unhappy about its internal invariants.
11406 - Implement CLOCK_SKEW general status event so controllers can learn
11407 when Tor thinks the system clock is set incorrectly.
11408 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11409 server status events so controllers can learn when their descriptors
11410 are accepted by a directory.
11411 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11412 server status events so controllers can learn about Tor's progress in
11413 deciding whether it's reachable from the outside.
11414 - Implement BAD_LIBEVENT general status event so controllers can learn
11415 when we have a version/method combination in libevent that needs to
11417 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11418 and DNS_USELESS server status events so controllers can learn
11419 about changes to DNS server status.
11421 o Minor features (directory):
11422 - Authorities no longer recommend exits as guards if this would shift
11423 too much load to the exit nodes.
11426 Changes in version 0.1.2.5-alpha - 2007-01-06
11428 - Enable write limiting as well as read limiting. Now we sacrifice
11429 capacity if we're pushing out lots of directory traffic, rather
11430 than overrunning the user's intended bandwidth limits.
11431 - Include TLS overhead when counting bandwidth usage; previously, we
11432 would count only the bytes sent over TLS, but not the bytes used
11434 - Support running the Tor service with a torrc not in the same
11435 directory as tor.exe and default to using the torrc located in
11436 the %appdata%\Tor\ of the user who installed the service. Patch
11438 - Servers now check for the case when common DNS requests are going to
11439 wildcarded addresses (i.e. all getting the same answer), and change
11440 their exit policy to reject *:* if it's happening.
11441 - Implement BEGIN_DIR cells, so we can connect to the directory
11442 server via TLS to do encrypted directory requests rather than
11443 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11444 config options if you like.
11446 o Minor features (config and docs):
11447 - Start using the state file to store bandwidth accounting data:
11448 the bw_accounting file is now obsolete. We'll keep generating it
11449 for a while for people who are still using 0.1.2.4-alpha.
11450 - Try to batch changes to the state file so that we do as few
11451 disk writes as possible while still storing important things in
11453 - The state file and the bw_accounting file get saved less often when
11454 the AvoidDiskWrites config option is set.
11455 - Make PIDFile work on Windows (untested).
11456 - Add internal descriptions for a bunch of configuration options:
11457 accessible via controller interface and in comments in saved
11459 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11460 NNTP by default, so this seems like a sensible addition.
11461 - Clients now reject hostnames with invalid characters. This should
11462 avoid some inadvertent info leaks. Add an option
11463 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11464 is running a private network with hosts called @, !, and #.
11465 - Add a maintainer script to tell us which options are missing
11466 documentation: "make check-docs".
11467 - Add a new address-spec.txt document to describe our special-case
11468 addresses: .exit, .onion, and .noconnnect.
11470 o Minor features (DNS):
11471 - Ongoing work on eventdns infrastructure: now it has dns server
11472 and ipv6 support. One day Tor will make use of it.
11473 - Add client-side caching for reverse DNS lookups.
11474 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11475 - When we change nameservers or IP addresses, reset and re-launch
11476 our tests for DNS hijacking.
11478 o Minor features (directory):
11479 - Authorities now specify server versions in networkstatus. This adds
11480 about 2% to the size of compressed networkstatus docs, and allows
11481 clients to tell which servers support BEGIN_DIR and which don't.
11482 The implementation is forward-compatible with a proposed future
11483 protocol version scheme not tied to Tor versions.
11484 - DirServer configuration lines now have an orport= option so
11485 clients can open encrypted tunnels to the authorities without
11486 having downloaded their descriptors yet. Enabled for moria1,
11487 moria2, tor26, and lefkada now in the default configuration.
11488 - Directory servers are more willing to send a 503 "busy" if they
11489 are near their write limit, especially for v1 directory requests.
11490 Now they can use their limited bandwidth for actual Tor traffic.
11491 - Clients track responses with status 503 from dirservers. After a
11492 dirserver has given us a 503, we try not to use it until an hour has
11493 gone by, or until we have no dirservers that haven't given us a 503.
11494 - When we get a 503 from a directory, and we're not a server, we don't
11495 count the failure against the total number of failures allowed
11496 for the thing we're trying to download.
11497 - Report X-Your-Address-Is correctly from tunneled directory
11498 connections; don't report X-Your-Address-Is when it's an internal
11499 address; and never believe reported remote addresses when they're
11501 - Protect against an unlikely DoS attack on directory servers.
11502 - Add a BadDirectory flag to network status docs so that authorities
11503 can (eventually) tell clients about caches they believe to be
11506 o Minor features (controller):
11507 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11508 - Reimplement GETINFO so that info/names stays in sync with the
11510 - Implement "GETINFO fingerprint".
11511 - Implement "SETEVENTS GUARD" so controllers can get updates on
11512 entry guard status as it changes.
11514 o Minor features (clean up obsolete pieces):
11515 - Remove some options that have been deprecated since at least
11516 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11517 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11518 to set log options.
11519 - We no longer look for identity and onion keys in "identity.key" and
11520 "onion.key" -- these were replaced by secret_id_key and
11521 secret_onion_key in 0.0.8pre1.
11522 - We no longer require unrecognized directory entries to be
11525 o Major bugfixes (security):
11526 - Stop sending the HttpProxyAuthenticator string to directory
11527 servers when directory connections are tunnelled through Tor.
11528 - Clients no longer store bandwidth history in the state file.
11529 - Do not log introduction points for hidden services if SafeLogging
11531 - When generating bandwidth history, round down to the nearest
11532 1k. When storing accounting data, round up to the nearest 1k.
11533 - When we're running as a server, remember when we last rotated onion
11534 keys, so that we will rotate keys once they're a week old even if
11535 we never stay up for a week ourselves.
11537 o Major bugfixes (other):
11538 - Fix a longstanding bug in eventdns that prevented the count of
11539 timed-out resolves from ever being reset. This bug caused us to
11540 give up on a nameserver the third time it timed out, and try it
11541 10 seconds later... and to give up on it every time it timed out
11543 - Take out the '5 second' timeout from the connection retry
11544 schedule. Now the first connect attempt will wait a full 10
11545 seconds before switching to a new circuit. Perhaps this will help
11546 a lot. Based on observations from Mike Perry.
11547 - Fix a bug on the Windows implementation of tor_mmap_file() that
11548 would prevent the cached-routers file from ever loading. Reported
11552 - Fix an assert failure when a directory authority sets
11553 AuthDirRejectUnlisted and then receives a descriptor from an
11554 unlisted router. Reported by seeess.
11555 - Avoid a double-free when parsing malformed DirServer lines.
11556 - Fix a bug when a BSD-style PF socket is first used. Patch from
11558 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11559 to resolve an address at a given exit node even when they ask for
11561 - Servers no longer ever list themselves in their "family" line,
11562 even if configured to do so. This makes it easier to configure
11563 family lists conveniently.
11564 - When running as a server, don't fall back to 127.0.0.1 when no
11565 nameservers are configured in /etc/resolv.conf; instead, make the
11566 user fix resolv.conf or specify nameservers explicitly. (Resolves
11568 - Stop accepting certain malformed ports in configured exit policies.
11569 - Don't re-write the fingerprint file every restart, unless it has
11571 - Stop warning when a single nameserver fails: only warn when _all_ of
11572 our nameservers have failed. Also, when we only have one nameserver,
11573 raise the threshold for deciding that the nameserver is dead.
11574 - Directory authorities now only decide that routers are reachable
11575 if their identity keys are as expected.
11576 - When the user uses bad syntax in the Log config line, stop
11577 suggesting other bad syntax as a replacement.
11578 - Correctly detect ipv6 DNS capability on OpenBSD.
11580 o Minor bugfixes (controller):
11581 - Report the circuit number correctly in STREAM CLOSED events. Bug
11582 reported by Mike Perry.
11583 - Do not report bizarre values for results of accounting GETINFOs
11584 when the last second's write or read exceeds the allotted bandwidth.
11585 - Report "unrecognized key" rather than an empty string when the
11586 controller tries to fetch a networkstatus that doesn't exist.
11589 Changes in version 0.1.1.26 - 2006-12-14
11590 o Security bugfixes:
11591 - Stop sending the HttpProxyAuthenticator string to directory
11592 servers when directory connections are tunnelled through Tor.
11593 - Clients no longer store bandwidth history in the state file.
11594 - Do not log introduction points for hidden services if SafeLogging
11598 - Fix an assert failure when a directory authority sets
11599 AuthDirRejectUnlisted and then receives a descriptor from an
11600 unlisted router (reported by seeess).
11603 Changes in version 0.1.2.4-alpha - 2006-12-03
11605 - Add support for using natd; this allows FreeBSDs earlier than
11606 5.1.2 to have ipfw send connections through Tor without using
11607 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11610 - Make all connections to addresses of the form ".noconnect"
11611 immediately get closed. This lets application/controller combos
11612 successfully test whether they're talking to the same Tor by
11613 watching for STREAM events.
11614 - Make cross.sh cross-compilation script work even when autogen.sh
11615 hasn't been run. (Patch from Michael Mohr.)
11616 - Statistics dumped by -USR2 now include a breakdown of public key
11617 operations, for profiling.
11620 - Fix a major leak when directory authorities parse their
11621 approved-routers list, a minor memory leak when we fail to pick
11622 an exit node, and a few rare leaks on errors.
11623 - Handle TransPort connections even when the server sends data before
11624 the client sends data. Previously, the connection would just hang
11625 until the client sent data. (Patch from tup based on patch from
11627 - Avoid assert failure when our cached-routers file is empty on
11631 - Don't log spurious warnings when we see a circuit close reason we
11632 don't recognize; it's probably just from a newer version of Tor.
11633 - Have directory authorities allow larger amounts of drift in uptime
11634 without replacing the server descriptor: previously, a server that
11635 restarted every 30 minutes could have 48 "interesting" descriptors
11637 - Start linking to the Tor specification and Tor reference manual
11638 correctly in the Windows installer.
11639 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11640 Tor/Privoxy we also uninstall Vidalia.
11641 - Resume building on Irix64, and fix a lot of warnings from its
11642 MIPSpro C compiler.
11643 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11644 when we're running as a client.
11647 Changes in version 0.1.1.25 - 2006-11-04
11649 - When a client asks us to resolve (rather than connect to)
11650 an address, and we have a cached answer, give them the cached
11651 answer. Previously, we would give them no answer at all.
11652 - We were building exactly the wrong circuits when we predict
11653 hidden service requirements, meaning Tor would have to build all
11654 its circuits on demand.
11655 - If none of our live entry guards have a high uptime, but we
11656 require a guard with a high uptime, try adding a new guard before
11657 we give up on the requirement. This patch should make long-lived
11658 connections more stable on average.
11659 - When testing reachability of our DirPort, don't launch new
11660 tests when there's already one in progress -- unreachable
11661 servers were stacking up dozens of testing streams.
11663 o Security bugfixes:
11664 - When the user sends a NEWNYM signal, clear the client-side DNS
11665 cache too. Otherwise we continue to act on previous information.
11668 - Avoid a memory corruption bug when creating a hash table for
11670 - Avoid possibility of controller-triggered crash when misusing
11671 certain commands from a v0 controller on platforms that do not
11672 handle printf("%s",NULL) gracefully.
11673 - Avoid infinite loop on unexpected controller input.
11674 - Don't log spurious warnings when we see a circuit close reason we
11675 don't recognize; it's probably just from a newer version of Tor.
11676 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11677 Tor/Privoxy we also uninstall Vidalia.
11680 Changes in version 0.1.2.3-alpha - 2006-10-29
11682 - Prepare for servers to publish descriptors less often: never
11683 discard a descriptor simply for being too old until either it is
11684 recommended by no authorities, or until we get a better one for
11685 the same router. Make caches consider retaining old recommended
11686 routers for even longer.
11687 - If most authorities set a BadExit flag for a server, clients
11688 don't think of it as a general-purpose exit. Clients only consider
11689 authorities that advertise themselves as listing bad exits.
11690 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11691 headers for content, so that we can work better in the presence of
11692 caching HTTP proxies.
11693 - Allow authorities to list nodes as bad exits by fingerprint or by
11696 o Minor features, controller:
11697 - Add a REASON field to CIRC events; for backward compatibility, this
11698 field is sent only to controllers that have enabled the extended
11699 event format. Also, add additional reason codes to explain why
11700 a given circuit has been destroyed or truncated. (Patches from
11702 - Add a REMOTE_REASON field to extended CIRC events to tell the
11703 controller about why a remote OR told us to close a circuit.
11704 - Stream events also now have REASON and REMOTE_REASON fields,
11705 working much like those for circuit events.
11706 - There's now a GETINFO ns/... field so that controllers can ask Tor
11707 about the current status of a router.
11708 - A new event type "NS" to inform a controller when our opinion of
11709 a router's status has changed.
11710 - Add a GETINFO events/names and GETINFO features/names so controllers
11711 can tell which events and features are supported.
11712 - A new CLEARDNSCACHE signal to allow controllers to clear the
11713 client-side DNS cache without expiring circuits.
11715 o Security bugfixes:
11716 - When the user sends a NEWNYM signal, clear the client-side DNS
11717 cache too. Otherwise we continue to act on previous information.
11720 - Avoid sending junk to controllers or segfaulting when a controller
11721 uses EVENT_NEW_DESC with verbose nicknames.
11722 - Stop triggering asserts if the controller tries to extend hidden
11723 service circuits (reported by mwenge).
11724 - Avoid infinite loop on unexpected controller input.
11725 - When the controller does a "GETINFO network-status", tell it
11726 about even those routers whose descriptors are very old, and use
11727 long nicknames where appropriate.
11728 - Change NT service functions to be loaded on demand. This lets us
11729 build with MinGW without breaking Tor for Windows 98 users.
11730 - Do DirPort reachability tests less often, since a single test
11731 chews through many circuits before giving up.
11732 - In the hidden service example in torrc.sample, stop recommending
11733 esoteric and discouraged hidden service options.
11734 - When stopping an NT service, wait up to 10 sec for it to actually
11735 stop. Patch from Matt Edman; resolves bug 295.
11736 - Fix handling of verbose nicknames with ORCONN controller events:
11737 make them show up exactly when requested, rather than exactly when
11739 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
11740 printing a duplicate "$" in the keys we send (reported by mwenge).
11741 - Correctly set maximum connection limit on Cygwin. (This time
11743 - Try to detect Windows correctly when cross-compiling.
11744 - Detect the size of the routers file correctly even if it is
11745 corrupted (on systems without mmap) or not page-aligned (on systems
11746 with mmap). This bug was harmless.
11747 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11748 to open a stream fails; now we do in more cases. This should
11749 make clients able to find a good exit faster in some cases, since
11750 unhandleable requests will now get an error rather than timing out.
11751 - Resolve two memory leaks when rebuilding the on-disk router cache
11752 (reported by fookoowa).
11753 - Clean up minor code warnings suggested by the MIPSpro C compiler,
11754 and reported by some Centos users.
11755 - Controller signals now work on non-Unix platforms that don't define
11756 SIGUSR1 and SIGUSR2 the way we expect.
11757 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
11758 values before failing, and always enables eventdns.
11759 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
11760 Try to fix this in configure.in by checking for most functions
11761 before we check for libevent.
11764 Changes in version 0.1.2.2-alpha - 2006-10-07
11766 - Make our async eventdns library on-by-default for Tor servers,
11767 and plan to deprecate the separate dnsworker threads.
11768 - Add server-side support for "reverse" DNS lookups (using PTR
11769 records so clients can determine the canonical hostname for a given
11770 IPv4 address). Only supported by servers using eventdns; servers
11771 now announce in their descriptors whether they support eventdns.
11772 - Specify and implement client-side SOCKS5 interface for reverse DNS
11773 lookups (see doc/socks-extensions.txt).
11774 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
11775 connect to directory servers through Tor. Previously, clients needed
11776 to find Tor exits to make private connections to directory servers.
11777 - Avoid choosing Exit nodes for entry or middle hops when the
11778 total bandwidth available from non-Exit nodes is much higher than
11779 the total bandwidth available from Exit nodes.
11780 - Workaround for name servers (like Earthlink's) that hijack failing
11781 DNS requests and replace the no-such-server answer with a "helpful"
11782 redirect to an advertising-driven search portal. Also work around
11783 DNS hijackers who "helpfully" decline to hijack known-invalid
11784 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11785 lets you turn it off.
11786 - Send out a burst of long-range padding cells once we've established
11787 that we're reachable. Spread them over 4 circuits, so hopefully
11788 a few will be fast. This exercises our bandwidth and bootstraps
11789 us into the directory more quickly.
11791 o New/improved config options:
11792 - Add new config option "ResolvConf" to let the server operator
11793 choose an alternate resolve.conf file when using eventdns.
11794 - Add an "EnforceDistinctSubnets" option to control our "exclude
11795 servers on the same /16" behavior. It's still on by default; this
11796 is mostly for people who want to operate private test networks with
11797 all the machines on the same subnet.
11798 - If one of our entry guards is on the ExcludeNodes list, or the
11799 directory authorities don't think it's a good guard, treat it as
11800 if it were unlisted: stop using it as a guard, and throw it off
11801 the guards list if it stays that way for a long time.
11802 - Allow directory authorities to be marked separately as authorities
11803 for the v1 directory protocol, the v2 directory protocol, and
11804 as hidden service directories, to make it easier to retire old
11805 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11806 to continue being hidden service authorities too.
11807 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11809 o Minor features, controller:
11810 - Fix CIRC controller events so that controllers can learn the
11811 identity digests of non-Named servers used in circuit paths.
11812 - Let controllers ask for more useful identifiers for servers. Instead
11813 of learning identity digests for un-Named servers and nicknames
11814 for Named servers, the new identifiers include digest, nickname,
11815 and indication of Named status. Off by default; see control-spec.txt
11816 for more information.
11817 - Add a "getinfo address" controller command so it can display Tor's
11818 best guess to the user.
11819 - New controller event to alert the controller when our server
11820 descriptor has changed.
11821 - Give more meaningful errors on controller authentication failure.
11823 o Minor features, other:
11824 - When asked to resolve a hostname, don't use non-exit servers unless
11825 requested to do so. This allows servers with broken DNS to be
11826 useful to the network.
11827 - Divide eventdns log messages into warn and info messages.
11828 - Reserve the nickname "Unnamed" for routers that can't pick
11829 a hostname: any router can call itself Unnamed; directory
11830 authorities will never allocate Unnamed to any particular router;
11831 clients won't believe that any router is the canonical Unnamed.
11832 - Only include function names in log messages for info/debug messages.
11833 For notice/warn/err, the content of the message should be clear on
11834 its own, and printing the function name only confuses users.
11835 - Avoid some false positives during reachability testing: don't try
11836 to test via a server that's on the same /24 as us.
11837 - If we fail to build a circuit to an intended enclave, and it's
11838 not mandatory that we use that enclave, stop wanting it.
11839 - When eventdns is enabled, allow multithreaded builds on NetBSD and
11840 OpenBSD. (We had previously disabled threads on these platforms
11841 because they didn't have working thread-safe resolver functions.)
11843 o Major bugfixes, anonymity/security:
11844 - If a client asked for a server by name, and there's a named server
11845 in our network-status but we don't have its descriptor yet, we
11846 could return an unnamed server instead.
11847 - Fix NetBSD bug that could allow someone to force uninitialized RAM
11848 to be sent to a server's DNS resolver. This only affects NetBSD
11849 and other platforms that do not bounds-check tolower().
11850 - Reject (most) attempts to use Tor circuits with length one. (If
11851 many people start using Tor as a one-hop proxy, exit nodes become
11852 a more attractive target for compromise.)
11853 - Just because your DirPort is open doesn't mean people should be
11854 able to remotely teach you about hidden service descriptors. Now
11855 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11857 o Major bugfixes, other:
11858 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
11859 - When a client asks the server to resolve (not connect to)
11860 an address, and it has a cached answer, give them the cached answer.
11861 Previously, the server would give them no answer at all.
11862 - Allow really slow clients to not hang up five minutes into their
11863 directory downloads (suggested by Adam J. Richter).
11864 - We were building exactly the wrong circuits when we anticipated
11865 hidden service requirements, meaning Tor would have to build all
11866 its circuits on demand.
11867 - Avoid crashing when we mmap a router cache file of size 0.
11868 - When testing reachability of our DirPort, don't launch new
11869 tests when there's already one in progress -- unreachable
11870 servers were stacking up dozens of testing streams.
11872 o Minor bugfixes, correctness:
11873 - If we're a directory mirror and we ask for "all" network status
11874 documents, we would discard status documents from authorities
11875 we don't recognize.
11876 - Avoid a memory corruption bug when creating a hash table for
11878 - Avoid controller-triggered crash when misusing certain commands
11879 from a v0 controller on platforms that do not handle
11880 printf("%s",NULL) gracefully.
11881 - Don't crash when a controller sends a third argument to an
11882 "extendcircuit" request.
11883 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11884 response; fix error code when "getinfo dir/status/" fails.
11885 - Avoid crash when telling controller stream-status and a stream
11887 - Patch from Adam Langley to fix assert() in eventdns.c.
11888 - Fix a debug log message in eventdns to say "X resolved to Y"
11889 instead of "X resolved to X".
11890 - Make eventdns give strings for DNS errors, not just error numbers.
11891 - Track unreachable entry guards correctly: don't conflate
11892 'unreachable by us right now' with 'listed as down by the directory
11893 authorities'. With the old code, if a guard was unreachable by
11894 us but listed as running, it would clog our guard list forever.
11895 - Behave correctly in case we ever have a network with more than
11896 2GB/s total advertised capacity.
11897 - Make TrackExitHosts case-insensitive, and fix the behavior of
11898 ".suffix" TrackExitHosts items to avoid matching in the middle of
11900 - Finally fix the openssl warnings from newer gccs that believe that
11901 ignoring a return value is okay, but casting a return value and
11902 then ignoring it is a sign of madness.
11903 - Prevent the contrib/exitlist script from printing the same
11904 result more than once.
11905 - Patch from Steve Hildrey: Generate network status correctly on
11906 non-versioning dirservers.
11907 - Don't listen to the X-Your-Address-Is hint if you did the lookup
11908 via Tor; otherwise you'll think you're the exit node's IP address.
11910 o Minor bugfixes, performance:
11911 - Two small performance improvements on parsing descriptors.
11912 - Major performance improvement on inserting descriptors: change
11913 algorithm from O(n^2) to O(n).
11914 - Make the common memory allocation path faster on machines where
11915 malloc(0) returns a pointer.
11916 - Start remembering X-Your-Address-Is directory hints even if you're
11917 a client, so you can become a server more smoothly.
11918 - Avoid duplicate entries on MyFamily line in server descriptor.
11920 o Packaging, features:
11921 - Remove architecture from OS X builds. The official builds are
11922 now universal binaries.
11923 - The Debian package now uses --verify-config when (re)starting,
11924 to distinguish configuration errors from other errors.
11925 - Update RPMs to require libevent 1.1b.
11927 o Packaging, bugfixes:
11928 - Patches so Tor builds with MinGW on Windows.
11929 - Patches so Tor might run on Cygwin again.
11930 - Resume building on non-gcc compilers and ancient gcc. Resume
11931 building with the -O0 compile flag. Resume building cleanly on
11933 - Run correctly on OS X platforms with case-sensitive filesystems.
11934 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
11935 - Add autoconf checks so Tor can build on Solaris x86 again.
11938 - Documented (and renamed) ServerDNSSearchDomains and
11939 ServerDNSResolvConfFile options.
11940 - Be clearer that the *ListenAddress directives can be repeated
11944 Changes in version 0.1.1.24 - 2006-09-29
11946 - Allow really slow clients to not hang up five minutes into their
11947 directory downloads (suggested by Adam J. Richter).
11948 - Fix major performance regression from 0.1.0.x: instead of checking
11949 whether we have enough directory information every time we want to
11950 do something, only check when the directory information has changed.
11951 This should improve client CPU usage by 25-50%.
11952 - Don't crash if, after a server has been running for a while,
11953 it can't resolve its hostname.
11956 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11957 - Don't crash when the controller receives a third argument to an
11958 "extendcircuit" request.
11959 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11960 response; fix error code when "getinfo dir/status/" fails.
11961 - Fix configure.in to not produce broken configure files with
11962 more recent versions of autoconf. Thanks to Clint for his auto*
11964 - Fix security bug on NetBSD that could allow someone to force
11965 uninitialized RAM to be sent to a server's DNS resolver. This
11966 only affects NetBSD and other platforms that do not bounds-check
11968 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
11969 methods: these are known to be buggy.
11970 - If we're a directory mirror and we ask for "all" network status
11971 documents, we would discard status documents from authorities
11972 we don't recognize.
11975 Changes in version 0.1.2.1-alpha - 2006-08-27
11977 - Add "eventdns" async dns library from Adam Langley, tweaked to
11978 build on OSX and Windows. Only enabled if you pass the
11979 --enable-eventdns argument to configure.
11980 - Allow servers with no hostname or IP address to learn their
11981 IP address by asking the directory authorities. This code only
11982 kicks in when you would normally have exited with a "no address"
11983 error. Nothing's authenticated, so use with care.
11984 - Rather than waiting a fixed amount of time between retrying
11985 application connections, we wait only 5 seconds for the first,
11986 10 seconds for the second, and 15 seconds for each retry after
11987 that. Hopefully this will improve the expected user experience.
11988 - Patch from Tup to add support for transparent AP connections:
11989 this basically bundles the functionality of trans-proxy-tor
11990 into the Tor mainline. Now hosts with compliant pf/netfilter
11991 implementations can redirect TCP connections straight to Tor
11992 without diverting through SOCKS. Needs docs.
11993 - Busy directory servers save lots of memory by spooling server
11994 descriptors, v1 directories, and v2 networkstatus docs to buffers
11995 as needed rather than en masse. Also mmap the cached-routers
11996 files, so we don't need to keep the whole thing in memory too.
11997 - Automatically avoid picking more than one node from the same
11998 /16 network when constructing a circuit.
11999 - Revise and clean up the torrc.sample that we ship with; add
12000 a section for BandwidthRate and BandwidthBurst.
12003 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12004 split connection_t into edge, or, dir, control, and base structs.
12005 These will save quite a bit of memory on busy servers, and they'll
12006 also help us track down bugs in the code and bugs in the spec.
12007 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12008 or later. Log when we are doing this, so we can diagnose it when
12009 it fails. (Also, recommend libevent 1.1b for kqueue and
12010 win32 methods; deprecate libevent 1.0b harder; make libevent
12011 recommendation system saner.)
12012 - Start being able to build universal binaries on OS X (thanks
12014 - Export the default exit policy via the control port, so controllers
12015 don't need to guess what it is / will be later.
12016 - Add a man page entry for ProtocolWarnings.
12017 - Add TestVia config option to the man page.
12018 - Remove even more protocol-related warnings from Tor server logs,
12019 such as bad TLS handshakes and malformed begin cells.
12020 - Stop fetching descriptors if you're not a dir mirror and you
12021 haven't tried to establish any circuits lately. [This currently
12022 causes some dangerous behavior, because when you start up again
12023 you'll use your ancient server descriptors.]
12024 - New DirPort behavior: if you have your dirport set, you download
12025 descriptors aggressively like a directory mirror, whether or not
12026 your ORPort is set.
12027 - Get rid of the router_retry_connections notion. Now routers
12028 no longer try to rebuild long-term connections to directory
12029 authorities, and directory authorities no longer try to rebuild
12030 long-term connections to all servers. We still don't hang up
12031 connections in these two cases though -- we need to look at it
12032 more carefully to avoid flapping, and we likely need to wait til
12033 0.1.1.x is obsolete.
12034 - Drop compatibility with obsolete Tors that permit create cells
12035 to have the wrong circ_id_type.
12036 - Re-enable per-connection rate limiting. Get rid of the "OP
12037 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12038 separate global buckets that apply depending on what sort of conn
12040 - Start publishing one minute or so after we find our ORPort
12041 to be reachable. This will help reduce the number of descriptors
12042 we have for ourselves floating around, since it's quite likely
12043 other things (e.g. DirPort) will change during that minute too.
12044 - Fork the v1 directory protocol into its own spec document,
12045 and mark dir-spec.txt as the currently correct (v2) spec.
12048 - When we find our DirPort to be reachable, publish a new descriptor
12049 so we'll tell the world (reported by pnx).
12050 - Publish a new descriptor after we hup/reload. This is important
12051 if our config has changed such that we'll want to start advertising
12052 our DirPort now, etc.
12053 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12054 - When we have a state file we cannot parse, tell the user and
12055 move it aside. Now we avoid situations where the user starts
12056 Tor in 1904, Tor writes a state file with that timestamp in it,
12057 the user fixes her clock, and Tor refuses to start.
12058 - Fix configure.in to not produce broken configure files with
12059 more recent versions of autoconf. Thanks to Clint for his auto*
12061 - "tor --verify-config" now exits with -1(255) or 0 depending on
12062 whether the config options are bad or good.
12063 - Resolve bug 321 when using dnsworkers: append a period to every
12064 address we resolve at the exit node, so that we do not accidentally
12065 pick up local addresses, and so that failing searches are retried
12066 in the resolver search domains. (This is already solved for
12067 eventdns.) (This breaks Blossom servers for now.)
12068 - If we are using an exit enclave and we can't connect, e.g. because
12069 its webserver is misconfigured to not listen on localhost, then
12070 back off and try connecting from somewhere else before we fail.
12073 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12074 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12075 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12076 when the IP address is mapped through MapAddress to a hostname.
12077 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12078 useless IPv6 DNS resolves.
12079 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12080 before we execute the signal, in case the signal shuts us down.
12081 - Clean up AllowInvalidNodes man page entry.
12082 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12083 - Add more asserts to track down an assert error on a windows Tor
12084 server with connection_add being called with socket == -1.
12085 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12086 - Fix misleading log messages: an entry guard that is "unlisted",
12087 as well as not known to be "down" (because we've never heard
12088 of it), is not therefore "up".
12089 - Remove code to special-case "-cvs" ending, since it has not
12090 actually mattered since 0.0.9.
12091 - Make our socks5 handling more robust to broken socks clients:
12092 throw out everything waiting on the buffer in between socks
12093 handshake phases, since they can't possibly (so the theory
12094 goes) have predicted what we plan to respond to them.
12097 Changes in version 0.1.1.23 - 2006-07-30
12099 - Fast Tor servers, especially exit nodes, were triggering asserts
12100 due to a bug in handling the list of pending DNS resolves. Some
12101 bugs still remain here; we're hunting them.
12102 - Entry guards could crash clients by sending unexpected input.
12103 - More fixes on reachability testing: if you find yourself reachable,
12104 then don't ever make any client requests (so you stop predicting
12105 circuits), then hup or have your clock jump, then later your IP
12106 changes, you won't think circuits are working, so you won't try to
12107 test reachability, so you won't publish.
12110 - Avoid a crash if the controller does a resetconf firewallports
12111 and then a setconf fascistfirewall=1.
12112 - Avoid an integer underflow when the dir authority decides whether
12113 a router is stable: we might wrongly label it stable, and compute
12114 a slightly wrong median stability, when a descriptor is published
12116 - Fix a place where we might trigger an assert if we can't build our
12117 own server descriptor yet.
12120 Changes in version 0.1.1.22 - 2006-07-05
12122 - Fix a big bug that was causing servers to not find themselves
12123 reachable if they changed IP addresses. Since only 0.1.1.22+
12124 servers can do reachability testing correctly, now we automatically
12125 make sure to test via one of these.
12126 - Fix to allow clients and mirrors to learn directory info from
12127 descriptor downloads that get cut off partway through.
12128 - Directory authorities had a bug in deciding if a newly published
12129 descriptor was novel enough to make everybody want a copy -- a few
12130 servers seem to be publishing new descriptors many times a minute.
12132 - Fix a rare bug that was causing some servers to complain about
12133 "closing wedged cpuworkers" and skip some circuit create requests.
12134 - Make the Exit flag in directory status documents actually work.
12137 Changes in version 0.1.1.21 - 2006-06-10
12138 o Crash and assert fixes from 0.1.1.20:
12139 - Fix a rare crash on Tor servers that have enabled hibernation.
12140 - Fix a seg fault on startup for Tor networks that use only one
12141 directory authority.
12142 - Fix an assert from a race condition that occurs on Tor servers
12143 while exiting, where various threads are trying to log that they're
12144 exiting, and delete the logs, at the same time.
12145 - Make our unit tests pass again on certain obscure platforms.
12148 - Add support for building SUSE RPM packages.
12149 - Speed up initial bootstrapping for clients: if we are making our
12150 first ever connection to any entry guard, then don't mark it down
12152 - When only one Tor server in the network is labelled as a guard,
12153 and we've already picked him, we would cycle endlessly picking him
12154 again, being unhappy about it, etc. Now we specifically exclude
12155 current guards when picking a new guard.
12156 - Servers send create cells more reliably after the TLS connection
12157 is established: we were sometimes forgetting to send half of them
12158 when we had more than one pending.
12159 - If we get a create cell that asks us to extend somewhere, but the
12160 Tor server there doesn't match the expected digest, we now send
12161 a destroy cell back, rather than silently doing nothing.
12162 - Make options->RedirectExit work again.
12163 - Make cookie authentication for the controller work again.
12164 - Stop being picky about unusual characters in the arguments to
12165 mapaddress. It's none of our business.
12166 - Add a new config option "TestVia" that lets you specify preferred
12167 middle hops to use for test circuits. Perhaps this will let me
12168 debug the reachability problems better.
12170 o Log / documentation fixes:
12171 - If we're a server and some peer has a broken TLS certificate, don't
12172 log about it unless ProtocolWarnings is set, i.e., we want to hear
12173 about protocol violations by others.
12174 - Fix spelling of VirtualAddrNetwork in man page.
12175 - Add a better explanation at the top of the autogenerated torrc file
12176 about what happened to our old torrc.
12179 Changes in version 0.1.1.20 - 2006-05-23
12181 - Downgrade a log severity where servers complain that they're
12183 - Avoid a compile warning on FreeBSD.
12184 - Remove string size limit on NEWDESC messages; solve bug 291.
12185 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12186 more thoroughly when we're running on windows.
12189 Changes in version 0.1.1.19-rc - 2006-05-03
12191 - Regenerate our local descriptor if it's dirty and we try to use
12192 it locally (e.g. if it changes during reachability detection).
12193 - If we setconf our ORPort to 0, we continued to listen on the
12194 old ORPort and receive connections.
12195 - Avoid a second warning about machine/limits.h on Debian
12197 - Be willing to add our own routerinfo into the routerlist.
12198 Now authorities will include themselves in their directories
12199 and network-statuses.
12200 - Stop trying to upload rendezvous descriptors to every
12201 directory authority: only try the v1 authorities.
12202 - Servers no longer complain when they think they're not
12203 registered with the directory authorities. There were too many
12205 - Backport dist-rpm changes so rpms can be built without errors.
12208 - Implement an option, VirtualAddrMask, to set which addresses
12209 get handed out in response to mapaddress requests. This works
12210 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12213 Changes in version 0.1.1.18-rc - 2006-04-10
12215 - Work harder to download live network-statuses from all the
12216 directory authorities we know about. Improve the threshold
12217 decision logic so we're more robust to edge cases.
12218 - When fetching rendezvous descriptors, we were willing to ask
12219 v2 authorities too, which would always return 404.
12222 - Stop listing down or invalid nodes in the v1 directory. This will
12223 reduce its bulk by about 1/3, and reduce load on directory
12225 - When deciding whether a router is Fast or Guard-worthy, consider
12226 his advertised BandwidthRate and not just the BandwidthCapacity.
12227 - No longer ship INSTALL and README files -- they are useless now.
12228 - Force rpmbuild to behave and honor target_cpu.
12229 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12230 - Start to include translated versions of the tor-doc-*.html
12231 files, along with the screenshots. Still needs more work.
12232 - Start sending back 512 and 451 errors if mapaddress fails,
12233 rather than not sending anything back at all.
12234 - When we fail to bind or listen on an incoming or outgoing
12235 socket, we should close it before failing. otherwise we just
12236 leak it. (thanks to weasel for finding.)
12237 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12238 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12239 - Make NoPublish (even though deprecated) work again.
12240 - Fix a minor security flaw where a versioning auth dirserver
12241 could list a recommended version many times in a row to make
12242 clients more convinced that it's recommended.
12243 - Fix crash bug if there are two unregistered servers running
12244 with the same nickname, one of them is down, and you ask for
12245 them by nickname in your EntryNodes or ExitNodes. Also, try
12246 to pick the one that's running rather than an arbitrary one.
12247 - Fix an infinite loop we could hit if we go offline for too long.
12248 - Complain when we hit WSAENOBUFS on recv() or write() too.
12249 Perhaps this will help us hunt the bug.
12250 - If you're not a versioning dirserver, don't put the string
12251 "client-versions \nserver-versions \n" in your network-status.
12252 - Lower the minimum required number of file descriptors to 1000,
12253 so we can have some overhead for Valgrind on Linux, where the
12254 default ulimit -n is 1024.
12257 - Add tor.dizum.com as the fifth authoritative directory server.
12258 - Add a new config option FetchUselessDescriptors, off by default,
12259 for when you plan to run "exitlist" on your client and you want
12260 to know about even the non-running descriptors.
12263 Changes in version 0.1.1.17-rc - 2006-03-28
12265 - Clients and servers since 0.1.1.10-alpha have been expiring
12266 connections whenever they are idle for 5 minutes and they *do*
12267 have circuits on them. Oops. With this new version, clients will
12268 discard their previous entry guard choices and avoid choosing
12269 entry guards running these flawed versions.
12270 - Fix memory leak when uncompressing concatenated zlib streams. This
12271 was causing substantial leaks over time on Tor servers.
12272 - The v1 directory was including servers as much as 48 hours old,
12273 because that's how the new routerlist->routers works. Now only
12274 include them if they're 20 hours old or less.
12277 - Resume building on irix64, netbsd 2.0, etc.
12278 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12280 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12281 and it is confusing some users.
12282 - Mirrors stop caching the v1 directory so often.
12283 - Make the max number of old descriptors that a cache will hold
12284 rise with the number of directory authorities, so we can scale.
12285 - Change our win32 uname() hack to be more forgiving about what
12286 win32 versions it thinks it's found.
12289 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12291 - When the controller's *setconf commands fail, collect an error
12292 message in a string and hand it back to the controller.
12293 - Make the v2 dir's "Fast" flag based on relative capacity, just
12294 like "Stable" is based on median uptime. Name everything in the
12295 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12296 - Log server fingerprint on startup, so new server operators don't
12297 have to go hunting around their filesystem for it.
12298 - Return a robots.txt on our dirport to discourage google indexing.
12299 - Let the controller ask for GETINFO dir/status/foo so it can ask
12300 directly rather than connecting to the dir port. Only works when
12301 dirport is set for now.
12303 o New config options rather than constants in the code:
12304 - SocksTimeout: How long do we let a socks connection wait
12305 unattached before we fail it?
12306 - CircuitBuildTimeout: Cull non-open circuits that were born
12307 at least this many seconds ago.
12308 - CircuitIdleTimeout: Cull open clean circuits that were born
12309 at least this many seconds ago.
12312 Changes in version 0.1.1.16-rc - 2006-03-18
12313 o Bugfixes on 0.1.1.15-rc:
12314 - Fix assert when the controller asks to attachstream a connect-wait
12315 or resolve-wait stream.
12316 - Now do address rewriting when the controller asks us to attach
12317 to a particular circuit too. This will let Blossom specify
12318 "moria2.exit" without having to learn what moria2's IP address is.
12319 - Make the "tor --verify-config" command-line work again, so people
12320 can automatically check if their torrc will parse.
12321 - Authoritative dirservers no longer require an open connection from
12322 a server to consider him "reachable". We need this change because
12323 when we add new auth dirservers, old servers won't know not to
12325 - Let Tor build on Sun CC again.
12326 - Fix an off-by-one buffer size in dirserv.c that magically never
12327 hit our three authorities but broke sjmurdoch's own tor network.
12328 - If we as a directory mirror don't know of any v1 directory
12329 authorities, then don't try to cache any v1 directories.
12330 - Stop warning about unknown servers in our family when they are
12331 given as hex digests.
12332 - Stop complaining as quickly to the server operator that he
12333 hasn't registered his nickname/key binding.
12334 - Various cleanups so we can add new V2 Auth Dirservers.
12335 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12336 reflect the updated flags in our v2 dir protocol.
12337 - Resume allowing non-printable characters for exit streams (both
12338 for connecting and for resolving). Now we tolerate applications
12339 that don't follow the RFCs. But continue to block malformed names
12342 o Bugfixes on 0.1.0.x:
12343 - Fix assert bug in close_logs(): when we close and delete logs,
12344 remove them all from the global "logfiles" list.
12345 - Fix minor integer overflow in calculating when we expect to use up
12346 our bandwidth allocation before hibernating.
12347 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12348 there are multiple SSLs installed with different versions.
12349 - When we try to be a server and Address is not explicitly set and
12350 our hostname resolves to a private IP address, try to use an
12351 interface address if it has a public address. Now Windows machines
12352 that think of themselves as localhost can work by default.
12355 - Let the controller ask for GETINFO dir/server/foo so it can ask
12356 directly rather than connecting to the dir port.
12357 - Let the controller tell us about certain router descriptors
12358 that it doesn't want Tor to use in circuits. Implement
12359 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12360 - New config option SafeSocks to reject all application connections
12361 using unsafe socks protocols. Defaults to off.
12364 Changes in version 0.1.1.15-rc - 2006-03-11
12365 o Bugfixes and cleanups:
12366 - When we're printing strings from the network, don't try to print
12367 non-printable characters. This protects us against shell escape
12368 sequence exploits, and also against attacks to fool humans into
12369 misreading their logs.
12370 - Fix a bug where Tor would fail to establish any connections if you
12371 left it off for 24 hours and then started it: we were happy with
12372 the obsolete network statuses, but they all referred to router
12373 descriptors that were too old to fetch, so we ended up with no
12374 valid router descriptors.
12375 - Fix a seg fault in the controller's "getinfo orconn-status"
12376 command while listing status on incoming handshaking connections.
12377 Introduce a status name "NEW" for these connections.
12378 - If we get a linelist or linelist_s config option from the torrc
12379 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12380 silently resetting it to its default.
12381 - Don't abandon entry guards until they've been down or gone for
12383 - Cleaner and quieter log messages.
12386 - New controller signal NEWNYM that makes new application requests
12387 use clean circuits.
12388 - Add a new circuit purpose 'controller' to let the controller ask
12389 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12390 controller command to let you specify the purpose if you're
12391 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12392 command to let you change a circuit's purpose after it's been
12394 - Accept "private:*" in routerdesc exit policies; not generated yet
12395 because older Tors do not understand it.
12396 - Add BSD-style contributed startup script "rc.subr" from Peter
12400 Changes in version 0.1.1.14-alpha - 2006-02-20
12401 o Bugfixes on 0.1.1.x:
12402 - Don't die if we ask for a stdout or stderr log (even implicitly)
12403 and we're set to RunAsDaemon -- just warn.
12404 - We still had a few bugs in the OR connection rotation code that
12405 caused directory servers to slowly aggregate connections to other
12406 fast Tor servers. This time for sure!
12407 - Make log entries on Win32 include the name of the function again.
12408 - We were treating a pair of exit policies if they were equal even
12409 if one said accept and the other said reject -- causing us to
12410 not always publish a new descriptor since we thought nothing
12412 - Retry pending server downloads as well as pending networkstatus
12413 downloads when we unexpectedly get a socks request.
12414 - We were ignoring the IS_FAST flag in the directory status,
12415 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12417 - If the controller's SAVECONF command fails (e.g. due to file
12418 permissions), let the controller know that it failed.
12421 - If we're trying to be a Tor server and running Windows 95/98/ME
12422 as a server, explain that we'll likely crash.
12423 - When we're a server, a client asks for an old-style directory,
12424 and our write bucket is empty, don't give it to him. This way
12425 small servers can continue to serve the directory *sometimes*,
12426 without getting overloaded.
12427 - Compress exit policies even more -- look for duplicate lines
12429 - Clients now honor the "guard" flag in the router status when
12430 picking entry guards, rather than looking at is_fast or is_stable.
12431 - Retain unrecognized lines in $DATADIR/state file, so that we can
12432 be forward-compatible.
12433 - Generate 18.0.0.0/8 address policy format in descs when we can;
12434 warn when the mask is not reducible to a bit-prefix.
12435 - Let the user set ControlListenAddress in the torrc. This can be
12436 dangerous, but there are some cases (like a secured LAN) where it
12438 - Split ReachableAddresses into ReachableDirAddresses and
12439 ReachableORAddresses, so we can restrict Dir conns to port 80
12440 and OR conns to port 443.
12441 - Now we can target arch and OS in rpm builds (contributed by
12442 Phobos). Also make the resulting dist-rpm filename match the
12444 - New config options to help controllers: FetchServerDescriptors
12445 and FetchHidServDescriptors for whether to fetch server
12446 info and hidserv info or let the controller do it, and
12447 PublishServerDescriptor and PublishHidServDescriptors.
12448 - Also let the controller set the __AllDirActionsPrivate config
12449 option if you want all directory fetches/publishes to happen via
12450 Tor (it assumes your controller bootstraps your circuits).
12453 Changes in version 0.1.0.17 - 2006-02-17
12454 o Crash bugfixes on 0.1.0.x:
12455 - When servers with a non-zero DirPort came out of hibernation,
12456 sometimes they would trigger an assert.
12458 o Other important bugfixes:
12459 - On platforms that don't have getrlimit (like Windows), we were
12460 artificially constraining ourselves to a max of 1024
12461 connections. Now just assume that we can handle as many as 15000
12462 connections. Hopefully this won't cause other problems.
12464 o Backported features:
12465 - When we're a server, a client asks for an old-style directory,
12466 and our write bucket is empty, don't give it to him. This way
12467 small servers can continue to serve the directory *sometimes*,
12468 without getting overloaded.
12469 - Whenever you get a 503 in response to a directory fetch, try
12470 once more. This will become important once servers start sending
12471 503's whenever they feel busy.
12472 - Fetch a new directory every 120 minutes, not every 40 minutes.
12473 Now that we have hundreds of thousands of users running the old
12474 directory algorithm, it's starting to hurt a lot.
12475 - Bump up the period for forcing a hidden service descriptor upload
12476 from 20 minutes to 1 hour.
12479 Changes in version 0.1.1.13-alpha - 2006-02-09
12480 o Crashes in 0.1.1.x:
12481 - When you tried to setconf ORPort via the controller, Tor would
12482 crash. So people using TorCP to become a server were sad.
12483 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12484 servers. The problem appears to be something do with OpenSSL's
12485 random number generation, or how we call it, or something. Let me
12486 know if the crashes continue.
12487 - Turn crypto hardware acceleration off by default, until we find
12488 somebody smart who can test it for us. (It appears to produce
12489 seg faults in at least some cases.)
12490 - Fix a rare assert error when we've tried all intro points for
12491 a hidden service and we try fetching the service descriptor again:
12492 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12495 - Fix a major load balance bug: we were round-robining in 16 KB
12496 chunks, and servers with bandwidthrate of 20 KB, while downloading
12497 a 600 KB directory, would starve their other connections. Now we
12498 try to be a bit more fair.
12499 - Dir authorities and mirrors were never expiring the newest
12500 descriptor for each server, causing memory and directory bloat.
12501 - Fix memory-bloating and connection-bloating bug on servers: We
12502 were never closing any connection that had ever had a circuit on
12503 it, because we were checking conn->n_circuits == 0, yet we had a
12504 bug that let it go negative.
12505 - Make Tor work using squid as your http proxy again -- squid
12506 returns an error if you ask for a URL that's too long, and it uses
12507 a really generic error message. Plus, many people are behind a
12508 transparent squid so they don't even realize it.
12509 - On platforms that don't have getrlimit (like Windows), we were
12510 artificially constraining ourselves to a max of 1024
12511 connections. Now just assume that we can handle as many as 15000
12512 connections. Hopefully this won't cause other problems.
12513 - Add a new config option ExitPolicyRejectPrivate which defaults to
12514 1. This means all exit policies will begin with rejecting private
12515 addresses, unless the server operator explicitly turns it off.
12518 - Clients no longer download descriptors for non-running
12520 - Before we add new directory authorities, we should make it
12521 clear that only v1 authorities should receive/publish hidden
12522 service descriptors.
12525 - As soon as we've fetched some more directory info, immediately
12526 try to download more server descriptors. This way we don't have
12527 a 10 second pause during initial bootstrapping.
12528 - Remove even more loud log messages that the server operator can't
12530 - When we're running an obsolete or un-recommended version, make
12531 the log message more clear about what the problem is and what
12532 versions *are* still recommended.
12533 - Provide a more useful warn message when our onion queue gets full:
12534 the CPU is too slow or the exit policy is too liberal.
12535 - Don't warn when we receive a 503 from a dirserver/cache -- this
12536 will pave the way for them being able to refuse if they're busy.
12537 - When we fail to bind a listener, try to provide a more useful
12538 log message: e.g., "Is Tor already running?"
12539 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12540 Goldberg can prove things about our handshake protocol more
12542 - MaxConn has been obsolete for a while now. Document the ConnLimit
12543 config option, which is a *minimum* number of file descriptors
12544 that must be available else Tor refuses to start.
12545 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12546 if you log to syslog and want something other than LOG_DAEMON.
12547 - Make dirservers generate a separate "guard" flag to mean,
12548 "would make a good entry guard". Make clients parse it and vote
12549 on it. Not used by clients yet.
12550 - Implement --with-libevent-dir option to ./configure. Also, improve
12551 search techniques to find libevent, and use those for openssl too.
12552 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12553 - Only start testing reachability once we've established a
12554 circuit. This will make startup on dirservers less noisy.
12555 - Don't try to upload hidden service descriptors until we have
12556 established a circuit.
12557 - Fix the controller's "attachstream 0" command to treat conn like
12558 it just connected, doing address remapping, handling .exit and
12559 .onion idioms, and so on. Now we're more uniform in making sure
12560 that the controller hears about new and closing connections.
12563 Changes in version 0.1.1.12-alpha - 2006-01-11
12564 o Bugfixes on 0.1.1.x:
12565 - The fix to close duplicate server connections was closing all
12566 Tor client connections if they didn't establish a circuit
12567 quickly enough. Oops.
12568 - Fix minor memory issue (double-free) that happened on exit.
12570 o Bugfixes on 0.1.0.x:
12571 - Tor didn't warn when it failed to open a log file.
12574 Changes in version 0.1.1.11-alpha - 2006-01-10
12575 o Crashes in 0.1.1.x:
12576 - Include all the assert/crash fixes from 0.1.0.16.
12577 - If you start Tor and then quit very quickly, there were some
12578 races that tried to free things that weren't allocated yet.
12579 - Fix a rare memory stomp if you're running hidden services.
12580 - Fix segfault when specifying DirServer in config without nickname.
12581 - Fix a seg fault when you finish connecting to a server but at
12582 that moment you dump his server descriptor.
12583 - Extendcircuit and Attachstream controller commands would
12584 assert/crash if you don't give them enough arguments.
12585 - Fix an assert error when we're out of space in the connection_list
12586 and we try to post a hidden service descriptor (reported by weasel).
12587 - If you specify a relative torrc path and you set RunAsDaemon in
12588 your torrc, then it chdir()'s to the new directory. If you HUP,
12589 it tries to load the new torrc location, fails, and exits.
12590 The fix: no longer allow a relative path to torrc using -f.
12593 - Implement "entry guards": automatically choose a handful of entry
12594 nodes and stick with them for all circuits. Only pick new guards
12595 when the ones you have are unsuitable, and if the old guards
12596 become suitable again, switch back. This will increase security
12597 dramatically against certain end-point attacks. The EntryNodes
12598 config option now provides some hints about which entry guards you
12599 want to use most; and StrictEntryNodes means to only use those.
12600 - New directory logic: download by descriptor digest, not by
12601 fingerprint. Caches try to download all listed digests from
12602 authorities; clients try to download "best" digests from caches.
12603 This avoids partitioning and isolating attacks better.
12604 - Make the "stable" router flag in network-status be the median of
12605 the uptimes of running valid servers, and make clients pay
12606 attention to the network-status flags. Thus the cutoff adapts
12607 to the stability of the network as a whole, making IRC, IM, etc
12608 connections more reliable.
12611 - Tor servers with dynamic IP addresses were needing to wait 18
12612 hours before they could start doing reachability testing using
12613 the new IP address and ports. This is because they were using
12614 the internal descriptor to learn what to test, yet they were only
12615 rebuilding the descriptor once they decided they were reachable.
12616 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12617 to download certain server descriptors, throw them away, and then
12618 fetch them again after 30 minutes. Now mirrors throw away these
12619 server descriptors so clients can't get them.
12620 - We were leaving duplicate connections to other ORs open for a week,
12621 rather than closing them once we detect a duplicate. This only
12622 really affected authdirservers, but it affected them a lot.
12623 - Spread the authdirservers' reachability testing over the entire
12624 testing interval, so we don't try to do 500 TLS's at once every
12628 - If the network is down, and we try to connect to a conn because
12629 we have a circuit in mind, and we timeout (30 seconds) because the
12630 network never answers, we were expiring the circuit, but we weren't
12631 obsoleting the connection or telling the entry_guards functions.
12632 - Some Tor servers process billions of cells per day. These statistics
12633 need to be uint64_t's.
12634 - Check for integer overflows in more places, when adding elements
12635 to smartlists. This could possibly prevent a buffer overflow
12636 on malicious huge inputs. I don't see any, but I haven't looked
12638 - ReachableAddresses kept growing new "reject *:*" lines on every
12640 - When you "setconf log" via the controller, it should remove all
12641 logs. We were automatically adding back in a "log notice stdout".
12642 - Newly bootstrapped Tor networks couldn't establish hidden service
12643 circuits until they had nodes with high uptime. Be more tolerant.
12644 - We were marking servers down when they could not answer every piece
12645 of the directory request we sent them. This was far too harsh.
12646 - Fix the torify (tsocks) config file to not use Tor for localhost
12648 - Directory authorities now go to the proper authority when asking for
12649 a networkstatus, even when they want a compressed one.
12650 - Fix a harmless bug that was causing Tor servers to log
12651 "Got an end because of misc error, but we're not an AP. Closing."
12652 - Authorities were treating their own descriptor changes as cosmetic,
12653 meaning the descriptor available in the network-status and the
12654 descriptor that clients downloaded were different.
12655 - The OS X installer was adding a symlink for tor_resolve but
12656 the binary was called tor-resolve (reported by Thomas Hardly).
12657 - Workaround a problem with some http proxies where they refuse GET
12658 requests that specify "Content-Length: 0" (reported by Adrian).
12659 - Fix wrong log message when you add a "HiddenServiceNodes" config
12660 line without any HiddenServiceDir line (reported by Chris Thomas).
12663 - Write the TorVersion into the state file so we have a prayer of
12664 keeping forward and backward compatibility.
12665 - Revive the FascistFirewall config option rather than eliminating it:
12666 now it's a synonym for ReachableAddresses *:80,*:443.
12667 - Clients choose directory servers from the network status lists,
12668 not from their internal list of router descriptors. Now they can
12669 go to caches directly rather than needing to go to authorities
12671 - Directory authorities ignore router descriptors that have only
12672 cosmetic differences: do this for 0.1.0.x servers now too.
12673 - Add a new flag to network-status indicating whether the server
12674 can answer v2 directory requests too.
12675 - Authdirs now stop whining so loudly about bad descriptors that
12676 they fetch from other dirservers. So when there's a log complaint,
12677 it's for sure from a freshly uploaded descriptor.
12678 - Reduce memory requirements in our structs by changing the order
12680 - There used to be two ways to specify your listening ports in a
12681 server descriptor: on the "router" line and with a separate "ports"
12682 line. Remove support for the "ports" line.
12683 - New config option "AuthDirRejectUnlisted" for auth dirservers as
12684 a panic button: if we get flooded with unusable servers we can
12685 revert to only listing servers in the approved-routers file.
12686 - Auth dir servers can now mark a fingerprint as "!reject" or
12687 "!invalid" in the approved-routers file (as its nickname), to
12688 refuse descriptors outright or include them but marked as invalid.
12689 - Servers store bandwidth history across restarts/crashes.
12690 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12691 get a better idea of why their circuits failed. Not used yet.
12692 - Directory mirrors now cache up to 16 unrecognized network-status
12693 docs. Now we can add new authdirservers and they'll be cached too.
12694 - When picking a random directory, prefer non-authorities if any
12696 - New controller option "getinfo desc/all-recent" to fetch the
12697 latest server descriptor for every router that Tor knows about.
12700 Changes in version 0.1.0.16 - 2006-01-02
12701 o Crash bugfixes on 0.1.0.x:
12702 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12703 corrupting the heap, losing FDs, or crashing when we need to resize
12704 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12705 - It turns out sparc64 platforms crash on unaligned memory access
12706 too -- so detect and avoid this.
12707 - Handle truncated compressed data correctly (by detecting it and
12709 - Fix possible-but-unlikely free(NULL) in control.c.
12710 - When we were closing connections, there was a rare case that
12711 stomped on memory, triggering seg faults and asserts.
12712 - Avoid potential infinite recursion when building a descriptor. (We
12713 don't know that it ever happened, but better to fix it anyway.)
12714 - We were neglecting to unlink marked circuits from soon-to-close OR
12715 connections, which caused some rare scribbling on freed memory.
12716 - Fix a memory stomping race bug when closing the joining point of two
12717 rendezvous circuits.
12718 - Fix an assert in time parsing found by Steven Murdoch.
12720 o Other bugfixes on 0.1.0.x:
12721 - When we're doing reachability testing, provide more useful log
12722 messages so the operator knows what to expect.
12723 - Do not check whether DirPort is reachable when we are suppressing
12724 advertising it because of hibernation.
12725 - When building with -static or on Solaris, we sometimes needed -ldl.
12726 - When we're deciding whether a stream has enough circuits around
12727 that can handle it, count the freshly dirty ones and not the ones
12728 that are so dirty they won't be able to handle it.
12729 - When we're expiring old circuits, we had a logic error that caused
12730 us to close new rendezvous circuits rather than old ones.
12731 - Give a more helpful log message when you try to change ORPort via
12732 the controller: you should upgrade Tor if you want that to work.
12733 - We were failing to parse Tor versions that start with "Tor ".
12734 - Tolerate faulty streams better: when a stream fails for reason
12735 exitpolicy, stop assuming that the router is lying about his exit
12736 policy. When a stream fails for reason misc, allow it to retry just
12737 as if it was resolvefailed. When a stream has failed three times,
12738 reset its failure count so we can try again and get all three tries.
12741 Changes in version 0.1.1.10-alpha - 2005-12-11
12742 o Correctness bugfixes on 0.1.0.x:
12743 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12744 corrupting the heap, losing FDs, or crashing when we need to resize
12745 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12746 - Stop doing the complex voodoo overkill checking for insecure
12747 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12748 - When we were closing connections, there was a rare case that
12749 stomped on memory, triggering seg faults and asserts.
12750 - We were neglecting to unlink marked circuits from soon-to-close OR
12751 connections, which caused some rare scribbling on freed memory.
12752 - When we're deciding whether a stream has enough circuits around
12753 that can handle it, count the freshly dirty ones and not the ones
12754 that are so dirty they won't be able to handle it.
12755 - Recover better from TCP connections to Tor servers that are
12756 broken but don't tell you (it happens!); and rotate TLS
12757 connections once a week.
12758 - When we're expiring old circuits, we had a logic error that caused
12759 us to close new rendezvous circuits rather than old ones.
12760 - Fix a scary-looking but apparently harmless bug where circuits
12761 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12762 servers, and never switch to state CIRCUIT_STATE_OPEN.
12763 - When building with -static or on Solaris, we sometimes needed to
12765 - Give a useful message when people run Tor as the wrong user,
12766 rather than telling them to start chowning random directories.
12767 - We were failing to inform the controller about new .onion streams.
12769 o Security bugfixes on 0.1.0.x:
12770 - Refuse server descriptors if the fingerprint line doesn't match
12771 the included identity key. Tor doesn't care, but other apps (and
12772 humans) might actually be trusting the fingerprint line.
12773 - We used to kill the circuit when we receive a relay command we
12774 don't recognize. Now we just drop it.
12775 - Start obeying our firewall options more rigorously:
12776 . If we can't get to a dirserver directly, try going via Tor.
12777 . Don't ever try to connect (as a client) to a place our
12778 firewall options forbid.
12779 . If we specify a proxy and also firewall options, obey the
12780 firewall options even when we're using the proxy: some proxies
12781 can only proxy to certain destinations.
12782 - Fix a bug found by Lasse Overlier: when we were making internal
12783 circuits (intended to be cannibalized later for rendezvous and
12784 introduction circuits), we were picking them so that they had
12785 useful exit nodes. There was no need for this, and it actually
12786 aids some statistical attacks.
12787 - Start treating internal circuits and exit circuits separately.
12788 It's important to keep them separate because internal circuits
12789 have their last hops picked like middle hops, rather than like
12790 exit hops. So exiting on them will break the user's expectations.
12792 o Bugfixes on 0.1.1.x:
12793 - Take out the mis-feature where we tried to detect IP address
12794 flapping for people with DynDNS, and chose not to upload a new
12795 server descriptor sometimes.
12796 - Try to be compatible with OpenSSL 0.9.6 again.
12797 - Log fix: when the controller is logging about .onion addresses,
12798 sometimes it didn't include the ".onion" part of the address.
12799 - Don't try to modify options->DirServers internally -- if the
12800 user didn't specify any, just add the default ones directly to
12801 the trusted dirserver list. This fixes a bug where people running
12802 controllers would use SETCONF on some totally unrelated config
12803 option, and Tor would start yelling at them about changing their
12805 - Let the controller's redirectstream command specify a port, in
12806 case the controller wants to change that too.
12807 - When we requested a pile of server descriptors, we sometimes
12808 accidentally launched a duplicate request for the first one.
12809 - Bugfix for trackhostexits: write down the fingerprint of the
12810 chosen exit, not its nickname, because the chosen exit might not
12812 - When parsing foo.exit, if foo is unknown, and we are leaving
12813 circuits unattached, set the chosen_exit field and leave the
12814 address empty. This matters because controllers got confused
12816 - Directory authorities no longer try to download server
12817 descriptors that they know they will reject.
12819 o Features and updates:
12820 - Replace balanced trees with hash tables: this should make stuff
12821 significantly faster.
12822 - Resume using the AES counter-mode implementation that we ship,
12823 rather than OpenSSL's. Ours is significantly faster.
12824 - Many other CPU and memory improvements.
12825 - Add a new config option FastFirstHopPK (on by default) so clients
12826 do a trivial crypto handshake for their first hop, since TLS has
12827 already taken care of confidentiality and authentication.
12828 - Add a new config option TestSocks so people can see if their
12829 applications are using socks4, socks4a, socks5-with-ip, or
12830 socks5-with-hostname. This way they don't have to keep mucking
12831 with tcpdump and wondering if something got cached somewhere.
12832 - Warn when listening on a public address for socks. I suspect a
12833 lot of people are setting themselves up as open socks proxies,
12834 and they have no idea that jerks on the Internet are using them,
12835 since they simply proxy the traffic into the Tor network.
12836 - Add "private:*" as an alias in configuration for policies. Now
12837 you can simplify your exit policy rather than needing to list
12838 every single internal or nonroutable network space.
12839 - Add a new controller event type that allows controllers to get
12840 all server descriptors that were uploaded to a router in its role
12841 as authoritative dirserver.
12842 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12843 tor-doc-server.html, and stylesheet.css in the tarball.
12844 - Stop shipping tor-doc.html in the tarball.
12847 Changes in version 0.1.1.9-alpha - 2005-11-15
12848 o Usability improvements:
12849 - Start calling it FooListenAddress rather than FooBindAddress,
12850 since few of our users know what it means to bind an address
12852 - Reduce clutter in server logs. We're going to try to make
12853 them actually usable now. New config option ProtocolWarnings that
12854 lets you hear about how _other Tors_ are breaking the protocol. Off
12856 - Divide log messages into logging domains. Once we put some sort
12857 of interface on this, it will let people looking at more verbose
12858 log levels specify the topics they want to hear more about.
12859 - Make directory servers return better http 404 error messages
12860 instead of a generic "Servers unavailable".
12861 - Check for even more Windows version flags when writing the platform
12862 string in server descriptors, and note any we don't recognize.
12863 - Clean up more of the OpenSSL memory when exiting, so we can detect
12864 memory leaks better.
12865 - Make directory authorities be non-versioning, non-naming by
12866 default. Now we can add new directory servers without requiring
12867 their operators to pay close attention.
12868 - When logging via syslog, include the pid whenever we provide
12869 a log entry. Suggested by Todd Fries.
12871 o Performance improvements:
12872 - Directory servers now silently throw away new descriptors that
12873 haven't changed much if the timestamps are similar. We do this to
12874 tolerate older Tor servers that upload a new descriptor every 15
12875 minutes. (It seemed like a good idea at the time.)
12876 - Inline bottleneck smartlist functions; use fast versions by default.
12877 - Add a "Map from digest to void*" abstraction digestmap_t so we
12878 can do less hex encoding/decoding. Use it in router_get_by_digest()
12879 to resolve a performance bottleneck.
12880 - Allow tor_gzip_uncompress to extract as much as possible from
12881 truncated compressed data. Try to extract as many
12882 descriptors as possible from truncated http responses (when
12883 DIR_PURPOSE_FETCH_ROUTERDESC).
12884 - Make circ->onionskin a pointer, not a static array. moria2 was using
12885 125000 circuit_t's after it had been up for a few weeks, which
12886 translates to 20+ megs of wasted space.
12887 - The private half of our EDH handshake keys are now chosen out
12888 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
12890 o Security improvements:
12891 - Start making directory caches retain old routerinfos, so soon
12892 clients can start asking by digest of descriptor rather than by
12893 fingerprint of server.
12894 - Add half our entropy from RAND_poll in OpenSSL. This knows how
12895 to use egd (if present), openbsd weirdness (if present), vms/os2
12896 weirdness (if we ever port there), and more in the future.
12898 o Bugfixes on 0.1.0.x:
12899 - Do round-robin writes of at most 16 kB per write. This might be
12900 more fair on loaded Tor servers, and it might resolve our Windows
12901 crash bug. It might also slow things down.
12902 - Our TLS handshakes were generating a single public/private
12903 keypair for the TLS context, rather than making a new one for
12904 each new connections. Oops. (But we were still rotating them
12905 periodically, so it's not so bad.)
12906 - When we were cannibalizing a circuit with a particular exit
12907 node in mind, we weren't checking to see if that exit node was
12908 already present earlier in the circuit. Oops.
12909 - When a Tor server's IP changes (e.g. from a dyndns address),
12910 upload a new descriptor so clients will learn too.
12911 - Really busy servers were keeping enough circuits open on stable
12912 connections that they were wrapping around the circuit_id
12913 space. (It's only two bytes.) This exposed a bug where we would
12914 feel free to reuse a circuit_id even if it still exists but has
12915 been marked for close. Try to fix this bug. Some bug remains.
12916 - If we would close a stream early (e.g. it asks for a .exit that
12917 we know would refuse it) but the LeaveStreamsUnattached config
12918 option is set by the controller, then don't close it.
12920 o Bugfixes on 0.1.1.8-alpha:
12921 - Fix a big pile of memory leaks, some of them serious.
12922 - Do not try to download a routerdesc if we would immediately reject
12924 - Resume inserting a newline between all router descriptors when
12925 generating (old style) signed directories, since our spec says
12927 - When providing content-type application/octet-stream for
12928 server descriptors using .z, we were leaving out the
12929 content-encoding header. Oops. (Everything tolerated this just
12930 fine, but that doesn't mean we need to be part of the problem.)
12931 - Fix a potential seg fault in getconf and getinfo using version 1
12932 of the controller protocol.
12933 - Avoid crash: do not check whether DirPort is reachable when we
12934 are suppressing it because of hibernation.
12935 - Make --hash-password not crash on exit.
12938 Changes in version 0.1.1.8-alpha - 2005-10-07
12939 o New features (major):
12940 - Clients don't download or use the directory anymore. Now they
12941 download and use network-statuses from the trusted dirservers,
12942 and fetch individual server descriptors as needed from mirrors.
12943 See dir-spec.txt for all the gory details.
12944 - Be more conservative about whether to advertise our DirPort.
12945 The main change is to not advertise if we're running at capacity
12946 and either a) we could hibernate or b) our capacity is low and
12947 we're using a default DirPort.
12948 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
12950 o New features (minor):
12951 - Try to be smart about when to retry network-status and
12952 server-descriptor fetches. Still needs some tuning.
12953 - Stop parsing, storing, or using running-routers output (but
12954 mirrors still cache and serve it).
12955 - Consider a threshold of versioning dirservers (dirservers who have
12956 an opinion about which Tor versions are still recommended) before
12957 deciding whether to warn the user that he's obsolete.
12958 - Dirservers can now reject/invalidate by key and IP, with the
12959 config options "AuthDirInvalid" and "AuthDirReject". This is
12960 useful since currently we automatically list servers as running
12961 and usable even if we know they're jerks.
12962 - Provide dire warnings to any users who set DirServer; move it out
12963 of torrc.sample and into torrc.complete.
12964 - Add MyFamily to torrc.sample in the server section.
12965 - Add nicknames to the DirServer line, so we can refer to them
12966 without requiring all our users to memorize their IP addresses.
12967 - When we get an EOF or a timeout on a directory connection, note
12968 how many bytes of serverdesc we are dropping. This will help
12969 us determine whether it is smart to parse incomplete serverdesc
12971 - Add a new function to "change pseudonyms" -- that is, to stop
12972 using any currently-dirty circuits for new streams, so we don't
12973 link new actions to old actions. Currently it's only called on
12974 HUP (or SIGNAL RELOAD).
12975 - On sighup, if UseHelperNodes changed to 1, use new circuits.
12976 - Start using RAND_bytes rather than RAND_pseudo_bytes from
12977 OpenSSL. Also, reseed our entropy every hour, not just at
12978 startup. And entropy in 512-bit chunks, not 160-bit chunks.
12980 o Fixes on 0.1.1.7-alpha:
12981 - Nobody ever implemented EVENT_ADDRMAP for control protocol
12982 version 0, so don't let version 0 controllers ask for it.
12983 - If you requested something with too many newlines via the
12984 v1 controller protocol, you could crash tor.
12985 - Fix a number of memory leaks, including some pretty serious ones.
12986 - Re-enable DirPort testing again, so Tor servers will be willing
12987 to advertise their DirPort if it's reachable.
12988 - On TLS handshake, only check the other router's nickname against
12989 its expected nickname if is_named is set.
12991 o Fixes forward-ported from 0.1.0.15:
12992 - Don't crash when we don't have any spare file descriptors and we
12993 try to spawn a dns or cpu worker.
12994 - Make the numbers in read-history and write-history into uint64s,
12995 so they don't overflow and publish negatives in the descriptor.
12997 o Fixes on 0.1.0.x:
12998 - For the OS X package's modified privoxy config file, comment
12999 out the "logfile" line so we don't log everything passed
13001 - We were whining about using socks4 or socks5-with-local-lookup
13002 even when it's an IP in the "virtual" range we designed exactly
13004 - We were leaking some memory every time the client changes IPs.
13005 - Never call free() on tor_malloc()d memory. This will help us
13006 use dmalloc to detect memory leaks.
13007 - Check for named servers when looking them up by nickname;
13008 warn when we'recalling a non-named server by its nickname;
13009 don't warn twice about the same name.
13010 - Try to list MyFamily elements by key, not by nickname, and warn
13011 if we've not heard of the server.
13012 - Make windows platform detection (uname equivalent) smarter.
13013 - It turns out sparc64 doesn't like unaligned access either.
13016 Changes in version 0.1.0.15 - 2005-09-23
13017 o Bugfixes on 0.1.0.x:
13018 - Reject ports 465 and 587 (spam targets) in default exit policy.
13019 - Don't crash when we don't have any spare file descriptors and we
13020 try to spawn a dns or cpu worker.
13021 - Get rid of IgnoreVersion undocumented config option, and make us
13022 only warn, never exit, when we're running an obsolete version.
13023 - Don't try to print a null string when your server finds itself to
13024 be unreachable and the Address config option is empty.
13025 - Make the numbers in read-history and write-history into uint64s,
13026 so they don't overflow and publish negatives in the descriptor.
13027 - Fix a minor memory leak in smartlist_string_remove().
13028 - We were only allowing ourselves to upload a server descriptor at
13029 most every 20 minutes, even if it changed earlier than that.
13030 - Clean up log entries that pointed to old URLs.
13033 Changes in version 0.1.1.7-alpha - 2005-09-14
13034 o Fixes on 0.1.1.6-alpha:
13035 - Exit servers were crashing when people asked them to make a
13036 connection to an address not in their exit policy.
13037 - Looking up a non-existent stream for a v1 control connection would
13039 - Fix a seg fault if we ask a dirserver for a descriptor by
13040 fingerprint but he doesn't know about him.
13041 - SETCONF was appending items to linelists, not clearing them.
13042 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13043 out and refuse the setconf if it would fail.
13044 - Downgrade the dirserver log messages when whining about
13048 - Add Peter Palfrader's check-tor script to tor/contrib/
13049 It lets you easily check whether a given server (referenced by
13050 nickname) is reachable by you.
13051 - Numerous changes to move towards client-side v2 directories. Not
13054 o Fixes on 0.1.0.x:
13055 - If the user gave tor an odd number of command-line arguments,
13056 we were silently ignoring the last one. Now we complain and fail.
13057 [This wins the oldest-bug prize -- this bug has been present since
13058 November 2002, as released in Tor 0.0.0.]
13059 - Do not use unaligned memory access on alpha, mips, or mipsel.
13060 It *works*, but is very slow, so we treat them as if it doesn't.
13061 - Retry directory requests if we fail to get an answer we like
13062 from a given dirserver (we were retrying before, but only if
13063 we fail to connect).
13064 - When writing the RecommendedVersions line, sort them first.
13065 - When the client asked for a rendezvous port that the hidden
13066 service didn't want to provide, we were sending an IP address
13067 back along with the end cell. Fortunately, it was zero. But stop
13069 - Correct "your server is reachable" log entries to indicate that
13070 it was self-testing that told us so.
13073 Changes in version 0.1.1.6-alpha - 2005-09-09
13074 o Fixes on 0.1.1.5-alpha:
13075 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13076 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13077 - Fix bug with tor_memmem finding a match at the end of the string.
13078 - Make unit tests run without segfaulting.
13079 - Resolve some solaris x86 compile warnings.
13080 - Handle duplicate lines in approved-routers files without warning.
13081 - Fix bug where as soon as a server refused any requests due to his
13082 exit policy (e.g. when we ask for localhost and he tells us that's
13083 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13084 exit policy using him for any exits.
13085 - Only do openssl hardware accelerator stuff if openssl version is
13088 o New controller features/fixes:
13089 - Add a "RESETCONF" command so you can set config options like
13090 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13091 a config option in the torrc with no value, then it clears it
13092 entirely (rather than setting it to its default).
13093 - Add a "GETINFO config-file" to tell us where torrc is.
13094 - Avoid sending blank lines when GETINFO replies should be empty.
13095 - Add a QUIT command for the controller (for using it manually).
13096 - Fix a bug in SAVECONF that was adding default dirservers and
13097 other redundant entries to the torrc file.
13099 o Start on the new directory design:
13100 - Generate, publish, cache, serve new network-status format.
13101 - Publish individual descriptors (by fingerprint, by "all", and by
13103 - Publish client and server recommended versions separately.
13104 - Allow tor_gzip_uncompress() to handle multiple concatenated
13105 compressed strings. Serve compressed groups of router
13106 descriptors. The compression logic here could be more
13108 - Distinguish v1 authorities (all currently trusted directories)
13109 from v2 authorities (all trusted directories).
13110 - Change DirServers config line to note which dirs are v1 authorities.
13111 - Add configuration option "V1AuthoritativeDirectory 1" which
13112 moria1, moria2, and tor26 should set.
13113 - Remove option when getting directory cache to see whether they
13114 support running-routers; they all do now. Replace it with one
13115 to see whether caches support v2 stuff.
13118 - Dirservers now do their own external reachability testing of each
13119 Tor server, and only list them as running if they've been found to
13120 be reachable. We also send back warnings to the server's logs if
13121 it uploads a descriptor that we already believe is unreachable.
13122 - Implement exit enclaves: if we know an IP address for the
13123 destination, and there's a running Tor server at that address
13124 which allows exit to the destination, then extend the circuit to
13125 that exit first. This provides end-to-end encryption and end-to-end
13126 authentication. Also, if the user wants a .exit address or enclave,
13127 use 4 hops rather than 3, and cannibalize a general circ for it
13129 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13130 controller. Also, rotate dns and cpu workers if the controller
13131 changes options that will affect them; and initialize the dns
13132 worker cache tree whether or not we start out as a server.
13133 - Only upload a new server descriptor when options change, 18
13134 hours have passed, uptime is reset, or bandwidth changes a lot.
13135 - Check [X-]Forwarded-For headers in HTTP requests when generating
13136 log messages. This lets people run dirservers (and caches) behind
13137 Apache but still know which IP addresses are causing warnings.
13139 o Config option changes:
13140 - Replace (Fascist)Firewall* config options with a new
13141 ReachableAddresses option that understands address policies.
13142 For example, "ReachableAddresses *:80,*:443"
13143 - Get rid of IgnoreVersion undocumented config option, and make us
13144 only warn, never exit, when we're running an obsolete version.
13145 - Make MonthlyAccountingStart config option truly obsolete now.
13147 o Fixes on 0.1.0.x:
13148 - Reject ports 465 and 587 in the default exit policy, since
13149 people have started using them for spam too.
13150 - It turns out we couldn't bootstrap a network since we added
13151 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13152 has never gone down. Add an AssumeReachable config option to let
13153 servers and dirservers bootstrap. When we're trying to build a
13154 high-uptime or high-bandwidth circuit but there aren't enough
13155 suitable servers, try being less picky rather than simply failing.
13156 - Our logic to decide if the OR we connected to was the right guy
13157 was brittle and maybe open to a mitm for unverified routers.
13158 - We weren't cannibalizing circuits correctly for
13159 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13160 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13161 build those from scratch. This should make hidden services faster.
13162 - Predict required circuits better, with an eye toward making hidden
13163 services faster on the service end.
13164 - Retry streams if the exit node sends back a 'misc' failure. This
13165 should result in fewer random failures. Also, after failing
13166 from resolve failed or misc, reset the num failures, so we give
13167 it a fair shake next time we try.
13168 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13169 - Reduce severity on logs about dns worker spawning and culling.
13170 - When we're shutting down and we do something like try to post a
13171 server descriptor or rendezvous descriptor, don't complain that
13172 we seem to be unreachable. Of course we are, we're shutting down.
13173 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13174 We don't use them yet, but maybe one day our DNS resolver will be
13175 able to discover them.
13176 - Make ContactInfo mandatory for authoritative directory servers.
13177 - Require server descriptors to list IPv4 addresses -- hostnames
13178 are no longer allowed. This also fixes some potential security
13179 problems with people providing hostnames as their address and then
13180 preferentially resolving them to partition users.
13181 - Change log line for unreachability to explicitly suggest /etc/hosts
13182 as the culprit. Also make it clearer what IP address and ports we're
13183 testing for reachability.
13184 - Put quotes around user-supplied strings when logging so users are
13185 more likely to realize if they add bad characters (like quotes)
13187 - Let auth dir servers start without specifying an Address config
13189 - Make unit tests (and other invocations that aren't the real Tor)
13190 run without launching listeners, creating subdirectories, and so on.
13193 Changes in version 0.1.1.5-alpha - 2005-08-08
13194 o Bugfixes included in 0.1.0.14.
13196 o Bugfixes on 0.1.0.x:
13197 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13198 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13199 it would silently using ignore the 6668.
13202 Changes in version 0.1.0.14 - 2005-08-08
13203 o Bugfixes on 0.1.0.x:
13204 - Fix the other half of the bug with crypto handshakes
13206 - Fix an assert trigger if you send a 'signal term' via the
13207 controller when it's listening for 'event info' messages.
13210 Changes in version 0.1.1.4-alpha - 2005-08-04
13211 o Bugfixes included in 0.1.0.13.
13214 - Improve tor_gettimeofday() granularity on windows.
13215 - Make clients regenerate their keys when their IP address changes.
13216 - Implement some more GETINFO goodness: expose helper nodes, config
13217 options, getinfo keys.
13220 Changes in version 0.1.0.13 - 2005-08-04
13221 o Bugfixes on 0.1.0.x:
13222 - Fix a critical bug in the security of our crypto handshakes.
13223 - Fix a size_t underflow in smartlist_join_strings2() that made
13224 it do bad things when you hand it an empty smartlist.
13225 - Fix Windows installer to ship Tor license (thanks to Aphex for
13226 pointing out this oversight) and put a link to the doc directory
13228 - Explicitly set no-unaligned-access for sparc: it turns out the
13229 new gcc's let you compile broken code, but that doesn't make it
13233 Changes in version 0.1.1.3-alpha - 2005-07-23
13234 o Bugfixes on 0.1.1.2-alpha:
13235 - Fix a bug in handling the controller's "post descriptor"
13237 - Fix several bugs in handling the controller's "extend circuit"
13239 - Fix a bug in handling the controller's "stream status" event.
13240 - Fix an assert failure if we have a controller listening for
13241 circuit events and we go offline.
13242 - Re-allow hidden service descriptors to publish 0 intro points.
13243 - Fix a crash when generating your hidden service descriptor if
13244 you don't have enough intro points already.
13246 o New features on 0.1.1.2-alpha:
13247 - New controller function "getinfo accounting", to ask how
13248 many bytes we've used in this time period.
13249 - Experimental support for helper nodes: a lot of the risk from
13250 a small static adversary comes because users pick new random
13251 nodes every time they rebuild a circuit. Now users will try to
13252 stick to the same small set of entry nodes if they can. Not
13253 enabled by default yet.
13255 o Bugfixes on 0.1.0.12:
13256 - If you're an auth dir server, always publish your dirport,
13257 even if you haven't yet found yourself to be reachable.
13258 - Fix a size_t underflow in smartlist_join_strings2() that made
13259 it do bad things when you hand it an empty smartlist.
13262 Changes in version 0.1.0.12 - 2005-07-18
13263 o New directory servers:
13264 - tor26 has changed IP address.
13266 o Bugfixes on 0.1.0.x:
13267 - Fix a possible double-free in tor_gzip_uncompress().
13268 - When --disable-threads is set, do not search for or link against
13269 pthreads libraries.
13270 - Don't trigger an assert if an authoritative directory server
13271 claims its dirport is 0.
13272 - Fix bug with removing Tor as an NT service: some people were
13273 getting "The service did not return an error." Thanks to Matt
13277 Changes in version 0.1.1.2-alpha - 2005-07-15
13278 o New directory servers:
13279 - tor26 has changed IP address.
13281 o Bugfixes on 0.1.0.x, crashes/leaks:
13282 - Port the servers-not-obeying-their-exit-policies fix from
13284 - Fix an fd leak in start_daemon().
13285 - On Windows, you can't always reopen a port right after you've
13286 closed it. So change retry_listeners() to only close and re-open
13287 ports that have changed.
13288 - Fix a possible double-free in tor_gzip_uncompress().
13290 o Bugfixes on 0.1.0.x, usability:
13291 - When tor_socketpair() fails in Windows, give a reasonable
13292 Windows-style errno back.
13293 - Let people type "tor --install" as well as "tor -install" when
13295 want to make it an NT service.
13296 - NT service patch from Matt Edman to improve error messages.
13297 - When the controller asks for a config option with an abbreviated
13298 name, give the full name in our response.
13299 - Correct the man page entry on TrackHostExitsExpire.
13300 - Looks like we were never delivering deflated (i.e. compressed)
13301 running-routers lists, even when asked. Oops.
13302 - When --disable-threads is set, do not search for or link against
13303 pthreads libraries.
13305 o Bugfixes on 0.1.1.x:
13306 - Fix a seg fault with autodetecting which controller version is
13310 - New hidden service descriptor format: put a version in it, and
13311 let people specify introduction/rendezvous points that aren't
13312 in "the directory" (which is subjective anyway).
13313 - Allow the DEBUG controller event to work again. Mark certain log
13314 entries as "don't tell this to controllers", so we avoid cycles.
13317 Changes in version 0.1.0.11 - 2005-06-30
13318 o Bugfixes on 0.1.0.x:
13319 - Fix major security bug: servers were disregarding their
13320 exit policies if clients behaved unexpectedly.
13321 - Make OS X init script check for missing argument, so we don't
13322 confuse users who invoke it incorrectly.
13323 - Fix a seg fault in "tor --hash-password foo".
13324 - The MAPADDRESS control command was broken.
13327 Changes in version 0.1.1.1-alpha - 2005-06-29
13329 - Make OS X init script check for missing argument, so we don't
13330 confuse users who invoke it incorrectly.
13331 - Fix a seg fault in "tor --hash-password foo".
13332 - Fix a possible way to DoS dirservers.
13333 - When we complain that your exit policy implicitly allows local or
13334 private address spaces, name them explicitly so operators can
13336 - Make the log message less scary when all the dirservers are
13337 temporarily unreachable.
13338 - We were printing the number of idle dns workers incorrectly when
13342 - Revised controller protocol (version 1) that uses ascii rather
13343 than binary. Add supporting libraries in python and java so you
13344 can use the controller from your applications without caring how
13345 our protocol works.
13346 - Spiffy new support for crypto hardware accelerators. Can somebody
13350 Changes in version 0.0.9.10 - 2005-06-16
13351 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13352 - Refuse relay cells that claim to have a length larger than the
13353 maximum allowed. This prevents a potential attack that could read
13354 arbitrary memory (e.g. keys) from an exit server's process
13358 Changes in version 0.1.0.10 - 2005-06-14
13359 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13360 libevent before 1.1a.
13363 Changes in version 0.1.0.9-rc - 2005-06-09
13365 - Reset buf->highwater every time buf_shrink() is called, not just on
13366 a successful shrink. This was causing significant memory bloat.
13367 - Fix buffer overflow when checking hashed passwords.
13368 - Security fix: if seeding the RNG on Win32 fails, quit.
13369 - Allow seeding the RNG on Win32 even when you're not running as
13371 - Disable threading on Solaris too. Something is wonky with it,
13372 cpuworkers, and reentrant libs.
13373 - Reenable the part of the code that tries to flush as soon as an
13374 OR outbuf has a full TLS record available. Perhaps this will make
13375 OR outbufs not grow as huge except in rare cases, thus saving lots
13376 of CPU time plus memory.
13377 - Reject malformed .onion addresses rather then passing them on as
13378 normal web requests.
13379 - Adapt patch from Adam Langley: fix possible memory leak in
13380 tor_lookup_hostname().
13381 - Initialize libevent later in the startup process, so the logs are
13382 already established by the time we start logging libevent warns.
13383 - Use correct errno on win32 if libevent fails.
13384 - Check and warn about known-bad/slow libevent versions.
13385 - Pay more attention to the ClientOnly config option.
13386 - Have torctl.in/tor.sh.in check for location of su binary (needed
13388 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13389 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13390 HttpProxyAuthenticator
13391 - Stop warning about sigpipes in the logs. We're going to
13392 pretend that getting these occassionally is normal and fine.
13393 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13395 installer screens; and don't put stuff into StartupItems unless
13396 the user asks you to.
13397 - Require servers that use the default dirservers to have public IP
13398 addresses. We have too many servers that are configured with private
13399 IPs and their admins never notice the log entries complaining that
13400 their descriptors are being rejected.
13401 - Add OSX uninstall instructions. An actual uninstall script will
13405 Changes in version 0.1.0.8-rc - 2005-05-23
13407 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13408 panics. Disable kqueue on all OS X Tors.
13409 - Fix RPM: remove duplicate line accidentally added to the rpm
13411 - Disable threads on openbsd too, since its gethostaddr is not
13413 - Tolerate libevent 0.8 since it still works, even though it's
13415 - Enable building on Red Hat 9.0 again.
13416 - Allow the middle hop of the testing circuit to be running any
13417 version, now that most of them have the bugfix to let them connect
13418 to unknown servers. This will allow reachability testing to work
13419 even when 0.0.9.7-0.0.9.9 become obsolete.
13420 - Handle relay cells with rh.length too large. This prevents
13421 a potential attack that could read arbitrary memory (maybe even
13422 keys) from the exit server's process.
13423 - We screwed up the dirport reachability testing when we don't yet
13424 have a cached version of the directory. Hopefully now fixed.
13425 - Clean up router_load_single_router() (used by the controller),
13426 so it doesn't seg fault on error.
13427 - Fix a minor memory leak when somebody establishes an introduction
13428 point at your Tor server.
13429 - If a socks connection ends because read fails, don't warn that
13430 you're not sending a socks reply back.
13433 - Add HttpProxyAuthenticator config option too, that works like
13434 the HttpsProxyAuthenticator config option.
13435 - Encode hashed controller passwords in hex instead of base64,
13436 to make it easier to write controllers.
13439 Changes in version 0.1.0.7-rc - 2005-05-17
13441 - Fix a bug in the OS X package installer that prevented it from
13442 installing on Tiger.
13443 - Fix a script bug in the OS X package installer that made it
13444 complain during installation.
13445 - Find libevent even if it's hiding in /usr/local/ and your
13446 CFLAGS and LDFLAGS don't tell you to look there.
13447 - Be able to link with libevent as a shared library (the default
13448 after 1.0d), even if it's hiding in /usr/local/lib and even
13449 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13450 assuming you're running gcc. Otherwise fail and give a useful
13452 - Fix a bug in the RPM packager: set home directory for _tor to
13453 something more reasonable when first installing.
13454 - Free a minor amount of memory that is still reachable on exit.
13457 Changes in version 0.1.0.6-rc - 2005-05-14
13459 - Implement --disable-threads configure option. Disable threads on
13460 netbsd by default, because it appears to have no reentrant resolver
13462 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13463 release (1.1) detects and disables kqueue if it's broken.
13464 - Append default exit policy before checking for implicit internal
13465 addresses. Now we don't log a bunch of complaints on startup
13466 when using the default exit policy.
13467 - Some people were putting "Address " in their torrc, and they had
13468 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13469 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13470 LOCALSTATEDIR/tor instead.
13471 - Fix fragmented-message bug in TorControl.py.
13472 - Resolve a minor bug which would prevent unreachable dirports
13473 from getting suppressed in the published descriptor.
13474 - When the controller gave us a new descriptor, we weren't resolving
13475 it immediately, so Tor would think its address was 0.0.0.0 until
13476 we fetched a new directory.
13477 - Fix an uppercase/lowercase case error in suppressing a bogus
13478 libevent warning on some Linuxes.
13481 - Begin scrubbing sensitive strings from logs by default. Turn off
13482 the config option SafeLogging if you need to do debugging.
13483 - Switch to a new buffer management algorithm, which tries to avoid
13484 reallocing and copying quite as much. In first tests it looks like
13485 it uses *more* memory on average, but less cpu.
13486 - First cut at support for "create-fast" cells. Clients can use
13487 these when extending to their first hop, since the TLS already
13488 provides forward secrecy and authentication. Not enabled on
13490 - When dirservers refuse a router descriptor, we now log its
13491 contactinfo, platform, and the poster's IP address.
13492 - Call tor_free_all instead of connections_free_all after forking, to
13493 save memory on systems that need to fork.
13494 - Whine at you if you're a server and you don't set your contactinfo.
13495 - Implement --verify-config command-line option to check if your torrc
13496 is valid without actually launching Tor.
13497 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13498 rather than just rejecting it.
13501 Changes in version 0.1.0.5-rc - 2005-04-27
13503 - Stop trying to print a null pointer if an OR conn fails because
13504 we didn't like its cert.
13506 - Switch our internal buffers implementation to use a ring buffer,
13507 to hopefully improve performance for fast servers a lot.
13508 - Add HttpsProxyAuthenticator support (basic auth only), based
13509 on patch from Adam Langley.
13510 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13511 the fast servers that have been joining lately.
13512 - Give hidden service accesses extra time on the first attempt,
13513 since 60 seconds is often only barely enough. This might improve
13515 - Improve performance for dirservers: stop re-parsing the whole
13516 directory every time you regenerate it.
13517 - Add more debugging info to help us find the weird dns freebsd
13518 pthreads bug; cleaner debug messages to help track future issues.
13521 Changes in version 0.0.9.9 - 2005-04-23
13522 o Bugfixes on 0.0.9.x:
13523 - If unofficial Tor clients connect and send weird TLS certs, our
13524 Tor server triggers an assert. This release contains a minimal
13525 backport from the broader fix that we put into 0.1.0.4-rc.
13528 Changes in version 0.1.0.4-rc - 2005-04-23
13530 - If unofficial Tor clients connect and send weird TLS certs, our
13531 Tor server triggers an assert. Stop asserting, and start handling
13532 TLS errors better in other situations too.
13533 - When the controller asks us to tell it about all the debug-level
13534 logs, it turns out we were generating debug-level logs while
13535 telling it about them, which turns into a bad loop. Now keep
13536 track of whether you're sending a debug log to the controller,
13537 and don't log when you are.
13538 - Fix the "postdescriptor" feature of the controller interface: on
13539 non-complete success, only say "done" once.
13541 - Clients are now willing to load balance over up to 2mB, not 1mB,
13542 of advertised bandwidth capacity.
13543 - Add a NoPublish config option, so you can be a server (e.g. for
13544 testing running Tor servers in other Tor networks) without
13545 publishing your descriptor to the primary dirservers.
13548 Changes in version 0.1.0.3-rc - 2005-04-08
13549 o Improvements on 0.1.0.2-rc:
13550 - Client now retries when streams end early for 'hibernating' or
13551 'resource limit' reasons, rather than failing them.
13552 - More automated handling for dirserver operators:
13553 - Automatically approve nodes running 0.1.0.2-rc or later,
13554 now that the the reachability detection stuff is working.
13555 - Now we allow two unverified servers with the same nickname
13556 but different keys. But if a nickname is verified, only that
13557 nickname+key are allowed.
13558 - If you're an authdirserver connecting to an address:port,
13559 and it's not the OR you were expecting, forget about that
13560 descriptor. If he *was* the one you were expecting, then forget
13561 about all other descriptors for that address:port.
13562 - Allow servers to publish descriptors from 12 hours in the future.
13563 Corollary: only whine about clock skew from the dirserver if
13564 he's a trusted dirserver (since now even verified servers could
13565 have quite wrong clocks).
13566 - Adjust maximum skew and age for rendezvous descriptors: let skew
13567 be 48 hours rather than 90 minutes.
13568 - Efficiency improvements:
13569 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13570 it much faster to look up a circuit for each relay cell.
13571 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13572 since they're eating our cpu on exit nodes.
13573 - Stop wasting time doing a case insensitive comparison for every
13574 dns name every time we do any lookup. Canonicalize the names to
13575 lowercase and be done with it.
13576 - Start sending 'truncated' cells back rather than destroy cells,
13577 if the circuit closes in front of you. This means we won't have
13578 to abandon partially built circuits.
13579 - Only warn once per nickname from add_nickname_list_to_smartlist
13580 per failure, so an entrynode or exitnode choice that's down won't
13582 - Put a note in the torrc about abuse potential with the default
13584 - Revise control spec and implementation to allow all log messages to
13585 be sent to controller with their severities intact (suggested by
13586 Matt Edman). Update TorControl to handle new log event types.
13587 - Provide better explanation messages when controller's POSTDESCRIPTOR
13589 - Stop putting nodename in the Platform string in server descriptors.
13590 It doesn't actually help, and it is confusing/upsetting some people.
13592 o Bugfixes on 0.1.0.2-rc:
13593 - We were printing the host mask wrong in exit policies in server
13594 descriptors. This isn't a critical bug though, since we were still
13595 obeying the exit policy internally.
13596 - Fix Tor when compiled with libevent but without pthreads: move
13597 connection_unregister() from _connection_free() to
13599 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13600 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13601 when we look through the connection array, we'll find any of the
13602 cpu/dnsworkers. This is no good.
13604 o Bugfixes on 0.0.9.8:
13605 - Fix possible bug on threading platforms (e.g. win32) which was
13606 leaking a file descriptor whenever a cpuworker or dnsworker died.
13607 - When using preferred entry or exit nodes, ignore whether the
13608 circuit wants uptime or capacity. They asked for the nodes, they
13610 - chdir() to your datadirectory at the *end* of the daemonize process,
13611 not the beginning. This was a problem because the first time you
13612 run tor, if your datadir isn't there, and you have runasdaemon set
13613 to 1, it will try to chdir to it before it tries to create it. Oops.
13614 - Handle changed router status correctly when dirserver reloads
13615 fingerprint file. We used to be dropping all unverified descriptors
13616 right then. The bug was hidden because we would immediately
13617 fetch a directory from another dirserver, which would include the
13618 descriptors we just dropped.
13619 - When we're connecting to an OR and he's got a different nickname/key
13620 than we were expecting, only complain loudly if we're an OP or a
13621 dirserver. Complaining loudly to the OR admins just confuses them.
13622 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13623 artificially capped at 500kB.
13626 Changes in version 0.0.9.8 - 2005-04-07
13627 o Bugfixes on 0.0.9.x:
13628 - We have a bug that I haven't found yet. Sometimes, very rarely,
13629 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13630 thinks of itself as idle. This meant that no new circuits ever got
13631 established. Here's a workaround to kill any cpuworker that's been
13632 busy for more than 100 seconds.
13635 Changes in version 0.1.0.2-rc - 2005-04-01
13636 o Bugfixes on 0.1.0.1-rc:
13637 - Fixes on reachability detection:
13638 - Don't check for reachability while hibernating.
13639 - If ORPort is reachable but DirPort isn't, still publish the
13640 descriptor, but zero out DirPort until it's found reachable.
13641 - When building testing circs for ORPort testing, use only
13642 high-bandwidth nodes, so fewer circuits fail.
13643 - Complain about unreachable ORPort separately from unreachable
13644 DirPort, so the user knows what's going on.
13645 - Make sure we only conclude ORPort reachability if we didn't
13646 initiate the conn. Otherwise we could falsely conclude that
13647 we're reachable just because we connected to the guy earlier
13648 and he used that same pipe to extend to us.
13649 - Authdirservers shouldn't do ORPort reachability detection,
13650 since they're in clique mode, so it will be rare to find a
13651 server not already connected to them.
13652 - When building testing circuits, always pick middle hops running
13653 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13654 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13656 - When we decide we're reachable, actually publish our descriptor
13658 - Fix bug in redirectstream in the controller.
13659 - Fix the state descriptor strings so logs don't claim edge streams
13660 are in a different state than they actually are.
13661 - Use recent libevent features when possible (this only really affects
13662 win32 and osx right now, because the new libevent with these
13663 features hasn't been released yet). Add code to suppress spurious
13665 - Prevent possible segfault in connection_close_unattached_ap().
13666 - Fix newlines on torrc in win32.
13667 - Improve error msgs when tor-resolve fails.
13669 o Improvements on 0.0.9.x:
13670 - New experimental script tor/contrib/ExerciseServer.py (needs more
13671 work) that uses the controller interface to build circuits and
13672 fetch pages over them. This will help us bootstrap servers that
13673 have lots of capacity but haven't noticed it yet.
13674 - New experimental script tor/contrib/PathDemo.py (needs more work)
13675 that uses the controller interface to let you choose whole paths
13677 "<hostname>.<path,separated by dots>.<length of path>.path"
13678 - When we've connected to an OR and handshaked but didn't like
13679 the result, we were closing the conn without sending destroy
13680 cells back for pending circuits. Now send those destroys.
13683 Changes in version 0.0.9.7 - 2005-04-01
13684 o Bugfixes on 0.0.9.x:
13685 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13686 - Compare identity to identity, not to nickname, when extending to
13687 a router not already in the directory. This was preventing us from
13688 extending to unknown routers. Oops.
13689 - Make sure to create OS X Tor user in <500 range, so we aren't
13690 creating actual system users.
13691 - Note where connection-that-hasn't-sent-end was marked, and fix
13692 a few really loud instances of this harmless bug (it's fixed more
13696 Changes in version 0.1.0.1-rc - 2005-03-28
13698 - Add reachability testing. Your Tor server will automatically try
13699 to see if its ORPort and DirPort are reachable from the outside,
13700 and it won't upload its descriptor until it decides they are.
13701 - Handle unavailable hidden services better. Handle slow or busy
13702 hidden services better.
13703 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13705 - New exit policy: accept most low-numbered ports, rather than
13706 rejecting most low-numbered ports.
13707 - More Tor controller support (still experimental). See
13708 http://tor.eff.org/doc/control-spec.txt for all the new features,
13709 including signals to emulate unix signals from any platform;
13710 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13711 closestream; closecircuit; etc.
13712 - Make nt services work and start on startup on win32 (based on
13713 patch by Matt Edman).
13714 - Add a new AddressMap config directive to rewrite incoming socks
13715 addresses. This lets you, for example, declare an implicit
13716 required exit node for certain sites.
13717 - Add a new TrackHostExits config directive to trigger addressmaps
13718 for certain incoming socks addresses -- for sites that break when
13719 your exit keeps changing (based on patch by Mike Perry).
13720 - Redo the client-side dns cache so it's just an addressmap too.
13721 - Notice when our IP changes, and reset stats/uptime/reachability.
13722 - When an application is using socks5, give him the whole variety of
13723 potential socks5 responses (connect refused, host unreachable, etc),
13724 rather than just "success" or "failure".
13725 - A more sane version numbering system. See
13726 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13727 - New contributed script "exitlist": a simple python script to
13728 parse directories and find Tor nodes that exit to listed
13730 - New contributed script "privoxy-tor-toggle" to toggle whether
13731 Privoxy uses Tor. Seems to be configured for Debian by default.
13732 - Report HTTP reasons to client when getting a response from directory
13733 servers -- so you can actually know what went wrong.
13734 - New config option MaxAdvertisedBandwidth which lets you advertise
13735 a low bandwidthrate (to not attract as many circuits) while still
13736 allowing a higher bandwidthrate in reality.
13738 o Robustness/stability fixes:
13739 - Make Tor use Niels Provos's libevent instead of its current
13740 poll-but-sometimes-select mess. This will let us use faster async
13741 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
13743 - pthread support now too. This was forced because when we forked,
13744 we ended up wasting a lot of duplicate ram over time. Also switch
13745 to foo_r versions of some library calls to allow reentry and
13747 - Better handling for heterogeneous / unreliable nodes:
13748 - Annotate circuits w/ whether they aim to contain high uptime nodes
13749 and/or high capacity nodes. When building circuits, choose
13751 - This means that every single node in an intro rend circuit,
13752 not just the last one, will have a minimum uptime.
13753 - New config option LongLivedPorts to indicate application streams
13754 that will want high uptime circuits.
13755 - Servers reset uptime when a dir fetch entirely fails. This
13756 hopefully reflects stability of the server's network connectivity.
13757 - If somebody starts his tor server in Jan 2004 and then fixes his
13758 clock, don't make his published uptime be a year.
13759 - Reset published uptime when you wake up from hibernation.
13760 - Introduce a notion of 'internal' circs, which are chosen without
13761 regard to the exit policy of the last hop. Intro and rendezvous
13762 circs must be internal circs, to avoid leaking information. Resolve
13763 and connect streams can use internal circs if they want.
13764 - New circuit pooling algorithm: make sure to have enough circs around
13765 to satisfy any predicted ports, and also make sure to have 2 internal
13766 circs around if we've required internal circs lately (and with high
13767 uptime if we've seen that lately too).
13768 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13769 which describes how often we retry making new circuits if current
13770 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13771 how long we're willing to make use of an already-dirty circuit.
13772 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13773 circ as necessary, if there are any completed ones lying around
13774 when we try to launch one.
13775 - Make hidden services try to establish a rendezvous for 30 seconds,
13776 rather than for n (where n=3) attempts to build a circuit.
13777 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
13778 "ShutdownWaitLength".
13779 - Try to be more zealous about calling connection_edge_end when
13780 things go bad with edge conns in connection.c.
13781 - Revise tor-spec to add more/better stream end reasons.
13782 - Revise all calls to connection_edge_end to avoid sending "misc",
13783 and to take errno into account where possible.
13786 - Fix a race condition that can trigger an assert, when we have a
13787 pending create cell and an OR connection fails right then.
13788 - Fix several double-mark-for-close bugs, e.g. where we were finding
13789 a conn for a cell even if that conn is already marked for close.
13790 - Make sequence of log messages when starting on win32 with no config
13791 file more reasonable.
13792 - When choosing an exit node for a new non-internal circ, don't take
13793 into account whether it'll be useful for any pending x.onion
13794 addresses -- it won't.
13795 - Turn addr_policy_compare from a tristate to a quadstate; this should
13796 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13797 for google.com" problem.
13798 - Make "platform" string in descriptor more accurate for Win32 servers,
13799 so it's not just "unknown platform".
13800 - Fix an edge case in parsing config options (thanks weasel).
13801 If they say "--" on the commandline, it's not an option.
13802 - Reject odd-looking addresses at the client (e.g. addresses that
13803 contain a colon), rather than having the server drop them because
13805 - tor-resolve requests were ignoring .exit if there was a working circuit
13806 they could use instead.
13807 - REUSEADDR on normal platforms means you can rebind to the port
13808 right after somebody else has let it go. But REUSEADDR on win32
13809 means to let you bind to the port _even when somebody else
13810 already has it bound_! So, don't do that on Win32.
13811 - Change version parsing logic: a version is "obsolete" if it is not
13812 recommended and (1) there is a newer recommended version in the
13813 same series, or (2) there are no recommended versions in the same
13814 series, but there are some recommended versions in a newer series.
13815 A version is "new" if it is newer than any recommended version in
13817 - Stop most cases of hanging up on a socks connection without sending
13821 - Require BandwidthRate to be at least 20kB/s for servers.
13822 - When a dirserver causes you to give a warn, mention which dirserver
13824 - New config option DirAllowPrivateAddresses for authdirservers.
13825 Now by default they refuse router descriptors that have non-IP or
13826 private-IP addresses.
13827 - Stop publishing socksport in the directory, since it's not
13828 actually meant to be public. For compatibility, publish a 0 there
13830 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13831 smart" value, that is low for servers and high for clients.
13832 - If our clock jumps forward by 100 seconds or more, assume something
13833 has gone wrong with our network and abandon all not-yet-used circs.
13834 - Warn when exit policy implicitly allows local addresses.
13835 - If we get an incredibly skewed timestamp from a dirserver mirror
13836 that isn't a verified OR, don't warn -- it's probably him that's
13838 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13839 cookies to disk and doesn't log each web request to disk. (Thanks
13840 to Brett Carrington for pointing this out.)
13841 - When a client asks us for a dir mirror and we don't have one,
13842 launch an attempt to get a fresh one.
13843 - If we're hibernating and we get a SIGINT, exit immediately.
13844 - Add --with-dmalloc ./configure option, to track memory leaks.
13845 - And try to free all memory on closing, so we can detect what
13847 - Cache local dns resolves correctly even when they're .exit
13849 - Give a better warning when some other server advertises an
13850 ORPort that is actually an apache running ssl.
13851 - Add "opt hibernating 1" to server descriptor to make it clearer
13852 whether the server is hibernating.
13855 Changes in version 0.0.9.6 - 2005-03-24
13856 o Bugfixes on 0.0.9.x (crashes and asserts):
13857 - Add new end stream reasons to maintainance branch. Fix bug where
13858 reason (8) could trigger an assert. Prevent bug from recurring.
13859 - Apparently win32 stat wants paths to not end with a slash.
13860 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13861 blowing away the circuit that conn->cpath_layer points to, then
13862 checking to see if the circ is well-formed. Backport check to make
13863 sure we dont use the cpath on a closed connection.
13864 - Prevent circuit_resume_edge_reading_helper() from trying to package
13865 inbufs for marked-for-close streams.
13866 - Don't crash on hup if your options->address has become unresolvable.
13867 - Some systems (like OS X) sometimes accept() a connection and tell
13868 you the remote host is 0.0.0.0:0. If this happens, due to some
13869 other mis-features, we get confused; so refuse the conn for now.
13871 o Bugfixes on 0.0.9.x (other):
13872 - Fix harmless but scary "Unrecognized content encoding" warn message.
13873 - Add new stream error reason: TORPROTOCOL reason means "you are not
13874 speaking a version of Tor I understand; say bye-bye to your stream."
13875 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
13876 into the future, now that we are more tolerant of skew. This
13877 resolves a bug where a Tor server would refuse to cache a directory
13878 because all the directories it gets are too far in the future;
13879 yet the Tor server never logs any complaints about clock skew.
13880 - Mac packaging magic: make man pages useable, and do not overwrite
13881 existing torrc files.
13882 - Make OS X log happily to /var/log/tor/tor.log
13885 Changes in version 0.0.9.5 - 2005-02-22
13886 o Bugfixes on 0.0.9.x:
13887 - Fix an assert race at exit nodes when resolve requests fail.
13888 - Stop picking unverified dir mirrors--it only leads to misery.
13889 - Patch from Matt Edman to make NT services work better. Service
13890 support is still not compiled into the executable by default.
13891 - Patch from Dmitri Bely so the Tor service runs better under
13892 the win32 SYSTEM account.
13893 - Make tor-resolve actually work (?) on Win32.
13894 - Fix a sign bug when getrlimit claims to have 4+ billion
13895 file descriptors available.
13896 - Stop refusing to start when bandwidthburst == bandwidthrate.
13897 - When create cells have been on the onion queue more than five
13898 seconds, just send back a destroy and take them off the list.
13901 Changes in version 0.0.9.4 - 2005-02-03
13902 o Bugfixes on 0.0.9:
13903 - Fix an assert bug that took down most of our servers: when
13904 a server claims to have 1 GB of bandwidthburst, don't
13906 - Don't crash as badly if we have spawned the max allowed number
13907 of dnsworkers, or we're out of file descriptors.
13908 - Block more file-sharing ports in the default exit policy.
13909 - MaxConn is now automatically set to the hard limit of max
13910 file descriptors we're allowed (ulimit -n), minus a few for
13912 - Give a clearer message when servers need to raise their
13913 ulimit -n when they start running out of file descriptors.
13914 - SGI Compatibility patches from Jan Schaumann.
13915 - Tolerate a corrupt cached directory better.
13916 - When a dirserver hasn't approved your server, list which one.
13917 - Go into soft hibernation after 95% of the bandwidth is used,
13918 not 99%. This is especially important for daily hibernators who
13919 have a small accounting max. Hopefully it will result in fewer
13920 cut connections when the hard hibernation starts.
13921 - Load-balance better when using servers that claim more than
13922 800kB/s of capacity.
13923 - Make NT services work (experimental, only used if compiled in).
13926 Changes in version 0.0.9.3 - 2005-01-21
13927 o Bugfixes on 0.0.9:
13928 - Backport the cpu use fixes from main branch, so busy servers won't
13929 need as much processor time.
13930 - Work better when we go offline and then come back, or when we
13931 run Tor at boot before the network is up. We do this by
13932 optimistically trying to fetch a new directory whenever an
13933 application request comes in and we think we're offline -- the
13934 human is hopefully a good measure of when the network is back.
13935 - Backport some minimal hidserv bugfixes: keep rend circuits open as
13936 long as you keep using them; actually publish hidserv descriptors
13937 shortly after they change, rather than waiting 20-40 minutes.
13938 - Enable Mac startup script by default.
13939 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
13940 - When you update AllowUnverifiedNodes or FirewallPorts via the
13941 controller's setconf feature, we were always appending, never
13943 - When you update HiddenServiceDir via setconf, it was screwing up
13944 the order of reading the lines, making it fail.
13945 - Do not rewrite a cached directory back to the cache; otherwise we
13946 will think it is recent and not fetch a newer one on startup.
13947 - Workaround for webservers that lie about Content-Encoding: Tor
13948 now tries to autodetect compressed directories and compression
13949 itself. This lets us Proxypass dir fetches through apache.
13952 Changes in version 0.0.9.2 - 2005-01-04
13953 o Bugfixes on 0.0.9 (crashes and asserts):
13954 - Fix an assert on startup when the disk is full and you're logging
13956 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
13957 style address, then we'd crash.
13958 - Fix an assert trigger when the running-routers string we get from
13959 a dirserver is broken.
13960 - Make worker threads start and run on win32. Now win32 servers
13962 - Bandaid (not actually fix, but now it doesn't crash) an assert
13963 where the dns worker dies mysteriously and the main Tor process
13964 doesn't remember anything about the address it was resolving.
13966 o Bugfixes on 0.0.9 (Win32):
13967 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
13968 name out of the warning/assert messages.
13969 - Fix a superficial "unhandled error on read" bug on win32.
13970 - The win32 installer no longer requires a click-through for our
13971 license, since our Free Software license grants rights but does not
13973 - Win32: When connecting to a dirserver fails, try another one
13974 immediately. (This was already working for non-win32 Tors.)
13975 - Stop trying to parse $HOME on win32 when hunting for default
13977 - Make tor-resolve.c work on win32 by calling network_init().
13979 o Bugfixes on 0.0.9 (other):
13980 - Make 0.0.9.x build on Solaris again.
13981 - Due to a fencepost error, we were blowing away the \n when reporting
13982 confvalue items in the controller. So asking for multiple config
13983 values at once couldn't work.
13984 - When listing circuits that are pending on an opening OR connection,
13985 if we're an OR we were listing circuits that *end* at us as
13986 being pending on every listener, dns/cpu worker, etc. Stop that.
13987 - Dirservers were failing to create 'running-routers' or 'directory'
13988 strings if we had more than some threshold of routers. Fix them so
13989 they can handle any number of routers.
13990 - Fix a superficial "Duplicate mark for close" bug.
13991 - Stop checking for clock skew for OR connections, even for servers.
13992 - Fix a fencepost error that was chopping off the last letter of any
13993 nickname that is the maximum allowed nickname length.
13994 - Update URLs in log messages so they point to the new website.
13995 - Fix a potential problem in mangling server private keys while
13996 writing to disk (not triggered yet, as far as we know).
13997 - Include the licenses for other free software we include in Tor,
13998 now that we're shipping binary distributions more regularly.
14001 Changes in version 0.0.9.1 - 2004-12-15
14002 o Bugfixes on 0.0.9:
14003 - Make hibernation actually work.
14004 - Make HashedControlPassword config option work.
14005 - When we're reporting event circuit status to a controller,
14006 don't use the stream status code.
14009 Changes in version 0.0.9 - 2004-12-12
14011 - Clean up manpage and torrc.sample file.
14012 - Clean up severities and text of log warnings.
14014 - Make servers trigger an assert when they enter hibernation.
14017 Changes in version 0.0.9rc7 - 2004-12-08
14018 o Bugfixes on 0.0.9rc:
14019 - Fix a stack-trashing crash when an exit node begins hibernating.
14020 - Avoid looking at unallocated memory while considering which
14021 ports we need to build circuits to cover.
14022 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14023 we shouldn't hold-open-until-flush if the eof arrived first.
14024 - Fix a bug with init_cookie_authentication() in the controller.
14025 - When recommending new-format log lines, if the upper bound is
14026 LOG_ERR, leave it implicit.
14028 o Bugfixes on 0.0.8.1:
14029 - Fix a whole slew of memory leaks.
14030 - Fix isspace() and friends so they still make Solaris happy
14031 but also so they don't trigger asserts on win32.
14032 - Fix parse_iso_time on platforms without strptime (eg win32).
14033 - win32: tolerate extra "readable" events better.
14034 - win32: when being multithreaded, leave parent fdarray open.
14035 - Make unit tests work on win32.
14038 Changes in version 0.0.9rc6 - 2004-12-06
14039 o Bugfixes on 0.0.9pre:
14040 - Clean up some more integer underflow opportunities (not exploitable
14042 - While hibernating, hup should not regrow our listeners.
14043 - Send an end to the streams we close when we hibernate, rather
14044 than just chopping them off.
14045 - React to eof immediately on non-open edge connections.
14047 o Bugfixes on 0.0.8.1:
14048 - Calculate timeout for waiting for a connected cell from the time
14049 we sent the begin cell, not from the time the stream started. If
14050 it took a long time to establish the circuit, we would time out
14051 right after sending the begin cell.
14052 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14053 of * as always matching, so we were picking reject *:* nodes as
14054 exit nodes too. Oops.
14057 - New circuit building strategy: keep a list of ports that we've
14058 used in the past 6 hours, and always try to have 2 circuits open
14059 or on the way that will handle each such port. Seed us with port
14060 80 so web users won't complain that Tor is "slow to start up".
14061 - Make kill -USR1 dump more useful stats about circuits.
14062 - When warning about retrying or giving up, print the address, so
14063 the user knows which one it's talking about.
14064 - If you haven't used a clean circuit in an hour, throw it away,
14065 just to be on the safe side. (This means after 6 hours a totally
14066 unused Tor client will have no circuits open.)
14069 Changes in version 0.0.9rc5 - 2004-12-01
14070 o Bugfixes on 0.0.8.1:
14071 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14072 - Let resolve conns retry/expire also, rather than sticking around
14074 - If we are using select, make sure we stay within FD_SETSIZE.
14076 o Bugfixes on 0.0.9pre:
14077 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14078 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14080 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14081 instead. Impose minima and maxima for all *Period options; impose
14082 even tighter maxima for fetching if we are a caching dirserver.
14083 Clip rather than rejecting.
14084 - Fetch cached running-routers from servers that serve it (that is,
14085 authdirservers and servers running 0.0.9rc5-cvs or later.)
14088 - Accept *:706 (silc) in default exit policy.
14089 - Implement new versioning format for post 0.1.
14090 - Support "foo.nickname.exit" addresses, to let Alice request the
14091 address "foo" as viewed by exit node "nickname". Based on a patch
14093 - Make tor --version --version dump the cvs Id of every file.
14096 Changes in version 0.0.9rc4 - 2004-11-28
14097 o Bugfixes on 0.0.8.1:
14098 - Make windows sockets actually non-blocking (oops), and handle
14099 win32 socket errors better.
14101 o Bugfixes on 0.0.9rc1:
14102 - Actually catch the -USR2 signal.
14105 Changes in version 0.0.9rc3 - 2004-11-25
14106 o Bugfixes on 0.0.8.1:
14107 - Flush the log file descriptor after we print "Tor opening log file",
14108 so we don't see those messages days later.
14110 o Bugfixes on 0.0.9rc1:
14111 - Make tor-resolve work again.
14112 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14113 - Fix an assert trigger for clients/servers handling resolves.
14116 Changes in version 0.0.9rc2 - 2004-11-24
14117 o Bugfixes on 0.0.9rc1:
14118 - I broke socks5 support while fixing the eof bug.
14119 - Allow unitless bandwidths and intervals; they default to bytes
14121 - New servers don't start out hibernating; they are active until
14122 they run out of bytes, so they have a better estimate of how
14123 long it takes, and so their operators can know they're working.
14126 Changes in version 0.0.9rc1 - 2004-11-23
14127 o Bugfixes on 0.0.8.1:
14128 - Finally fix a bug that's been plaguing us for a year:
14129 With high load, circuit package window was reaching 0. Whenever
14130 we got a circuit-level sendme, we were reading a lot on each
14131 socket, but only writing out a bit. So we would eventually reach
14132 eof. This would be noticed and acted on even when there were still
14133 bytes sitting in the inbuf.
14134 - When poll() is interrupted, we shouldn't believe the revents values.
14136 o Bugfixes on 0.0.9pre6:
14137 - Fix hibernate bug that caused pre6 to be broken.
14138 - Don't keep rephist info for routers that haven't had activity for
14139 24 hours. (This matters now that clients have keys, since we track
14141 - Never call close_temp_logs while validating log options.
14142 - Fix backslash-escaping on tor.sh.in and torctl.in.
14145 - Implement weekly/monthly/daily accounting: now you specify your
14146 hibernation properties by
14147 AccountingMax N bytes|KB|MB|GB|TB
14148 AccountingStart day|week|month [day] HH:MM
14149 Defaults to "month 1 0:00".
14150 - Let bandwidth and interval config options be specified as 5 bytes,
14151 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14152 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14153 get back to normal.)
14154 - If your requested entry or exit node has advertised bandwidth 0,
14156 - Be more greedy about filling up relay cells -- we try reading again
14157 once we've processed the stuff we read, in case enough has arrived
14158 to fill the last cell completely.
14159 - Apply NT service patch from Osamu Fujino. Still needs more work.
14162 Changes in version 0.0.9pre6 - 2004-11-15
14163 o Bugfixes on 0.0.8.1:
14164 - Fix assert failure on malformed socks4a requests.
14165 - Use identity comparison, not nickname comparison, to choose which
14166 half of circuit-ID-space each side gets to use. This is needed
14167 because sometimes we think of a router as a nickname, and sometimes
14168 as a hex ID, and we can't predict what the other side will do.
14169 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14170 write() call will fail and we handle it there.
14171 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14172 and smartlist_len, which are two major profiling offenders.
14174 o Bugfixes on 0.0.9pre5:
14175 - Fix a bug in read_all that was corrupting config files on windows.
14176 - When we're raising the max number of open file descriptors to
14177 'unlimited', don't log that we just raised it to '-1'.
14178 - Include event code with events, as required by control-spec.txt.
14179 - Don't give a fingerprint when clients do --list-fingerprint:
14180 it's misleading, because it will never be the same again.
14181 - Stop using strlcpy in tor_strndup, since it was slowing us
14183 - Remove warn on startup about missing cached-directory file.
14184 - Make kill -USR1 work again.
14185 - Hibernate if we start tor during the "wait for wakeup-time" phase
14186 of an accounting interval. Log our hibernation plans better.
14187 - Authoritative dirservers now also cache their directory, so they
14188 have it on start-up.
14191 - Fetch running-routers; cache running-routers; compress
14192 running-routers; serve compressed running-routers.z
14193 - Add NSI installer script contributed by J Doe.
14194 - Commit VC6 and VC7 workspace/project files.
14195 - Commit a tor.spec for making RPM files, with help from jbash.
14196 - Add contrib/torctl.in contributed by Glenn Fink.
14197 - Implement the control-spec's SAVECONF command, to write your
14198 configuration to torrc.
14199 - Get cookie authentication for the controller closer to working.
14200 - Include control-spec.txt in the tarball.
14201 - When set_conf changes our server descriptor, upload a new copy.
14202 But don't upload it too often if there are frequent changes.
14203 - Document authentication config in man page, and document signals
14205 - Clean up confusing parts of man page and torrc.sample.
14206 - Make expand_filename handle ~ and ~username.
14207 - Use autoconf to enable largefile support where necessary. Use
14208 ftello where available, since ftell can fail at 2GB.
14209 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14210 log more informatively.
14211 - Give a slightly more useful output for "tor -h".
14212 - Refuse application socks connections to port 0.
14213 - Check clock skew for verified servers, but allow unverified
14214 servers and clients to have any clock skew.
14215 - Break DirFetchPostPeriod into:
14216 - DirFetchPeriod for fetching full directory,
14217 - StatusFetchPeriod for fetching running-routers,
14218 - DirPostPeriod for posting server descriptor,
14219 - RendPostPeriod for posting hidden service descriptors.
14220 - Make sure the hidden service descriptors are at a random offset
14221 from each other, to hinder linkability.
14224 Changes in version 0.0.9pre5 - 2004-11-09
14225 o Bugfixes on 0.0.9pre4:
14226 - Fix a seg fault in unit tests (doesn't affect main program).
14227 - Fix an assert bug where a hidden service provider would fail if
14228 the first hop of his rendezvous circuit was down.
14229 - Hidden service operators now correctly handle version 1 style
14230 INTRODUCE1 cells (nobody generates them still, so not a critical
14232 - If do_hup fails, actually notice.
14233 - Handle more errnos from accept() without closing the listener.
14234 Some OpenBSD machines were closing their listeners because
14235 they ran out of file descriptors.
14236 - Send resolve cells to exit routers that are running a new
14237 enough version of the resolve code to work right.
14238 - Better handling of winsock includes on non-MSV win32 compilers.
14239 - Some people had wrapped their tor client/server in a script
14240 that would restart it whenever it died. This did not play well
14241 with our "shut down if your version is obsolete" code. Now people
14242 don't fetch a new directory if their local cached version is
14244 - Make our autogen.sh work on ksh as well as bash.
14247 - Hibernation: New config option "AccountingMaxKB" lets you
14248 set how many KBytes per month you want to allow your server to
14249 consume. Rather than spreading those bytes out evenly over the
14250 month, we instead hibernate for some of the month and pop up
14251 at a deterministic time, work until the bytes are consumed, then
14252 hibernate again. Config option "MonthlyAccountingStart" lets you
14253 specify which day of the month your billing cycle starts on.
14254 - Control interface: a separate program can now talk to your
14255 client/server over a socket, and get/set config options, receive
14256 notifications of circuits and streams starting/finishing/dying,
14257 bandwidth used, etc. The next step is to get some GUIs working.
14258 Let us know if you want to help out. See doc/control-spec.txt .
14259 - Ship a contrib/tor-control.py as an example script to interact
14260 with the control port.
14261 - "tor --hash-password zzyxz" will output a salted password for
14262 use in authenticating to the control interface.
14263 - New log format in config:
14264 "Log minsev[-maxsev] stdout|stderr|syslog" or
14265 "Log minsev[-maxsev] file /var/foo"
14268 - DirPolicy config option, to let people reject incoming addresses
14269 from their dirserver.
14270 - "tor --list-fingerprint" will list your identity key fingerprint
14272 - Add "pass" target for RedirectExit, to make it easier to break
14273 out of a sequence of RedirectExit rules.
14274 - Clients now generate a TLS cert too, in preparation for having
14275 them act more like real nodes.
14276 - Ship src/win32/ in the tarball, so people can use it to build.
14277 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14279 - New "router-status" line in directory, to better bind each verified
14280 nickname to its identity key.
14281 - Deprecate unofficial config option abbreviations, and abbreviations
14282 not on the command line.
14283 - Add a pure-C tor-resolve implementation.
14284 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14285 1024) file descriptors.
14287 o Code security improvements, inspired by Ilja:
14288 - Replace sprintf with snprintf. (I think they were all safe, but
14290 - Replace strcpy/strncpy with strlcpy in more places.
14291 - Avoid strcat; use snprintf or strlcat instead.
14292 - snprintf wrapper with consistent (though not C99) overflow behavior.
14295 Changes in version 0.0.9pre4 - 2004-10-17
14296 o Bugfixes on 0.0.9pre3:
14297 - If the server doesn't specify an exit policy, use the real default
14298 exit policy, not reject *:*.
14299 - Ignore fascistfirewall when uploading/downloading hidden service
14300 descriptors, since we go through Tor for those; and when using
14301 an HttpProxy, since we assume it can reach them all.
14302 - When looking for an authoritative dirserver, use only the ones
14303 configured at boot. Don't bother looking in the directory.
14304 - The rest of the fix for get_default_conf_file() on older win32.
14305 - Make 'Routerfile' config option obsolete.
14308 - New 'MyFamily nick1,...' config option for a server to
14309 specify other servers that shouldn't be used in the same circuit
14310 with it. Only believed if nick1 also specifies us.
14311 - New 'NodeFamily nick1,nick2,...' config option for a client to
14312 specify nodes that it doesn't want to use in the same circuit.
14313 - New 'Redirectexit pattern address:port' config option for a
14314 server to redirect exit connections, e.g. to a local squid.
14317 Changes in version 0.0.9pre3 - 2004-10-13
14318 o Bugfixes on 0.0.8.1:
14319 - Better torrc example lines for dirbindaddress and orbindaddress.
14320 - Improved bounds checking on parsed ints (e.g. config options and
14321 the ones we find in directories.)
14322 - Better handling of size_t vs int, so we're more robust on 64
14324 - Fix the rest of the bug where a newly started OR would appear
14325 as unverified even after we've added his fingerprint and hupped
14327 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14328 close it without sending back an end. So 'connection refused'
14329 would simply be ignored and the user would get no response.
14331 o Bugfixes on 0.0.9pre2:
14332 - Serving the cached-on-disk directory to people is bad. We now
14333 provide no directory until we've fetched a fresh one.
14334 - Workaround for bug on windows where cached-directories get crlf
14336 - Make get_default_conf_file() work on older windows too.
14337 - If we write a *:* exit policy line in the descriptor, don't write
14338 any more exit policy lines.
14341 - Use only 0.0.9pre1 and later servers for resolve cells.
14342 - Make the dirservers file obsolete.
14343 - Include a dir-signing-key token in directories to tell the
14344 parsing entity which key is being used to sign.
14345 - Remove the built-in bulky default dirservers string.
14346 - New config option "Dirserver %s:%d [fingerprint]", which can be
14347 repeated as many times as needed. If no dirservers specified,
14348 default to moria1,moria2,tor26.
14349 - Make moria2 advertise a dirport of 80, so people behind firewalls
14350 will be able to get a directory.
14351 - Http proxy support
14352 - Dirservers translate requests for http://%s:%d/x to /x
14353 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14354 be routed through this host.
14355 - Clients ask for /tor/x rather than /x for new enough dirservers.
14356 This way we can one day coexist peacefully with apache.
14357 - Clients specify a "Host: %s%d" http header, to be compatible
14358 with more proxies, and so running squid on an exit node can work.
14361 Changes in version 0.0.8.1 - 2004-10-13
14363 - Fix a seg fault that can be triggered remotely for Tor
14364 clients/servers with an open dirport.
14365 - Fix a rare assert trigger, where routerinfos for entries in
14366 our cpath would expire while we're building the path.
14367 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14368 - Fix a rare seg fault for people running hidden services on
14369 intermittent connections.
14370 - Fix a bug in parsing opt keywords with objects.
14371 - Fix a stale pointer assert bug when a stream detaches and
14373 - Fix a string format vulnerability (probably not exploitable)
14374 in reporting stats locally.
14375 - Fix an assert trigger: sometimes launching circuits can fail
14376 immediately, e.g. because too many circuits have failed recently.
14377 - Fix a compile warning on 64 bit platforms.
14380 Changes in version 0.0.9pre2 - 2004-10-03
14382 - Make fetching a cached directory work for 64-bit platforms too.
14383 - Make zlib.h a required header, not an optional header.
14386 Changes in version 0.0.9pre1 - 2004-10-01
14388 - Stop using separate defaults for no-config-file and
14389 empty-config-file. Now you have to explicitly turn off SocksPort,
14390 if you don't want it open.
14391 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14392 - Improve man page to mention more of the 0.0.8 features.
14393 - Fix a rare seg fault for people running hidden services on
14394 intermittent connections.
14395 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14397 - Fix more dns related bugs: send back resolve_failed and end cells
14398 more reliably when the resolve fails, rather than closing the
14399 circuit and then trying to send the cell. Also attach dummy resolve
14400 connections to a circuit *before* calling dns_resolve(), to fix
14401 a bug where cached answers would never be sent in RESOLVED cells.
14402 - When we run out of disk space, or other log writing error, don't
14403 crash. Just stop logging to that log and continue.
14404 - We were starting to daemonize before we opened our logs, so if
14405 there were any problems opening logs, we would complain to stderr,
14406 which wouldn't work, and then mysteriously exit.
14407 - Fix a rare bug where sometimes a verified OR would connect to us
14408 before he'd uploaded his descriptor, which would cause us to
14409 assign conn->nickname as though he's unverified. Now we look through
14410 the fingerprint list to see if he's there.
14411 - Fix a rare assert trigger, where routerinfos for entries in
14412 our cpath would expire while we're building the path.
14415 - Clients can ask dirservers for /dir.z to get a compressed version
14416 of the directory. Only works for servers running 0.0.9, of course.
14417 - Make clients cache directories and use them to seed their router
14418 lists at startup. This means clients have a datadir again.
14419 - Configuration infrastructure support for warning on obsolete
14421 - Respond to content-encoding headers by trying to uncompress as
14423 - Reply with a deflated directory when a client asks for "dir.z".
14424 We could use allow-encodings instead, but allow-encodings isn't
14425 specified in HTTP 1.0.
14426 - Raise the max dns workers from 50 to 100.
14427 - Discourage people from setting their dirfetchpostperiod more often
14428 than once per minute.
14429 - Protect dirservers from overzealous descriptor uploading -- wait
14430 10 seconds after directory gets dirty, before regenerating.
14433 Changes in version 0.0.8 - 2004-08-25
14434 o Port it to SunOS 5.9 / Athena
14437 Changes in version 0.0.8rc2 - 2004-08-20
14438 o Make it compile on cygwin again.
14439 o When picking unverified routers, skip those with low uptime and/or
14440 low bandwidth, depending on what properties you care about.
14443 Changes in version 0.0.8rc1 - 2004-08-18
14444 o Changes from 0.0.7.3:
14446 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14447 don't put it into the client dns cache.
14448 - If a begin failed due to exit policy, but we believe the IP address
14449 should have been allowed, switch that router to exitpolicy reject *:*
14450 until we get our next directory.
14452 - Clients choose nodes proportional to advertised bandwidth.
14453 - Avoid using nodes with low uptime as introduction points.
14454 - Handle servers with dynamic IP addresses: don't replace
14455 options->Address with the resolved one at startup, and
14456 detect our address right before we make a routerinfo each time.
14457 - 'FascistFirewall' option to pick dirservers and ORs on specific
14458 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14459 which ports are open. (Defaults to 80,443)
14460 - Be more aggressive about trying to make circuits when the network
14461 has changed (e.g. when you unsuspend your laptop).
14462 - Check for time skew on http headers; report date in response to
14464 - If the entrynode config line has only one node, don't pick it as
14466 - Add strict{entry|exit}nodes config options. If set to 1, then
14467 we refuse to build circuits that don't include the specified entry
14469 - OutboundBindAddress config option, to bind to a specific
14470 IP address for outgoing connect()s.
14471 - End truncated log entries (e.g. directories) with "[truncated]".
14473 o Patches to 0.0.8preX:
14475 - Patches to compile and run on win32 again (maybe)?
14476 - Fix crash when looking for ~/.torrc with no $HOME set.
14477 - Fix a race bug in the unit tests.
14478 - Handle verified/unverified name collisions better when new
14479 routerinfo's arrive in a directory.
14480 - Sometimes routers were getting entered into the stats before
14481 we'd assigned their identity_digest. Oops.
14482 - Only pick and establish intro points after we've gotten a
14485 - AllowUnverifiedNodes config option to let circuits choose no-name
14486 routers in entry,middle,exit,introduction,rendezvous positions.
14487 Allow middle and rendezvous positions by default.
14488 - Add a man page for tor-resolve.
14491 Changes in version 0.0.7.3 - 2004-08-12
14492 o Stop dnsworkers from triggering an assert failure when you
14493 ask them to resolve the host "".
14496 Changes in version 0.0.8pre3 - 2004-08-09
14497 o Changes from 0.0.7.2:
14498 - Allow multiple ORs with same nickname in routerlist -- now when
14499 people give us one identity key for a nickname, then later
14500 another, we don't constantly complain until the first expires.
14501 - Remember used bandwidth (both in and out), and publish 15-minute
14502 snapshots for the past day into our descriptor.
14503 - You can now fetch $DIRURL/running-routers to get just the
14504 running-routers line, not the whole descriptor list. (But
14505 clients don't use this yet.)
14506 - When people mistakenly use Tor as an http proxy, point them
14507 at the tor-doc.html rather than the INSTALL.
14508 - Remove our mostly unused -- and broken -- hex_encode()
14509 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14510 for pointing out this bug.)
14511 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14512 fewer problems with people using the wrong key.
14513 - Change the default exit policy to reject the default edonkey,
14514 kazaa, gnutella ports.
14515 - Add replace_file() to util.[ch] to handle win32's rename().
14517 o Changes from 0.0.8preX:
14518 - Fix two bugs in saving onion keys to disk when rotating, so
14519 hopefully we'll get fewer people using old onion keys.
14520 - Fix an assert error that was making SocksPolicy not work.
14521 - Be willing to expire routers that have an open dirport -- it's
14522 just the authoritative dirservers we want to not forget.
14523 - Reject tor-resolve requests for .onion addresses early, so we
14524 don't build a whole rendezvous circuit and then fail.
14525 - When you're warning a server that he's unverified, don't cry
14526 wolf unpredictably.
14527 - Fix a race condition: don't try to extend onto a connection
14528 that's still handshaking.
14529 - For servers in clique mode, require the conn to be open before
14530 you'll choose it for your path.
14531 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14532 end relay cell, etc.
14533 - Measure bandwidth capacity over the last 24 hours, not just 12
14534 - Bugfix: authoritative dirservers were making and signing a new
14535 directory for each client, rather than reusing the cached one.
14538 Changes in version 0.0.8pre2 - 2004-08-04
14539 o Changes from 0.0.7.2:
14541 - Check directory signature _before_ you decide whether you're
14542 you're running an obsolete version and should exit.
14543 - Check directory signature _before_ you parse the running-routers
14544 list to decide who's running or verified.
14545 - Bugfixes and features:
14546 - Check return value of fclose while writing to disk, so we don't
14547 end up with broken files when servers run out of disk space.
14548 - Log a warning if the user uses an unsafe socks variant, so people
14549 are more likely to learn about privoxy or socat.
14550 - Dirservers now include RFC1123-style dates in the HTTP headers,
14551 which one day we will use to better detect clock skew.
14553 o Changes from 0.0.8pre1:
14554 - Make it compile without warnings again on win32.
14555 - Log a warning if you're running an unverified server, to let you
14556 know you might want to get it verified.
14557 - Only pick a default nickname if you plan to be a server.
14560 Changes in version 0.0.8pre1 - 2004-07-23
14562 - Made our unit tests compile again on OpenBSD 3.5, and tor
14563 itself compile again on OpenBSD on a sparc64.
14564 - We were neglecting milliseconds when logging on win32, so
14565 everything appeared to happen at the beginning of each second.
14567 o Protocol changes:
14568 - 'Extend' relay cell payloads now include the digest of the
14569 intended next hop's identity key. Now we can verify that we're
14570 extending to the right router, and also extend to routers we
14571 hadn't heard of before.
14574 - Tor nodes can now act as relays (with an advertised ORPort)
14575 without being manually verified by the dirserver operators.
14576 - Uploaded descriptors of unverified routers are now accepted
14577 by the dirservers, and included in the directory.
14578 - Verified routers are listed by nickname in the running-routers
14579 list; unverified routers are listed as "$<fingerprint>".
14580 - We now use hash-of-identity-key in most places rather than
14581 nickname or addr:port, for improved security/flexibility.
14582 - To avoid Sybil attacks, paths still use only verified servers.
14583 But now we have a chance to play around with hybrid approaches.
14584 - Nodes track bandwidth usage to estimate capacity (not used yet).
14585 - ClientOnly option for nodes that never want to become servers.
14586 - Directory caching.
14587 - "AuthoritativeDir 1" option for the official dirservers.
14588 - Now other nodes (clients and servers) will cache the latest
14589 directory they've pulled down.
14590 - They can enable their DirPort to serve it to others.
14591 - Clients will pull down a directory from any node with an open
14592 DirPort, and check the signature/timestamp correctly.
14593 - Authoritative dirservers now fetch directories from other
14594 authdirservers, to stay better synced.
14595 - Running-routers list tells who's down also, along with noting
14596 if they're verified (listed by nickname) or unverified (listed
14598 - Allow dirservers to serve running-router list separately.
14599 This isn't used yet.
14600 - ORs connect-on-demand to other ORs
14601 - If you get an extend cell to an OR you're not connected to,
14602 connect, handshake, and forward the create cell.
14603 - The authoritative dirservers stay connected to everybody,
14604 and everybody stays connected to 0.0.7 servers, but otherwise
14605 clients/servers expire unused connections after 5 minutes.
14606 - When servers get a sigint, they delay 30 seconds (refusing new
14607 connections) then exit. A second sigint causes immediate exit.
14608 - File and name management:
14609 - Look for .torrc if no CONFDIR "torrc" is found.
14610 - If no datadir is defined, then choose, make, and secure ~/.tor
14612 - If torrc not found, exitpolicy reject *:*.
14613 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14614 - If no nickname is defined, derive default from hostname.
14615 - Rename secret key files, e.g. identity.key -> secret_id_key,
14616 to discourage people from mailing their identity key to tor-ops.
14617 - Refuse to build a circuit before the directory has arrived --
14618 it won't work anyway, since you won't know the right onion keys
14620 - Try other dirservers immediately if the one you try is down. This
14621 should tolerate down dirservers better now.
14622 - Parse tor version numbers so we can do an is-newer-than check
14623 rather than an is-in-the-list check.
14624 - New socks command 'resolve', to let us shim gethostbyname()
14626 - A 'tor_resolve' script to access the socks resolve functionality.
14627 - A new socks-extensions.txt doc file to describe our
14628 interpretation and extensions to the socks protocols.
14629 - Add a ContactInfo option, which gets published in descriptor.
14630 - Publish OR uptime in descriptor (and thus in directory) too.
14631 - Write tor version at the top of each log file
14632 - New docs in the tarball:
14634 - Document that you should proxy your SSL traffic too.
14637 Changes in version 0.0.7.2 - 2004-07-07
14638 o A better fix for the 0.0.0.0 problem, that will hopefully
14639 eliminate the remaining related assertion failures.
14642 Changes in version 0.0.7.1 - 2004-07-04
14643 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14644 since internally we use 0.0.0.0 to signify "not yet resolved".
14647 Changes in version 0.0.7 - 2004-06-07
14648 o Updated the man page to reflect the new features.
14651 Changes in version 0.0.7rc2 - 2004-06-06
14652 o Changes from 0.0.7rc1:
14653 - Make it build on Win32 again.
14654 o Changes from 0.0.6.2:
14655 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14659 Changes in version 0.0.7rc1 - 2004-06-02
14661 - On sighup, we were adding another log without removing the first
14662 one. So log messages would get duplicated n times for n sighups.
14663 - Several cases of using a connection after we'd freed it. The
14664 problem was that connections that are pending resolve are in both
14665 the pending_resolve tree, and also the circuit's resolving_streams
14666 list. When you want to remove one, you must remove it from both.
14667 - Fix a double-mark-for-close where an end cell arrived for a
14668 resolving stream, and then the resolve failed.
14669 - Check directory signatures based on name of signer, not on whom
14670 we got the directory from. This will let us cache directories more
14673 - Crank up some of our constants to handle more users.
14676 Changes in version 0.0.7pre1 - 2004-06-02
14677 o Fixes for crashes and other obnoxious bugs:
14678 - Fix an epipe bug: sometimes when directory connections failed
14679 to connect, we would give them a chance to flush before closing
14681 - When we detached from a circuit because of resolvefailed, we
14682 would immediately try the same circuit twice more, and then
14683 give up on the resolve thinking we'd tried three different
14685 - Limit the number of intro circuits we'll attempt to build for a
14686 hidden service per 15-minute period.
14687 - Check recommended-software string *early*, before actually parsing
14688 the directory. Thus we can detect an obsolete version and exit,
14689 even if the new directory format doesn't parse.
14690 o Fixes for security bugs:
14691 - Remember which nodes are dirservers when you startup, and if a
14692 random OR enables his dirport, don't automatically assume he's
14693 a trusted dirserver.
14695 - Directory connections were asking the wrong poll socket to
14696 start writing, and not asking themselves to start writing.
14697 - When we detached from a circuit because we sent a begin but
14698 didn't get a connected, we would use it again the first time;
14699 but after that we would correctly switch to a different one.
14700 - Stop warning when the first onion decrypt attempt fails; they
14701 will sometimes legitimately fail now that we rotate keys.
14702 - Override unaligned-access-ok check when $host_cpu is ia64 or
14703 arm. Apparently they allow it but the kernel whines.
14704 - Dirservers try to reconnect periodically too, in case connections
14706 - Fix some memory leaks in directory servers.
14707 - Allow backslash in Win32 filenames.
14708 - Made Tor build complain-free on FreeBSD, hopefully without
14709 breaking other BSD builds. We'll see.
14711 - Doxygen markup on all functions and global variables.
14712 - Make directory functions update routerlist, not replace it. So
14713 now directory disagreements are not so critical a problem.
14714 - Remove the upper limit on number of descriptors in a dirserver's
14715 directory (not that we were anywhere close).
14716 - Allow multiple logfiles at different severity ranges.
14717 - Allow *BindAddress to specify ":port" rather than setting *Port
14718 separately. Allow multiple instances of each BindAddress config
14719 option, so you can bind to multiple interfaces if you want.
14720 - Allow multiple exit policy lines, which are processed in order.
14721 Now we don't need that huge line with all the commas in it.
14722 - Enable accept/reject policies on SOCKS connections, so you can bind
14723 to 0.0.0.0 but still control who can use your OP.
14726 Changes in version 0.0.6.2 - 2004-05-16
14727 o Our integrity-checking digest was checking only the most recent cell,
14728 not the previous cells like we'd thought.
14729 Thanks to Stefan Mark for finding the flaw!
14732 Changes in version 0.0.6.1 - 2004-05-06
14733 o Fix two bugs in our AES counter-mode implementation (this affected
14734 onion-level stream encryption, but not TLS-level). It turns
14735 out we were doing something much more akin to a 16-character
14736 polyalphabetic cipher. Oops.
14737 Thanks to Stefan Mark for finding the flaw!
14738 o Retire moria3 as a directory server, and add tor26 as a directory
14742 Changes in version 0.0.6 - 2004-05-02
14743 [version bump only]
14746 Changes in version 0.0.6rc4 - 2004-05-01
14747 o Update the built-in dirservers list to use the new directory format
14748 o Fix a rare seg fault: if a node offering a hidden service attempts
14749 to build a circuit to Alice's rendezvous point and fails before it
14750 reaches the last hop, it retries with a different circuit, but
14752 o Handle windows socket errors correctly.
14755 Changes in version 0.0.6rc3 - 2004-04-28
14756 o Don't expire non-general excess circuits (if we had enough
14757 circuits open, we were expiring rendezvous circuits -- even
14758 when they had a stream attached. oops.)
14759 o Fetch randomness from /dev/urandom better (not via fopen/fread)
14760 o Better debugging for tls errors
14761 o Some versions of openssl have an SSL_pending function that erroneously
14762 returns bytes when there is a non-application record pending.
14763 o Set Content-Type on the directory and hidserv descriptor.
14764 o Remove IVs from cipher code, since AES-ctr has none.
14765 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14766 o We were using an array of length zero in a few places.
14767 o win32's gethostbyname can't resolve an IP to an IP.
14768 o win32's close can't close a socket.
14771 Changes in version 0.0.6rc2 - 2004-04-26
14772 o Fix a bug where we were closing tls connections intermittently.
14773 It turns out openssl keeps its errors around -- so if an error
14774 happens, and you don't ask about it, and then another openssl
14775 operation happens and succeeds, and you ask if there was an error,
14776 it tells you about the first error. Fun fun.
14777 o Fix a bug that's been lurking since 27 may 03 (!)
14778 When passing back a destroy cell, we would use the wrong circ id.
14779 'Mostly harmless', but still worth fixing.
14780 o Since we don't support truncateds much, don't bother sending them;
14781 just close the circ.
14782 o check for <machine/limits.h> so we build on NetBSD again (I hope).
14783 o don't crash if a conn that sent a begin has suddenly lost its circuit
14784 (this was quite rare).
14787 Changes in version 0.0.6rc1 - 2004-04-25
14788 o We now rotate link (tls context) keys and onion keys.
14789 o CREATE cells now include oaep padding, so you can tell
14790 if you decrypted them correctly.
14791 o Add bandwidthburst to server descriptor.
14792 o Directories now say which dirserver signed them.
14793 o Use a tor_assert macro that logs failed assertions too.
14796 Changes in version 0.0.6pre5 - 2004-04-18
14797 o changes from 0.0.6pre4:
14798 - make tor build on broken freebsd 5.2 installs
14799 - fix a failed assert when you try an intro point, get a nack, and try
14800 a second one and it works.
14801 - when alice uses a port that the hidden service doesn't accept,
14802 it now sends back an end cell (denied by exit policy). otherwise
14803 alice would just have to wait to time out.
14804 - fix another rare bug: when we had tried all the intro
14805 points for a hidden service, we fetched the descriptor
14806 again, but we left our introcirc thinking it had already
14807 sent an intro, so it kept waiting for a response...
14808 - bugfix: when you sleep your hidden-service laptop, as soon
14809 as it wakes up it tries to upload a service descriptor, but
14810 socketpair fails for some reason (localhost not up yet?).
14811 now we simply give up on that upload, and we'll try again later.
14812 i'd still like to find the bug though.
14813 - if an intro circ waiting for an ack dies before getting one, then
14815 - we were reusing stale service descriptors and refetching usable
14819 Changes in version 0.0.6pre4 - 2004-04-14
14820 o changes from 0.0.6pre3:
14821 - when bob fails to connect to the rendezvous point, and his
14822 circ didn't fail because of the rendezvous point itself, then
14823 he retries a couple of times
14824 - we expire introduction and rendezvous circs more thoroughly
14825 (sometimes they were hanging around forever)
14826 - we expire unattached rendezvous streams that have been around
14827 too long (they were sticking around forever).
14828 - fix a measly fencepost error that was crashing everybody with
14832 Changes in version 0.0.6pre3 - 2004-04-14
14833 o changes from 0.0.6pre2:
14834 - make hup work again
14835 - fix some memory leaks for dirservers
14836 - allow more skew in rendezvous descriptor timestamps, to help
14837 handle people like blanu who don't know what time it is
14838 - normal circs are 3 hops, but some rend/intro circs are 4, if
14839 the initiator doesn't get to choose the last hop
14840 - send acks for introductions, so alice can know whether to try
14842 - bob publishes intro points more correctly
14843 o changes from 0.0.5:
14844 - fix an assert trigger that's been plaguing us since the days
14845 of 0.0.2prexx (thanks weasel!)
14846 - retry stream correctly when we fail to connect because of
14847 exit-policy-reject (should try another) or can't-resolve-address
14848 (also should try another, because dns on random internet servers
14850 - when we hup a dirserver and we've *removed* a server from the
14851 approved-routers list, now we remove that server from the
14852 in-memory directories too
14855 Changes in version 0.0.6pre2 - 2004-04-08
14856 o We fixed our base32 implementation. Now it works on all architectures.
14859 Changes in version 0.0.6pre1 - 2004-04-08
14861 - Hidden services and rendezvous points are implemented. Go to
14862 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14863 hidden services. (This only works via a socks4a proxy such as
14864 Privoxy, and currently it's quite slow.)
14867 Changes in version 0.0.5 - 2004-03-30
14868 [version bump only]
14871 Changes in version 0.0.5rc3 - 2004-03-29
14872 o Install torrc as torrc.sample -- we no longer clobber your
14874 o Re-enable recommendedversion checking (we broke it in rc2, oops)
14875 o Add in a 'notice' log level for things the operator should hear
14876 but that aren't warnings
14879 Changes in version 0.0.5rc2 - 2004-03-29
14880 o Hold socks connection open until reply is flushed (if possible)
14881 o Make exit nodes resolve IPs to IPs immediately, rather than asking
14882 the dns farm to do it.
14883 o Fix c99 aliasing warnings in rephist.c
14884 o Don't include server descriptors that are older than 24 hours in the
14886 o Give socks 'reject' replies their whole 15s to attempt to flush,
14887 rather than seeing the 60s timeout and assuming the flush had failed.
14888 o Clean automake droppings from the cvs repository
14891 Changes in version 0.0.5rc1 - 2004-03-28
14892 o Fix mangled-state bug in directory fetching (was causing sigpipes).
14893 o Only build circuits after we've fetched the directory: clients were
14894 using only the directory servers before they'd fetched a directory.
14895 This also means longer startup time; so it goes.
14896 o Fix an assert trigger where an OP would fail to handshake, and we'd
14897 expect it to have a nickname.
14898 o Work around a tsocks bug: do a socks reject when AP connection dies
14899 early, else tsocks goes into an infinite loop.
14902 Changes in version 0.0.4 - 2004-03-26
14903 o When connecting to a dirserver or OR and the network is down,
14907 Changes in version 0.0.3 - 2004-03-26
14908 o Warn and fail if server chose a nickname with illegal characters
14909 o Port to Solaris and Sparc:
14910 - include missing header fcntl.h
14911 - have autoconf find -lsocket -lnsl automatically
14912 - deal with hardware word alignment
14913 - make uname() work (solaris has a different return convention)
14914 - switch from using signal() to sigaction()
14915 o Preliminary work on reputation system:
14916 - Keep statistics on success/fail of connect attempts; they're published
14917 by kill -USR1 currently.
14918 - Add a RunTesting option to try to learn link state by creating test
14919 circuits, even when SocksPort is off.
14920 - Remove unused open circuits when there are too many.
14923 Changes in version 0.0.2 - 2004-03-19
14924 - Include strlcpy and strlcat for safer string ops
14925 - define INADDR_NONE so we compile (but still not run) on solaris
14928 Changes in version 0.0.2pre27 - 2004-03-14
14930 - Allow internal tor networks (we were rejecting internal IPs,
14931 now we allow them if they're set explicitly).
14932 - And fix a few endian issues.
14935 Changes in version 0.0.2pre26 - 2004-03-14
14937 - If a stream times out after 15s without a connected cell, don't
14938 try that circuit again: try a new one.
14939 - Retry streams at most 4 times. Then give up.
14940 - When a dirserver gets a descriptor from an unknown router, it
14941 logs its fingerprint (so the dirserver operator can choose to
14942 accept it even without mail from the server operator).
14943 - Inform unapproved servers when we reject their descriptors.
14944 - Make tor build on Windows again. It works as a client, who knows
14946 - Clearer instructions in the torrc for how to set up a server.
14947 - Be more efficient about reading fd's when our global token bucket
14948 (used for rate limiting) becomes empty.
14950 - Stop asserting that computers always go forward in time. It's
14952 - When we sent a cell (e.g. destroy) and then marked an OR connection
14953 expired, we might close it before finishing a flush if the other
14954 side isn't reading right then.
14955 - Don't allow dirservers to start if they haven't defined
14956 RecommendedVersions
14957 - We were caching transient dns failures. Oops.
14958 - Prevent servers from publishing an internal IP as their address.
14959 - Address a strcat vulnerability in circuit.c
14962 Changes in version 0.0.2pre25 - 2004-03-04
14964 - Put the OR's IP in its router descriptor, not its fqdn. That way
14965 we'll stop being stalled by gethostbyname for nodes with flaky dns,
14968 - If the user typed in an address that didn't resolve, the server
14972 Changes in version 0.0.2pre24 - 2004-03-03
14974 - Fix an assertion failure in dns.c, where we were trying to dequeue
14975 a pending dns resolve even if it wasn't pending
14976 - Fix a spurious socks5 warning about still trying to write after the
14977 connection is finished.
14978 - Hold certain marked_for_close connections open until they're finished
14979 flushing, rather than losing bytes by closing them too early.
14980 - Correctly report the reason for ending a stream
14981 - Remove some duplicate calls to connection_mark_for_close
14982 - Put switch_id and start_daemon earlier in the boot sequence, so it
14983 will actually try to chdir() to options.DataDirectory
14984 - Make 'make test' exit(1) if a test fails; fix some unit tests
14985 - Make tor fail when you use a config option it doesn't know about,
14986 rather than warn and continue.
14987 - Make --version work
14988 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
14991 Changes in version 0.0.2pre23 - 2004-02-29
14993 - Print a statement when the first circ is finished, so the user
14994 knows it's working.
14995 - If a relay cell is unrecognized at the end of the circuit,
14996 send back a destroy. (So attacks to mutate cells are more
14998 - New config option 'excludenodes' to avoid certain nodes for circuits.
14999 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15000 so you can collect coredumps there.
15002 - Fix a bug in tls flushing where sometimes data got wedged and
15003 didn't flush until more data got sent. Hopefully this bug was
15004 a big factor in the random delays we were seeing.
15005 - Make 'connected' cells include the resolved IP, so the client
15006 dns cache actually gets populated.
15007 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15008 - When we time-out on a stream and detach from the circuit, send an
15009 end cell down it first.
15010 - Only warn about an unknown router (in exitnodes, entrynodes,
15011 excludenodes) after we've fetched a directory.
15014 Changes in version 0.0.2pre22 - 2004-02-26
15016 - Servers publish less revealing uname information in descriptors.
15017 - More memory tracking and assertions, to crash more usefully when
15019 - If the default torrc isn't there, just use some default defaults.
15020 Plus provide an internal dirservers file if they don't have one.
15021 - When the user tries to use Tor as an http proxy, give them an http
15022 501 failure explaining that we're a socks proxy.
15023 - Dump a new router.desc on hup, to help confused people who change
15024 their exit policies and then wonder why router.desc doesn't reflect
15026 - Clean up the generic tor.sh init script that we ship with.
15028 - If the exit stream is pending on the resolve, and a destroy arrives,
15029 then the stream wasn't getting removed from the pending list. I
15030 think this was the one causing recent server crashes.
15031 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15032 - When it couldn't resolve any dirservers, it was useless from then on.
15033 Now it reloads the RouterFile (or default dirservers) if it has no
15035 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15036 many users don't even *have* a /usr/local/sbin/.
15039 Changes in version 0.0.2pre21 - 2004-02-18
15041 - There's a ChangeLog file that actually reflects the changelog.
15042 - There's a 'torify' wrapper script, with an accompanying
15043 tor-tsocks.conf, that simplifies the process of using tsocks for
15044 tor. It even has a man page.
15045 - The tor binary gets installed to sbin rather than bin now.
15046 - Retry streams where the connected cell hasn't arrived in 15 seconds
15047 - Clean up exit policy handling -- get the default out of the torrc,
15048 so we can update it without forcing each server operator to fix
15050 - Allow imaps and pop3s in default exit policy
15052 - Prevent picking middleman nodes as the last node in the circuit
15055 Changes in version 0.0.2pre20 - 2004-01-30
15057 - We now have a deb package, and it's in debian unstable. Go to
15058 it, apt-getters. :)
15059 - I've split the TotalBandwidth option into BandwidthRate (how many
15060 bytes per second you want to allow, long-term) and
15061 BandwidthBurst (how many bytes you will allow at once before the cap
15062 kicks in). This better token bucket approach lets you, say, set
15063 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15064 performance while not exceeding your monthly bandwidth quota.
15065 - Push out a tls record's worth of data once you've got it, rather
15066 than waiting until you've read everything waiting to be read. This
15067 may improve performance by pipelining better. We'll see.
15068 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15069 from failed circuits (if they haven't been connected yet) and attach
15071 - Expire old streams that haven't managed to connect. Some day we'll
15072 have them reattach to new circuits instead.
15075 - Fix several memory leaks that were causing servers to become bloated
15077 - Fix a few very rare assert triggers. A few more remain.
15078 - Setuid to User _before_ complaining about running as root.
15081 Changes in version 0.0.2pre19 - 2004-01-07
15083 - Fix deadlock condition in dns farm. We were telling a child to die by
15084 closing the parent's file descriptor to him. But newer children were
15085 inheriting the open file descriptor from the parent, and since they
15086 weren't closing it, the socket never closed, so the child never read
15087 eof, so he never knew to exit. Similarly, dns workers were holding
15088 open other sockets, leading to all sorts of chaos.
15089 - New cleaner daemon() code for forking and backgrounding.
15090 - If you log to a file, it now prints an entry at the top of the
15091 logfile so you know it's working.
15092 - The onionskin challenge length was 30 bytes longer than necessary.
15093 - Started to patch up the spec so it's not quite so out of date.
15096 Changes in version 0.0.2pre18 - 2004-01-02
15098 - Fix endian issues with the 'integrity' field in the relay header.
15099 - Fix a potential bug where connections in state
15100 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15103 Changes in version 0.0.2pre17 - 2003-12-30
15105 - Made --debuglogfile (or any second log file, actually) work.
15106 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15107 adversary could force us into an infinite loop.
15110 - Each onionskin handshake now includes a hash of the computed key,
15111 to prove the server's identity and help perfect forward secrecy.
15112 - Changed cell size from 256 to 512 bytes (working toward compatibility
15114 - Changed cell length to 2 bytes, and moved it to the relay header.
15115 - Implemented end-to-end integrity checking for the payloads of
15117 - Separated streamid from 'recognized' (otherwise circuits will get
15118 messed up when we try to have streams exit from the middle). We
15119 use the integrity-checking to confirm that a cell is addressed to
15121 - Randomize the initial circid and streamid values, so an adversary who
15122 breaks into a node can't learn how many circuits or streams have
15126 Changes in version 0.0.2pre16 - 2003-12-14
15128 - Fixed a bug that made HUP trigger an assert
15129 - Fixed a bug where a circuit that immediately failed wasn't being
15130 counted as a failed circuit in counting retries.
15133 - Now we close the circuit when we get a truncated cell: otherwise we're
15134 open to an anonymity attack where a bad node in the path truncates
15135 the circuit and then we open streams at him.
15136 - Add port ranges to exit policies
15137 - Add a conservative default exit policy
15138 - Warn if you're running tor as root
15139 - on HUP, retry OR connections and close/rebind listeners
15140 - options.EntryNodes: try these nodes first when picking the first node
15141 - options.ExitNodes: if your best choices happen to include any of
15142 your preferred exit nodes, you choose among just those preferred
15144 - options.ExcludedNodes: nodes that are never picked in path building
15147 Changes in version 0.0.2pre15 - 2003-12-03
15148 o Robustness and bugfixes:
15149 - Sometimes clients would cache incorrect DNS resolves, which would
15150 really screw things up.
15151 - An OP that goes offline would slowly leak all its sockets and stop
15153 - A wide variety of bugfixes in exit node selection, exit policy
15154 handling, and processing pending streams when a new circuit is
15156 - Pick nodes for a path only from those the directory says are up
15157 - Choose randomly from all running dirservers, not always the first one
15158 - Increase allowed http header size for directory fetch.
15159 - Stop writing to stderr (if we're daemonized it will be closed).
15160 - Enable -g always, so cores will be more useful to me.
15161 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15164 - Wrote a man page. It lists commonly used options.
15167 - Change default loglevel to warn.
15168 - Make PidFile default to null rather than littering in your CWD.
15169 - OnionRouter config option is now obsolete. Instead it just checks
15171 - Moved to a single unified torrc file for both clients and servers.
15174 Changes in version 0.0.2pre14 - 2003-11-29
15175 o Robustness and bugfixes:
15176 - Force the admin to make the DataDirectory himself
15177 - to get ownership/permissions right
15178 - so clients no longer make a DataDirectory and then never use it
15179 - fix bug where a client who was offline for 45 minutes would never
15180 pull down a directory again
15181 - fix (or at least hide really well) the dns assert bug that was
15182 causing server crashes
15183 - warnings and improved robustness wrt clockskew for certs
15184 - use the native daemon(3) to daemonize, when available
15185 - exit if bind() fails
15186 - exit if neither socksport nor orport is defined
15187 - include our own tor_timegm (Win32 doesn't have its own)
15188 - bugfix for win32 with lots of connections
15189 - fix minor bias in PRNG
15190 - make dirserver more robust to corrupt cached directory
15193 - Wrote the design document (woo)
15195 o Circuit building and exit policies:
15196 - Circuits no longer try to use nodes that the directory has told them
15198 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15199 bitcounts (18.0.0.0/8).
15200 - Make AP connections standby for a circuit if no suitable circuit
15201 exists, rather than failing
15202 - Circuits choose exit node based on addr/port, exit policies, and
15203 which AP connections are standing by
15204 - Bump min pathlen from 2 to 3
15205 - Relay end cells have a payload to describe why the stream ended.
15206 - If the stream failed because of exit policy, try again with a new
15208 - Clients have a dns cache to remember resolved addresses.
15209 - Notice more quickly when we have no working circuits
15212 - APPort is now called SocksPort
15213 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15215 - RecommendedVersions is now a config variable rather than
15216 hardcoded (for dirservers)
15217 - Reloads config on HUP
15218 - Usage info on -h or --help
15219 - If you set User and Group config vars, it'll setu/gid to them.
15222 Changes in version 0.0.2pre13 - 2003-10-19
15223 o General stability:
15224 - SSL_write no longer fails when it returns WANTWRITE and the number
15225 of bytes in the buf has changed by the next SSL_write call.
15226 - Fix segfault fetching directory when network is down
15227 - Fix a variety of minor memory leaks
15228 - Dirservers reload the fingerprints file on HUP, so I don't have
15229 to take down the network when I approve a new router
15230 - Default server config file has explicit Address line to specify fqdn
15233 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15234 - Make listener connections not ever alloc bufs
15236 o Autoconf improvements:
15237 - don't clobber an external CFLAGS in ./configure
15238 - Make install now works
15239 - create var/lib/tor on make install
15240 - autocreate a tor.sh initscript to help distribs
15241 - autocreate the torrc and sample-server-torrc with correct paths
15243 o Log files and Daemonizing now work:
15244 - If --DebugLogFile is specified, log to it at -l debug
15245 - If --LogFile is specified, use it instead of commandline
15246 - If --RunAsDaemon is set, tor forks and backgrounds on startup