1 Changes in version 0.2.2.16-alpha - 2010-09-17
2 o Major bugfixes (stream-level fairness):
3 - When receiving a circuit-level SENDME for a blocked circuit, try
4 to package cells fairly from all the streams that had previously
5 been blocked on that circuit. Previously, we had started with the
6 oldest stream, and allowed each stream to potentially exhaust
7 the circuit's package window. This gave older streams on any
8 given circuit priority over newer ones. Fixes bug 1937. Detected
9 originally by Camilo Viecco. This bug was introduced before the
10 first Tor release, in svn commit r152: it is the new winner of
11 the longest-lived bug prize.
12 - When the exit relay got a circuit-level sendme cell, it started
13 reading on the exit streams, even if had 500 cells queued in the
14 circuit queue already, so the circuit queue just grew and grew in
15 some cases. We fix this by not re-enabling reading on receipt of a
16 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
17 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
19 - Newly created streams were allowed to read cells onto circuits,
20 even if the circuit's cell queue was blocked and waiting to drain.
21 This created potential unfairness, as older streams would be
22 blocked, but newer streams would gladly fill the queue completely.
23 We add code to detect this situation and prevent any stream from
24 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
28 - Update to the September 1 2010 Maxmind GeoLite Country database.
29 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
30 not. This would lead to a cookie that is still not group readable.
31 Closes bug 1843. Suggested by katmagic.
32 - When logging a rate-limited warning, we now mention how many messages
33 got suppressed since the last warning.
34 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
35 do individual connection-level rate limiting of clients. The torrc
36 config options with the same names trump the consensus params, if
37 both are present. Replaces the old "bwconnrate" and "bwconnburst"
38 consensus params which were broken from 0.2.2.7-alpha through
39 0.2.2.14-alpha. Closes bug 1947.
40 - When a router changes IP address or port, authorities now launch
41 a new reachability test for it. Implements ticket 1899.
42 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
43 2 no signature, 4 required" messages about consensus signatures
44 easier to read, and make sure they get logged at the same severity
45 as the messages explaining which keys are which. Fixes bug 1290.
46 - Don't warn when we have a consensus that we can't verify because
47 of missing certificates, unless those certificates are ones
48 that we have been trying and failing to download. Fixes bug 1145.
49 - If you configure your bridge with a known identity fingerprint,
50 and the bridge authority is unreachable (as it is in at least
51 one country now), fall back to directly requesting the descriptor
52 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
54 - When building with --enable-gcc-warnings on OpenBSD, disable
55 warnings in system headers. This makes --enable-gcc-warnings
58 o Minor bugfixes (on 0.2.1.x and earlier):
59 - Authorities will now attempt to download consensuses if their
60 own efforts to make a live consensus have failed. This change
61 means authorities that restart will fetch a valid consensus, and
62 it means authorities that didn't agree with the current consensus
63 will still fetch and serve it if it has enough signatures. Bugfix
64 on 0.2.0.9-alpha; fixes bug 1300.
65 - Ensure DNS requests launched by "RESOLVE" commands from the
66 controller respect the __LeaveStreamsUnattached setconf options. The
67 same goes for requests launched via DNSPort or transparent
68 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
69 - Allow handshaking OR connections to take a full KeepalivePeriod
70 seconds to handshake. Previously, we would close them after
71 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
72 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
74 - Rate-limit "Failed to hand off onionskin" warnings.
75 - Never relay a cell for a circuit we have already destroyed.
76 Between marking a circuit as closeable and finally closing it,
77 it may have been possible for a few queued cells to get relayed,
78 even though they would have been immediately dropped by the next
79 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
80 - Never queue a cell for a circuit that's already been marked
82 - Never vote for a server as "Running" if we have a descriptor for
83 it claiming to be hibernating, and that descriptor was published
84 more recently than our last contact with the server. Bugfix on
85 0.2.0.3-alpha; fixes bug 911.
86 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
89 o Minor bugfixes (on 0.2.2.x):
90 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
91 down if a directory fetch fails and you've configured either
92 bridges or EntryNodes. The intent was to mark the relay as down
93 _unless_ you're using bridges or EntryNodes, since if you are
94 then you could quickly run out of entry points.
95 - Fix the Windows directory-listing code. A bug introduced in
96 0.2.2.14-alpha could make Windows directory servers forget to load
97 some of their cached v2 networkstatus files.
98 - Really allow clients to use relays as bridges. Fixes bug 1776;
99 bugfix on 0.2.2.15-alpha.
100 - Demote a warn to info that happens when the CellStatistics option
101 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
102 Reported by Moritz Bartl.
103 - On Windows, build correctly either with or without Unicode support.
104 This is necessary so that Tor can support fringe platforms like
105 Windows 98 (which has no Unicode), or Windows CE (which has no
106 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
109 - Add a unit test for cross-platform directory-listing code.
112 Changes in version 0.2.2.15-alpha - 2010-08-18
114 - Stop assigning the HSDir flag to relays that disable their
115 DirPort (and thus will refuse to answer directory requests). This
116 fix should dramatically improve the reachability of hidden services:
117 hidden services and hidden service clients pick six HSDir relays
118 to store and retrieve the hidden service descriptor, and currently
119 about half of the HSDir relays will refuse to work. Bugfix on
120 0.2.0.10-alpha; fixes part of bug 1693.
121 - The PerConnBWRate and Burst config options, along with the
122 bwconnrate and bwconnburst consensus params, initialized each conn's
123 token bucket values only when the connection is established. Now we
124 update them if the config options change, and update them every time
125 we get a new consensus. Otherwise we can encounter an ugly edge
126 case where we initialize an OR conn to client-level bandwidth,
127 but then later the relay joins the consensus and we leave it
128 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
129 - Fix a regression that caused Tor to rebind its ports if it receives
130 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
133 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
134 should give us approximately 40-50% more Guard-flagged nodes,
135 improving the anonymity the Tor network can provide and also
136 decreasing the dropoff in throughput that relays experience when
137 they first get the Guard flag.
138 - Allow enabling or disabling the *Statistics config options while
142 - Update to the August 1 2010 Maxmind GeoLite Country database.
143 - Have the controller interface give a more useful message than
144 "Internal Error" in response to failed GETINFO requests.
145 - Warn when the same option is provided more than once in a torrc
146 file, on the command line, or in a single SETCONF statement, and
147 the option is one that only accepts a single line. Closes bug 1384.
148 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
149 Patch from mingw-san.
150 - Add support for the country code "{??}" in torrc options like
151 ExcludeNodes, to indicate all routers of unknown country. Closes
153 - Relays report the number of bytes spent on answering directory
154 requests in extra-info descriptors similar to {read,write}-history.
155 Implements enhancement 1790.
157 o Minor bugfixes (on 0.2.1.x and earlier):
158 - Complain if PublishServerDescriptor is given multiple arguments that
159 include 0 or 1. This configuration will be rejected in the future.
160 Bugfix on 0.2.0.1-alpha; closes bug 1107.
161 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
162 Bugfix on 0.2.0.13-alpha; closes bug 928.
163 - Change "Application request when we're believed to be offline."
164 notice to "Application request when we haven't used client
165 functionality lately.", to clarify that it's not an error. Bugfix
166 on 0.0.9.3; fixes bug 1222.
167 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
168 would return "551 Internal error" rather than "552 Unrecognized key
169 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
170 - Users can't configure a regular relay to be their bridge. It didn't
171 work because when Tor fetched the bridge descriptor, it found
172 that it already had it, and didn't realize that the purpose of the
173 descriptor had changed. Now we replace routers with a purpose other
174 than bridge with bridge descriptors when fetching them. Bugfix on
175 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
176 refetch the descriptor with router purpose 'general', disabling
178 - Fix a rare bug in rend_fn unit tests: we would fail a test when
179 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
180 on 0.2.0.10-alpha; fixes bug 1808.
181 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
182 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
183 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
184 Servers can start sending this code when enough clients recognize
185 it. Also update the spec to reflect this new reason. Bugfix on
186 0.1.0.1-rc; fixes part of bug 1793.
187 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
188 when we switch from being a public relay to a bridge. Otherwise
189 there will still be clients that see the relay in their consensus,
190 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
192 - Instead of giving an assertion failure on an internal mismatch
193 on estimated freelist size, just log a BUG warning and try later.
194 Mitigates but does not fix bug 1125.
195 - Fix an assertion failure that could occur in caches or bridge users
196 when using a very short voting interval on a testing network.
197 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
199 o Minor bugfixes (on 0.2.2.x):
200 - Alter directory authorities to always consider Exit-flagged nodes
201 as potential Guard nodes in their votes. The actual decision to
202 use Exits as Guards is done in the consensus bandwidth weights.
203 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
204 - When the controller is reporting the purpose of circuits that
205 didn't finish building before the circuit build timeout, it was
206 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
207 - Our libevent version parsing code couldn't handle versions like
208 1.4.14b-stable and incorrectly warned the user about using an
209 old and broken version of libevent. Treat 1.4.14b-stable like
210 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
212 - Don't use substitution references like $(VAR:MOD) when
213 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
214 '$(:x)' to 'x' rather than the empty string. This bites us in
215 doc/ when configured with --disable-asciidoc. Bugfix on
216 0.2.2.9-alpha; fixes bug 1773.
217 - Remove a spurious hidden service server-side log notice about
218 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
220 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
222 - Correctly report written bytes on linked connections. Found while
223 implementing 1790. Bugfix on 0.2.2.4-alpha.
224 - Fix three memory leaks: one in circuit_build_times_parse_state(),
225 one in dirvote_add_signatures_to_pending_consensus(), and one every
226 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
227 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
229 o Code simplifications and refactoring:
230 - Take a first step towards making or.h smaller by splitting out
231 function definitions for all source files in src/or/. Leave
232 structures and defines in or.h for now.
233 - Remove a bunch of unused function declarations as well as a block of
234 #if 0'd code from the unit tests. Closes bug 1824.
235 - New unit tests for exit-port history statistics; refactored exit
236 statistics code to be more easily tested.
237 - Remove the old debian/ directory from the main Tor distribution.
238 The official Tor-for-debian git repository lives at the URL
239 https://git.torproject.org/debian/tor.git
242 Changes in version 0.2.2.14-alpha - 2010-07-12
243 Tor 0.2.2.14-alpha greatly improves client-side handling of
244 circuit build timeouts, which are used to estimate speed and improve
245 performance. We also move to a much better GeoIP database, port Tor to
246 Windows CE, introduce new compile flags that improve code security,
247 add an eighth v3 directory authority, and address a lot of more
251 - Tor directory authorities no longer crash when started with a
252 cached-microdesc-consensus file in their data directory. Bugfix
253 on 0.2.2.6-alpha; fixes bug 1532.
254 - Treat an unset $HOME like an empty $HOME rather than triggering an
255 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
256 - Ignore negative and large circuit build timeout values that can
257 happen during a suspend or hibernate. These values caused various
258 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
259 - Alter calculation of Pareto distribution parameter 'Xm' for
260 Circuit Build Timeout learning to use the weighted average of the
261 top N=3 modes (because we have three entry guards). Considering
262 multiple modes should improve the timeout calculation in some cases,
263 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
265 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
266 right censored distribution model. This approach improves over the
267 synthetic timeout generation approach that was producing insanely
268 high timeout values. Now we calculate build timeouts using truncated
269 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
270 - Do not close circuits that are under construction when they reach
271 the circuit build timeout. Instead, leave them building (but do not
272 use them) for up until the time corresponding to the 95th percentile
273 on the Pareto CDF or 60 seconds, whichever is greater. This is done
274 to provide better data for the new Pareto model. This percentile
275 can be controlled by the consensus.
278 - Move to the June 2010 Maxmind GeoLite country db (rather than the
279 June 2009 ip-to-country GeoIP db) for our statistics that count
280 how many users relays are seeing from each country. Now we have
281 more accurate data for many African countries.
282 - Port Tor to build and run correctly on Windows CE systems, using
283 the wcecompat library. Contributed by Valerio Lupi.
284 - New "--enable-gcc-hardening" ./configure flag (off by default)
285 to turn on gcc compile time hardening options. It ensures
286 that signed ints have defined behavior (-fwrapv), enables
287 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
288 with canaries (-fstack-protector-all), turns on ASLR protection if
289 supported by the kernel (-fPIE, -pie), and adds additional security
290 related warnings. Verified to work on Mac OS X and Debian Lenny.
291 - New "--enable-linker-hardening" ./configure flag (off by default)
292 to turn on ELF specific hardening features (relro, now). This does
293 not work with Mac OS X or any other non-ELF binary format.
295 o New directory authorities:
296 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
300 - New config option "WarnUnsafeSocks 0" disables the warning that
301 occurs whenever Tor receives only an IP address instead of a
302 hostname. Setups that do DNS locally over Tor are fine, and we
303 shouldn't spam the logs in that case.
304 - Convert the HACKING file to asciidoc, and add a few new sections
305 to it, explaining how we use Git, how we make changelogs, and
306 what should go in a patch.
307 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
308 event, to give information on the current rate of circuit timeouts
309 over our stored history.
310 - Add ability to disable circuit build time learning via consensus
311 parameter and via a LearnCircuitBuildTimeout config option. Also
312 automatically disable circuit build time calculation if we are
313 either a AuthoritativeDirectory, or if we fail to write our state
314 file. Fixes bug 1296.
315 - More gracefully handle corrupt state files, removing asserts
316 in favor of saving a backup and resetting state.
317 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
321 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
323 - When a2x fails, mention that the user could disable manpages instead
324 of trying to fix their asciidoc installation.
325 - Where available, use Libevent 2.0's periodic timers so that our
326 once-per-second cleanup code gets called even more closely to
327 once per second than it would otherwise. Fixes bug 943.
328 - If you run a bridge that listens on multiple IP addresses, and
329 some user configures a bridge address that uses a different IP
330 address than your bridge writes in its router descriptor, and the
331 user doesn't specify an identity key, their Tor would discard the
332 descriptor because "it isn't one of our configured bridges", and
333 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
334 Bugfix on 0.2.0.3-alpha.
335 - If OpenSSL fails to make a duplicate of a private or public key, log
336 an error message and try to exit cleanly. May help with debugging
337 if bug 1209 ever remanifests.
338 - Save a couple bytes in memory allocation every time we escape
339 certain characters in a string. Patch from Florian Zumbiehl.
340 - Make it explicit that we don't cannibalize one-hop circuits. This
341 happens in the wild, but doesn't turn out to be a problem because
342 we fortunately don't use those circuits. Many thanks to outofwords
343 for the initial analysis and to swissknife who confirmed that
344 two-hop circuits are actually created.
345 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
346 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
347 - Eliminate a case where a circuit build time warning was displayed
348 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
351 Changes in version 0.2.1.26 - 2010-05-02
352 Tor 0.2.1.26 addresses the recent connection and memory overload
353 problems we've been seeing on relays, especially relays with their
354 DirPort open. If your relay has been crashing, or you turned it off
355 because it used too many resources, give this release a try.
357 This release also fixes yet another instance of broken OpenSSL libraries
358 that was causing some relays to drop out of the consensus.
361 - Teach relays to defend themselves from connection overload. Relays
362 now close idle circuits early if it looks like they were intended
363 for directory fetches. Relays are also more aggressive about closing
364 TLS connections that have no circuits on them. Such circuits are
365 unlikely to be re-used, and tens of thousands of them were piling
366 up at the fast relays, causing the relays to run out of sockets
367 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
368 their directory fetches over TLS).
369 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
370 that claim to be earlier than 0.9.8m, but which have in reality
371 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
372 behavior. Possible fix for some cases of bug 1346.
373 - Directory mirrors were fetching relay descriptors only from v2
374 directory authorities, rather than v3 authorities like they should.
375 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
376 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
379 - Finally get rid of the deprecated and now harmful notion of "clique
380 mode", where directory authorities maintain TLS connections to
384 - In the util/threads test, no longer free the test_mutex before all
385 worker threads have finished. Bugfix on 0.2.1.6-alpha.
386 - The master thread could starve the worker threads quite badly on
387 certain systems, causing them to run only partially in the allowed
388 window. This resulted in test failures. Now the master thread sleeps
389 occasionally for a few microseconds while the two worker-threads
390 compete for the mutex. Bugfix on 0.2.0.1-alpha.
393 Changes in version 0.2.2.13-alpha - 2010-04-24
394 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
395 problems we've been seeing on relays, especially relays with their
396 DirPort open. If your relay has been crashing, or you turned it off
397 because it used too many resources, give this release a try.
400 - Teach relays to defend themselves from connection overload. Relays
401 now close idle circuits early if it looks like they were intended
402 for directory fetches. Relays are also more aggressive about closing
403 TLS connections that have no circuits on them. Such circuits are
404 unlikely to be re-used, and tens of thousands of them were piling
405 up at the fast relays, causing the relays to run out of sockets
406 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
407 their directory fetches over TLS).
410 - Finally get rid of the deprecated and now harmful notion of "clique
411 mode", where directory authorities maintain TLS connections to
413 - Directory authorities now do an immediate reachability check as soon
414 as they hear about a new relay. This change should slightly reduce
415 the time between setting up a relay and getting listed as running
416 in the consensus. It should also improve the time between setting
417 up a bridge and seeing use by bridge users.
418 - Directory authorities no longer launch a TLS connection to every
419 relay as they startup. Now that we have 2k+ descriptors cached,
420 the resulting network hiccup is becoming a burden. Besides,
421 authorities already avoid voting about Running for the first half
422 hour of their uptime.
425 Changes in version 0.2.2.12-alpha - 2010-04-20
426 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
427 handle and vote on descriptors. It was causing relays to drop out of
431 - Many relays have been falling out of the consensus lately because
432 not enough authorities know about their descriptor for them to get
433 a majority of votes. When we deprecated the v2 directory protocol,
434 we got rid of the only way that v3 authorities can hear from each
435 other about other descriptors. Now authorities examine every v3
436 vote for new descriptors, and fetch them from that authority. Bugfix
438 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
439 and a warning in or.h related to bandwidth_weight_rule_t that
440 prevented clean compile on OS X. Fixes bug 1363; bugfix on
442 - Fix a segfault on relays when DirReqStatistics is enabled
443 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
447 - Demote a confusing TLS warning that relay operators might get when
448 someone tries to talk to their OrPort. It is neither the operator's
449 fault nor can they do anything about it. Fixes bug 1364; bugfix
453 Changes in version 0.2.2.11-alpha - 2010-04-15
454 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
455 libraries that was causing some relays to drop out of the consensus.
458 - Directory mirrors were fetching relay descriptors only from v2
459 directory authorities, rather than v3 authorities like they should.
460 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
461 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
462 - Fix a parsing error that made every possible value of
463 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
464 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
465 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
466 about the option without breaking older ones.
467 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
468 that claim to be earlier than 0.9.8m, but which have in reality
469 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
470 behavior. Possible fix for some cases of bug 1346.
473 - Experiment with a more aggressive approach to preventing clients
474 from making one-hop exit streams. Exit relays who want to try it
475 out can set "RefuseUnknownExits 1" in their torrc, and then look
476 for "Attempt by %s to open a stream" log messages. Let us know
478 - Add support for statically linking zlib by specifying
479 --enable-static-zlib, to go with our support for statically linking
480 openssl and libevent. Resolves bug 1358.
483 - Fix a segfault that happens whenever a Tor client that is using
484 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
486 - When we cleaned up the contrib/tor-exit-notice.html file, we left
487 out the first line. Fixes bug 1295.
488 - When building the manpage from a tarball, we required asciidoc, but
489 the asciidoc -> roff/html conversion was already done for the
490 tarball. Make 'make' complain only when we need asciidoc (either
491 because we're compiling directly from git, or because we altered
492 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
493 - When none of the directory authorities vote on any params, Tor
494 segfaulted when trying to make the consensus from the votes. We
495 didn't trigger the bug in practice, because authorities do include
496 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
499 - In the util/threads test, no longer free the test_mutex before all
500 worker threads have finished. Bugfix on 0.2.1.6-alpha.
501 - The master thread could starve the worker threads quite badly on
502 certain systems, causing them to run only partially in the allowed
503 window. This resulted in test failures. Now the master thread sleeps
504 occasionally for a few microseconds while the two worker-threads
505 compete for the mutex. Bugfix on 0.2.0.1-alpha.
508 Changes in version 0.2.2.10-alpha - 2010-03-07
509 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
510 could prevent relays from guessing their IP address correctly. It also
511 starts the groundwork for another client-side performance boost, since
512 currently we're not making efficient use of relays that have both the
513 Guard flag and the Exit flag.
516 - Fix a regression from our patch for bug 1244 that caused relays
517 to guess their IP address incorrectly if they didn't set Address
518 in their torrc and/or their address fails to resolve. Bugfix on
519 0.2.2.9-alpha; fixes bug 1269.
521 o Major features (performance):
522 - Directory authorities now compute consensus weightings that instruct
523 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
524 and no flag. Clients that use these weightings will distribute
525 network load more evenly across these different relay types. The
526 weightings are in the consensus so we can change them globally in
527 the future. Extra thanks to "outofwords" for finding some nasty
528 security bugs in the first implementation of this feature.
530 o Minor features (performance):
531 - Always perform router selections using weighted relay bandwidth,
532 even if we don't need a high capacity circuit at the time. Non-fast
533 circuits now only differ from fast ones in that they can use relays
534 not marked with the Fast flag. This "feature" could turn out to
535 be a horrible bug; we should investigate more before it goes into
539 - Allow disabling building of the manpages. Skipping the manpage
540 speeds up the build considerably.
542 o Minor bugfixes (on 0.2.2.x):
543 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
544 Bugfix on 0.2.2.9-alpha.
545 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
546 config option. Bugfix on 0.2.2.7-alpha.
547 - Ship the asciidoc-helper file in the tarball, so that people can
548 build from source if they want to, and touching the .1.txt files
549 doesn't break the build. Bugfix on 0.2.2.9-alpha.
551 o Minor bugfixes (on 0.2.1.x or earlier):
552 - Fix a dereference-then-NULL-check sequence when publishing
553 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
555 - Fix another dereference-then-NULL-check sequence. Bugfix on
556 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
557 - Make sure we treat potentially not NUL-terminated strings correctly.
558 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
560 o Code simplifications and refactoring:
561 - Fix some urls in the exit notice file and make it XHTML1.1 strict
562 compliant. Based on a patch from Christian Kujau.
563 - Don't use sed in asciidoc-helper anymore.
564 - Make the build process fail if asciidoc cannot be found and
565 building with asciidoc isn't disabled.
568 Changes in version 0.2.2.9-alpha - 2010-02-22
569 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
570 location of a directory authority, and cleans up a bunch of small bugs.
572 o Directory authority changes:
573 - Change IP address for dannenberg (v3 directory authority), and
574 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
575 service directory authority) from the list.
578 - Make Tor work again on the latest OS X: when deciding whether to
579 use strange flags to turn TLS renegotiation on, detect the OpenSSL
580 version at run-time, not compile time. We need to do this because
581 Apple doesn't update its dev-tools headers when it updates its
582 libraries in a security patch.
583 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
584 that could happen on 32-bit platforms with 64-bit time_t. Also fix
585 a memory leak when requesting a hidden service descriptor we've
586 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
588 - Authorities could be tricked into giving out the Exit flag to relays
589 that didn't allow exiting to any ports. This bug could screw
590 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
591 1238. Bug discovered by Martin Kowalczyk.
592 - When freeing a session key, zero it out completely. We only zeroed
593 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
594 patched by ekir. Fixes bug 1254.
597 - Fix static compilation by listing the openssl libraries in the right
598 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
599 - Resume handling .exit hostnames in a special way: originally we
600 stripped the .exit part and used the requested exit relay. In
601 0.2.2.1-alpha we stopped treating them in any special way, meaning
602 if you use a .exit address then Tor will pass it on to the exit
603 relay. Now we reject the .exit stream outright, since that behavior
604 might be more expected by the user. Found and diagnosed by Scott
605 Bennett and Downie on or-talk.
606 - Don't spam the controller with events when we have no file
607 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
608 for log messages was already solved from bug 748.)
609 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
611 - Make the DNSPort option work with libevent 2.x. Don't alter the
612 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
613 - Emit a GUARD DROPPED controller event for a case we missed.
614 - Make more fields in the controller protocol case-insensitive, since
615 control-spec.txt said they were.
616 - Refactor resolve_my_address() to not use gethostbyname() anymore.
617 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
618 - Fix a spec conformance issue: the network-status-version token
619 must be the first token in a v3 consensus or vote. Discovered by
620 parakeep. Bugfix on 0.2.0.3-alpha.
622 o Code simplifications and refactoring:
623 - Generate our manpage and HTML documentation using Asciidoc. This
624 change should make it easier to maintain the documentation, and
626 - Remove the --enable-iphone option. According to reports from Marco
627 Bonetti, Tor builds fine without any special tweaking on recent
629 - Removed some unnecessary files from the source distribution. The
630 AUTHORS file has now been merged into the people page on the
631 website. The roadmaps and design doc can now be found in the
632 projects directory in svn.
633 - Enabled various circuit build timeout constants to be controlled
634 by consensus parameters. Also set better defaults for these
635 parameters based on experimentation on broadband and simulated
639 - The 'EXTENDCIRCUIT' control port command can now be used with
640 a circ id of 0 and no path. This feature will cause Tor to build
641 a new 'fast' general purpose circuit using its own path selection
643 - Added a BUILDTIMEOUT_SET controller event to describe changes
644 to the circuit build timeout.
645 - Future-proof the controller protocol a bit by ignoring keyword
646 arguments we do not recognize.
647 - Expand homedirs passed to tor-checkkey. This should silence a
648 coverity complaint about passing a user-supplied string into
649 open() without checking it.
652 Changes in version 0.2.1.25 - 2010-03-16
653 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
654 prevent relays from guessing their IP address correctly. It also fixes
655 several minor potential security bugs.
658 - Fix a regression from our patch for bug 1244 that caused relays
659 to guess their IP address incorrectly if they didn't set Address
660 in their torrc and/or their address fails to resolve. Bugfix on
661 0.2.1.23; fixes bug 1269.
662 - When freeing a session key, zero it out completely. We only zeroed
663 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
664 patched by ekir. Fixes bug 1254.
667 - Fix a dereference-then-NULL-check sequence when publishing
668 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
670 - Fix another dereference-then-NULL-check sequence. Bugfix on
671 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
672 - Make sure we treat potentially not NUL-terminated strings correctly.
673 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
677 Changes in version 0.2.1.24 - 2010-02-21
678 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
682 - Work correctly out-of-the-box with even more vendor-patched versions
683 of OpenSSL. In particular, make it so Debian and OS X don't need
684 customized patches to run/build.
687 Changes in version 0.2.1.23 - 2010-02-13
688 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
689 again on the latest OS X, and updates the location of a directory
692 o Major bugfixes (performance):
693 - We were selecting our guards uniformly at random, and then weighting
694 which of our guards we'd use uniformly at random. This imbalance
695 meant that Tor clients were severely limited on throughput (and
696 probably latency too) by the first hop in their circuit. Now we
697 select guards weighted by currently advertised bandwidth. We also
698 automatically discard guards picked using the old algorithm. Fixes
699 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
702 - Make Tor work again on the latest OS X: when deciding whether to
703 use strange flags to turn TLS renegotiation on, detect the OpenSSL
704 version at run-time, not compile time. We need to do this because
705 Apple doesn't update its dev-tools headers when it updates its
706 libraries in a security patch.
707 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
708 that could happen on 32-bit platforms with 64-bit time_t. Also fix
709 a memory leak when requesting a hidden service descriptor we've
710 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
713 o Directory authority changes:
714 - Change IP address for dannenberg (v3 directory authority), and
715 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
716 service directory authority) from the list.
719 - Refactor resolve_my_address() to not use gethostbyname() anymore.
720 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
723 - Avoid a mad rush at the beginning of each month when each client
724 rotates half of its guards. Instead we spread the rotation out
725 throughout the month, but we still avoid leaving a precise timestamp
726 in the state file about when we first picked the guard. Improves
727 over the behavior introduced in 0.1.2.17.
730 Changes in version 0.2.2.8-alpha - 2010-01-26
731 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
732 causing bridge relays to disappear. If you're running a bridge,
736 - Fix a memory corruption bug on bridges that occured during the
737 inclusion of stats data in extra-info descriptors. Also fix the
738 interface for geoip_get_bridge_stats* to prevent similar bugs in
739 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
740 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
743 - Ignore OutboundBindAddress when connecting to localhost.
744 Connections to localhost need to come _from_ localhost, or else
745 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
749 Changes in version 0.2.2.7-alpha - 2010-01-19
750 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
751 as laying the groundwork for further relay-side performance fixes. It
752 also starts cleaning up client behavior with respect to the EntryNodes,
753 ExitNodes, and StrictNodes config options.
755 This release also rotates two directory authority keys, due to a
756 security breach of some of the Torproject servers.
758 o Directory authority changes:
759 - Rotate keys (both v3 identity and relay identity) for moria1
762 o Major features (performance):
763 - We were selecting our guards uniformly at random, and then weighting
764 which of our guards we'd use uniformly at random. This imbalance
765 meant that Tor clients were severely limited on throughput (and
766 probably latency too) by the first hop in their circuit. Now we
767 select guards weighted by currently advertised bandwidth. We also
768 automatically discard guards picked using the old algorithm. Fixes
769 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
770 - When choosing which cells to relay first, relays can now favor
771 circuits that have been quiet recently, to provide lower latency
772 for low-volume circuits. By default, relays enable or disable this
773 feature based on a setting in the consensus. You can override
774 this default by using the new "CircuitPriorityHalflife" config
775 option. Design and code by Ian Goldberg, Can Tang, and Chris
777 - Add separate per-conn write limiting to go with the per-conn read
778 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
779 but never per-conn write limits.
780 - New consensus params "bwconnrate" and "bwconnburst" to let us
781 rate-limit client connections as they enter the network. It's
782 controlled in the consensus so we can turn it on and off for
783 experiments. It's starting out off. Based on proposal 163.
785 o Major features (relay selection options):
786 - Switch to a StrictNodes config option, rather than the previous
787 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
788 "StrictExcludeNodes" option.
789 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
790 change during a config reload, mark and discard all our origin
791 circuits. This fix should address edge cases where we change the
792 config options and but then choose a circuit that we created before
794 - If EntryNodes or ExitNodes are set, be more willing to use an
795 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
797 - Make EntryNodes config option much more aggressive even when
798 StrictNodes is not set. Before it would prepend your requested
799 entrynodes to your list of guard nodes, but feel free to use others
800 after that. Now it chooses only from your EntryNodes if any of
801 those are available, and only falls back to others if a) they're
802 all down and b) StrictNodes is not set.
803 - Now we refresh your entry guards from EntryNodes at each consensus
804 fetch -- rather than just at startup and then they slowly rot as
808 - Stop bridge directory authorities from answering dbg-stability.txt
809 directory queries, which would let people fetch a list of all
810 bridge identities they track. Bugfix on 0.2.1.6-alpha.
813 - Log a notice when we get a new control connection. Now it's easier
814 for security-conscious users to recognize when a local application
815 is knocking on their controller door. Suggested by bug 1196.
816 - New config option "CircuitStreamTimeout" to override our internal
817 timeout schedule for how many seconds until we detach a stream from
818 a circuit and try a new circuit. If your network is particularly
819 slow, you might want to set this to a number like 60.
820 - New controller command "getinfo config-text". It returns the
821 contents that Tor would write if you send it a SAVECONF command,
822 so the controller can write the file to disk itself.
823 - New options for SafeLogging to allow scrubbing only log messages
824 generated while acting as a relay.
825 - Ship the bridges spec file in the tarball too.
826 - Avoid a mad rush at the beginning of each month when each client
827 rotates half of its guards. Instead we spread the rotation out
828 throughout the month, but we still avoid leaving a precise timestamp
829 in the state file about when we first picked the guard. Improves
830 over the behavior introduced in 0.1.2.17.
832 o Minor bugfixes (compiling):
833 - Fix compilation on OS X 10.3, which has a stub mlockall() but
834 hides it. Bugfix on 0.2.2.6-alpha.
835 - Fix compilation on Solaris by removing support for the
836 DisableAllSwap config option. Solaris doesn't have an rlimit for
837 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
840 o Minor bugfixes (crashes):
841 - Do not segfault when writing buffer stats when we haven't observed
842 a single circuit to report about. Found by Fabian Lanze. Bugfix on
844 - If we're in the pathological case where there's no exit bandwidth
845 but there is non-exit bandwidth, or no guard bandwidth but there
846 is non-guard bandwidth, don't crash during path selection. Bugfix
848 - Fix an impossible-to-actually-trigger buffer overflow in relay
849 descriptor generation. Bugfix on 0.1.0.15.
851 o Minor bugfixes (privacy):
852 - Fix an instance where a Tor directory mirror might accidentally
853 log the IP address of a misbehaving Tor client. Bugfix on
855 - Don't list Windows capabilities in relay descriptors. We never made
856 use of them, and maybe it's a bad idea to publish them. Bugfix
859 o Minor bugfixes (other):
860 - Resolve an edge case in path weighting that could make us misweight
861 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
862 - Fix statistics on client numbers by country as seen by bridges that
863 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
864 intervals instead of variable 12-to-48-hour intervals.
865 - After we free an internal connection structure, overwrite it
866 with a different memory value than we use for overwriting a freed
867 internal circuit structure. Should help with debugging. Suggested
869 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
873 - Remove the HSAuthorityRecordStats option that version 0 hidden
874 service authorities could have used to track statistics of overall
875 hidden service usage.
878 Changes in version 0.2.1.22 - 2010-01-19
879 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
880 authorities -- it would tell you its whole history of bridge descriptors
881 if you make the right directory request. This stable update also
882 rotates two of the seven v3 directory authority keys and locations.
884 o Directory authority changes:
885 - Rotate keys (both v3 identity and relay identity) for moria1
889 - Stop bridge directory authorities from answering dbg-stability.txt
890 directory queries, which would let people fetch a list of all
891 bridge identities they track. Bugfix on 0.2.1.6-alpha.
894 Changes in version 0.2.1.21 - 2009-12-21
895 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
896 library. If you use Tor on Linux / Unix and you're getting SSL
897 renegotiation errors, upgrading should help. We also recommend an
898 upgrade if you're an exit relay.
901 - Work around a security feature in OpenSSL 0.9.8l that prevents our
902 handshake from working unless we explicitly tell OpenSSL that we
903 are using SSL renegotiation safely. We are, of course, but OpenSSL
904 0.9.8l won't work unless we say we are.
905 - Avoid crashing if the client is trying to upload many bytes and the
906 circuit gets torn down at the same time, or if the flip side
907 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
910 - Do not refuse to learn about authority certs and v2 networkstatus
911 documents that are older than the latest consensus. This bug might
912 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
913 Spotted and fixed by xmux.
914 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
915 trigger platform-specific option misparsing case found by Coverity
917 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
918 trigger assert. Fixes bug 1173.
921 Changes in version 0.2.2.6-alpha - 2009-11-19
922 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
923 support for the new lower-footprint "microdescriptor" directory design,
924 future-proofing our consensus format against new hash functions or
925 other changes, and an Android port. It also makes Tor compatible with
926 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
929 - Directory authorities can now create, vote on, and serve multiple
930 parallel formats of directory data as part of their voting process.
931 Partially implements Proposal 162: "Publish the consensus in
933 - Directory authorities can now agree on and publish small summaries
934 of router information that clients can use in place of regular
935 server descriptors. This transition will eventually allow clients
936 to use far less bandwidth for downloading information about the
937 network. Begins the implementation of Proposal 158: "Clients
938 download consensus + microdescriptors".
939 - The directory voting system is now extensible to use multiple hash
940 algorithms for signatures and resource selection. Newer formats
941 are signed with SHA256, with a possibility for moving to a better
942 hash algorithm in the future.
943 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
944 current and future memory pages via mlockall(). On supported
945 platforms (modern Linux and probably BSD but not Windows or OS X),
946 this should effectively disable any and all attempts to page out
947 memory. This option requires that you start your Tor as root --
948 if you use DisableAllSwap, please consider using the User option
949 to properly reduce the privileges of your Tor.
950 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
951 to help Tor build correctly for Android phones.
954 - Work around a security feature in OpenSSL 0.9.8l that prevents our
955 handshake from working unless we explicitly tell OpenSSL that we
956 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
957 won't work unless we say we are.
960 - Fix a crash bug when trying to initialize the evdns module in
961 Libevent 2. Bugfix on 0.2.1.16-rc.
962 - Stop logging at severity 'warn' when some other Tor client tries
963 to establish a circuit with us using weak DH keys. It's a protocol
964 violation, but that doesn't mean ordinary users need to hear about
965 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
966 - Do not refuse to learn about authority certs and v2 networkstatus
967 documents that are older than the latest consensus. This bug might
968 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
969 Spotted and fixed by xmux.
970 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
971 - If all authorities restart at once right before a consensus vote,
972 nobody will vote about "Running", and clients will get a consensus
973 with no usable relays. Instead, authorities refuse to build a
974 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
975 - If your relay can't keep up with the number of incoming create
976 cells, it would log one warning per failure into your logs. Limit
977 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
978 - Bridges now use "reject *:*" as their default exit policy. Bugfix
979 on 0.2.0.3-alpha; fixes bug 1113.
980 - Fix a memory leak on directory authorities during voting that was
981 introduced in 0.2.2.1-alpha. Found via valgrind.
984 Changes in version 0.2.1.20 - 2009-10-15
985 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
986 services at once, prepares for more performance improvements, and
987 fixes a bunch of smaller bugs.
989 The Windows and OS X bundles also include a more recent Vidalia,
990 and switch from Privoxy to Polipo.
992 The OS X installers are now drag and drop. It's best to un-install
993 Tor/Vidalia and then install this new bundle, rather than upgrade. If
994 you want to upgrade, you'll need to update the paths for Tor and Polipo
995 in the Vidalia Settings window.
998 - Send circuit or stream sendme cells when our window has decreased
999 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1000 by Karsten when testing the "reduce circuit window" performance
1001 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1002 before the release of Tor 0.0.0. This is the new winner of the
1004 - Fix a remotely triggerable memory leak when a consensus document
1005 contains more than one signature from the same voter. Bugfix on
1007 - Avoid segfault in rare cases when finishing an introduction circuit
1008 as a client and finding out that we don't have an introduction key
1009 for it. Fixes bug 1073. Reported by Aaron Swartz.
1012 - Tor now reads the "circwindow" parameter out of the consensus,
1013 and uses that value for its circuit package window rather than the
1014 default of 1000 cells. Begins the implementation of proposal 168.
1016 o New directory authorities:
1017 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1019 - Move moria1 and tonga to alternate IP addresses.
1022 - Fix a signed/unsigned compile warning in 0.2.1.19.
1023 - Fix possible segmentation fault on directory authorities. Bugfix on
1025 - Fix an extremely rare infinite recursion bug that could occur if
1026 we tried to log a message after shutting down the log subsystem.
1027 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1028 - Fix an obscure bug where hidden services on 64-bit big-endian
1029 systems might mis-read the timestamp in v3 introduce cells, and
1030 refuse to connect back to the client. Discovered by "rotor".
1031 Bugfix on 0.2.1.6-alpha.
1032 - We were triggering a CLOCK_SKEW controller status event whenever
1033 we connect via the v2 connection protocol to any relay that has
1034 a wrong clock. Instead, we should only inform the controller when
1035 it's a trusted authority that claims our clock is wrong. Bugfix
1036 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1037 - We were telling the controller about CHECKING_REACHABILITY and
1038 REACHABILITY_FAILED status events whenever we launch a testing
1039 circuit or notice that one has failed. Instead, only tell the
1040 controller when we want to inform the user of overall success or
1041 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1043 - Don't warn when we're using a circuit that ends with a node
1044 excluded in ExcludeExitNodes, but the circuit is not used to access
1045 the outside world. This should help fix bug 1090. Bugfix on
1047 - Work around a small memory leak in some versions of OpenSSL that
1048 stopped the memory used by the hostname TLS extension from being
1052 - Add a "getinfo status/accepted-server-descriptor" controller
1053 command, which is the recommended way for controllers to learn
1054 whether our server descriptor has been successfully received by at
1055 least on directory authority. Un-recommend good-server-descriptor
1056 getinfo and status events until we have a better design for them.
1059 Changes in version 0.2.2.5-alpha - 2009-10-11
1060 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
1063 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
1065 o New directory authorities:
1066 - Move dizum to an alternate IP address.
1069 Changes in version 0.2.2.4-alpha - 2009-10-10
1070 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
1071 introduces a new unit test framework, shifts directry authority
1072 addresses around to reduce the impact from recent blocking events,
1073 and fixes a few smaller bugs.
1076 - Fix several more asserts in the circuit_build_times code, for
1077 example one that causes Tor to fail to start once we have
1078 accumulated 5000 build times in the state file. Bugfixes on
1079 0.2.2.2-alpha; fixes bug 1108.
1081 o New directory authorities:
1082 - Move moria1 and Tonga to alternate IP addresses.
1085 - Log SSL state transitions at debug level during handshake, and
1086 include SSL states in error messages. This may help debug future
1087 SSL handshake issues.
1088 - Add a new "Handshake" log domain for activities that happen
1089 during the TLS handshake.
1090 - Revert to the "June 3 2009" ip-to-country file. The September one
1091 seems to have removed most US IP addresses.
1092 - Directory authorities now reject Tor relays with versions less than
1093 0.1.2.14. This step cuts out four relays from the current network,
1094 none of which are very big.
1097 - Fix a couple of smaller issues with gathering statistics. Bugfixes
1099 - Fix two memory leaks in the error case of
1100 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
1101 - Don't count one-hop circuits when we're estimating how long it
1102 takes circuits to build on average. Otherwise we'll set our circuit
1103 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
1104 - Directory authorities no longer change their opinion of, or vote on,
1105 whether a router is Running, unless they have themselves been
1106 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
1109 o Code simplifications and refactoring:
1110 - Revise our unit tests to use the "tinytest" framework, so we
1111 can run tests in their own processes, have smarter setup/teardown
1112 code, and so on. The unit test code has moved to its own
1113 subdirectory, and has been split into multiple modules.
1116 Changes in version 0.2.2.3-alpha - 2009-09-23
1117 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
1120 - Fix an overzealous assert in our new circuit build timeout code.
1121 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
1124 - If the networkstatus consensus tells us that we should use a
1125 negative circuit package window, ignore it. Otherwise we'll
1126 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
1129 Changes in version 0.2.2.2-alpha - 2009-09-21
1130 Tor 0.2.2.2-alpha introduces our latest performance improvement for
1131 clients: Tor tracks the average time it takes to build a circuit, and
1132 avoids using circuits that take too long to build. For fast connections,
1133 this feature can cut your expected latency in half. For slow or flaky
1134 connections, it could ruin your Tor experience. Let us know if it does!
1137 - Tor now tracks how long it takes to build client-side circuits
1138 over time, and adapts its timeout to local network performance.
1139 Since a circuit that takes a long time to build will also provide
1140 bad performance, we get significant latency improvements by
1141 discarding the slowest 20% of circuits. Specifically, Tor creates
1142 circuits more aggressively than usual until it has enough data
1143 points for a good timeout estimate. Implements proposal 151.
1144 We are especially looking for reports (good and bad) from users with
1145 both EDGE and broadband connections that can move from broadband
1146 to EDGE and find out if the build-time data in the .tor/state gets
1147 reset without loss of Tor usability. You should also see a notice
1148 log message telling you that Tor has reset its timeout.
1149 - Directory authorities can now vote on arbitary integer values as
1150 part of the consensus process. This is designed to help set
1151 network-wide parameters. Implements proposal 167.
1152 - Tor now reads the "circwindow" parameter out of the consensus,
1153 and uses that value for its circuit package window rather than the
1154 default of 1000 cells. Begins the implementation of proposal 168.
1157 - Fix a remotely triggerable memory leak when a consensus document
1158 contains more than one signature from the same voter. Bugfix on
1162 - Fix an extremely rare infinite recursion bug that could occur if
1163 we tried to log a message after shutting down the log subsystem.
1164 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1165 - Fix parsing for memory or time units given without a space between
1166 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
1167 - A networkstatus vote must contain exactly one signature. Spec
1168 conformance issue. Bugfix on 0.2.0.3-alpha.
1169 - Fix an obscure bug where hidden services on 64-bit big-endian
1170 systems might mis-read the timestamp in v3 introduce cells, and
1171 refuse to connect back to the client. Discovered by "rotor".
1172 Bugfix on 0.2.1.6-alpha.
1173 - We were triggering a CLOCK_SKEW controller status event whenever
1174 we connect via the v2 connection protocol to any relay that has
1175 a wrong clock. Instead, we should only inform the controller when
1176 it's a trusted authority that claims our clock is wrong. Bugfix
1177 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1178 - We were telling the controller about CHECKING_REACHABILITY and
1179 REACHABILITY_FAILED status events whenever we launch a testing
1180 circuit or notice that one has failed. Instead, only tell the
1181 controller when we want to inform the user of overall success or
1182 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1184 - Don't warn when we're using a circuit that ends with a node
1185 excluded in ExcludeExitNodes, but the circuit is not used to access
1186 the outside world. This should help fix bug 1090, but more problems
1187 remain. Bugfix on 0.2.1.6-alpha.
1188 - Work around a small memory leak in some versions of OpenSSL that
1189 stopped the memory used by the hostname TLS extension from being
1191 - Make our 'torify' script more portable; if we have only one of
1192 'torsocks' or 'tsocks' installed, don't complain to the user;
1193 and explain our warning about tsocks better.
1196 - Add a "getinfo status/accepted-server-descriptor" controller
1197 command, which is the recommended way for controllers to learn
1198 whether our server descriptor has been successfully received by at
1199 least on directory authority. Un-recommend good-server-descriptor
1200 getinfo and status events until we have a better design for them.
1201 - Update to the "September 4 2009" ip-to-country file.
1204 Changes in version 0.2.2.1-alpha - 2009-08-26
1205 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
1206 Tor clients to bootstrap on networks where only port 80 is reachable,
1207 makes it more straightforward to support hardware crypto accelerators,
1208 and starts the groundwork for gathering stats safely at relays.
1211 - Start the process of disabling ".exit" address notation, since it
1212 can be used for a variety of esoteric application-level attacks
1213 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
1216 o New directory authorities:
1217 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1221 - New AccelName and AccelDir options add support for dynamic OpenSSL
1222 hardware crypto acceleration engines.
1223 - Tor now supports tunneling all of its outgoing connections over
1224 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
1225 configuration options. Code by Christopher Davis.
1228 - Send circuit or stream sendme cells when our window has decreased
1229 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1230 by Karsten when testing the "reduce circuit window" performance
1231 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1232 before the release of Tor 0.0.0. This is the new winner of the
1235 o New options for gathering stats safely:
1236 - Directories that set "DirReqStatistics 1" write statistics on
1237 directory request to disk every 24 hours. As compared to the
1238 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
1239 1) stats are written to disk exactly every 24 hours; 2) estimated
1240 shares of v2 and v3 requests are determined as mean values, not at
1241 the end of a measurement period; 3) unresolved requests are listed
1242 with country code '??'; 4) directories also measure download times.
1243 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
1244 number of exit streams and transferred bytes per port to disk every
1246 - Relays that set "CellStatistics 1" write statistics on how long
1247 cells spend in their circuit queues to disk every 24 hours.
1248 - Entry nodes that set "EntryStatistics 1" write statistics on the
1249 rough number and origins of connecting clients to disk every 24
1251 - Relays that write any of the above statistics to disk and set
1252 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
1253 their extra-info documents.
1256 - New --digests command-line switch to output the digests of the
1257 source files Tor was built with.
1258 - The "torify" script now uses torsocks where available.
1259 - The memarea code now uses a sentinel value at the end of each area
1260 to make sure nothing writes beyond the end of an area. This might
1261 help debug some conceivable causes of bug 930.
1262 - Time and memory units in the configuration file can now be set to
1263 fractional units. For example, "2.5 GB" is now a valid value for
1265 - Certain Tor clients (such as those behind check.torproject.org) may
1266 want to fetch the consensus in an extra early manner. To enable this
1267 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
1268 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
1269 as only certain clients who must have this information sooner should
1271 - Instead of adding the svn revision to the Tor version string, report
1272 the git commit (when we're building from a git checkout).
1275 - If any the v3 certs we download are unparseable, we should actually
1276 notice the failure so we don't retry indefinitely. Bugfix on
1277 0.2.0.x; reported by "rotator".
1278 - If the cached cert file is unparseable, warn but don't exit.
1279 - Fix possible segmentation fault on directory authorities. Bugfix on
1281 - When Tor fails to parse a descriptor of any kind, dump it to disk.
1282 Might help diagnosing bug 1051.
1284 o Deprecated and removed features:
1285 - The controller no longer accepts the old obsolete "addr-mappings/"
1286 or "unregistered-servers-" GETINFO values.
1287 - Hidden services no longer publish version 0 descriptors, and clients
1288 do not request or use version 0 descriptors. However, the old hidden
1289 service authorities still accept and serve version 0 descriptors
1290 when contacted by older hidden services/clients.
1291 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1292 always on; using them is necessary for correct forward-compatible
1294 - Remove support for .noconnect style addresses. Nobody was using
1295 them, and they provided another avenue for detecting Tor users
1296 via application-level web tricks.
1298 o Packaging changes:
1299 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
1300 installer bundles. See
1301 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
1302 for details of what's new in Vidalia 0.2.3.
1303 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
1304 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
1305 configuration file, rather than the old Privoxy.
1306 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
1307 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
1308 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
1309 better compatibility with OS X 10.6, aka Snow Leopard.
1310 - OS X Vidalia Bundle: The multi-package installer is now replaced
1311 by a simple drag and drop to the /Applications folder. This change
1312 occurred with the upgrade to Vidalia 0.2.3.
1315 Changes in version 0.2.1.19 - 2009-07-28
1316 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
1317 services on Tor 0.2.1.3-alpha through 0.2.1.18.
1320 - Make accessing hidden services on 0.2.1.x work right again.
1321 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
1322 part of patch provided by "optimist".
1325 - When a relay/bridge is writing out its identity key fingerprint to
1326 the "fingerprint" file and to its logs, write it without spaces. Now
1327 it will look like the fingerprints in our bridges documentation,
1328 and confuse fewer users.
1331 - Relays no longer publish a new server descriptor if they change
1332 their MaxAdvertisedBandwidth config option but it doesn't end up
1333 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
1334 fixes bug 1026. Patch from Sebastian.
1335 - Avoid leaking memory every time we get a create cell but we have
1336 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
1337 fixes bug 1034. Reported by BarkerJr.
1340 Changes in version 0.2.1.18 - 2009-07-24
1341 Tor 0.2.1.18 lays the foundations for performance improvements,
1342 adds status events to help users diagnose bootstrap problems, adds
1343 optional authentication/authorization for hidden services, fixes a
1344 variety of potential anonymity problems, and includes a huge pile of
1345 other features and bug fixes.
1348 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
1351 Changes in version 0.2.1.17-rc - 2009-07-07
1352 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
1353 candidate for the 0.2.1.x series. It lays the groundwork for further
1354 client performance improvements, and also fixes a big bug with directory
1355 authorities that were causing them to assign Guard and Stable flags
1358 The Windows bundles also finally include the geoip database that we
1359 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
1360 should actually install Torbutton rather than giving you a cryptic
1361 failure message (oops).
1364 - Clients now use the bandwidth values in the consensus, rather than
1365 the bandwidth values in each relay descriptor. This approach opens
1366 the door to more accurate bandwidth estimates once the directory
1367 authorities start doing active measurements. Implements more of
1371 - When Tor clients restart after 1-5 days, they discard all their
1372 cached descriptors as too old, but they still use the cached
1373 consensus document. This approach is good for robustness, but
1374 bad for performance: since they don't know any bandwidths, they
1375 end up choosing at random rather than weighting their choice by
1376 speed. Fixed by the above feature of putting bandwidths in the
1377 consensus. Bugfix on 0.2.0.x.
1378 - Directory authorities were neglecting to mark relays down in their
1379 internal histories if the relays fall off the routerlist without
1380 ever being found unreachable. So there were relays in the histories
1381 that haven't been seen for eight months, and are listed as being
1382 up for eight months. This wreaked havoc on the "median wfu"
1383 and "median mtbf" calculations, in turn making Guard and Stable
1384 flags very wrong, hurting network performance. Fixes bugs 696 and
1385 969. Bugfix on 0.2.0.6-alpha.
1388 - Serve the DirPortFrontPage page even when we have been approaching
1389 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
1390 - The control port would close the connection before flushing long
1391 replies, such as the network consensus, if a QUIT command was issued
1392 before the reply had completed. Now, the control port flushes all
1393 pending replies before closing the connection. Also fixed a spurious
1394 warning when a QUIT command is issued after a malformed or rejected
1395 AUTHENTICATE command, but before the connection was closed. Patch
1396 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
1397 - When we can't find an intro key for a v2 hidden service descriptor,
1398 fall back to the v0 hidden service descriptor and log a bug message.
1399 Workaround for bug 1024.
1400 - Fix a log message that did not respect the SafeLogging option.
1404 - If we're a relay and we change our IP address, be more verbose
1405 about the reason that made us change. Should help track down
1406 further bugs for relays on dynamic IP addresses.
1409 Changes in version 0.2.0.35 - 2009-06-24
1411 - Avoid crashing in the presence of certain malformed descriptors.
1412 Found by lark, and by automated fuzzing.
1413 - Fix an edge case where a malicious exit relay could convince a
1414 controller that the client's DNS question resolves to an internal IP
1415 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1418 - Finally fix the bug where dynamic-IP relays disappear when their
1419 IP address changes: directory mirrors were mistakenly telling
1420 them their old address if they asked via begin_dir, so they
1421 never got an accurate answer about their new address, so they
1422 just vanished after a day. For belt-and-suspenders, relays that
1423 don't set Address in their config now avoid using begin_dir for
1424 all direct connections. Should fix bugs 827, 883, and 900.
1425 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1426 that would occur on some exit nodes when DNS failures and timeouts
1427 occurred in certain patterns. Fix for bug 957.
1430 - When starting with a cache over a few days old, do not leak
1431 memory for the obsolete router descriptors in it. Bugfix on
1432 0.2.0.33; fixes bug 672.
1433 - Hidden service clients didn't use a cached service descriptor that
1434 was older than 15 minutes, but wouldn't fetch a new one either,
1435 because there was already one in the cache. Now, fetch a v2
1436 descriptor unless the same descriptor was added to the cache within
1437 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1440 Changes in version 0.2.1.16-rc - 2009-06-20
1441 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
1442 a bunch of minor bugs.
1445 - Fix an edge case where a malicious exit relay could convince a
1446 controller that the client's DNS question resolves to an internal IP
1447 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1449 o Major performance improvements (on 0.2.0.x):
1450 - Disable and refactor some debugging checks that forced a linear scan
1451 over the whole server-side DNS cache. These accounted for over 50%
1452 of CPU time on a relatively busy exit node's gprof profile. Found
1454 - Disable some debugging checks that appeared in exit node profile
1458 - Update to the "June 3 2009" ip-to-country file.
1459 - Do not have tor-resolve automatically refuse all .onion addresses;
1460 if AutomapHostsOnResolve is set in your torrc, this will work fine.
1462 o Minor bugfixes (on 0.2.0.x):
1463 - Log correct error messages for DNS-related network errors on
1465 - Fix a race condition that could cause crashes or memory corruption
1466 when running as a server with a controller listening for log
1468 - Avoid crashing when we have a policy specified in a DirPolicy or
1469 SocksPolicy or ReachableAddresses option with ports set on it,
1470 and we re-load the policy. May fix bug 996.
1471 - Hidden service clients didn't use a cached service descriptor that
1472 was older than 15 minutes, but wouldn't fetch a new one either,
1473 because there was already one in the cache. Now, fetch a v2
1474 descriptor unless the same descriptor was added to the cache within
1475 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1477 o Minor bugfixes (on 0.2.1.x):
1478 - Don't warn users about low port and hibernation mix when they
1479 provide a *ListenAddress directive to fix that. Bugfix on
1481 - When switching back and forth between bridge mode, do not start
1482 gathering GeoIP data until two hours have passed.
1483 - Do not complain that the user has requested an excluded node as
1484 an exit when the node is not really an exit. This could happen
1485 because the circuit was for testing, or an introduction point.
1489 Changes in version 0.2.1.15-rc - 2009-05-25
1490 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
1491 series. It fixes a major bug on fast exit relays, as well as a variety
1494 o Major bugfixes (on 0.2.0.x):
1495 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1496 that would occur on some exit nodes when DNS failures and timeouts
1497 occurred in certain patterns. Fix for bug 957.
1499 o Minor bugfixes (on 0.2.0.x):
1500 - Actually return -1 in the error case for read_bandwidth_usage().
1501 Harmless bug, since we currently don't care about the return value
1502 anywhere. Bugfix on 0.2.0.9-alpha.
1503 - Provide a more useful log message if bug 977 (related to buffer
1504 freelists) ever reappears, and do not crash right away.
1505 - Fix an assertion failure on 64-bit platforms when we allocated
1506 memory right up to the end of a memarea, then realigned the memory
1507 one step beyond the end. Fixes a possible cause of bug 930.
1508 - Protect the count of open sockets with a mutex, so we can't
1509 corrupt it when two threads are closing or opening sockets at once.
1510 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
1511 - Don't allow a bridge to publish its router descriptor to a
1512 non-bridge directory authority. Fixes part of bug 932.
1513 - When we change to or from being a bridge, reset our counts of
1514 client usage by country. Fixes bug 932.
1515 - Fix a bug that made stream bandwidth get misreported to the
1517 - Stop using malloc_usable_size() to use more area than we had
1518 actually allocated: it was safe, but made valgrind really unhappy.
1519 - Fix a memory leak when v3 directory authorities load their keys
1520 and cert from disk. Bugfix on 0.2.0.1-alpha.
1522 o Minor bugfixes (on 0.2.1.x):
1523 - Fix use of freed memory when deciding to mark a non-addable
1524 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
1527 Changes in version 0.2.1.14-rc - 2009-04-12
1528 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
1529 series. It begins fixing some major performance problems, and also
1530 finally addresses the bug that was causing relays on dynamic IP
1531 addresses to fall out of the directory.
1534 - Clients replace entry guards that were chosen more than a few months
1535 ago. This change should significantly improve client performance,
1536 especially once more people upgrade, since relays that have been
1537 a guard for a long time are currently overloaded.
1539 o Major bugfixes (on 0.2.0):
1540 - Finally fix the bug where dynamic-IP relays disappear when their
1541 IP address changes: directory mirrors were mistakenly telling
1542 them their old address if they asked via begin_dir, so they
1543 never got an accurate answer about their new address, so they
1544 just vanished after a day. For belt-and-suspenders, relays that
1545 don't set Address in their config now avoid using begin_dir for
1546 all direct connections. Should fix bugs 827, 883, and 900.
1547 - Relays were falling out of the networkstatus consensus for
1548 part of a day if they changed their local config but the
1549 authorities discarded their new descriptor as "not sufficiently
1550 different". Now directory authorities accept a descriptor as changed
1551 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
1553 - Avoid crashing in the presence of certain malformed descriptors.
1554 Found by lark, and by automated fuzzing.
1557 - When generating circuit events with verbose nicknames for
1558 controllers, try harder to look up nicknames for routers on a
1559 circuit. (Previously, we would look in the router descriptors we had
1560 for nicknames, but not in the consensus.) Partial fix for bug 941.
1561 - If the bridge config line doesn't specify a port, assume 443.
1562 This makes bridge lines a bit smaller and easier for users to
1564 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
1565 bytes (aka 20KB/s), to match our documentation. Also update
1566 directory authorities so they always assign the Fast flag to relays
1567 with 20KB/s of capacity. Now people running relays won't suddenly
1568 find themselves not seeing any use, if the network gets faster
1570 - Update to the "April 3 2009" ip-to-country file.
1573 - Avoid trying to print raw memory to the logs when we decide to
1574 give up on downloading a given relay descriptor. Bugfix on
1576 - In tor-resolve, when the Tor client to use is specified by
1577 <hostname>:<port>, actually use the specified port rather than
1578 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
1579 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
1580 - When starting with a cache over a few days old, do not leak
1581 memory for the obsolete router descriptors in it. Bugfix on
1583 - Avoid double-free on list of successfully uploaded hidden
1584 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
1585 - Change memarea_strndup() implementation to work even when
1586 duplicating a string at the end of a page. This bug was
1587 harmless for now, but could have meant crashes later. Fix by
1588 lark. Bugfix on 0.2.1.1-alpha.
1589 - Limit uploaded directory documents to be 16M rather than 500K.
1590 The directory authorities were refusing v3 consensus votes from
1591 other authorities, since the votes are now 504K. Fixes bug 959;
1592 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
1593 - Directory authorities should never send a 503 "busy" response to
1594 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
1598 Changes in version 0.2.1.13-alpha - 2009-03-09
1599 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
1600 cleanups. We're finally getting close to a release candidate.
1603 - Correctly update the list of which countries we exclude as
1604 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
1605 lark. Bugfix on 0.2.1.6-alpha.
1607 o Minor bugfixes (on 0.2.0.x and earlier):
1608 - Automatically detect MacOSX versions earlier than 10.4.0, and
1609 disable kqueue from inside Tor when running with these versions.
1610 We previously did this from the startup script, but that was no
1611 help to people who didn't use the startup script. Resolves bug 863.
1612 - When we had picked an exit node for a connection, but marked it as
1613 "optional", and it turned out we had no onion key for the exit,
1614 stop wanting that exit and try again. This situation may not
1615 be possible now, but will probably become feasible with proposal
1616 158. Spotted by rovv. Fixes another case of bug 752.
1617 - Clients no longer cache certificates for authorities they do not
1618 recognize. Bugfix on 0.2.0.9-alpha.
1619 - When we can't transmit a DNS request due to a network error, retry
1620 it after a while, and eventually transmit a failing response to
1621 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
1622 - If the controller claimed responsibility for a stream, but that
1623 stream never finished making its connection, it would live
1624 forever in circuit_wait state. Now we close it after SocksTimeout
1625 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
1626 - Drop begin cells to a hidden service if they come from the middle
1627 of a circuit. Patch from lark.
1628 - When we erroneously receive two EXTEND cells for the same circuit
1629 ID on the same connection, drop the second. Patch from lark.
1630 - Fix a crash that occurs on exit nodes when a nameserver request
1631 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
1632 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
1634 - Do not assume that a stack-allocated character array will be
1635 64-bit aligned on platforms that demand that uint64_t access is
1636 aligned. Possible fix for bug 604.
1637 - Parse dates and IPv4 addresses in a locale- and libc-independent
1638 manner, to avoid platform-dependent behavior on malformed input.
1639 - Build correctly when configured to build outside the main source
1640 path. Patch from Michael Gold.
1641 - We were already rejecting relay begin cells with destination port
1642 of 0. Now also reject extend cells with destination port or address
1643 of 0. Suggested by lark.
1645 o Minor bugfixes (on 0.2.1.x):
1646 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
1647 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
1648 - If we're an exit node, scrub the IP address to which we are exiting
1649 in the logs. Bugfix on 0.2.1.8-alpha.
1652 - On Linux, use the prctl call to re-enable core dumps when the user
1654 - New controller event NEWCONSENSUS that lists the networkstatus
1655 lines for every recommended relay. Now controllers like Torflow
1656 can keep up-to-date on which relays they should be using.
1657 - Update to the "February 26 2009" ip-to-country file.
1660 Changes in version 0.2.0.34 - 2009-02-08
1661 Tor 0.2.0.34 features several more security-related fixes. You should
1662 upgrade, especially if you run an exit relay (remote crash) or a
1663 directory authority (remote infinite loop), or you're on an older
1664 (pre-XP) or not-recently-patched Windows (remote exploit).
1666 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
1667 have many known flaws, and nobody should be using them. You should
1668 upgrade. If you're using a Linux or BSD and its packages are obsolete,
1669 stop using those packages and upgrade anyway.
1672 - Fix an infinite-loop bug on handling corrupt votes under certain
1673 circumstances. Bugfix on 0.2.0.8-alpha.
1674 - Fix a temporary DoS vulnerability that could be performed by
1675 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1676 - Avoid a potential crash on exit nodes when processing malformed
1677 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
1678 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1679 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1682 - Fix compilation on systems where time_t is a 64-bit integer.
1683 Patch from Matthias Drochner.
1684 - Don't consider expiring already-closed client connections. Fixes
1685 bug 893. Bugfix on 0.0.2pre20.
1688 Changes in version 0.2.1.12-alpha - 2009-02-08
1689 Tor 0.2.1.12-alpha features several more security-related fixes. You
1690 should upgrade, especially if you run an exit relay (remote crash) or
1691 a directory authority (remote infinite loop), or you're on an older
1692 (pre-XP) or not-recently-patched Windows (remote exploit). It also
1693 includes a big pile of minor bugfixes and cleanups.
1696 - Fix an infinite-loop bug on handling corrupt votes under certain
1697 circumstances. Bugfix on 0.2.0.8-alpha.
1698 - Fix a temporary DoS vulnerability that could be performed by
1699 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1700 - Avoid a potential crash on exit nodes when processing malformed
1701 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
1704 - Let controllers actually ask for the "clients_seen" event for
1705 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
1706 reported by Matt Edman.
1707 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
1709 - Fix a bug in address parsing that was preventing bridges or hidden
1710 service targets from being at IPv6 addresses.
1711 - Solve a bug that kept hardware crypto acceleration from getting
1712 enabled when accounting was turned on. Fixes bug 907. Bugfix on
1714 - Remove a bash-ism from configure.in to build properly on non-Linux
1715 platforms. Bugfix on 0.2.1.1-alpha.
1716 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
1717 headers. Bugfix on 0.2.0.10-alpha.
1718 - Don't consider expiring already-closed client connections. Fixes
1719 bug 893. Bugfix on 0.0.2pre20.
1720 - Fix another interesting corner-case of bug 891 spotted by rovv:
1721 Previously, if two hosts had different amounts of clock drift, and
1722 one of them created a new connection with just the wrong timing,
1723 the other might decide to deprecate the new connection erroneously.
1724 Bugfix on 0.1.1.13-alpha.
1725 - Resolve a very rare crash bug that could occur when the user forced
1726 a nameserver reconfiguration during the middle of a nameserver
1727 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
1728 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
1729 Bugfix on 0.2.1.7-alpha.
1730 - If we're using bridges and our network goes away, be more willing
1731 to forgive our bridges and try again when we get an application
1732 request. Bugfix on 0.2.0.x.
1735 - Support platforms where time_t is 64 bits long. (Congratulations,
1736 NetBSD!) Patch from Matthias Drochner.
1737 - Add a 'getinfo status/clients-seen' controller command, in case
1738 controllers want to hear clients_seen events but connect late.
1741 - Disable GCC's strict alias optimization by default, to avoid the
1742 likelihood of its introducing subtle bugs whenever our code violates
1743 the letter of C99's alias rules.
1746 Changes in version 0.2.0.33 - 2009-01-21
1747 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
1748 useful to users. It also finally fixes a bug where a relay or client
1749 that's been off for many days would take a long time to bootstrap.
1751 This update also fixes an important security-related bug reported by
1752 Ilja van Sprundel. You should upgrade. (We'll send out more details
1753 about the bug once people have had some time to upgrade.)
1756 - Fix a heap-corruption bug that may be remotely triggerable on
1757 some platforms. Reported by Ilja van Sprundel.
1760 - When a stream at an exit relay is in state "resolving" or
1761 "connecting" and it receives an "end" relay cell, the exit relay
1762 would silently ignore the end cell and not close the stream. If
1763 the client never closes the circuit, then the exit relay never
1764 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
1766 - When sending CREATED cells back for a given circuit, use a 64-bit
1767 connection ID to find the right connection, rather than an addr:port
1768 combination. Now that we can have multiple OR connections between
1769 the same ORs, it is no longer possible to use addr:port to uniquely
1770 identify a connection.
1771 - Bridge relays that had DirPort set to 0 would stop fetching
1772 descriptors shortly after startup, and then briefly resume
1773 after a new bandwidth test and/or after publishing a new bridge
1774 descriptor. Bridge users that try to bootstrap from them would
1775 get a recent networkstatus but would get descriptors from up to
1776 18 hours earlier, meaning most of the descriptors were obsolete
1777 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1778 - Prevent bridge relays from serving their 'extrainfo' document
1779 to anybody who asks, now that extrainfo docs include potentially
1780 sensitive aggregated client geoip summaries. Bugfix on
1782 - If the cached networkstatus consensus is more than five days old,
1783 discard it rather than trying to use it. In theory it could be
1784 useful because it lists alternate directory mirrors, but in practice
1785 it just means we spend many minutes trying directory mirrors that
1786 are long gone from the network. Also discard router descriptors as
1787 we load them if they are more than five days old, since the onion
1788 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
1791 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1792 could make gcc generate non-functional binary search code. Bugfix
1794 - Build correctly on platforms without socklen_t.
1795 - Compile without warnings on solaris.
1796 - Avoid potential crash on internal error during signature collection.
1797 Fixes bug 864. Patch from rovv.
1798 - Correct handling of possible malformed authority signing key
1799 certificates with internal signature types. Fixes bug 880.
1800 Bugfix on 0.2.0.3-alpha.
1801 - Fix a hard-to-trigger resource leak when logging credential status.
1803 - When we can't initialize DNS because the network is down, do not
1804 automatically stop Tor from starting. Instead, we retry failed
1805 dns_init() every 10 minutes, and change the exit policy to reject
1806 *:* until one succeeds. Fixes bug 691.
1807 - Use 64 bits instead of 32 bits for connection identifiers used with
1808 the controller protocol, to greatly reduce risk of identifier reuse.
1809 - When we're choosing an exit node for a circuit, and we have
1810 no pending streams, choose a good general exit rather than one that
1811 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1812 - Fix another case of assuming, when a specific exit is requested,
1813 that we know more than the user about what hosts it allows.
1814 Fixes one case of bug 752. Patch from rovv.
1815 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1816 seconds. Warn the user if lower values are given in the
1817 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1818 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1819 user if lower values are given in the configuration. Bugfix on
1820 0.1.1.17-rc. Patch by Sebastian.
1821 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
1822 the cache because we already had a v0 descriptor with the same ID.
1823 Bugfix on 0.2.0.18-alpha.
1824 - Fix a race condition when freeing keys shared between main thread
1825 and CPU workers that could result in a memory leak. Bugfix on
1826 0.1.0.1-rc. Fixes bug 889.
1827 - Send a valid END cell back when a client tries to connect to a
1828 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1829 840. Patch from rovv.
1830 - Check which hops rendezvous stream cells are associated with to
1831 prevent possible guess-the-streamid injection attacks from
1832 intermediate hops. Fixes another case of bug 446. Based on patch
1834 - If a broken client asks a non-exit router to connect somewhere,
1835 do not even do the DNS lookup before rejecting the connection.
1836 Fixes another case of bug 619. Patch from rovv.
1837 - When a relay gets a create cell it can't decrypt (e.g. because it's
1838 using the wrong onion key), we were dropping it and letting the
1839 client time out. Now actually answer with a destroy cell. Fixes
1840 bug 904. Bugfix on 0.0.2pre8.
1842 o Minor bugfixes (hidden services):
1843 - Do not throw away existing introduction points on SIGHUP. Bugfix on
1844 0.0.6pre1. Patch by Karsten. Fixes bug 874.
1847 - Report the case where all signatures in a detached set are rejected
1848 differently than the case where there is an error handling the
1850 - When we realize that another process has modified our cached
1851 descriptors, print out a more useful error message rather than
1852 triggering an assertion. Fixes bug 885. Patch from Karsten.
1853 - Implement the 0x20 hack to better resist DNS poisoning: set the
1854 case on outgoing DNS requests randomly, and reject responses that do
1855 not match the case correctly. This logic can be disabled with the
1856 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
1857 of servers that do not reliably preserve case in replies. See
1858 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1860 - Check DNS replies for more matching fields to better resist DNS
1862 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1863 compress cells, which are basically all encrypted, compressed, or
1867 Changes in version 0.2.1.11-alpha - 2009-01-20
1868 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
1869 week it will take a long time to bootstrap again" bug. It also fixes
1870 an important security-related bug reported by Ilja van Sprundel. You
1871 should upgrade. (We'll send out more details about the bug once people
1872 have had some time to upgrade.)
1875 - Fix a heap-corruption bug that may be remotely triggerable on
1876 some platforms. Reported by Ilja van Sprundel.
1879 - Discard router descriptors as we load them if they are more than
1880 five days old. Otherwise if Tor is off for a long time and then
1881 starts with cached descriptors, it will try to use the onion
1882 keys in those obsolete descriptors when building circuits. Bugfix
1883 on 0.2.0.x. Fixes bug 887.
1886 - Try to make sure that the version of Libevent we're running with
1887 is binary-compatible with the one we built with. May address bug
1889 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
1890 for bug 905. Bugfix on 0.2.1.7-alpha.
1891 - Add a new --enable-local-appdata configuration switch to change
1892 the default location of the datadir on win32 from APPDATA to
1893 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
1894 entirely. Patch from coderman.
1897 - Make outbound DNS packets respect the OutboundBindAddress setting.
1898 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
1899 - When our circuit fails at the first hop (e.g. we get a destroy
1900 cell back), avoid using that OR connection anymore, and also
1901 tell all the one-hop directory requests waiting for it that they
1902 should fail. Bugfix on 0.2.1.3-alpha.
1903 - In the torify(1) manpage, mention that tsocks will leak your
1907 Changes in version 0.2.1.10-alpha - 2009-01-06
1908 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
1909 would make the bridge relay not so useful if it had DirPort set to 0,
1910 and one that could let an attacker learn a little bit of information
1911 about the bridge's users), and a bug that would cause your Tor relay
1912 to ignore a circuit create request it can't decrypt (rather than reply
1913 with an error). It also fixes a wide variety of other bugs.
1916 - If the cached networkstatus consensus is more than five days old,
1917 discard it rather than trying to use it. In theory it could
1918 be useful because it lists alternate directory mirrors, but in
1919 practice it just means we spend many minutes trying directory
1920 mirrors that are long gone from the network. Helps bug 887 a bit;
1922 - Bridge relays that had DirPort set to 0 would stop fetching
1923 descriptors shortly after startup, and then briefly resume
1924 after a new bandwidth test and/or after publishing a new bridge
1925 descriptor. Bridge users that try to bootstrap from them would
1926 get a recent networkstatus but would get descriptors from up to
1927 18 hours earlier, meaning most of the descriptors were obsolete
1928 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1929 - Prevent bridge relays from serving their 'extrainfo' document
1930 to anybody who asks, now that extrainfo docs include potentially
1931 sensitive aggregated client geoip summaries. Bugfix on
1935 - New controller event "clients_seen" to report a geoip-based summary
1936 of which countries we've seen clients from recently. Now controllers
1937 like Vidalia can show bridge operators that they're actually making
1939 - Build correctly against versions of OpenSSL 0.9.8 or later built
1940 without support for deprecated functions.
1941 - Update to the "December 19 2008" ip-to-country file.
1943 o Minor bugfixes (on 0.2.0.x):
1944 - Authorities now vote for the Stable flag for any router whose
1945 weighted MTBF is at least 5 days, regardless of the mean MTBF.
1946 - Do not remove routers as too old if we do not have any consensus
1947 document. Bugfix on 0.2.0.7-alpha.
1948 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1949 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1950 - When an exit relay resolves a stream address to a local IP address,
1951 do not just keep retrying that same exit relay over and
1952 over. Instead, just close the stream. Addresses bug 872. Bugfix
1953 on 0.2.0.32. Patch from rovv.
1954 - If a hidden service sends us an END cell, do not consider
1955 retrying the connection; just close it. Patch from rovv.
1956 - When we made bridge authorities stop serving bridge descriptors over
1957 unencrypted links, we also broke DirPort reachability testing for
1958 bridges. So bridges with a non-zero DirPort were printing spurious
1959 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
1960 - When a relay gets a create cell it can't decrypt (e.g. because it's
1961 using the wrong onion key), we were dropping it and letting the
1962 client time out. Now actually answer with a destroy cell. Fixes
1963 bug 904. Bugfix on 0.0.2pre8.
1964 - Squeeze 2-5% out of client performance (according to oprofile) by
1965 improving the implementation of some policy-manipulation functions.
1967 o Minor bugfixes (on 0.2.1.x):
1968 - Make get_interface_address() function work properly again; stop
1969 guessing the wrong parts of our address as our address.
1970 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
1971 send on that circuit. Otherwise we might violate the proposal-110
1972 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
1974 - When we're sending non-EXTEND cells to the first hop in a circuit,
1975 for example to use an encrypted directory connection, we don't need
1976 to use RELAY_EARLY cells: the first hop knows what kind of cell
1977 it is, and nobody else can even see the cell type. Conserving
1978 RELAY_EARLY cells makes it easier to cannibalize circuits like
1980 - Stop logging nameserver addresses in reverse order.
1981 - If we are retrying a directory download slowly over and over, do
1982 not automatically give up after the 254th failure. Bugfix on
1984 - Resume reporting accurate "stream end" reasons to the local control
1985 port. They were lost in the changes for Proposal 148. Bugfix on
1988 o Deprecated and removed features:
1989 - The old "tor --version --version" command, which would print out
1990 the subversion "Id" of most of the source files, is now removed. It
1991 turned out to be less useful than we'd expected, and harder to
1994 o Code simplifications and refactoring:
1995 - Change our header file guard macros to be less likely to conflict
1996 with system headers. Adam Langley noticed that we were conflicting
1997 with log.h on Android.
1998 - Tool-assisted documentation cleanup. Nearly every function or
1999 static variable in Tor should have its own documentation now.
2002 Changes in version 0.2.1.9-alpha - 2008-12-25
2003 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
2005 o New directory authorities:
2006 - gabelmoo (the authority run by Karsten Loesing) now has a new
2010 - Never use a connection with a mismatched address to extend a
2011 circuit, unless that connection is canonical. A canonical
2012 connection is one whose address is authenticated by the router's
2013 identity key, either in a NETINFO cell or in a router descriptor.
2014 - Avoid a possible memory corruption bug when receiving hidden service
2015 descriptors. Bugfix on 0.2.1.6-alpha.
2018 - Fix a logic error that would automatically reject all but the first
2019 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
2020 part of bug 813/868. Bug spotted by coderman.
2021 - When a stream at an exit relay is in state "resolving" or
2022 "connecting" and it receives an "end" relay cell, the exit relay
2023 would silently ignore the end cell and not close the stream. If
2024 the client never closes the circuit, then the exit relay never
2025 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
2027 - When we can't initialize DNS because the network is down, do not
2028 automatically stop Tor from starting. Instead, retry failed
2029 dns_init() every 10 minutes, and change the exit policy to reject
2030 *:* until one succeeds. Fixes bug 691.
2033 - Give a better error message when an overzealous init script says
2034 "sudo -u username tor --user username". Makes Bug 882 easier for
2036 - When a directory authority gives us a new guess for our IP address,
2037 log which authority we used. Hopefully this will help us debug
2038 the recent complaints about bad IP address guesses.
2039 - Detect svn revision properly when we're using git-svn.
2040 - Try not to open more than one descriptor-downloading connection
2041 to an authority at once. This should reduce load on directory
2042 authorities. Fixes bug 366.
2043 - Add cross-certification to newly generated certificates, so that
2044 a signing key is enough information to look up a certificate.
2045 Partial implementation of proposal 157.
2046 - Start serving certificates by <identity digest, signing key digest>
2047 pairs. Partial implementation of proposal 157.
2048 - Clients now never report any stream end reason except 'MISC'.
2049 Implements proposal 148.
2050 - On platforms with a maximum syslog string length, truncate syslog
2051 messages to that length ourselves, rather than relying on the
2052 system to do it for us.
2053 - Optimize out calls to time(NULL) that occur for every IO operation,
2054 or for every cell. On systems where time() is a slow syscall,
2055 this fix will be slightly helpful.
2056 - Exit servers can now answer resolve requests for ip6.arpa addresses.
2057 - When we download a descriptor that we then immediately (as
2058 a directory authority) reject, do not retry downloading it right
2059 away. Should save some bandwidth on authorities. Fix for bug
2060 888. Patch by Sebastian Hahn.
2061 - When a download gets us zero good descriptors, do not notify
2062 Tor that new directory information has arrived.
2063 - Avoid some nasty corner cases in the logic for marking connections
2064 as too old or obsolete or noncanonical for circuits. Partial
2067 o Minor features (controller):
2068 - New CONSENSUS_ARRIVED event to note when a new consensus has
2069 been fetched and validated.
2070 - When we realize that another process has modified our cached
2071 descriptors file, print out a more useful error message rather
2072 than triggering an assertion. Fixes bug 885. Patch from Karsten.
2073 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
2074 controllers to prevent SIGHUP from reloading the
2075 configuration. Fixes bug 856.
2078 - Resume using the correct "REASON=" stream when telling the
2079 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
2080 - When a canonical connection appears later in our internal list
2081 than a noncanonical one for a given OR ID, always use the
2082 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
2084 - Clip the MaxCircuitDirtiness config option to a minimum of 10
2085 seconds. Warn the user if lower values are given in the
2086 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
2087 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
2088 user if lower values are given in the configuration. Bugfix on
2089 0.1.1.17-rc. Patch by Sebastian.
2090 - Fix a race condition when freeing keys shared between main thread
2091 and CPU workers that could result in a memory leak. Bugfix on
2092 0.1.0.1-rc. Fixes bug 889.
2094 o Minor bugfixes (hidden services):
2095 - Do not throw away existing introduction points on SIGHUP (bugfix on
2096 0.0.6pre1); also, do not stall hidden services because we're
2097 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
2098 by John Brooks. Patch by Karsten. Fixes bug 874.
2099 - Fix a memory leak when we decline to add a v2 rendezvous
2100 descriptor to the cache because we already had a v0 descriptor
2101 with the same ID. Bugfix on 0.2.0.18-alpha.
2103 o Deprecated and removed features:
2104 - RedirectExits has been removed. It was deprecated since
2106 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
2107 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
2108 - Cell pools are now always enabled; --disable-cell-pools is ignored.
2110 o Code simplifications and refactoring:
2111 - Rename the confusing or_is_obsolete field to the more appropriate
2112 is_bad_for_new_circs, and move it to or_connection_t where it
2114 - Move edge-only flags from connection_t to edge_connection_t: not
2115 only is this better coding, but on machines of plausible alignment,
2116 it should save 4-8 bytes per connection_t. "Every little bit helps."
2117 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
2118 for consistency; keep old option working for backward compatibility.
2119 - Simplify the code for finding connections to use for a circuit.
2122 Changes in version 0.2.1.8-alpha - 2008-12-08
2123 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
2124 builds better on unusual platforms like Solaris and old OS X, and
2125 fixes a variety of other issues.
2128 - New DirPortFrontPage option that takes an html file and publishes
2129 it as "/" on the DirPort. Now relay operators can provide a
2130 disclaimer without needing to set up a separate webserver. There's
2131 a sample disclaimer in contrib/tor-exit-notice.html.
2134 - When the client is choosing entry guards, now it selects at most
2135 one guard from a given relay family. Otherwise we could end up with
2136 all of our entry points into the network run by the same operator.
2137 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
2140 - Fix a DOS opportunity during the voting signature collection process
2141 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2142 - Fix a possible segfault when establishing an exit connection. Bugfix
2146 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
2148 - Made Tor a little less aggressive about deleting expired
2149 certificates. Partial fix for bug 854.
2150 - Stop doing unaligned memory access that generated bus errors on
2151 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
2152 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
2153 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
2154 - Make USR2 log-level switch take effect immediately. Bugfix on
2156 - If one win32 nameserver fails to get added, continue adding the
2157 rest, and don't automatically fail.
2158 - Use fcntl() for locking when flock() is not available. Should fix
2159 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
2160 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2161 could make gcc generate non-functional binary search code. Bugfix
2163 - Build correctly on platforms without socklen_t.
2164 - Avoid potential crash on internal error during signature collection.
2165 Fixes bug 864. Patch from rovv.
2166 - Do not use C's stdio library for writing to log files. This will
2167 improve logging performance by a minute amount, and will stop
2168 leaking fds when our disk is full. Fixes bug 861.
2169 - Stop erroneous use of O_APPEND in cases where we did not in fact
2170 want to re-seek to the end of a file before every last write().
2171 - Correct handling of possible malformed authority signing key
2172 certificates with internal signature types. Fixes bug 880. Bugfix
2174 - Fix a hard-to-trigger resource leak when logging credential status.
2178 - Directory mirrors no longer fetch the v1 directory or
2179 running-routers files. They are obsolete, and nobody asks for them
2180 anymore. This is the first step to making v1 authorities obsolete.
2182 o Minor features (controller):
2183 - Return circuit purposes in response to GETINFO circuit-status. Fixes
2187 Changes in version 0.2.0.32 - 2008-11-20
2188 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
2189 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2190 a smaller security flaw that might allow an attacker to access local
2191 services, further improves hidden service performance, and fixes a
2192 variety of other issues.
2195 - The "User" and "Group" config options did not clear the
2196 supplementary group entries for the Tor process. The "User" option
2197 is now more robust, and we now set the groups to the specified
2198 user's primary group. The "Group" option is now ignored. For more
2199 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2200 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2201 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
2202 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2203 consistently obeyed: if an exit relay refuses a stream because its
2204 exit policy doesn't allow it, we would remember what IP address
2205 the relay said the destination address resolves to, even if it's
2206 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2209 - Fix a DOS opportunity during the voting signature collection process
2210 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2212 o Major bugfixes (hidden services):
2213 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2214 we were failing the whole hidden service request when the v0
2215 descriptor fetch fails, even if the v2 fetch is still pending and
2216 might succeed. Similarly, if the last v2 fetch fails, we were
2217 failing the whole hidden service request even if a v0 fetch is
2218 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2219 - When extending a circuit to a hidden service directory to upload a
2220 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2221 requests failed, because the router descriptor has not been
2222 downloaded yet. In these cases, do not attempt to upload the
2223 rendezvous descriptor, but wait until the router descriptor is
2224 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
2225 descriptor from a hidden service directory for which the router
2226 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
2230 - Fix several infrequent memory leaks spotted by Coverity.
2231 - When testing for libevent functions, set the LDFLAGS variable
2232 correctly. Found by Riastradh.
2233 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2234 bootstrapping with tunneled directory connections. Bugfix on
2235 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2236 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2237 and we know that server B rejects most-but-not all connections to
2238 port 80, we would previously reject the connection. Now, we assume
2239 the user knows what they were asking for. Fixes bug 752. Bugfix
2240 on 0.0.9rc5. Diagnosed by BarkerJr.
2241 - If we overrun our per-second write limits a little, count this as
2242 having used up our write allocation for the second, and choke
2243 outgoing directory writes. Previously, we had only counted this when
2244 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
2245 Bugfix on 0.2.0.x (??).
2246 - Remove the old v2 directory authority 'lefkada' from the default
2247 list. It has been gone for many months.
2248 - Stop doing unaligned memory access that generated bus errors on
2249 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
2250 - Make USR2 log-level switch take effect immediately. Bugfix on
2253 o Minor bugfixes (controller):
2254 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
2255 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
2258 Changes in version 0.2.1.7-alpha - 2008-11-08
2259 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
2260 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2261 a smaller security flaw that might allow an attacker to access local
2262 services, adds better defense against DNS poisoning attacks on exit
2263 relays, further improves hidden service performance, and fixes a
2264 variety of other issues.
2267 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2268 consistently obeyed: if an exit relay refuses a stream because its
2269 exit policy doesn't allow it, we would remember what IP address
2270 the relay said the destination address resolves to, even if it's
2271 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2272 - The "User" and "Group" config options did not clear the
2273 supplementary group entries for the Tor process. The "User" option
2274 is now more robust, and we now set the groups to the specified
2275 user's primary group. The "Group" option is now ignored. For more
2276 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2277 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2278 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
2279 - Do not use or believe expired v3 authority certificates. Patch
2280 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
2283 - Now NodeFamily and MyFamily config options allow spaces in
2284 identity fingerprints, so it's easier to paste them in.
2285 Suggested by Lucky Green.
2286 - Implement the 0x20 hack to better resist DNS poisoning: set the
2287 case on outgoing DNS requests randomly, and reject responses that do
2288 not match the case correctly. This logic can be disabled with the
2289 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
2290 of servers that do not reliably preserve case in replies. See
2291 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2293 - Preserve case in replies to DNSPort requests in order to support
2294 the 0x20 hack for resisting DNS poisoning attacks.
2296 o Hidden service performance improvements:
2297 - When the client launches an introduction circuit, retry with a
2298 new circuit after 30 seconds rather than 60 seconds.
2299 - Launch a second client-side introduction circuit in parallel
2300 after a delay of 15 seconds (based on work by Christian Wilms).
2301 - Hidden services start out building five intro circuits rather
2302 than three, and when the first three finish they publish a service
2303 descriptor using those. Now we publish our service descriptor much
2304 faster after restart.
2307 - Minor fix in the warning messages when you're having problems
2308 bootstrapping; also, be more forgiving of bootstrap problems when
2309 we're still making incremental progress on a given bootstrap phase.
2310 - When we're choosing an exit node for a circuit, and we have
2311 no pending streams, choose a good general exit rather than one that
2312 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2313 - Send a valid END cell back when a client tries to connect to a
2314 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2315 840. Patch from rovv.
2316 - If a broken client asks a non-exit router to connect somewhere,
2317 do not even do the DNS lookup before rejecting the connection.
2318 Fixes another case of bug 619. Patch from rovv.
2319 - Fix another case of assuming, when a specific exit is requested,
2320 that we know more than the user about what hosts it allows.
2321 Fixes another case of bug 752. Patch from rovv.
2322 - Check which hops rendezvous stream cells are associated with to
2323 prevent possible guess-the-streamid injection attacks from
2324 intermediate hops. Fixes another case of bug 446. Based on patch
2326 - Avoid using a negative right-shift when comparing 32-bit
2327 addresses. Possible fix for bug 845 and bug 811.
2328 - Make the assert_circuit_ok() function work correctly on circuits that
2329 have already been marked for close.
2330 - Fix read-off-the-end-of-string error in unit tests when decoding
2331 introduction points.
2332 - Fix uninitialized size field for memory area allocation: may improve
2333 memory performance during directory parsing.
2334 - Treat duplicate certificate fetches as failures, so that we do
2335 not try to re-fetch an expired certificate over and over and over.
2336 - Do not say we're fetching a certificate when we'll in fact skip it
2337 because of a pending download.
2340 Changes in version 0.2.1.6-alpha - 2008-09-30
2341 Tor 0.2.1.6-alpha further improves performance and robustness of
2342 hidden services, starts work on supporting per-country relay selection,
2343 and fixes a variety of smaller issues.
2346 - Implement proposal 121: make it possible to build hidden services
2347 that only certain clients are allowed to connect to. This is
2348 enforced at several points, so that unauthorized clients are unable
2349 to send INTRODUCE cells to the service, or even (depending on the
2350 type of authentication) to learn introduction points. This feature
2351 raises the bar for certain kinds of active attacks against hidden
2352 services. Code by Karsten Loesing.
2353 - Relays now store and serve v2 hidden service descriptors by default,
2354 i.e., the new default value for HidServDirectoryV2 is 1. This is
2355 the last step in proposal 114, which aims to make hidden service
2356 lookups more reliable.
2357 - Start work to allow node restrictions to include country codes. The
2358 syntax to exclude nodes in a country with country code XX is
2359 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
2360 refinement to decide what config options should take priority if
2361 you ask to both use a particular node and exclude it.
2362 - Allow ExitNodes list to include IP ranges and country codes, just
2363 like the Exclude*Nodes lists. Patch from Robert Hogan.
2366 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
2367 Tor to fail to start if you had it configured to use a bridge
2368 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
2369 - When extending a circuit to a hidden service directory to upload a
2370 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2371 requests failed, because the router descriptor had not been
2372 downloaded yet. In these cases, we now wait until the router
2373 descriptor is downloaded, and then retry. Likewise, clients
2374 now skip over a hidden service directory if they don't yet have
2375 its router descriptor, rather than futilely requesting it and
2376 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
2378 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2379 we were failing the whole hidden service request when the v0
2380 descriptor fetch fails, even if the v2 fetch is still pending and
2381 might succeed. Similarly, if the last v2 fetch fails, we were
2382 failing the whole hidden service request even if a v0 fetch is
2383 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2384 - DNS replies need to have names matching their requests, but
2385 these names should be in the questions section, not necessarily
2386 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
2389 - Update to the "September 1 2008" ip-to-country file.
2390 - Allow ports 465 and 587 in the default exit policy again. We had
2391 rejected them in 0.1.0.15, because back in 2005 they were commonly
2392 misconfigured and ended up as spam targets. We hear they are better
2393 locked down these days.
2394 - Use a lockfile to make sure that two Tor processes are not
2395 simultaneously running with the same datadir.
2396 - Serve the latest v3 networkstatus consensus via the control
2397 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2398 - Better logging about stability/reliability calculations on directory
2400 - Drop the requirement to have an open dir port for storing and
2401 serving v2 hidden service descriptors.
2402 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2403 help debug WFU and MTBF calculations.
2404 - Implement most of Proposal 152: allow specialized servers to permit
2405 single-hop circuits, and clients to use those servers to build
2406 single-hop circuits when using a specialized controller. Patch
2407 from Josh Albrecht. Resolves feature request 768.
2408 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2409 people find host:port too confusing.
2410 - Make TrackHostExit mappings expire a while after their last use, not
2411 after their creation. Patch from Robert Hogan.
2412 - Provide circuit purposes along with circuit events to the controller.
2415 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
2417 - Fixed some memory leaks -- some quite frequent, some almost
2418 impossible to trigger -- based on results from Coverity.
2419 - When testing for libevent functions, set the LDFLAGS variable
2420 correctly. Found by Riastradh.
2421 - Fix an assertion bug in parsing policy-related options; possible fix
2423 - Catch and report a few more bootstrapping failure cases when Tor
2424 fails to establish a TCP connection. Cleanup on 0.2.1.x.
2425 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2426 bootstrapping with tunneled directory connections. Bugfix on
2427 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2428 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2429 and we know that server B rejects most-but-not all connections to
2430 port 80, we would previously reject the connection. Now, we assume
2431 the user knows what they were asking for. Fixes bug 752. Bugfix
2432 on 0.0.9rc5. Diagnosed by BarkerJr.
2433 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2434 service directories if they have no advertised dir port. Bugfix
2436 - If we overrun our per-second write limits a little, count this as
2437 having used up our write allocation for the second, and choke
2438 outgoing directory writes. Previously, we had only counted this when
2439 we had met our limits precisely. Fixes bug 824. Patch by rovv.
2440 Bugfix on 0.2.0.x (??).
2441 - Avoid a "0 divided by 0" calculation when calculating router uptime
2442 at directory authorities. Bugfix on 0.2.0.8-alpha.
2443 - Make DNS resolved controller events into "CLOSED", not
2444 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2446 - Fix a bug where an unreachable relay would establish enough
2447 reachability testing circuits to do a bandwidth test -- if
2448 we already have a connection to the middle hop of the testing
2449 circuit, then it could establish the last hop by using the existing
2450 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2451 circuits no longer use entry guards in 0.2.1.3-alpha.
2452 - If we have correct permissions on $datadir, we complain to stdout
2453 and fail to start. But dangerous permissions on
2454 $datadir/cached-status/ would cause us to open a log and complain
2455 there. Now complain to stdout and fail to start in both cases. Fixes
2456 bug 820, reported by seeess.
2457 - Remove the old v2 directory authority 'lefkada' from the default
2458 list. It has been gone for many months.
2460 o Code simplifications and refactoring:
2461 - Revise the connection_new functions so that a more typesafe variant
2462 exists. This will work better with Coverity, and let us find any
2463 actual mistakes we're making here.
2464 - Refactor unit testing logic so that dmalloc can be used sensibly
2465 with unit tests to check for memory leaks.
2466 - Move all hidden-service related fields from connection and circuit
2467 structure to substructures: this way they won't eat so much memory.
2470 Changes in version 0.2.0.31 - 2008-09-03
2471 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
2472 a big bug we're seeing where in rare cases traffic from one Tor stream
2473 gets mixed into another stream, and fixes a variety of smaller issues.
2476 - Make sure that two circuits can never exist on the same connection
2477 with the same circuit ID, even if one is marked for close. This
2478 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
2479 - Relays now reject risky extend cells: if the extend cell includes
2480 a digest of all zeroes, or asks to extend back to the relay that
2481 sent the extend cell, tear down the circuit. Ideas suggested
2483 - If not enough of our entry guards are available so we add a new
2484 one, we might use the new one even if it overlapped with the
2485 current circuit's exit relay (or its family). Anonymity bugfix
2486 pointed out by rovv.
2489 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2490 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2491 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2492 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2493 - Pick size of default geoip filename string correctly on windows.
2494 Fixes bug 806. Bugfix on 0.2.0.30.
2495 - Make the autoconf script accept the obsolete --with-ssl-dir
2496 option as an alias for the actually-working --with-openssl-dir
2497 option. Fix the help documentation to recommend --with-openssl-dir.
2498 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2499 - When using the TransPort option on OpenBSD, and using the User
2500 option to change UID and drop privileges, make sure to open
2501 /dev/pf before dropping privileges. Fixes bug 782. Patch from
2502 Christopher Davis. Bugfix on 0.1.2.1-alpha.
2503 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2504 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2505 on the client side when connecting to a hidden service. Bugfix
2506 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2507 - When closing an application-side connection because its circuit is
2508 getting torn down, generate the stream event correctly. Bugfix on
2509 0.1.2.x. Anonymous patch.
2512 Changes in version 0.2.1.5-alpha - 2008-08-31
2513 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
2514 in a lot of the infrastructure for adding authorization to hidden
2515 services, lays the groundwork for having clients read their load
2516 balancing information out of the networkstatus consensus rather than
2517 the individual router descriptors, addresses two potential anonymity
2518 issues, and fixes a variety of smaller issues.
2521 - Convert many internal address representations to optionally hold
2523 - Generate and accept IPv6 addresses in many protocol elements.
2524 - Make resolver code handle nameservers located at ipv6 addresses.
2525 - Begin implementation of proposal 121 ("Client authorization for
2526 hidden services"): configure hidden services with client
2527 authorization, publish descriptors for them, and configure
2528 authorization data for hidden services at clients. The next
2529 step is to actually access hidden services that perform client
2531 - More progress toward proposal 141: Network status consensus
2532 documents and votes now contain bandwidth information for each
2533 router and a summary of that router's exit policy. Eventually this
2534 will be used by clients so that they do not have to download every
2535 known descriptor before building circuits.
2537 o Major bugfixes (on 0.2.0.x and before):
2538 - When sending CREATED cells back for a given circuit, use a 64-bit
2539 connection ID to find the right connection, rather than an addr:port
2540 combination. Now that we can have multiple OR connections between
2541 the same ORs, it is no longer possible to use addr:port to uniquely
2542 identify a connection.
2543 - Relays now reject risky extend cells: if the extend cell includes
2544 a digest of all zeroes, or asks to extend back to the relay that
2545 sent the extend cell, tear down the circuit. Ideas suggested
2547 - If not enough of our entry guards are available so we add a new
2548 one, we might use the new one even if it overlapped with the
2549 current circuit's exit relay (or its family). Anonymity bugfix
2550 pointed out by rovv.
2553 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2554 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2555 - When using the TransPort option on OpenBSD, and using the User
2556 option to change UID and drop privileges, make sure to open /dev/pf
2557 before dropping privileges. Fixes bug 782. Patch from Christopher
2558 Davis. Bugfix on 0.1.2.1-alpha.
2559 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2560 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2561 - Add a missing safe_str() call for a debug log message.
2562 - Use 64 bits instead of 32 bits for connection identifiers used with
2563 the controller protocol, to greatly reduce risk of identifier reuse.
2564 - Make the autoconf script accept the obsolete --with-ssl-dir
2565 option as an alias for the actually-working --with-openssl-dir
2566 option. Fix the help documentation to recommend --with-openssl-dir.
2567 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2570 - Rate-limit too-many-sockets messages: when they happen, they happen
2571 a lot. Resolves bug 748.
2572 - Resist DNS poisoning a little better by making sure that names in
2573 answer sections match.
2574 - Print the SOCKS5 error message string as well as the error code
2575 when a tor-resolve request fails. Patch from Jacob.
2578 Changes in version 0.2.1.4-alpha - 2008-08-04
2579 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
2582 - The address part of exit policies was not correctly written
2583 to router descriptors. This generated router descriptors that failed
2584 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
2586 - Tor triggered a false assert when extending a circuit to a relay
2587 but we already have a connection open to that relay. Noticed by
2588 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
2591 - Fix a hidden service logging bug: in some edge cases, the router
2592 descriptor of a previously picked introduction point becomes
2593 obsolete and we need to give up on it rather than continually
2594 complaining that it has become obsolete. Observed by xiando. Bugfix
2598 - Take out the TestVia config option, since it was a workaround for
2599 a bug that was fixed in Tor 0.1.1.21.
2602 Changes in version 0.2.1.3-alpha - 2008-08-03
2603 Tor 0.2.1.3-alpha implements most of the pieces to prevent
2604 infinite-length circuit attacks (see proposal 110); fixes a bug that
2605 might cause exit relays to corrupt streams they send back; allows
2606 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
2607 ExcludeExitNodes config options; and fixes a big pile of bugs.
2609 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
2610 - Send a bootstrap problem "warn" event on the first problem if the
2611 reason is NO_ROUTE (that is, our network is down).
2614 - Implement most of proposal 110: The first K cells to be sent
2615 along a circuit are marked as special "early" cells; only K "early"
2616 cells will be allowed. Once this code is universal, we can block
2617 certain kinds of DOS attack by requiring that EXTEND commands must
2618 be sent using an "early" cell.
2621 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2622 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2623 on the client side when connecting to a hidden service. Bugfix
2624 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2625 - Ensure that two circuits can never exist on the same connection
2626 with the same circuit ID, even if one is marked for close. This
2627 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
2630 - When relays do their initial bandwidth measurement, don't limit
2631 to just our entry guards for the test circuits. Otherwise we tend
2632 to have multiple test circuits going through a single entry guard,
2633 which makes our bandwidth test less accurate. Fixes part of bug 654;
2634 patch contributed by Josh Albrecht.
2635 - Add an ExcludeExitNodes option so users can list a set of nodes
2636 that should be be excluded from the exit node position, but
2637 allowed elsewhere. Implements proposal 151.
2638 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
2639 ExcludeNodes and ExcludeExitNodes lists.
2640 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2641 be more efficient. Formerly it was quadratic in the number of
2642 servers; now it should be linear. Fixes bug 509.
2643 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2644 and n_conn_id_digest fields into a separate structure that's
2645 only needed when the circuit has not yet attached to an n_conn.
2648 - Change the contrib/tor.logrotate script so it makes the new
2649 logs as "_tor:_tor" rather than the default, which is generally
2650 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
2651 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2652 warnings (occasionally), but it can also cause the compiler to
2653 eliminate error-checking code. Suggested by Peter Gutmann.
2654 - When a hidden service is giving up on an introduction point candidate
2655 that was not included in the last published rendezvous descriptor,
2656 don't reschedule publication of the next descriptor. Fixes bug 763.
2658 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2659 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2660 and nobody claims to be using them. Fixes bug 754. Bugfix on
2661 0.1.0.1-rc. Patch from Christian Wilms.
2662 - Fix a small alignment and memory-wasting bug on buffer chunks.
2665 o Minor bugfixes (controller):
2666 - When closing an application-side connection because its circuit
2667 is getting torn down, generate the stream event correctly.
2668 Bugfix on 0.1.2.x. Anonymous patch.
2671 - Remove all backward-compatibility code to support relays running
2672 versions of Tor so old that they no longer work at all on the
2676 Changes in version 0.2.0.30 - 2008-07-15
2678 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2679 warnings (occasionally), but it can also cause the compiler to
2680 eliminate error-checking code. Suggested by Peter Gutmann.
2683 Changes in version 0.2.0.29-rc - 2008-07-08
2684 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
2685 hidden-service performance bugs, and fixes a bunch of smaller bugs.
2688 - If you have more than one bridge but don't know their keys,
2689 you would only launch a request for the descriptor of the first one
2690 on your list. (Tor considered launching requests for the others, but
2691 found that it already had a connection on the way for $0000...0000
2692 so it didn't open another.) Bugfix on 0.2.0.x.
2693 - If you have more than one bridge but don't know their keys, and the
2694 connection to one of the bridges failed, you would cancel all
2695 pending bridge connections. (After all, they all have the same
2696 digest.) Bugfix on 0.2.0.x.
2697 - When a hidden service was trying to establish an introduction point,
2698 and Tor had built circuits preemptively for such purposes, we
2699 were ignoring all the preemptive circuits and launching a new one
2700 instead. Bugfix on 0.2.0.14-alpha.
2701 - When a hidden service was trying to establish an introduction point,
2702 and Tor *did* manage to reuse one of the preemptively built
2703 circuits, it didn't correctly remember which one it used,
2704 so it asked for another one soon after, until there were no
2705 more preemptive circuits, at which point it launched one from
2706 scratch. Bugfix on 0.0.9.x.
2707 - Make directory servers include the X-Your-Address-Is: http header in
2708 their responses even for begin_dir conns. Now clients who only
2709 ever use begin_dir connections still have a way to learn their IP
2710 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
2713 - Fix a macro/CPP interaction that was confusing some compilers:
2714 some GCCs don't like #if/#endif pairs inside macro arguments.
2716 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
2717 Fixes bug 704; fix from Steven Murdoch.
2718 - When opening /dev/null in finish_daemonize(), do not pass the
2719 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
2720 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
2721 - Correctly detect transparent proxy support on Linux hosts that
2722 require in.h to be included before netfilter_ipv4.h. Patch
2724 - Disallow session resumption attempts during the renegotiation
2725 stage of the v2 handshake protocol. Clients should never be trying
2726 session resumption at this point, but apparently some did, in
2727 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
2728 found by Geoff Goodell.
2731 Changes in version 0.2.1.2-alpha - 2008-06-20
2732 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
2733 make it easier to set up your own private Tor network; fixes several
2734 big bugs with using more than one bridge relay; fixes a big bug with
2735 offering hidden services quickly after Tor starts; and uses a better
2736 API for reporting potential bootstrapping problems to the controller.
2739 - New TestingTorNetwork config option to allow adjustment of
2740 previously constant values that, while reasonable, could slow
2741 bootstrapping. Implements proposal 135. Patch from Karsten.
2744 - If you have more than one bridge but don't know their digests,
2745 you would only learn a request for the descriptor of the first one
2746 on your list. (Tor considered launching requests for the others, but
2747 found that it already had a connection on the way for $0000...0000
2748 so it didn't open another.) Bugfix on 0.2.0.x.
2749 - If you have more than one bridge but don't know their digests,
2750 and the connection to one of the bridges failed, you would cancel
2751 all pending bridge connections. (After all, they all have the
2752 same digest.) Bugfix on 0.2.0.x.
2753 - When establishing a hidden service, introduction points that
2754 originate from cannibalized circuits are completely ignored and not
2755 included in rendezvous service descriptors. This might be another
2756 reason for delay in making a hidden service available. Bugfix
2757 from long ago (0.0.9.x?)
2760 - Allow OpenSSL to use dynamic locks if it wants.
2761 - When building a consensus, do not include routers that are down.
2762 This will cut down 30% to 40% on consensus size. Implements
2764 - In directory authorities' approved-routers files, allow
2765 fingerprints with or without space.
2766 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
2767 controller can query our current bootstrap state in case it attaches
2768 partway through and wants to catch up.
2769 - Send an initial "Starting" bootstrap status event, so we have a
2770 state to start out in.
2773 - Asking for a conditional consensus at .../consensus/<fingerprints>
2774 would crash a dirserver if it did not already have a
2775 consensus. Bugfix on 0.2.1.1-alpha.
2776 - Clean up some macro/CPP interactions: some GCC versions don't like
2777 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
2780 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
2781 - Directory authorities shouldn't complain about bootstrapping
2782 problems just because they do a lot of reachability testing and
2783 some of the connection attempts fail.
2784 - Start sending "count" and "recommendation" key/value pairs in
2785 bootstrap problem status events, so the controller can hear about
2786 problems even before Tor decides they're worth reporting for sure.
2787 - If you're using bridges, generate "bootstrap problem" warnings
2788 as soon as you run out of working bridges, rather than waiting
2789 for ten failures -- which will never happen if you have less than
2791 - If we close our OR connection because there's been a circuit
2792 pending on it for too long, we were telling our bootstrap status
2793 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
2796 Changes in version 0.2.1.1-alpha - 2008-06-13
2797 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
2798 were making the Tor process bloat especially on Linux; makes our TLS
2799 handshake blend in better; sends "bootstrap phase" status events to
2800 the controller, so it can keep the user informed of progress (and
2801 problems) fetching directory information and establishing circuits;
2802 and adds a variety of smaller features.
2805 - More work on making our TLS handshake blend in: modify the list
2806 of ciphers advertised by OpenSSL in client mode to even more
2807 closely resemble a common web browser. We cheat a little so that
2808 we can advertise ciphers that the locally installed OpenSSL doesn't
2810 - Start sending "bootstrap phase" status events to the controller,
2811 so it can keep the user informed of progress fetching directory
2812 information and establishing circuits. Also inform the controller
2813 if we think we're stuck at a particular bootstrap phase. Implements
2815 - Resume using OpenSSL's RAND_poll() for better (and more portable)
2816 cross-platform entropy collection again. We used to use it, then
2817 stopped using it because of a bug that could crash systems that
2818 called RAND_poll when they had a lot of fds open. It looks like the
2819 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
2820 at startup, and to call RAND_poll() when we reseed later only if
2821 we have a non-buggy OpenSSL version.
2824 - When we choose to abandon a new entry guard because we think our
2825 older ones might be better, close any circuits pending on that
2826 new entry guard connection. This fix should make us recover much
2827 faster when our network is down and then comes back. Bugfix on
2828 0.1.2.8-beta; found by lodger.
2830 o Memory fixes and improvements:
2831 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
2832 to avoid unused RAM in buffer chunks and memory pools.
2833 - Speed up parsing and cut down on memory fragmentation by using
2834 stack-style allocations for parsing directory objects. Previously,
2835 this accounted for over 40% of allocations from within Tor's code
2836 on a typical directory cache.
2837 - Use a Bloom filter rather than a digest-based set to track which
2838 descriptors we need to keep around when we're cleaning out old
2839 router descriptors. This speeds up the computation significantly,
2840 and may reduce fragmentation.
2841 - Reduce the default smartlist size from 32 to 16; it turns out that
2842 most smartlists hold around 8-12 elements tops.
2843 - Make dumpstats() log the fullness and size of openssl-internal
2845 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
2846 patch to their OpenSSL, turn it on to save memory on servers. This
2847 patch will (with any luck) get included in a mainline distribution
2849 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2850 compress cells, which are basically all encrypted, compressed,
2854 - Stop reloading the router list from disk for no reason when we
2855 run out of reachable directory mirrors. Once upon a time reloading
2856 it would set the 'is_running' flag back to 1 for them. It hasn't
2857 done that for a long time.
2858 - In very rare situations new hidden service descriptors were
2859 published earlier than 30 seconds after the last change to the
2860 service. (We currently think that a hidden service descriptor
2861 that's been stable for 30 seconds is worth publishing.)
2864 - Allow separate log levels to be configured for different logging
2865 domains. For example, this allows one to log all notices, warnings,
2866 or errors, plus all memory management messages of level debug or
2867 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
2868 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
2869 and stop using a warning that had become unfixably verbose under
2871 - New --hush command-line option similar to --quiet. While --quiet
2872 disables all logging to the console on startup, --hush limits the
2873 output to messages of warning and error severity.
2874 - Servers support a new URL scheme for consensus downloads that
2875 allows the client to specify which authorities are trusted.
2876 The server then only sends the consensus if the client will trust
2877 it. Otherwise a 404 error is sent back. Clients use this
2878 new scheme when the server supports it (meaning it's running
2879 0.2.1.1-alpha or later). Implements proposal 134.
2880 - New configure/torrc options (--enable-geoip-stats,
2881 DirRecordUsageByCountry) to record how many IPs we've served
2882 directory info to in each country code, how many status documents
2883 total we've sent to each country code, and what share of the total
2884 directory requests we should expect to see.
2885 - Use the TLS1 hostname extension to more closely resemble browser
2887 - Lots of new unit tests.
2888 - Add a macro to implement the common pattern of iterating through
2889 two parallel lists in lockstep.
2892 Changes in version 0.2.0.28-rc - 2008-06-13
2893 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
2894 performance bug, and fixes a bunch of smaller bugs.
2897 - Fix a bug where, when we were choosing the 'end stream reason' to
2898 put in our relay end cell that we send to the exit relay, Tor
2899 clients on Windows were sometimes sending the wrong 'reason'. The
2900 anonymity problem is that exit relays may be able to guess whether
2901 the client is running Windows, thus helping partition the anonymity
2902 set. Down the road we should stop sending reasons to exit relays,
2903 or otherwise prevent future versions of this bug.
2906 - While setting up a hidden service, some valid introduction circuits
2907 were overlooked and abandoned. This might be the reason for
2908 the long delay in making a hidden service available. Bugfix on
2912 - Update to the "June 9 2008" ip-to-country file.
2913 - Run 'make test' as part of 'make dist', so we stop releasing so
2914 many development snapshots that fail their unit tests.
2917 - When we're checking if we have enough dir info for each relay
2918 to begin establishing circuits, make sure that we actually have
2919 the descriptor listed in the consensus, not just any descriptor.
2921 - Bridge relays no longer print "xx=0" in their extrainfo document
2922 for every single country code in the geoip db. Bugfix on
2924 - Only warn when we fail to load the geoip file if we were planning to
2925 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
2926 - If we change our MaxAdvertisedBandwidth and then reload torrc,
2927 Tor won't realize it should publish a new relay descriptor. Fixes
2928 bug 688, reported by mfr. Bugfix on 0.1.2.x.
2929 - When we haven't had any application requests lately, don't bother
2930 logging that we have expired a bunch of descriptors. Bugfix
2932 - Make relay cells written on a connection count as non-padding when
2933 tracking how long a connection has been in use. Bugfix on
2934 0.2.0.1-alpha. Spotted by lodger.
2935 - Fix unit tests in 0.2.0.27-rc.
2936 - Fix compile on Windows.
2939 Changes in version 0.2.0.27-rc - 2008-06-03
2940 Tor 0.2.0.27-rc adds a few features we left out of the earlier
2941 release candidates. In particular, we now include an IP-to-country
2942 GeoIP database, so controllers can easily look up what country a
2943 given relay is in, and so bridge relays can give us some sanitized
2944 summaries about which countries are making use of bridges. (See proposal
2945 126-geoip-fetching.txt for details.)
2948 - Include an IP-to-country GeoIP file in the tarball, so bridge
2949 relays can report sanitized summaries of the usage they're seeing.
2952 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
2953 Robert Hogan. Fixes the first part of bug 681.
2954 - Make bridge authorities never serve extrainfo docs.
2955 - Add support to detect Libevent versions in the 1.4.x series
2957 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
2958 - Include a new contrib/tor-exit-notice.html file that exit relay
2959 operators can put on their website to help reduce abuse queries.
2962 - When tunneling an encrypted directory connection, and its first
2963 circuit fails, do not leave it unattached and ask the controller
2964 to deal. Fixes the second part of bug 681.
2965 - Make bridge authorities correctly expire old extrainfo documents
2969 Changes in version 0.2.0.26-rc - 2008-05-13
2970 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
2971 in Debian's OpenSSL packages. All users running any 0.2.0.x version
2972 should upgrade, whether they're running Debian or not.
2974 o Major security fixes:
2975 - Use new V3 directory authority keys on the tor26, gabelmoo, and
2976 moria1 V3 directory authorities. The old keys were generated with
2977 a vulnerable version of Debian's OpenSSL package, and must be
2978 considered compromised. Other authorities' keys were not generated
2979 with an affected version of OpenSSL.
2982 - List authority signatures as "unrecognized" based on DirServer
2983 lines, not on cert cache. Bugfix on 0.2.0.x.
2986 - Add a new V3AuthUseLegacyKey option to make it easier for
2987 authorities to change their identity keys if they have to.
2990 Changes in version 0.2.0.25-rc - 2008-04-23
2991 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
2994 - Remember to initialize threading before initializing logging.
2995 Otherwise, many BSD-family implementations will crash hard on
2996 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
2999 - Authorities correctly free policies on bad servers on
3000 exit. Fixes bug 672. Bugfix on 0.2.0.x.
3003 Changes in version 0.2.0.24-rc - 2008-04-22
3004 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
3005 v3 directory authority, makes relays with dynamic IP addresses and no
3006 DirPort notice more quickly when their IP address changes, fixes a few
3007 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
3009 o New directory authorities:
3010 - Take lefkada out of the list of v3 directory authorities, since
3011 it has been down for months.
3012 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
3016 - Detect address changes more quickly on non-directory mirror
3017 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
3019 o Minor features (security):
3020 - Reject requests for reverse-dns lookup of names that are in
3021 a private address space. Patch from lodger.
3022 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
3025 o Minor bugfixes (crashes):
3026 - Avoid a rare assert that can trigger when Tor doesn't have much
3027 directory information yet and it tries to fetch a v2 hidden
3028 service descriptor. Fixes bug 651, reported by nwf.
3029 - Initialize log mutex before initializing dmalloc. Otherwise,
3030 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
3031 - Use recursive pthread mutexes in order to avoid deadlock when
3032 logging debug-level messages to a controller. Bug spotted by nwf,
3033 bugfix on 0.2.0.16-alpha.
3035 o Minor bugfixes (resource management):
3036 - Keep address policies from leaking memory: start their refcount
3037 at 1, not 2. Bugfix on 0.2.0.16-alpha.
3038 - Free authority certificates on exit, so they don't look like memory
3039 leaks. Bugfix on 0.2.0.19-alpha.
3040 - Free static hashtables for policy maps and for TLS connections on
3041 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
3042 - Avoid allocating extra space when computing consensuses on 64-bit
3043 platforms. Bug spotted by aakova.
3045 o Minor bugfixes (misc):
3046 - Do not read the configuration file when we've only been told to
3047 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
3048 based on patch from Sebastian Hahn.
3049 - Exit relays that are used as a client can now reach themselves
3050 using the .exit notation, rather than just launching an infinite
3051 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
3052 - When attempting to open a logfile fails, tell us why.
3053 - Fix a dumb bug that was preventing us from knowing that we should
3054 preemptively build circuits to handle expected directory requests.
3055 Fixes bug 660. Bugfix on 0.1.2.x.
3056 - Warn less verbosely about clock skew from netinfo cells from
3057 untrusted sources. Fixes bug 663.
3058 - Make controller stream events for DNS requests more consistent,
3059 by adding "new stream" events for DNS requests, and removing
3060 spurious "stream closed" events" for cached reverse resolves.
3061 Patch from mwenge. Fixes bug 646.
3062 - Correctly notify one-hop connections when a circuit build has
3063 failed. Possible fix for bug 669. Found by lodger.
3066 Changes in version 0.2.0.23-rc - 2008-03-24
3067 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
3068 makes bootstrapping faster if the first directory mirror you contact
3069 is down. The bundles also include the new Vidalia 0.1.2 release.
3072 - When a tunneled directory request is made to a directory server
3073 that's down, notice after 30 seconds rather than 120 seconds. Also,
3074 fail any begindir streams that are pending on it, so they can
3075 retry elsewhere. This was causing multi-minute delays on bootstrap.
3078 Changes in version 0.2.0.22-rc - 2008-03-18
3079 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
3080 enables encrypted directory connections by default for non-relays, fixes
3081 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
3082 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
3085 - Enable encrypted directory connections by default for non-relays,
3086 so censor tools that block Tor directory connections based on their
3087 plaintext patterns will no longer work. This means Tor works in
3088 certain censored countries by default again.
3091 - Make sure servers always request certificates from clients during
3092 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
3093 - Do not enter a CPU-eating loop when a connection is closed in
3094 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
3095 diagnosed by lodger; bugfix on 0.2.0.20-rc.
3096 - Fix assertion failure that could occur when a blocked circuit
3097 became unblocked, and it had pending client DNS requests. Bugfix
3098 on 0.2.0.1-alpha. Fixes bug 632.
3100 o Minor bugfixes (on 0.1.2.x):
3101 - Generate "STATUS_SERVER" events rather than misspelled
3102 "STATUS_SEVER" events. Caught by mwenge.
3103 - When counting the number of bytes written on a TLS connection,
3104 look at the BIO actually used for writing to the network, not
3105 at the BIO used (sometimes) to buffer data for the network.
3106 Looking at different BIOs could result in write counts on the
3107 order of ULONG_MAX. Fixes bug 614.
3108 - On Windows, correctly detect errors when listing the contents of
3109 a directory. Fix from lodger.
3111 o Minor bugfixes (on 0.2.0.x):
3112 - Downgrade "sslv3 alert handshake failure" message to INFO.
3113 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
3114 left BandwidthRate and BandwidthBurst at the default, we would be
3115 silently limited by those defaults. Now raise them to match the
3116 RelayBandwidth* values.
3117 - Fix the SVK version detection logic to work correctly on a branch.
3118 - Make --enable-openbsd-malloc work correctly on Linux with alpha
3119 CPUs. Fixes bug 625.
3120 - Logging functions now check that the passed severity is sane.
3121 - Use proper log levels in the testsuite call of
3122 get_interface_address6().
3123 - When using a nonstandard malloc, do not use the platform values for
3124 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
3125 - Make the openbsd malloc code use 8k pages on alpha CPUs and
3127 - Detect mismatched page sizes when using --enable-openbsd-malloc.
3128 - Avoid double-marked-for-close warning when certain kinds of invalid
3129 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
3130 for bug 617. Bugfix on 0.2.0.1-alpha.
3131 - Make sure that the "NULL-means-reject *:*" convention is followed by
3132 all the policy manipulation functions, avoiding some possible crash
3133 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
3134 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
3135 actually works, and doesn't warn about every single reverse lookup.
3136 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
3139 - Only log guard node status when guard node status has changed.
3140 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
3141 make "INFO" 75% less verbose.
3144 Changes in version 0.2.0.21-rc - 2008-03-02
3145 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
3146 makes Tor work well with Vidalia again, fixes a rare assert bug,
3147 and fixes a pair of more minor bugs. The bundles also include Vidalia
3148 0.1.0 and Torbutton 1.1.16.
3151 - The control port should declare that it requires password auth
3152 when HashedControlSessionPassword is set too. Patch from Matt Edman;
3153 bugfix on 0.2.0.20-rc. Fixes bug 615.
3154 - Downgrade assert in connection_buckets_decrement() to a log message.
3155 This may help us solve bug 614, and in any case will make its
3156 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
3157 - We were sometimes miscounting the number of bytes read from the
3158 network, causing our rate limiting to not be followed exactly.
3159 Bugfix on 0.2.0.16-alpha. Reported by lodger.
3162 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
3163 OpenSSL versions should have been working fine. Diagnosis and patch
3164 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
3165 Bugfix on 0.2.0.20-rc.
3168 Changes in version 0.2.0.20-rc - 2008-02-24
3169 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
3170 makes more progress towards normalizing Tor's TLS handshake, makes
3171 hidden services work better again, helps relays bootstrap if they don't
3172 know their IP address, adds optional support for linking in openbsd's
3173 allocator or tcmalloc, allows really fast relays to scale past 15000
3174 sockets, and fixes a bunch of minor bugs reported by Veracode.
3177 - Enable the revised TLS handshake based on the one designed by
3178 Steven Murdoch in proposal 124, as revised in proposal 130. It
3179 includes version negotiation for OR connections as described in
3180 proposal 105. The new handshake is meant to be harder for censors
3181 to fingerprint, and it adds the ability to detect certain kinds of
3182 man-in-the-middle traffic analysis attacks. The version negotiation
3183 feature will allow us to improve Tor's link protocol more safely
3185 - Choose which bridge to use proportional to its advertised bandwidth,
3186 rather than uniformly at random. This should speed up Tor for
3187 bridge users. Also do this for people who set StrictEntryNodes.
3188 - When a TrackHostExits-chosen exit fails too many times in a row,
3189 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
3192 - Resolved problems with (re-)fetching hidden service descriptors.
3193 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
3195 - If we only ever used Tor for hidden service lookups or posts, we
3196 would stop building circuits and start refusing connections after
3197 24 hours, since we falsely believed that Tor was dormant. Reported
3198 by nwf; bugfix on 0.1.2.x.
3199 - Servers that don't know their own IP address should go to the
3200 authorities for their first directory fetch, even if their DirPort
3201 is off or if they don't know they're reachable yet. This will help
3202 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
3203 - When counting the number of open sockets, count not only the number
3204 of sockets we have received from the socket() call, but also
3205 the number we've gotten from accept() and socketpair(). This bug
3206 made us fail to count all sockets that we were using for incoming
3207 connections. Bugfix on 0.2.0.x.
3208 - Fix code used to find strings within buffers, when those strings
3209 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
3210 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
3211 - Add a new __HashedControlSessionPassword option for controllers
3212 to use for one-off session password hashes that shouldn't get
3213 saved to disk by SAVECONF --- Vidalia users were accumulating a
3214 pile of HashedControlPassword lines in their torrc files, one for
3215 each time they had restarted Tor and then clicked Save. Make Tor
3216 automatically convert "HashedControlPassword" to this new option but
3217 only when it's given on the command line. Partial fix for bug 586.
3219 o Minor features (performance):
3220 - Tune parameters for cell pool allocation to minimize amount of
3222 - Add OpenBSD malloc code from phk as an optional malloc
3223 replacement on Linux: some glibc libraries do very poorly
3224 with Tor's memory allocation patterns. Pass
3225 --enable-openbsd-malloc to get the replacement malloc code.
3226 - Add a --with-tcmalloc option to the configure script to link
3227 against tcmalloc (if present). Does not yet search for
3228 non-system include paths.
3229 - Stop imposing an arbitrary maximum on the number of file descriptors
3230 used for busy servers. Bug reported by Olaf Selke; patch from
3233 o Minor features (other):
3234 - When SafeLogging is disabled, log addresses along with all TLS
3236 - When building with --enable-gcc-warnings, check for whether Apple's
3237 warning "-Wshorten-64-to-32" is available.
3238 - Add a --passphrase-fd argument to the tor-gencert command for
3241 o Minor bugfixes (memory leaks and code problems):
3242 - We were leaking a file descriptor if Tor started with a zero-length
3243 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
3244 - Detect size overflow in zlib code. Reported by Justin Ferguson and
3246 - We were comparing the raw BridgePassword entry with a base64'ed
3247 version of it, when handling a "/tor/networkstatus-bridges"
3248 directory request. Now compare correctly. Noticed by Veracode.
3249 - Recover from bad tracked-since value in MTBF-history file.
3251 - Alter the code that tries to recover from unhandled write
3252 errors, to not try to flush onto a socket that's given us
3253 unhandled errors. Bugfix on 0.1.2.x.
3254 - Make Unix controlsockets work correctly on OpenBSD. Patch from
3255 tup. Bugfix on 0.2.0.3-alpha.
3257 o Minor bugfixes (other):
3258 - If we have an extra-info document for our server, always make
3259 it available on the control port, even if we haven't gotten
3260 a copy of it from an authority yet. Patch from mwenge.
3261 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
3262 - Directory mirrors no longer include a guess at the client's IP
3263 address if the connection appears to be coming from the same /24
3264 network; it was producing too many wrong guesses.
3265 - Make the new hidden service code respect the SafeLogging setting.
3266 Bugfix on 0.2.0.x. Patch from Karsten.
3267 - When starting as an authority, do not overwrite all certificates
3268 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
3269 - If we're trying to flush the last bytes on a connection (for
3270 example, when answering a directory request), reset the
3271 time-to-give-up timeout every time we manage to write something
3272 on the socket. Bugfix on 0.1.2.x.
3273 - Change the behavior of "getinfo status/good-server-descriptor"
3274 so it doesn't return failure when any authority disappears.
3275 - Even though the man page said that "TrackHostExits ." should
3276 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
3277 - Report TLS "zero return" case as a "clean close" and "IO error"
3278 as a "close". Stop calling closes "unexpected closes": existing
3279 Tors don't use SSL_close(), so having a connection close without
3280 the TLS shutdown handshake is hardly unexpected.
3281 - Send NAMESERVER_STATUS messages for a single failed nameserver
3284 o Code simplifications and refactoring:
3285 - Remove the tor_strpartition function: its logic was confused,
3286 and it was only used for one thing that could be implemented far
3290 Changes in version 0.2.0.19-alpha - 2008-02-09
3291 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
3292 handshake, makes path selection for relays more secure and IP address
3293 guessing more robust, and generally fixes a lot of bugs in preparation
3294 for calling the 0.2.0 branch stable.
3297 - Do not include recognizeable strings in the commonname part of
3298 Tor's x509 certificates.
3301 - If we're a relay, avoid picking ourselves as an introduction point,
3302 a rendezvous point, or as the final hop for internal circuits. Bug
3303 reported by taranis and lodger. Bugfix on 0.1.2.x.
3304 - Patch from "Andrew S. Lists" to catch when we contact a directory
3305 mirror at IP address X and he says we look like we're coming from
3306 IP address X. Bugfix on 0.1.2.x.
3308 o Minor features (security):
3309 - Be more paranoid about overwriting sensitive memory on free(),
3310 as a defensive programming tactic to ensure forward secrecy.
3312 o Minor features (directory authority):
3313 - Actually validate the options passed to AuthDirReject,
3314 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
3315 - Reject router descriptors with out-of-range bandwidthcapacity or
3316 bandwidthburst values.
3318 o Minor features (controller):
3319 - Reject controller commands over 1MB in length. This keeps rogue
3320 processes from running us out of memory.
3322 o Minor features (misc):
3323 - Give more descriptive well-formedness errors for out-of-range
3324 hidden service descriptor/protocol versions.
3325 - Make memory debugging information describe more about history
3326 of cell allocation, so we can help reduce our memory use.
3328 o Deprecated features (controller):
3329 - The status/version/num-versioning and status/version/num-concurring
3330 GETINFO options are no longer useful in the v3 directory protocol:
3331 treat them as deprecated, and warn when they're used.
3334 - When our consensus networkstatus has been expired for a while, stop
3335 being willing to build circuits using it. Fixes bug 401. Bugfix
3337 - Directory caches now fetch certificates from all authorities
3338 listed in a networkstatus consensus, even when they do not
3339 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
3340 - When connecting to a bridge without specifying its key, insert
3341 the connection into the identity-to-connection map as soon as
3342 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
3343 - Detect versions of OS X where malloc_good_size() is present in the
3344 library but never actually declared. Resolves bug 587. Bugfix
3346 - Stop incorrectly truncating zlib responses to directory authority
3347 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
3348 - Stop recommending that every server operator send mail to tor-ops.
3349 Resolves bug 597. Bugfix on 0.1.2.x.
3350 - Don't trigger an assert if we start a directory authority with a
3351 private IP address (like 127.0.0.1).
3352 - Avoid possible failures when generating a directory with routers
3353 with over-long versions strings, or too many flags set. Bugfix
3355 - If an attempt to launch a DNS resolve request over the control
3356 port fails because we have overrun the limit on the number of
3357 connections, tell the controller that the request has failed.
3358 - Avoid using too little bandwidth when our clock skips a few
3359 seconds. Bugfix on 0.1.2.x.
3360 - Fix shell error when warning about missing packages in configure
3361 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
3362 - Do not become confused when receiving a spurious VERSIONS-like
3363 cell from a confused v1 client. Bugfix on 0.2.0.x.
3364 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
3365 introduction points for a hidden service have failed. Patch from
3366 Karsten Loesing. Bugfix on 0.2.0.x.
3368 o Code simplifications and refactoring:
3369 - Remove some needless generality from cpuworker code, for improved
3371 - Stop overloading the circuit_t.onionskin field for both "onionskin
3372 from a CREATE cell that we are waiting for a cpuworker to be
3373 assigned" and "onionskin from an EXTEND cell that we are going to
3374 send to an OR as soon as we are connected". Might help with bug 600.
3375 - Add an in-place version of aes_crypt() so that we can avoid doing a
3376 needless memcpy() call on each cell payload.
3379 Changes in version 0.2.0.18-alpha - 2008-01-25
3380 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
3381 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
3382 that can warn or reject connections to ports generally associated with
3383 vulnerable-plaintext protocols.
3385 o New directory authorities:
3386 - Set up dannenberg (run by CCC) as the sixth v3 directory
3390 - Fix a major memory leak when attempting to use the v2 TLS
3391 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
3392 - We accidentally enabled the under-development v2 TLS handshake
3393 code, which was causing log entries like "TLS error while
3394 renegotiating handshake". Disable it again. Resolves bug 590.
3395 - We were computing the wrong Content-Length: header for directory
3396 responses that need to be compressed on the fly, causing clients
3397 asking for those items to always fail. Bugfix on 0.2.0.x; partially
3401 - Avoid going directly to the directory authorities even if you're a
3402 relay, if you haven't found yourself reachable yet or if you've
3403 decided not to advertise your dirport yet. Addresses bug 556.
3404 - If we've gone 12 hours since our last bandwidth check, and we
3405 estimate we have less than 50KB bandwidth capacity but we could
3406 handle more, do another bandwidth test.
3407 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3408 Tor can warn and/or refuse connections to ports commonly used with
3409 vulnerable-plaintext protocols. Currently we warn on ports 23,
3410 109, 110, and 143, but we don't reject any.
3413 - When we setconf ClientOnly to 1, close any current OR and Dir
3414 listeners. Reported by mwenge.
3415 - When we get a consensus that's been signed by more people than
3416 we expect, don't log about it; it's not a big deal. Reported
3420 - Don't answer "/tor/networkstatus-bridges" directory requests if
3421 the request isn't encrypted.
3422 - Make "ClientOnly 1" config option disable directory ports too.
3423 - Patches from Karsten Loesing to make v2 hidden services more
3424 robust: work even when there aren't enough HSDir relays available;
3425 retry when a v2 rend desc fetch fails; but don't retry if we
3426 already have a usable v0 rend desc.
3429 Changes in version 0.2.0.17-alpha - 2008-01-17
3430 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
3433 - Make the tor-gencert man page get included correctly in the tarball.
3436 Changes in version 0.2.0.16-alpha - 2008-01-17
3437 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
3438 Loesing, and generally cleans up a lot of features and minor bugs.
3440 o New directory authorities:
3441 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
3444 o Major performance improvements:
3445 - Switch our old ring buffer implementation for one more like that
3446 used by free Unix kernels. The wasted space in a buffer with 1mb
3447 of data will now be more like 8k than 1mb. The new implementation
3448 also avoids realloc();realloc(); patterns that can contribute to
3449 memory fragmentation.
3452 - Configuration files now accept C-style strings as values. This
3453 helps encode characters not allowed in the current configuration
3454 file format, such as newline or #. Addresses bug 557.
3455 - Although we fixed bug 539 (where servers would send HTTP status 503
3456 responses _and_ send a body too), there are still servers out
3457 there that haven't upgraded. Therefore, make clients parse such
3458 bodies when they receive them.
3459 - When we're not serving v2 directory information, there is no reason
3460 to actually keep any around. Remove the obsolete files and directory
3461 on startup if they are very old and we aren't going to serve them.
3463 o Minor performance improvements:
3464 - Reference-count and share copies of address policy entries; only 5%
3465 of them were actually distinct.
3466 - Never walk through the list of logs if we know that no log is
3467 interested in a given message.
3470 - When an authority has not signed a consensus, do not try to
3471 download a nonexistent "certificate with key 00000000". Bugfix
3472 on 0.2.0.x. Fixes bug 569.
3473 - Fix a rare assert error when we're closing one of our threads:
3474 use a mutex to protect the list of logs, so we never write to the
3475 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
3476 bug 575, which is kind of the revenge of bug 222.
3477 - Patch from Karsten Loesing to complain less at both the client
3478 and the relay when a relay used to have the HSDir flag but doesn't
3479 anymore, and we try to upload a hidden service descriptor.
3480 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
3482 - Do not try to download missing certificates until we have tried
3483 to check our fallback consensus. Fixes bug 583.
3484 - Make bridges round reported GeoIP stats info up to the nearest
3485 estimate, not down. Now we can distinguish between "0 people from
3486 this country" and "1 person from this country".
3487 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
3488 - Avoid possible segfault if key generation fails in
3489 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
3490 - Avoid segfault in the case where a badly behaved v2 versioning
3491 directory sends a signed networkstatus with missing client-versions.
3493 - Avoid segfaults on certain complex invocations of
3494 router_get_by_hexdigest(). Bugfix on 0.1.2.
3495 - Correct bad index on array access in parse_http_time(). Bugfix
3497 - Fix possible bug in vote generation when server versions are present
3498 but client versions are not.
3499 - Fix rare bug on REDIRECTSTREAM control command when called with no
3500 port set: it could erroneously report an error when none had
3502 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
3503 compressing large objects and find ourselves with more than 4k
3504 left over. Bugfix on 0.2.0.
3505 - Fix a small memory leak when setting up a hidden service.
3506 - Fix a few memory leaks that could in theory happen under bizarre
3508 - Fix an assert if we post a general-purpose descriptor via the
3509 control port but that descriptor isn't mentioned in our current
3510 network consensus. Bug reported by Jon McLachlan; bugfix on
3513 o Minor features (controller):
3514 - Get NS events working again. Patch from tup.
3515 - The GETCONF command now escapes and quotes configuration values
3516 that don't otherwise fit into the torrc file.
3517 - The SETCONF command now handles quoted values correctly.
3519 o Minor features (directory authorities):
3520 - New configuration options to override default maximum number of
3521 servers allowed on a single IP address. This is important for
3522 running a test network on a single host.
3523 - Actually implement the -s option to tor-gencert.
3524 - Add a manual page for tor-gencert.
3526 o Minor features (bridges):
3527 - Bridge authorities no longer serve bridge descriptors over
3528 unencrypted connections.
3530 o Minor features (other):
3531 - Add hidden services and DNSPorts to the list of things that make
3532 Tor accept that it has running ports. Change starting Tor with no
3533 ports from a fatal error to a warning; we might change it back if
3534 this turns out to confuse anybody. Fixes bug 579.
3537 Changes in version 0.1.2.19 - 2008-01-17
3538 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3539 exit policy a little bit more conservative so it's safer to run an
3540 exit relay on a home system, and fixes a variety of smaller issues.
3543 - Exit policies now reject connections that are addressed to a
3544 relay's public (external) IP address too, unless
3545 ExitPolicyRejectPrivate is turned off. We do this because too
3546 many relays are running nearby to services that trust them based
3550 - When the clock jumps forward a lot, do not allow the bandwidth
3551 buckets to become negative. Fixes bug 544.
3552 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3553 on every successful resolve. Reported by Mike Perry.
3554 - Purge old entries from the "rephist" database and the hidden
3555 service descriptor database even when DirPort is zero.
3556 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3557 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3558 crashing or mis-answering these requests.
3559 - When we decide to send a 503 response to a request for servers, do
3560 not then also send the server descriptors: this defeats the whole
3561 purpose. Fixes bug 539.
3564 - Changing the ExitPolicyRejectPrivate setting should cause us to
3565 rebuild our server descriptor.
3566 - Fix handling of hex nicknames when answering controller requests for
3567 networkstatus by name, or when deciding whether to warn about
3568 unknown routers in a config option. (Patch from mwenge.)
3569 - Fix a couple of hard-to-trigger autoconf problems that could result
3570 in really weird results on platforms whose sys/types.h files define
3571 nonstandard integer types.
3572 - Don't try to create the datadir when running --verify-config or
3573 --hash-password. Resolves bug 540.
3574 - If we were having problems getting a particular descriptor from the
3575 directory caches, and then we learned about a new descriptor for
3576 that router, we weren't resetting our failure count. Reported
3578 - Although we fixed bug 539 (where servers would send HTTP status 503
3579 responses _and_ send a body too), there are still servers out there
3580 that haven't upgraded. Therefore, make clients parse such bodies
3581 when they receive them.
3582 - Run correctly on systems where rlim_t is larger than unsigned long.
3583 This includes some 64-bit systems.
3584 - Run correctly on platforms (like some versions of OS X 10.5) where
3585 the real limit for number of open files is OPEN_FILES, not rlim_max
3586 from getrlimit(RLIMIT_NOFILES).
3587 - Avoid a spurious free on base64 failure.
3588 - Avoid segfaults on certain complex invocations of
3589 router_get_by_hexdigest().
3590 - Fix rare bug on REDIRECTSTREAM control command when called with no
3591 port set: it could erroneously report an error when none had
3595 Changes in version 0.2.0.15-alpha - 2007-12-25
3596 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
3597 features added in 0.2.0.13-alpha.
3600 - Fix several remotely triggerable asserts based on DirPort requests
3601 for a v2 or v3 networkstatus object before we were prepared. This
3602 was particularly bad for 0.2.0.13 and later bridge relays, who
3603 would never have a v2 networkstatus and would thus always crash
3604 when used. Bugfixes on 0.2.0.x.
3605 - Estimate the v3 networkstatus size more accurately, rather than
3606 estimating it at zero bytes and giving it artificially high priority
3607 compared to other directory requests. Bugfix on 0.2.0.x.
3610 - Fix configure.in logic for cross-compilation.
3611 - When we load a bridge descriptor from the cache, and it was
3612 previously unreachable, mark it as retriable so we won't just
3613 ignore it. Also, try fetching a new copy immediately. Bugfixes
3615 - The bridge GeoIP stats were counting other relays, for example
3616 self-reachability and authority-reachability tests.
3619 - Support compilation to target iPhone; patch from cjacker huang.
3620 To build for iPhone, pass the --enable-iphone option to configure.
3623 Changes in version 0.2.0.14-alpha - 2007-12-23
3625 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
3626 without a datadirectory from a previous Tor install. Reported
3628 - Fix a crash when we fetch a descriptor that turns out to be
3629 unexpected (it used to be in our networkstatus when we started
3630 fetching it, but it isn't in our current networkstatus), and we
3631 aren't using bridges. Bugfix on 0.2.0.x.
3632 - Fix a crash when accessing hidden services: it would work the first
3633 time you use a given introduction point for your service, but
3634 on subsequent requests we'd be using garbage memory. Fixed by
3635 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
3636 - Fix a crash when we load a bridge descriptor from disk but we don't
3637 currently have a Bridge line for it in our torrc. Bugfix on
3641 - If bridge authorities set BridgePassword, they will serve a
3642 snapshot of known bridge routerstatuses from their DirPort to
3643 anybody who knows that password. Unset by default.
3646 - Make the unit tests build again.
3647 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
3648 - Make PublishServerDescriptor default to 1, so the default doesn't
3649 have to change as we invent new directory protocol versions.
3650 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
3651 be included unless sys/time.h is already included. Fixes
3652 bug 553. Bugfix on 0.2.0.x.
3653 - If we receive a general-purpose descriptor and then receive an
3654 identical bridge-purpose descriptor soon after, don't discard
3655 the next one as a duplicate.
3658 - If BridgeRelay is set to 1, then the default for
3659 PublishServerDescriptor is now "bridge" rather than "v2,v3".
3660 - If the user sets RelayBandwidthRate but doesn't set
3661 RelayBandwidthBurst, then make them equal rather than erroring out.
3664 Changes in version 0.2.0.13-alpha - 2007-12-21
3665 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
3666 Goodell, fixes many more bugs, and adds a lot of infrastructure for
3669 o New directory authorities:
3670 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
3674 - Only update guard status (usable / not usable) once we have
3675 enough directory information. This was causing us to always pick
3676 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
3677 causing us to discard all our guards on startup if we hadn't been
3678 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
3679 - Purge old entries from the "rephist" database and the hidden
3680 service descriptor databases even when DirPort is zero. Bugfix
3682 - We were ignoring our RelayBandwidthRate for the first 30 seconds
3683 after opening a circuit -- even a relayed circuit. Bugfix on
3685 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3686 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3687 crashing or mis-answering these types of requests.
3688 - Relays were publishing their server descriptor to v1 and v2
3689 directory authorities, but they didn't try publishing to v3-only
3690 authorities. Fix this; and also stop publishing to v1 authorities.
3692 - When we were reading router descriptors from cache, we were ignoring
3693 the annotations -- so for example we were reading in bridge-purpose
3694 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
3695 - When we decided to send a 503 response to a request for servers, we
3696 were then also sending the server descriptors: this defeats the
3697 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
3700 - Bridge relays now behave like clients with respect to time
3701 intervals for downloading new consensus documents -- otherwise they
3702 stand out. Bridge users now wait until the end of the interval,
3703 so their bridge relay will be sure to have a new consensus document.
3704 - Three new config options (AlternateDirAuthority,
3705 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3706 user selectively replace the default directory authorities by type,
3707 rather than the all-or-nothing replacement that DirServer offers.
3708 - Tor can now be configured to read a GeoIP file from disk in one
3709 of two formats. This can be used by controllers to map IP addresses
3710 to countries. Eventually, it may support exit-by-country.
3711 - When possible, bridge relays remember which countries users
3712 are coming from, and report aggregate information in their
3713 extra-info documents, so that the bridge authorities can learn
3714 where Tor is blocked.
3715 - Bridge directory authorities now do reachability testing on the
3716 bridges they know. They provide router status summaries to the
3717 controller via "getinfo ns/purpose/bridge", and also dump summaries
3718 to a file periodically.
3719 - Stop fetching directory info so aggressively if your DirPort is
3720 on but your ORPort is off; stop fetching v2 dir info entirely.
3721 You can override these choices with the new FetchDirInfoEarly
3725 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
3726 consensus documents when there are too many relays at a single
3727 IP address. Now clear it in v2 network status documents too, and
3728 also clear it in routerinfo_t when the relay is no longer listed
3729 in the relevant networkstatus document.
3730 - Don't crash if we get an unexpected value for the
3731 PublishServerDescriptor config option. Reported by Matt Edman;
3732 bugfix on 0.2.0.9-alpha.
3733 - Our new v2 hidden service descriptor format allows descriptors
3734 that have no introduction points. But Tor crashed when we tried
3735 to build a descriptor with no intro points (and it would have
3736 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
3738 - Fix building with dmalloc 5.5.2 with glibc.
3739 - Reject uploaded descriptors and extrainfo documents if they're
3740 huge. Otherwise we'll cache them all over the network and it'll
3741 clog everything up. Reported by Aljosha Judmayer.
3742 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
3743 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
3744 - When the DANGEROUS_VERSION controller status event told us we're
3745 running an obsolete version, it used the string "OLD" to describe
3746 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3747 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
3748 - If we can't expand our list of entry guards (e.g. because we're
3749 using bridges or we have StrictEntryNodes set), don't mark relays
3750 down when they fail a directory request. Otherwise we're too quick
3751 to mark all our entry points down. Bugfix on 0.1.2.x.
3752 - Fix handling of hex nicknames when answering controller requests for
3753 networkstatus by name, or when deciding whether to warn about unknown
3754 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
3755 - Fix a couple of hard-to-trigger autoconf problems that could result
3756 in really weird results on platforms whose sys/types.h files define
3757 nonstandard integer types. Bugfix on 0.1.2.x.
3758 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
3759 - Don't crash on name lookup when we have no current consensus. Fixes
3760 bug 538; bugfix on 0.2.0.x.
3761 - Only Tors that want to mirror the v2 directory info should
3762 create the "cached-status" directory in their datadir. (All Tors
3763 used to create it.) Bugfix on 0.2.0.9-alpha.
3764 - Directory authorities should only automatically download Extra Info
3765 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
3768 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
3769 consumers. (We already do this on HUP.)
3770 - Authorities and caches fetch the v2 networkstatus documents
3771 less often, now that v3 is encouraged.
3772 - Add a new config option BridgeRelay that specifies you want to
3773 be a bridge relay. Right now the only difference is that it makes
3774 you answer begin_dir requests, and it makes you cache dir info,
3775 even if your DirPort isn't on.
3776 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
3777 ask about source, timestamp of arrival, purpose, etc. We need
3778 something like this to help Vidalia not do GeoIP lookups on bridge
3780 - Allow multiple HashedControlPassword config lines, to support
3781 multiple controller passwords.
3782 - Authorities now decide whether they're authoritative for a given
3783 router based on the router's purpose.
3784 - New config options AuthDirBadDir and AuthDirListBadDirs for
3785 authorities to mark certain relays as "bad directories" in the
3786 networkstatus documents. Also supports the "!baddir" directive in
3787 the approved-routers file.
3790 Changes in version 0.2.0.12-alpha - 2007-11-16
3791 This twelfth development snapshot fixes some more build problems as
3792 well as a few minor bugs.
3795 - Make it build on OpenBSD again. Patch from tup.
3796 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
3797 package-building for Red Hat, OS X, etc.
3799 o Minor bugfixes (on 0.1.2.x):
3800 - Changing the ExitPolicyRejectPrivate setting should cause us to
3801 rebuild our server descriptor.
3803 o Minor bugfixes (on 0.2.0.x):
3804 - When we're lacking a consensus, don't try to perform rendezvous
3805 operations. Reported by Karsten Loesing.
3806 - Fix a small memory leak whenever we decide against using a
3807 newly picked entry guard. Reported by Mike Perry.
3808 - When authorities detected more than two relays running on the same
3809 IP address, they were clearing all the status flags but forgetting
3810 to clear the "hsdir" flag. So clients were being told that a
3811 given relay was the right choice for a v2 hsdir lookup, yet they
3812 never had its descriptor because it was marked as 'not running'
3814 - If we're trying to fetch a bridge descriptor and there's no way
3815 the bridge authority could help us (for example, we don't know
3816 a digest, or there is no bridge authority), don't be so eager to
3817 fall back to asking the bridge authority.
3818 - If we're using bridges or have strictentrynodes set, and our
3819 chosen exit is in the same family as all our bridges/entry guards,
3820 then be flexible about families.
3823 - When we negotiate a v2 link-layer connection (not yet implemented),
3824 accept RELAY_EARLY cells and turn them into RELAY cells if we've
3825 negotiated a v1 connection for their next step. Initial code for
3829 Changes in version 0.2.0.11-alpha - 2007-11-12
3830 This eleventh development snapshot fixes some build problems with
3831 the previous snapshot. It also includes a more secure-by-default exit
3832 policy for relays, fixes an enormous memory leak for exit relays, and
3833 fixes another bug where servers were falling out of the directory list.
3836 - Exit policies now reject connections that are addressed to a
3837 relay's public (external) IP address too, unless
3838 ExitPolicyRejectPrivate is turned off. We do this because too
3839 many relays are running nearby to services that trust them based
3840 on network address. Bugfix on 0.1.2.x.
3843 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3844 on every successful resolve. Reported by Mike Perry; bugfix
3846 - On authorities, never downgrade to old router descriptors simply
3847 because they're listed in the consensus. This created a catch-22
3848 where we wouldn't list a new descriptor because there was an
3849 old one in the consensus, and we couldn't get the new one in the
3850 consensus because we wouldn't list it. Possible fix for bug 548.
3851 Also, this might cause bug 543 to appear on authorities; if so,
3852 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
3854 o Packaging fixes on 0.2.0.10-alpha:
3855 - We were including instructions about what to do with the
3856 src/config/fallback-consensus file, but we weren't actually
3857 including it in the tarball. Disable all of that for now.
3860 - Allow people to say PreferTunnelledDirConns rather than
3861 PreferTunneledDirConns, for those alternate-spellers out there.
3864 - Don't reevaluate all the information from our consensus document
3865 just because we've downloaded a v2 networkstatus that we intend
3866 to cache. Fixes bug 545; bugfix on 0.2.0.x.
3869 Changes in version 0.2.0.10-alpha - 2007-11-10
3870 This tenth development snapshot adds a third v3 directory authority
3871 run by Mike Perry, adds most of Karsten Loesing's new hidden service
3872 descriptor format, fixes a bad crash bug and new bridge bugs introduced
3873 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
3874 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
3875 addresses many more minor issues.
3877 o New directory authorities:
3878 - Set up ides (run by Mike Perry) as the third v3 directory authority.
3881 - Allow tunnelled directory connections to ask for an encrypted
3882 "begin_dir" connection or an anonymized "uses a full Tor circuit"
3883 connection independently. Now we can make anonymized begin_dir
3884 connections for (e.g.) more secure hidden service posting and
3886 - More progress on proposal 114: code from Karsten Loesing to
3887 implement new hidden service descriptor format.
3888 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
3889 accommodate the growing number of servers that use the default
3890 and are reaching it.
3891 - Directory authorities use a new formula for selecting which nodes
3892 to advertise as Guards: they must be in the top 7/8 in terms of
3893 how long we have known about them, and above the median of those
3894 nodes in terms of weighted fractional uptime.
3895 - Make "not enough dir info yet" warnings describe *why* Tor feels
3896 it doesn't have enough directory info yet.
3899 - Stop servers from crashing if they set a Family option (or
3900 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
3902 - Make bridge users work again -- the move to v3 directories in
3903 0.2.0.9-alpha had introduced a number of bugs that made bridges
3904 no longer work for clients.
3905 - When the clock jumps forward a lot, do not allow the bandwidth
3906 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
3908 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
3909 - When the consensus lists a router descriptor that we previously were
3910 mirroring, but that we considered non-canonical, reload the
3911 descriptor as canonical. This fixes bug 543 where Tor servers
3912 would start complaining after a few days that they don't have
3913 enough directory information to build a circuit.
3914 - Consider replacing the current consensus when certificates arrive
3915 that make the pending consensus valid. Previously, we were only
3916 considering replacement when the new certs _didn't_ help.
3917 - Fix an assert error on startup if we didn't already have the
3918 consensus and certs cached in our datadirectory: we were caching
3919 the consensus in consensus_waiting_for_certs but then free'ing it
3921 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
3922 Request) if we need more v3 certs but we've already got pending
3923 requests for all of them.
3924 - Correctly back off from failing certificate downloads. Fixes
3926 - Authorities don't vote on the Running flag if they have been running
3927 for less than 30 minutes themselves. Fixes bug 547, where a newly
3928 started authority would vote that everyone was down.
3931 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
3932 it, it had no AES, and it hasn't seen any security patches since
3936 - Clients now hold circuitless TLS connections open for 1.5 times
3937 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
3938 rebuild a new circuit over them within that timeframe. Previously,
3939 they held them open only for KeepalivePeriod (5 minutes).
3940 - Use "If-Modified-Since" to avoid retrieving consensus
3941 networkstatuses that we already have.
3942 - When we have no consensus, check FallbackNetworkstatusFile (defaults
3943 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
3944 we start knowing some directory caches.
3945 - When we receive a consensus from the future, warn about skew.
3946 - Improve skew reporting: try to give the user a better log message
3947 about how skewed they are, and how much this matters.
3948 - When we have a certificate for an authority, believe that
3949 certificate's claims about the authority's IP address.
3950 - New --quiet command-line option to suppress the default console log.
3951 Good in combination with --hash-password.
3952 - Authorities send back an X-Descriptor-Not-New header in response to
3953 an accepted-but-discarded descriptor upload. Partially implements
3955 - Make the log message for "tls error. breaking." more useful.
3956 - Better log messages about certificate downloads, to attempt to
3957 track down the second incarnation of bug 546.
3959 o Minor features (bridges):
3960 - If bridge users set UpdateBridgesFromAuthority, but the digest
3961 they ask for is a 404 from the bridge authority, they now fall
3962 back to trying the bridge directly.
3963 - Bridges now use begin_dir to publish their server descriptor to
3964 the bridge authority, even when they haven't set TunnelDirConns.
3966 o Minor features (controller):
3967 - When reporting clock skew, and we know that the clock is _at least
3968 as skewed_ as some value, but we don't know the actual value,
3969 report the value as a "minimum skew."
3972 - Update linux-tor-prio.sh script to allow QoS based on the uid of
3973 the Tor process. Patch from Marco Bonetti with tweaks from Mike
3977 - Refuse to start if both ORPort and UseBridges are set. Bugfix
3978 on 0.2.0.x, suggested by Matt Edman.
3979 - Don't stop fetching descriptors when FetchUselessDescriptors is
3980 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
3981 reported by tup and ioerror.
3982 - Better log message on vote from unknown authority.
3983 - Don't log "Launching 0 request for 0 router" message.
3985 o Minor bugfixes (memory leaks):
3986 - Stop leaking memory every time we parse a v3 certificate. Bugfix
3988 - Stop leaking memory every time we load a v3 certificate. Bugfix
3989 on 0.2.0.1-alpha. Fixes bug 536.
3990 - Stop leaking a cached networkstatus on exit. Bugfix on
3992 - Stop leaking voter information every time we free a consensus.
3993 Bugfix on 0.2.0.3-alpha.
3994 - Stop leaking signed data every time we check a voter signature.
3995 Bugfix on 0.2.0.3-alpha.
3996 - Stop leaking a signature every time we fail to parse a consensus or
3997 a vote. Bugfix on 0.2.0.3-alpha.
3998 - Stop leaking v2_download_status_map on shutdown. Bugfix on
4000 - Stop leaking conn->nickname every time we make a connection to a
4001 Tor relay without knowing its expected identity digest (e.g. when
4002 using bridges). Bugfix on 0.2.0.3-alpha.
4004 - Minor bugfixes (portability):
4005 - Run correctly on platforms where rlim_t is larger than unsigned
4006 long, and/or where the real limit for number of open files is
4007 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
4008 particular, these may be needed for OS X 10.5.
4011 Changes in version 0.1.2.18 - 2007-10-28
4012 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
4013 hidden service introduction that were causing huge delays, and a big
4014 bug that was causing some servers to disappear from the network status
4015 lists for a few hours each day.
4017 o Major bugfixes (crashes):
4018 - If a connection is shut down abruptly because of something that
4019 happened inside connection_flushed_some(), do not call
4020 connection_finished_flushing(). Should fix bug 451:
4021 "connection_stop_writing: Assertion conn->write_event failed"
4022 Bugfix on 0.1.2.7-alpha.
4023 - Fix possible segfaults in functions called from
4024 rend_process_relay_cell().
4026 o Major bugfixes (hidden services):
4027 - Hidden services were choosing introduction points uniquely by
4028 hexdigest, but when constructing the hidden service descriptor
4029 they merely wrote the (potentially ambiguous) nickname.
4030 - Clients now use the v2 intro format for hidden service
4031 connections: they specify their chosen rendezvous point by identity
4032 digest rather than by (potentially ambiguous) nickname. These
4033 changes could speed up hidden service connections dramatically.
4035 o Major bugfixes (other):
4036 - Stop publishing a new server descriptor just because we get a
4037 HUP signal. This led (in a roundabout way) to some servers getting
4038 dropped from the networkstatus lists for a few hours each day.
4039 - When looking for a circuit to cannibalize, consider family as well
4040 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4041 circuit cannibalization).
4042 - When a router wasn't listed in a new networkstatus, we were leaving
4043 the flags for that router alone -- meaning it remained Named,
4044 Running, etc -- even though absence from the networkstatus means
4045 that it shouldn't be considered to exist at all anymore. Now we
4046 clear all the flags for routers that fall out of the networkstatus
4047 consensus. Fixes bug 529.
4050 - Don't try to access (or alter) the state file when running
4051 --list-fingerprint or --verify-config or --hash-password. Resolves
4053 - When generating information telling us how to extend to a given
4054 router, do not try to include the nickname if it is
4055 absent. Resolves bug 467.
4056 - Fix a user-triggerable segfault in expand_filename(). (There isn't
4057 a way to trigger this remotely.)
4058 - When sending a status event to the controller telling it that an
4059 OR address is reachable, set the port correctly. (Previously we
4060 were reporting the dir port.)
4061 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4062 command. Bugfix on 0.1.2.17.
4063 - When loading bandwidth history, do not believe any information in
4064 the future. Fixes bug 434.
4065 - When loading entry guard information, do not believe any information
4067 - When we have our clock set far in the future and generate an
4068 onion key, then re-set our clock to be correct, we should not stop
4069 the onion key from getting rotated.
4070 - On some platforms, accept() can return a broken address. Detect
4071 this more quietly, and deal accordingly. Fixes bug 483.
4072 - It's not actually an error to find a non-pending entry in the DNS
4073 cache when canceling a pending resolve. Don't log unless stuff
4074 is fishy. Resolves bug 463.
4075 - Don't reset trusted dir server list when we set a configuration
4076 option. Patch from Robert Hogan.
4077 - Don't try to create the datadir when running --verify-config or
4078 --hash-password. Resolves bug 540.
4081 Changes in version 0.2.0.9-alpha - 2007-10-24
4082 This ninth development snapshot switches clients to the new v3 directory
4083 system; allows servers to be listed in the network status even when they
4084 have the same nickname as a registered server; and fixes many other
4085 bugs including a big one that was causing some servers to disappear
4086 from the network status lists for a few hours each day.
4088 o Major features (directory system):
4089 - Clients now download v3 consensus networkstatus documents instead
4090 of v2 networkstatus documents. Clients and caches now base their
4091 opinions about routers on these consensus documents. Clients only
4092 download router descriptors listed in the consensus.
4093 - Authorities now list servers who have the same nickname as
4094 a different named server, but list them with a new flag,
4095 "Unnamed". Now we can list servers that happen to pick the same
4096 nickname as a server that registered two years ago and then
4097 disappeared. Partially implements proposal 122.
4098 - If the consensus lists a router as "Unnamed", the name is assigned
4099 to a different router: do not identify the router by that name.
4100 Partially implements proposal 122.
4101 - Authorities can now come to a consensus on which method to use to
4102 compute the consensus. This gives us forward compatibility.
4105 - Stop publishing a new server descriptor just because we HUP or
4106 when we find our DirPort to be reachable but won't actually publish
4107 it. New descriptors without any real changes are dropped by the
4108 authorities, and can screw up our "publish every 18 hours" schedule.
4110 - When a router wasn't listed in a new networkstatus, we were leaving
4111 the flags for that router alone -- meaning it remained Named,
4112 Running, etc -- even though absence from the networkstatus means
4113 that it shouldn't be considered to exist at all anymore. Now we
4114 clear all the flags for routers that fall out of the networkstatus
4115 consensus. Fixes bug 529; bugfix on 0.1.2.x.
4116 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
4117 extrainfo documents and then discard them immediately for not
4118 matching the latest router. Bugfix on 0.2.0.1-alpha.
4120 o Minor features (v3 directory protocol):
4121 - Allow tor-gencert to generate a new certificate without replacing
4123 - Allow certificates to include an address.
4124 - When we change our directory-cache settings, reschedule all voting
4125 and download operations.
4126 - Reattempt certificate downloads immediately on failure, as long as
4127 we haven't failed a threshold number of times yet.
4128 - Delay retrying consensus downloads while we're downloading
4129 certificates to verify the one we just got. Also, count getting a
4130 consensus that we already have (or one that isn't valid) as a failure,
4131 and count failing to get the certificates after 20 minutes as a
4133 - Build circuits and download descriptors even if our consensus is a
4134 little expired. (This feature will go away once authorities are
4137 o Minor features (router descriptor cache):
4138 - If we find a cached-routers file that's been sitting around for more
4139 than 28 days unmodified, then most likely it's a leftover from
4140 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
4142 - When we (as a cache) download a descriptor because it was listed
4143 in a consensus, remember when the consensus was supposed to expire,
4144 and don't expire the descriptor until then.
4146 o Minor features (performance):
4147 - Call routerlist_remove_old_routers() much less often. This should
4148 speed startup, especially on directory caches.
4149 - Don't try to launch new descriptor downloads quite so often when we
4150 already have enough directory information to build circuits.
4151 - Base64 decoding was actually showing up on our profile when parsing
4152 the initial descriptor file; switch to an in-process all-at-once
4153 implementation that's about 3.5x times faster than calling out to
4156 o Minor features (compilation):
4157 - Detect non-ASCII platforms (if any still exist) and refuse to
4158 build there: some of our code assumes that 'A' is 65 and so on.
4160 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
4161 - Make the "next period" votes into "current period" votes immediately
4162 after publishing the consensus; avoid a heisenbug that made them
4163 stick around indefinitely.
4164 - When we discard a vote as a duplicate, do not report this as
4166 - Treat missing v3 keys or certificates as an error when running as a
4167 v3 directory authority.
4168 - When we're configured to be a v3 authority, but we're only listed
4169 as a non-v3 authority in our DirServer line for ourself, correct
4171 - If an authority doesn't have a qualified hostname, just put
4172 its address in the vote. This fixes the problem where we referred to
4173 "moria on moria:9031."
4174 - Distinguish between detached signatures for the wrong period, and
4175 detached signatures for a divergent vote.
4176 - Fix a small memory leak when computing a consensus.
4177 - When there's no concensus, we were forming a vote every 30
4178 minutes, but writing the "valid-after" line in our vote based
4179 on our configured V3AuthVotingInterval: so unless the intervals
4180 matched up, we immediately rejected our own vote because it didn't
4181 start at the voting interval that caused us to construct a vote.
4183 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
4184 - Delete unverified-consensus when the real consensus is set.
4185 - Consider retrying a consensus networkstatus fetch immediately
4186 after one fails: don't wait 60 seconds to notice.
4187 - When fetching a consensus as a cache, wait until a newer consensus
4188 should exist before trying to replace the current one.
4189 - Use a more forgiving schedule for retrying failed consensus
4190 downloads than for other types.
4192 o Minor bugfixes (other directory issues):
4193 - Correct the implementation of "download votes by digest." Bugfix on
4195 - Authorities no longer send back "400 you're unreachable please fix
4196 it" errors to Tor servers that aren't online all the time. We're
4197 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
4199 o Minor bugfixes (controller):
4200 - Don't reset trusted dir server list when we set a configuration
4201 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
4202 - Respond to INT and TERM SIGNAL commands before we execute the
4203 signal, in case the signal shuts us down. We had a patch in
4204 0.1.2.1-alpha that tried to do this by queueing the response on
4205 the connection's buffer before shutting down, but that really
4206 isn't the same thing at all. Bug located by Matt Edman.
4208 o Minor bugfixes (misc):
4209 - Correctly check for bad options to the "PublishServerDescriptor"
4210 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
4211 - Stop leaking memory on failing case of base32_decode, and make
4212 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
4213 - Don't try to download extrainfo documents when we're trying to
4214 fetch enough directory info to build a circuit: having enough
4215 info should get priority. Bugfix on 0.2.0.x.
4216 - Don't complain that "your server has not managed to confirm that its
4217 ports are reachable" if we haven't been able to build any circuits
4218 yet. Bug found by spending four hours without a v3 consensus. Bugfix
4220 - Detect the reason for failing to mmap a descriptor file we just
4221 wrote, and give a more useful log message. Fixes bug 533. Bugfix
4224 o Code simplifications and refactoring:
4225 - Remove support for the old bw_accounting file: we've been storing
4226 bandwidth accounting information in the state file since
4227 0.1.2.5-alpha. This may result in bandwidth accounting errors
4228 if you try to upgrade from 0.1.1.x or earlier, or if you try to
4229 downgrade to 0.1.1.x or earlier.
4230 - New convenience code to locate a file within the DataDirectory.
4231 - Move non-authority functionality out of dirvote.c.
4232 - Refactor the arguments for router_pick_{directory_|trusteddir}server
4233 so that they all take the same named flags.
4236 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
4237 Unix users an easy way to script their Tor process (e.g. by
4238 adjusting bandwidth based on the time of the day).
4241 Changes in version 0.2.0.8-alpha - 2007-10-12
4242 This eighth development snapshot fixes a crash bug that's been bothering
4243 us since February 2007, lets bridge authorities store a list of bridge
4244 descriptors they've seen, gets v3 directory voting closer to working,
4245 starts caching v3 directory consensus documents on directory mirrors,
4246 and fixes a variety of smaller issues including some minor memory leaks.
4248 o Major features (router descriptor cache):
4249 - Store routers in a file called cached-descriptors instead of in
4250 cached-routers. Initialize cached-descriptors from cached-routers
4251 if the old format is around. The new format allows us to store
4252 annotations along with descriptors.
4253 - Use annotations to record the time we received each descriptor, its
4254 source, and its purpose.
4255 - Disable the SETROUTERPURPOSE controller command: it is now
4257 - Controllers should now specify cache=no or cache=yes when using
4258 the +POSTDESCRIPTOR command.
4259 - Bridge authorities now write bridge descriptors to disk, meaning
4260 we can export them to other programs and begin distributing them
4263 o Major features (directory authorities):
4264 - When a v3 authority is missing votes or signatures, it now tries
4266 - Directory authorities track weighted fractional uptime as well as
4267 weighted mean-time-between failures. WFU is suitable for deciding
4268 whether a node is "usually up", while MTBF is suitable for deciding
4269 whether a node is "likely to stay up." We need both, because
4270 "usually up" is a good requirement for guards, while "likely to
4271 stay up" is a good requirement for long-lived connections.
4273 o Major features (v3 directory system):
4274 - Caches now download v3 network status documents as needed,
4275 and download the descriptors listed in them.
4276 - All hosts now attempt to download and keep fresh v3 authority
4277 certificates, and re-attempt after failures.
4278 - More internal-consistency checks for vote parsing.
4280 o Major bugfixes (crashes):
4281 - If a connection is shut down abruptly because of something that
4282 happened inside connection_flushed_some(), do not call
4283 connection_finished_flushing(). Should fix bug 451. Bugfix on
4286 o Major bugfixes (performance):
4287 - Fix really bad O(n^2) performance when parsing a long list of
4288 routers: Instead of searching the entire list for an "extra-info "
4289 string which usually wasn't there, once for every routerinfo
4290 we read, just scan lines forward until we find one we like.
4292 - When we add data to a write buffer in response to the data on that
4293 write buffer getting low because of a flush, do not consider the
4294 newly added data as a candidate for immediate flushing, but rather
4295 make it wait until the next round of writing. Otherwise, we flush
4296 and refill recursively, and a single greedy TLS connection can
4297 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
4299 o Minor features (v3 authority system):
4300 - Add more ways for tools to download the votes that lead to the
4302 - Send a 503 when low on bandwidth and a vote, consensus, or
4303 certificate is requested.
4304 - If-modified-since is now implemented properly for all kinds of
4305 certificate requests.
4307 o Minor bugfixes (network statuses):
4308 - Tweak the implementation of proposal 109 slightly: allow at most
4309 two Tor servers on the same IP address, except if it's the location
4310 of a directory authority, in which case allow five. Bugfix on
4313 o Minor bugfixes (controller):
4314 - When sending a status event to the controller telling it that an
4315 OR address is reachable, set the port correctly. (Previously we
4316 were reporting the dir port.) Bugfix on 0.1.2.x.
4318 o Minor bugfixes (v3 directory system):
4319 - Fix logic to look up a cert by its signing key digest. Bugfix on
4321 - Only change the reply to a vote to "OK" if it's not already
4322 set. This gets rid of annoying "400 OK" log messages, which may
4323 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
4324 - When we get a valid consensus, recompute the voting schedule.
4325 - Base the valid-after time of a vote on the consensus voting
4326 schedule, not on our preferred schedule.
4327 - Make the return values and messages from signature uploads and
4328 downloads more sensible.
4329 - Fix a memory leak when serving votes and consensus documents, and
4330 another when serving certificates.
4332 o Minor bugfixes (performance):
4333 - Use a slightly simpler string hashing algorithm (copying Python's
4334 instead of Java's) and optimize our digest hashing algorithm to take
4335 advantage of 64-bit platforms and to remove some possibly-costly
4337 - Fix a minor memory leak whenever we parse guards from our state
4338 file. Bugfix on 0.2.0.7-alpha.
4339 - Fix a minor memory leak whenever we write out a file. Bugfix on
4341 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4342 command. Bugfix on 0.2.0.5-alpha.
4344 o Minor bugfixes (portability):
4345 - On some platforms, accept() can return a broken address. Detect
4346 this more quietly, and deal accordingly. Fixes bug 483.
4347 - Stop calling tor_strlower() on uninitialized memory in some cases.
4348 Bugfix in 0.2.0.7-alpha.
4350 o Minor bugfixes (usability):
4351 - Treat some 403 responses from directory servers as INFO rather than
4352 WARN-severity events.
4353 - It's not actually an error to find a non-pending entry in the DNS
4354 cache when canceling a pending resolve. Don't log unless stuff is
4355 fishy. Resolves bug 463.
4357 o Minor bugfixes (anonymity):
4358 - Never report that we've used more bandwidth than we're willing to
4359 relay: it leaks how much non-relay traffic we're using. Resolves
4361 - When looking for a circuit to cannibalize, consider family as well
4362 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4363 circuit cannibalization).
4365 o Code simplifications and refactoring:
4366 - Make a bunch of functions static. Remove some dead code.
4367 - Pull out about a third of the really big routerlist.c; put it in a
4368 new module, networkstatus.c.
4369 - Merge the extra fields in local_routerstatus_t back into
4370 routerstatus_t: we used to need one routerstatus_t for each
4371 authority's opinion, plus a local_routerstatus_t for the locally
4372 computed consensus opinion. To save space, we put the locally
4373 modified fields into local_routerstatus_t, and only the common
4374 stuff into routerstatus_t. But once v3 directories are in use,
4375 clients and caches will no longer need to hold authority opinions;
4376 thus, the rationale for keeping the types separate is now gone.
4377 - Make the code used to reschedule and reattempt downloads more
4379 - Turn all 'Are we a directory server/mirror?' logic into a call to
4381 - Remove the code to generate the oldest (v1) directory format.
4382 The code has been disabled since 0.2.0.5-alpha.
4385 Changes in version 0.2.0.7-alpha - 2007-09-21
4386 This seventh development snapshot makes bridges work again, makes bridge
4387 authorities work for the first time, fixes two huge performance flaws
4388 in hidden services, and fixes a variety of minor issues.
4390 o New directory authorities:
4391 - Set up moria1 and tor26 as the first v3 directory authorities. See
4392 doc/spec/dir-spec.txt for details on the new directory design.
4394 o Major bugfixes (crashes):
4395 - Fix possible segfaults in functions called from
4396 rend_process_relay_cell(). Bugfix on 0.1.2.x.
4398 o Major bugfixes (bridges):
4399 - Fix a bug that made servers send a "404 Not found" in response to
4400 attempts to fetch their server descriptor. This caused Tor servers
4401 to take many minutes to establish reachability for their DirPort,
4402 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
4403 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
4404 users configure that and specify a bridge with an identity
4405 fingerprint, now they will lookup the bridge descriptor at the
4406 default bridge authority via a one-hop tunnel, but once circuits
4407 are established they will switch to a three-hop tunnel for later
4408 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
4410 o Major bugfixes (hidden services):
4411 - Hidden services were choosing introduction points uniquely by
4412 hexdigest, but when constructing the hidden service descriptor
4413 they merely wrote the (potentially ambiguous) nickname.
4414 - Clients now use the v2 intro format for hidden service
4415 connections: they specify their chosen rendezvous point by identity
4416 digest rather than by (potentially ambiguous) nickname. Both
4417 are bugfixes on 0.1.2.x, and they could speed up hidden service
4418 connections dramatically. Thanks to Karsten Loesing.
4420 o Minor features (security):
4421 - As a client, do not believe any server that tells us that an
4422 address maps to an internal address space.
4423 - Make it possible to enable HashedControlPassword and
4424 CookieAuthentication at the same time.
4426 o Minor features (guard nodes):
4427 - Tag every guard node in our state file with the version that
4428 we believe added it, or with our own version if we add it. This way,
4429 if a user temporarily runs an old version of Tor and then switches
4430 back to a new one, she doesn't automatically lose her guards.
4432 o Minor features (speed):
4433 - When implementing AES counter mode, update only the portions of the
4434 counter buffer that need to change, and don't keep separate
4435 network-order and host-order counters when they are the same (i.e.,
4436 on big-endian hosts.)
4438 o Minor features (controller):
4439 - Accept LF instead of CRLF on controller, since some software has a
4440 hard time generating real Internet newlines.
4441 - Add GETINFO values for the server status events
4442 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
4446 - Routers no longer include bandwidth-history lines in their
4447 descriptors; this information is already available in extra-info
4448 documents, and including it in router descriptors took up 60%
4449 (!) of compressed router descriptor downloads. Completes
4450 implementation of proposal 104.
4451 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
4452 and TorControl.py, as they use the old v0 controller protocol,
4453 and are obsoleted by TorFlow anyway.
4454 - Drop support for v1 rendezvous descriptors, since we never used
4455 them anyway, and the code has probably rotted by now. Based on
4456 patch from Karsten Loesing.
4457 - On OSX, stop warning the user that kqueue support in libevent is
4458 "experimental", since it seems to have worked fine for ages.
4461 - When generating information telling us how to extend to a given
4462 router, do not try to include the nickname if it is absent. Fixes
4463 bug 467. Bugfix on 0.2.0.3-alpha.
4464 - Fix a user-triggerable (but not remotely-triggerable) segfault
4465 in expand_filename(). Bugfix on 0.1.2.x.
4466 - Fix a memory leak when freeing incomplete requests from DNSPort.
4467 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
4468 - Don't try to access (or alter) the state file when running
4469 --list-fingerprint or --verify-config or --hash-password. (Resolves
4470 bug 499.) Bugfix on 0.1.2.x.
4471 - Servers used to decline to publish their DirPort if their
4472 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
4473 were below a threshold. Now they only look at BandwidthRate and
4474 RelayBandwidthRate. Bugfix on 0.1.2.x.
4475 - Remove an optimization in the AES counter-mode code that assumed
4476 that the counter never exceeded 2^68. When the counter can be set
4477 arbitrarily as an IV (as it is by Karsten's new hidden services
4478 code), this assumption no longer holds. Bugfix on 0.1.2.x.
4479 - Resume listing "AUTHORITY" flag for authorities in network status.
4480 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
4482 o Code simplifications and refactoring:
4483 - Revamp file-writing logic so we don't need to have the entire
4484 contents of a file in memory at once before we write to disk. Tor,
4486 - Turn "descriptor store" into a full-fledged type.
4487 - Move all NT services code into a separate source file.
4488 - Unify all code that computes medians, percentile elements, etc.
4489 - Get rid of a needless malloc when parsing address policies.
4492 Changes in version 0.1.2.17 - 2007-08-30
4493 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
4494 X bundles. Vidalia 0.0.14 makes authentication required for the
4495 ControlPort in the default configuration, which addresses important
4496 security risks. Everybody who uses Vidalia (or another controller)
4499 In addition, this Tor update fixes major load balancing problems with
4500 path selection, which should speed things up a lot once many people
4503 o Major bugfixes (security):
4504 - We removed support for the old (v0) control protocol. It has been
4505 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
4506 become more of a headache than it's worth.
4508 o Major bugfixes (load balancing):
4509 - When choosing nodes for non-guard positions, weight guards
4510 proportionally less, since they already have enough load. Patch
4512 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4513 will allow fast Tor servers to get more attention.
4514 - When we're upgrading from an old Tor version, forget our current
4515 guards and pick new ones according to the new weightings. These
4516 three load balancing patches could raise effective network capacity
4517 by a factor of four. Thanks to Mike Perry for measurements.
4519 o Major bugfixes (stream expiration):
4520 - Expire not-yet-successful application streams in all cases if
4521 they've been around longer than SocksTimeout. Right now there are
4522 some cases where the stream will live forever, demanding a new
4523 circuit every 15 seconds. Fixes bug 454; reported by lodger.
4525 o Minor features (controller):
4526 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4527 is valid before any authentication has been received. It tells
4528 a controller what kind of authentication is expected, and what
4529 protocol is spoken. Implements proposal 119.
4531 o Minor bugfixes (performance):
4532 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
4533 greatly speeding up loading cached-routers from disk on startup.
4534 - Disable sentinel-based debugging for buffer code: we squashed all
4535 the bugs that this was supposed to detect a long time ago, and now
4536 its only effect is to change our buffer sizes from nice powers of
4537 two (which platform mallocs tend to like) to values slightly over
4538 powers of two (which make some platform mallocs sad).
4540 o Minor bugfixes (misc):
4541 - If exit bandwidth ever exceeds one third of total bandwidth, then
4542 use the correct formula to weight exit nodes when choosing paths.
4543 Based on patch from Mike Perry.
4544 - Choose perfectly fairly among routers when choosing by bandwidth and
4545 weighting by fraction of bandwidth provided by exits. Previously, we
4546 would choose with only approximate fairness, and correct ourselves
4547 if we ran off the end of the list.
4548 - If we require CookieAuthentication but we fail to write the
4549 cookie file, we would warn but not exit, and end up in a state
4550 where no controller could authenticate. Now we exit.
4551 - If we require CookieAuthentication, stop generating a new cookie
4552 every time we change any piece of our config.
4553 - Refuse to start with certain directory authority keys, and
4554 encourage people using them to stop.
4555 - Terminate multi-line control events properly. Original patch
4557 - Fix a minor memory leak when we fail to find enough suitable
4558 servers to choose a circuit.
4559 - Stop leaking part of the descriptor when we run into a particularly
4560 unparseable piece of it.
4563 Changes in version 0.2.0.6-alpha - 2007-08-26
4564 This sixth development snapshot features a new Vidalia version in the
4565 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
4566 the ControlPort in the default configuration, which addresses important
4569 In addition, this snapshot fixes major load balancing problems
4570 with path selection, which should speed things up a lot once many
4571 people have upgraded. The directory authorities also use a new
4572 mean-time-between-failure approach to tracking which servers are stable,
4573 rather than just looking at the most recent uptime.
4575 o New directory authorities:
4576 - Set up Tonga as the default bridge directory authority.
4579 - Directory authorities now track servers by weighted
4580 mean-times-between-failures. When we have 4 or more days of data,
4581 use measured MTBF rather than declared uptime to decide whether
4582 to call a router Stable. Implements proposal 108.
4584 o Major bugfixes (load balancing):
4585 - When choosing nodes for non-guard positions, weight guards
4586 proportionally less, since they already have enough load. Patch
4588 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4589 will allow fast Tor servers to get more attention.
4590 - When we're upgrading from an old Tor version, forget our current
4591 guards and pick new ones according to the new weightings. These
4592 three load balancing patches could raise effective network capacity
4593 by a factor of four. Thanks to Mike Perry for measurements.
4595 o Major bugfixes (descriptor parsing):
4596 - Handle unexpected whitespace better in malformed descriptors. Bug
4597 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
4600 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
4601 GETINFO for Torstat to use until it can switch to using extrainfos.
4602 - Optionally (if built with -DEXPORTMALLINFO) export the output
4603 of mallinfo via http, as tor/mallinfo.txt. Only accessible
4607 - Do not intermix bridge routers with controller-added
4608 routers. (Bugfix on 0.2.0.x)
4609 - Do not fail with an assert when accept() returns an unexpected
4610 address family. Addresses but does not wholly fix bug 483. (Bugfix
4612 - Let directory authorities startup even when they can't generate
4613 a descriptor immediately, e.g. because they don't know their
4615 - Stop putting the authentication cookie in a file called "0"
4616 in your working directory if you don't specify anything for the
4617 new CookieAuthFile option. Reported by Matt Edman.
4618 - Make it possible to read the PROTOCOLINFO response in a way that
4619 conforms to our control-spec. Reported by Matt Edman.
4620 - Fix a minor memory leak when we fail to find enough suitable
4621 servers to choose a circuit. Bugfix on 0.1.2.x.
4622 - Stop leaking part of the descriptor when we run into a particularly
4623 unparseable piece of it. Bugfix on 0.1.2.x.
4624 - Unmap the extrainfo cache file on exit.
4627 Changes in version 0.2.0.5-alpha - 2007-08-19
4628 This fifth development snapshot fixes compilation on Windows again;
4629 fixes an obnoxious client-side bug that slowed things down and put
4630 extra load on the network; gets us closer to using the v3 directory
4631 voting scheme; makes it easier for Tor controllers to use cookie-based
4632 authentication; and fixes a variety of other bugs.
4635 - Version 1 directories are no longer generated in full. Instead,
4636 authorities generate and serve "stub" v1 directories that list
4637 no servers. This will stop Tor versions 0.1.0.x and earlier from
4638 working, but (for security reasons) nobody should be running those
4641 o Major bugfixes (compilation, 0.2.0.x):
4642 - Try to fix Win32 compilation again: improve checking for IPv6 types.
4643 - Try to fix MSVC compilation: build correctly on platforms that do
4644 not define s6_addr16 or s6_addr32.
4645 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
4648 o Major bugfixes (stream expiration):
4649 - Expire not-yet-successful application streams in all cases if
4650 they've been around longer than SocksTimeout. Right now there are
4651 some cases where the stream will live forever, demanding a new
4652 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
4655 o Minor features (directory servers):
4656 - When somebody requests a list of statuses or servers, and we have
4657 none of those, return a 404 rather than an empty 200.
4659 o Minor features (directory voting):
4660 - Store v3 consensus status consensuses on disk, and reload them
4663 o Minor features (security):
4664 - Warn about unsafe ControlPort configurations.
4665 - Refuse to start with certain directory authority keys, and
4666 encourage people using them to stop.
4668 o Minor features (controller):
4669 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4670 is valid before any authentication has been received. It tells
4671 a controller what kind of authentication is expected, and what
4672 protocol is spoken. Implements proposal 119.
4673 - New config option CookieAuthFile to choose a new location for the
4674 cookie authentication file, and config option
4675 CookieAuthFileGroupReadable to make it group-readable.
4677 o Minor features (unit testing):
4678 - Add command-line arguments to unit-test executable so that we can
4679 invoke any chosen test from the command line rather than having
4680 to run the whole test suite at once; and so that we can turn on
4681 logging for the unit tests.
4683 o Minor bugfixes (on 0.1.2.x):
4684 - If we require CookieAuthentication but we fail to write the
4685 cookie file, we would warn but not exit, and end up in a state
4686 where no controller could authenticate. Now we exit.
4687 - If we require CookieAuthentication, stop generating a new cookie
4688 every time we change any piece of our config.
4689 - When loading bandwidth history, do not believe any information in
4690 the future. Fixes bug 434.
4691 - When loading entry guard information, do not believe any information
4693 - When we have our clock set far in the future and generate an
4694 onion key, then re-set our clock to be correct, we should not stop
4695 the onion key from getting rotated.
4696 - Clean up torrc sample config file.
4697 - Do not automatically run configure from autogen.sh. This
4698 non-standard behavior tended to annoy people who have built other
4701 o Minor bugfixes (on 0.2.0.x):
4702 - Fix a bug with AutomapHostsOnResolve that would always cause
4703 the second request to fail. Bug reported by Kate. Bugfix on
4705 - Fix a bug in ADDRMAP controller replies that would sometimes
4706 try to print a NULL. Patch from tup.
4707 - Read v3 directory authority keys from the right location.
4708 - Numerous bugfixes to directory voting code.
4711 Changes in version 0.1.2.16 - 2007-08-01
4712 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
4713 remote attacker in certain situations to rewrite the user's torrc
4714 configuration file. This can completely compromise anonymity of users
4715 in most configurations, including those running the Vidalia bundles,
4716 TorK, etc. Or worse.
4718 o Major security fixes:
4719 - Close immediately after missing authentication on control port;
4720 do not allow multiple authentication attempts.
4723 Changes in version 0.2.0.4-alpha - 2007-08-01
4724 This fourth development snapshot fixes a critical security vulnerability
4725 for most users, specifically those running Vidalia, TorK, etc. Everybody
4726 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
4728 o Major security fixes:
4729 - Close immediately after missing authentication on control port;
4730 do not allow multiple authentication attempts.
4732 o Major bugfixes (compilation):
4733 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
4736 o Minor features (performance):
4737 - Be even more aggressive about releasing RAM from small
4738 empty buffers. Thanks to our free-list code, this shouldn't be too
4739 performance-intensive.
4740 - Disable sentinel-based debugging for buffer code: we squashed all
4741 the bugs that this was supposed to detect a long time ago, and
4742 now its only effect is to change our buffer sizes from nice
4743 powers of two (which platform mallocs tend to like) to values
4744 slightly over powers of two (which make some platform mallocs sad).
4745 - Log malloc statistics from mallinfo() on platforms where it
4749 Changes in version 0.2.0.3-alpha - 2007-07-29
4750 This third development snapshot introduces new experimental
4751 blocking-resistance features and a preliminary version of the v3
4752 directory voting design, and includes many other smaller features
4756 - The first pieces of our "bridge" design for blocking-resistance
4757 are implemented. People can run bridge directory authorities;
4758 people can run bridges; and people can configure their Tor clients
4759 with a set of bridges to use as the first hop into the Tor network.
4760 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
4762 - Create listener connections before we setuid to the configured
4763 User and Group. Now non-Windows users can choose port values
4764 under 1024, start Tor as root, and have Tor bind those ports
4765 before it changes to another UID. (Windows users could already
4767 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
4768 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
4769 on "vserver" accounts. (Patch from coderman.)
4770 - Be even more aggressive about separating local traffic from relayed
4771 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
4773 o Major features (experimental):
4774 - First cut of code for "v3 dir voting": directory authorities will
4775 vote on a common network status document rather than each publishing
4776 their own opinion. This code needs more testing and more corner-case
4777 handling before it's ready for use.
4780 - Directory authorities now call routers Fast if their bandwidth is
4781 at least 100KB/s, and consider their bandwidth adequate to be a
4782 Guard if it is at least 250KB/s, no matter the medians. This fix
4783 complements proposal 107. [Bugfix on 0.1.2.x]
4784 - Directory authorities now never mark more than 3 servers per IP as
4785 Valid and Running. (Implements proposal 109, by Kevin Bauer and
4787 - Minor change to organizationName and commonName generation
4788 procedures in TLS certificates during Tor handshakes, to invalidate
4789 some earlier censorware approaches. This is not a long-term
4790 solution, but applying it will give us a bit of time to look into
4791 the epidemiology of countermeasures as they spread.
4793 o Major bugfixes (directory):
4794 - Rewrite directory tokenization code to never run off the end of
4795 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
4797 o Minor features (controller):
4798 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
4799 match requests to applications. (Patch from Robert Hogan.)
4800 - Report address and port correctly on connections to DNSPort. (Patch
4802 - Add a RESOLVE command to launch hostname lookups. (Original patch
4804 - Add GETINFO status/enough-dir-info to let controllers tell whether
4805 Tor has downloaded sufficient directory information. (Patch
4807 - You can now use the ControlSocket option to tell Tor to listen for
4808 controller connections on Unix domain sockets on systems that
4809 support them. (Patch from Peter Palfrader.)
4810 - STREAM NEW events are generated for DNSPort requests and for
4811 tunneled directory connections. (Patch from Robert Hogan.)
4812 - New "GETINFO address-mappings/*" command to get address mappings
4813 with expiry information. "addr-mappings/*" is now deprecated.
4816 o Minor features (misc):
4817 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
4819 - The tor-gencert tool for v3 directory authorities now creates all
4820 files as readable to the file creator only, and write-protects
4821 the authority identity key.
4822 - When dumping memory usage, list bytes used in buffer memory
4824 - When running with dmalloc, dump more stats on hup and on exit.
4825 - Directory authorities now fail quickly and (relatively) harmlessly
4826 if they generate a network status document that is somehow
4829 o Traffic load balancing improvements:
4830 - If exit bandwidth ever exceeds one third of total bandwidth, then
4831 use the correct formula to weight exit nodes when choosing paths.
4832 (Based on patch from Mike Perry.)
4833 - Choose perfectly fairly among routers when choosing by bandwidth and
4834 weighting by fraction of bandwidth provided by exits. Previously, we
4835 would choose with only approximate fairness, and correct ourselves
4836 if we ran off the end of the list. [Bugfix on 0.1.2.x]
4838 o Performance improvements:
4839 - Be more aggressive with freeing buffer RAM or putting it on the
4841 - Use Critical Sections rather than Mutexes for synchronizing threads
4842 on win32; Mutexes are heavier-weight, and designed for synchronizing
4845 o Deprecated and removed features:
4846 - RedirectExits is now deprecated.
4847 - Stop allowing address masks that do not correspond to bit prefixes.
4848 We have warned about these for a really long time; now it's time
4849 to reject them. (Patch from croup.)
4851 o Minor bugfixes (directory):
4852 - Fix another crash bug related to extra-info caching. (Bug found by
4853 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
4854 - Directories no longer return a "304 not modified" when they don't
4855 have the networkstatus the client asked for. Also fix a memory
4856 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
4857 - We had accidentally labelled 0.1.2.x directory servers as not
4858 suitable for begin_dir requests, and had labelled no directory
4859 servers as suitable for uploading extra-info documents. [Bugfix
4862 o Minor bugfixes (dns):
4863 - Fix a crash when DNSPort is set more than once. (Patch from Robert
4864 Hogan.) [Bugfix on 0.2.0.2-alpha]
4865 - Add DNSPort connections to the global connection list, so that we
4866 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
4868 - Fix a dangling reference that could lead to a crash when DNSPort is
4869 changed or closed (Patch from Robert Hogan.) [Bugfix on
4872 o Minor bugfixes (controller):
4873 - Provide DNS expiry times in GMT, not in local time. For backward
4874 compatibility, ADDRMAP events only provide GMT expiry in an extended
4875 field. "GETINFO address-mappings" always does the right thing.
4876 - Use CRLF line endings properly in NS events.
4877 - Terminate multi-line control events properly. (Original patch
4878 from tup.) [Bugfix on 0.1.2.x-alpha]
4879 - Do not include spaces in SOURCE_ADDR fields in STREAM
4880 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
4883 Changes in version 0.1.2.15 - 2007-07-17
4884 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
4885 problems, fixes compilation on BSD, and fixes a variety of other
4886 bugs. Everybody should upgrade.
4888 o Major bugfixes (compilation):
4889 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
4891 o Major bugfixes (crashes):
4892 - Try even harder not to dereference the first character after
4893 an mmap(). Reported by lodger.
4894 - Fix a crash bug in directory authorities when we re-number the
4895 routerlist while inserting a new router.
4896 - When the cached-routers file is an even multiple of the page size,
4897 don't run off the end and crash. (Fixes bug 455; based on idea
4899 - Fix eventdns.c behavior on Solaris: It is critical to include
4900 orconfig.h _before_ sys/types.h, so that we can get the expected
4901 definition of _FILE_OFFSET_BITS.
4903 o Major bugfixes (security):
4904 - Fix a possible buffer overrun when using BSD natd support. Bug
4906 - When sending destroy cells from a circuit's origin, don't include
4907 the reason for tearing down the circuit. The spec says we didn't,
4908 and now we actually don't. Reported by lodger.
4909 - Keep streamids from different exits on a circuit separate. This
4910 bug may have allowed other routers on a given circuit to inject
4911 cells into streams. Reported by lodger; fixes bug 446.
4912 - If there's a never-before-connected-to guard node in our list,
4913 never choose any guards past it. This way we don't expand our
4914 guard list unless we need to.
4916 o Minor bugfixes (guard nodes):
4917 - Weight guard selection by bandwidth, so that low-bandwidth nodes
4918 don't get overused as guards.
4920 o Minor bugfixes (directory):
4921 - Correctly count the number of authorities that recommend each
4922 version. Previously, we were under-counting by 1.
4923 - Fix a potential crash bug when we load many server descriptors at
4924 once and some of them make others of them obsolete. Fixes bug 458.
4926 o Minor bugfixes (hidden services):
4927 - Stop tearing down the whole circuit when the user asks for a
4928 connection to a port that the hidden service didn't configure.
4931 o Minor bugfixes (misc):
4932 - On Windows, we were preventing other processes from reading
4933 cached-routers while Tor was running. Reported by janbar.
4934 - Fix a possible (but very unlikely) bug in picking routers by
4935 bandwidth. Add a log message to confirm that it is in fact
4936 unlikely. Patch from lodger.
4937 - Backport a couple of memory leak fixes.
4938 - Backport miscellaneous cosmetic bugfixes.
4941 Changes in version 0.2.0.2-alpha - 2007-06-02
4942 o Major bugfixes on 0.2.0.1-alpha:
4943 - Fix an assertion failure related to servers without extra-info digests.
4944 Resolves bugs 441 and 442.
4946 o Minor features (directory):
4947 - Support "If-Modified-Since" when answering HTTP requests for
4948 directories, running-routers documents, and network-status documents.
4949 (There's no need to support it for router descriptors, since those
4950 are downloaded by descriptor digest.)
4952 o Minor build issues:
4953 - Clear up some MIPSPro compiler warnings.
4954 - When building from a tarball on a machine that happens to have SVK
4955 installed, report the micro-revision as whatever version existed
4956 in the tarball, not as "x".
4959 Changes in version 0.2.0.1-alpha - 2007-06-01
4960 This early development snapshot provides new features for people running
4961 Tor as both a client and a server (check out the new RelayBandwidth
4962 config options); lets Tor run as a DNS proxy; and generally moves us
4963 forward on a lot of fronts.
4965 o Major features, server usability:
4966 - New config options RelayBandwidthRate and RelayBandwidthBurst:
4967 a separate set of token buckets for relayed traffic. Right now
4968 relayed traffic is defined as answers to directory requests, and
4969 OR connections that don't have any local circuits on them.
4971 o Major features, client usability:
4972 - A client-side DNS proxy feature to replace the need for
4973 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
4974 for DNS requests on port 9999, use the Tor network to resolve them
4975 anonymously, and send the reply back like a regular DNS server.
4976 The code still only implements a subset of DNS.
4977 - Make PreferTunneledDirConns and TunnelDirConns work even when
4978 we have no cached directory info. This means Tor clients can now
4979 do all of their connections protected by TLS.
4981 o Major features, performance and efficiency:
4982 - Directory authorities accept and serve "extra info" documents for
4983 routers. These documents contain fields from router descriptors
4984 that aren't usually needed, and that use a lot of excess
4985 bandwidth. Once these fields are removed from router descriptors,
4986 the bandwidth savings should be about 60%. [Partially implements
4988 - Servers upload extra-info documents to any authority that accepts
4989 them. Authorities (and caches that have been configured to download
4990 extra-info documents) download them as needed. [Partially implements
4992 - Change the way that Tor buffers data that it is waiting to write.
4993 Instead of queueing data cells in an enormous ring buffer for each
4994 client->OR or OR->OR connection, we now queue cells on a separate
4995 queue for each circuit. This lets us use less slack memory, and
4996 will eventually let us be smarter about prioritizing different kinds
4998 - Use memory pools to allocate cells with better speed and memory
4999 efficiency, especially on platforms where malloc() is inefficient.
5000 - Stop reading on edge connections when their corresponding circuit
5001 buffers are full; start again as the circuits empty out.
5003 o Major features, other:
5004 - Add an HSAuthorityRecordStats option that hidden service authorities
5005 can use to track statistics of overall hidden service usage without
5006 logging information that would be very useful to an attacker.
5007 - Start work implementing multi-level keys for directory authorities:
5008 Add a standalone tool to generate key certificates. (Proposal 103.)
5011 - Directory authorities now call routers Stable if they have an
5012 uptime of at least 30 days, even if that's not the median uptime
5013 in the network. Implements proposal 107, suggested by Kevin Bauer
5016 o Minor fixes (resource management):
5017 - Count the number of open sockets separately from the number
5018 of active connection_t objects. This will let us avoid underusing
5019 our allocated connection limit.
5020 - We no longer use socket pairs to link an edge connection to an
5021 anonymous directory connection or a DirPort test connection.
5022 Instead, we track the link internally and transfer the data
5023 in-process. This saves two sockets per "linked" connection (at the
5024 client and at the server), and avoids the nasty Windows socketpair()
5026 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
5027 for every single inactive connection_t. Free items from the
5028 4k/16k-buffer free lists when they haven't been used for a while.
5030 o Minor features (build):
5031 - Make autoconf search for libevent, openssl, and zlib consistently.
5032 - Update deprecated macros in configure.in.
5033 - When warning about missing headers, tell the user to let us
5034 know if the compile succeeds anyway, so we can downgrade the
5036 - Include the current subversion revision as part of the version
5037 string: either fetch it directly if we're in an SVN checkout, do
5038 some magic to guess it if we're in an SVK checkout, or use
5039 the last-detected version if we're building from a .tar.gz.
5040 Use this version consistently in log messages.
5042 o Minor features (logging):
5043 - Always prepend "Bug: " to any log message about a bug.
5044 - Put a platform string (e.g. "Linux i686") in the startup log
5045 message, so when people paste just their logs, we know if it's
5046 OpenBSD or Windows or what.
5047 - When logging memory usage, break down memory used in buffers by
5050 o Minor features (directory system):
5051 - New config option V2AuthoritativeDirectory that all directory
5052 authorities should set. This will let future authorities choose
5053 not to serve V2 directory information.
5054 - Directory authorities allow multiple router descriptors and/or extra
5055 info documents to be uploaded in a single go. This will make
5056 implementing proposal 104 simpler.
5058 o Minor features (controller):
5059 - Add a new config option __DisablePredictedCircuits designed for
5060 use by the controller, when we don't want Tor to build any circuits
5062 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
5063 so we can exit from the middle of the circuit.
5064 - Implement "getinfo status/circuit-established".
5065 - Implement "getinfo status/version/..." so a controller can tell
5066 whether the current version is recommended, and whether any versions
5067 are good, and how many authorities agree. (Patch from shibz.)
5069 o Minor features (hidden services):
5070 - Allow multiple HiddenServicePort directives with the same virtual
5071 port; when they occur, the user is sent round-robin to one
5072 of the target ports chosen at random. Partially fixes bug 393 by
5073 adding limited ad-hoc round-robining.
5075 o Minor features (other):
5077 - Add a new AutomapHostsOnResolve option: when it is enabled, any
5078 resolve request for hosts matching a given pattern causes Tor to
5079 generate an internal virtual address mapping for that host. This
5080 allows DNSPort to work sensibly with hidden service users. By
5081 default, .exit and .onion addresses are remapped; the list of
5082 patterns can be reconfigured with AutomapHostsSuffixes.
5083 - Add an "-F" option to tor-resolve to force a resolve for a .onion
5084 address. Thanks to the AutomapHostsOnResolve option, this is no
5085 longer a completely silly thing to do.
5086 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
5087 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
5088 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
5089 minus 1 byte: the actual maximum declared bandwidth.
5092 - Removed support for the old binary "version 0" controller protocol.
5093 This has been deprecated since 0.1.1, and warnings have been issued
5094 since 0.1.2. When we encounter a v0 control message, we now send
5095 back an error and close the connection.
5096 - Remove the old "dns worker" server DNS code: it hasn't been default
5097 since 0.1.2.2-alpha, and all the servers seem to be using the new
5100 o Minor bugfixes (portability):
5101 - Even though Windows is equally happy with / and \ as path separators,
5102 try to use \ consistently on Windows and / consistently on Unix: it
5103 makes the log messages nicer.
5104 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
5105 - Read resolv.conf files correctly on platforms where read() returns
5106 partial results on small file reads.
5108 o Minor bugfixes (directory):
5109 - Correctly enforce that elements of directory objects do not appear
5110 more often than they are allowed to appear.
5111 - When we are reporting the DirServer line we just parsed, we were
5112 logging the second stanza of the key fingerprint, not the first.
5114 o Minor bugfixes (logging):
5115 - When we hit an EOF on a log (probably because we're shutting down),
5116 don't try to remove the log from the list: just mark it as
5117 unusable. (Bulletproofs against bug 222.)
5119 o Minor bugfixes (other):
5120 - In the exitlist script, only consider the most recently published
5121 server descriptor for each server. Also, when the user requests
5122 a list of servers that _reject_ connections to a given address,
5123 explicitly exclude the IPs that also have servers that accept
5124 connections to that address. (Resolves bug 405.)
5125 - Stop allowing hibernating servers to be "stable" or "fast".
5126 - On Windows, we were preventing other processes from reading
5127 cached-routers while Tor was running. (Reported by janbar)
5128 - Make the NodeFamilies config option work. (Reported by
5129 lodger -- it has never actually worked, even though we added it
5131 - Check return values from pthread_mutex functions.
5132 - Don't save non-general-purpose router descriptors to the disk cache,
5133 because we have no way of remembering what their purpose was when
5135 - Add even more asserts to hunt down bug 417.
5136 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
5137 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
5138 Add a log message to confirm that it is in fact unlikely.
5140 o Minor bugfixes (controller):
5141 - Make 'getinfo fingerprint' return a 551 error if we're not a
5142 server, so we match what the control spec claims we do. Reported
5144 - Fix a typo in an error message when extendcircuit fails that
5145 caused us to not follow the \r\n-based delimiter protocol. Reported
5148 o Code simplifications and refactoring:
5149 - Stop passing around circuit_t and crypt_path_t pointers that are
5150 implicit in other procedure arguments.
5151 - Drop the old code to choke directory connections when the
5152 corresponding OR connections got full: thanks to the cell queue
5153 feature, OR conns don't get full any more.
5154 - Make dns_resolve() handle attaching connections to circuits
5155 properly, so the caller doesn't have to.
5156 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
5157 - Keep the connection array as a dynamic smartlist_t, rather than as
5158 a fixed-sized array. This is important, as the number of connections
5159 is becoming increasingly decoupled from the number of sockets.
5162 Changes in version 0.1.2.14 - 2007-05-25
5163 Tor 0.1.2.14 changes the addresses of two directory authorities (this
5164 change especially affects those who serve or use hidden services),
5165 and fixes several other crash- and security-related bugs.
5167 o Directory authority changes:
5168 - Two directory authorities (moria1 and moria2) just moved to new
5169 IP addresses. This change will particularly affect those who serve
5170 or use hidden services.
5172 o Major bugfixes (crashes):
5173 - If a directory server runs out of space in the connection table
5174 as it's processing a begin_dir request, it will free the exit stream
5175 but leave it attached to the circuit, leading to unpredictable
5176 behavior. (Reported by seeess, fixes bug 425.)
5177 - Fix a bug in dirserv_remove_invalid() that would cause authorities
5178 to corrupt memory under some really unlikely scenarios.
5179 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
5180 - Avoid segfaults when reading from mmaped descriptor file. (Reported
5183 o Major bugfixes (security):
5184 - When choosing an entry guard for a circuit, avoid using guards
5185 that are in the same family as the chosen exit -- not just guards
5186 that are exactly the chosen exit. (Reported by lodger.)
5188 o Major bugfixes (resource management):
5189 - If a directory authority is down, skip it when deciding where to get
5190 networkstatus objects or descriptors. Otherwise we keep asking
5191 every 10 seconds forever. Fixes bug 384.
5192 - Count it as a failure if we fetch a valid network-status but we
5193 don't want to keep it. Otherwise we'll keep fetching it and keep
5194 not wanting to keep it. Fixes part of bug 422.
5195 - If all of our dirservers have given us bad or no networkstatuses
5196 lately, then stop hammering them once per minute even when we
5197 think they're failed. Fixes another part of bug 422.
5200 - Actually set the purpose correctly for descriptors inserted with
5202 - When we have k non-v2 authorities in our DirServer config,
5203 we ignored the last k authorities in the list when updating our
5205 - Correctly back-off from requesting router descriptors that we are
5206 having a hard time downloading.
5207 - Read resolv.conf files correctly on platforms where read() returns
5208 partial results on small file reads.
5209 - Don't rebuild the entire router store every time we get 32K of
5210 routers: rebuild it when the journal gets very large, or when
5211 the gaps in the store get very large.
5214 - When routers publish SVN revisions in their router descriptors,
5215 authorities now include those versions correctly in networkstatus
5217 - Warn when using a version of libevent before 1.3b to run a server on
5218 OSX or BSD: these versions interact badly with userspace threads.
5221 Changes in version 0.1.2.13 - 2007-04-24
5222 This release features some major anonymity fixes, such as safer path
5223 selection; better client performance; faster bootstrapping, better
5224 address detection, and better DNS support for servers; write limiting as
5225 well as read limiting to make servers easier to run; and a huge pile of
5226 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
5228 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
5229 of the Freenode IRC network, remembering his patience and vision for
5230 free speech on the Internet.
5233 - Fix a memory leak when we ask for "all" networkstatuses and we
5234 get one we don't recognize.
5235 - Add more asserts to hunt down bug 417.
5236 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
5239 Changes in version 0.1.2.12-rc - 2007-03-16
5241 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
5242 directory information requested inside Tor connections (i.e. via
5243 begin_dir cells). It only triggered when the same connection was
5244 serving other data at the same time. Reported by seeess.
5247 - When creating a circuit via the controller, send a 'launched'
5248 event when we're done, so we follow the spec better.
5251 Changes in version 0.1.2.11-rc - 2007-03-15
5252 o Minor bugfixes (controller), reported by daejees:
5253 - Correct the control spec to match how the code actually responds
5254 to 'getinfo addr-mappings/*'.
5255 - The control spec described a GUARDS event, but the code
5256 implemented a GUARD event. Standardize on GUARD, but let people
5260 Changes in version 0.1.2.10-rc - 2007-03-07
5261 o Major bugfixes (Windows):
5262 - Do not load the NT services library functions (which may not exist)
5263 just to detect if we're a service trying to shut down. Now we run
5264 on Win98 and friends again.
5266 o Minor bugfixes (other):
5267 - Clarify a couple of log messages.
5268 - Fix a misleading socks5 error number.
5271 Changes in version 0.1.2.9-rc - 2007-03-02
5272 o Major bugfixes (Windows):
5273 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
5274 of the usual GCC "%llu". This prevents a bug when saving 64-bit
5275 int configuration values: the high-order 32 bits would get
5276 truncated. In particular, we were being bitten by the default
5277 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
5278 and maybe also bug 397.)
5280 o Minor bugfixes (performance):
5281 - Use OpenSSL's AES implementation on platforms where it's faster.
5282 This could save us as much as 10% CPU usage.
5284 o Minor bugfixes (server):
5285 - Do not rotate onion key immediately after setting it for the first
5288 o Minor bugfixes (directory authorities):
5289 - Stop calling servers that have been hibernating for a long time
5290 "stable". Also, stop letting hibernating or obsolete servers affect
5291 uptime and bandwidth cutoffs.
5292 - Stop listing hibernating servers in the v1 directory.
5294 o Minor bugfixes (hidden services):
5295 - Upload hidden service descriptors slightly less often, to reduce
5296 load on authorities.
5298 o Minor bugfixes (other):
5299 - Fix an assert that could trigger if a controller quickly set then
5300 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
5301 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
5303 - Fix a potential race condition in the rpm installer. Found by
5305 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
5306 of 2 as indicating that the server is completely bad; it sometimes
5307 means that the server is just bad for the request in question. (may fix
5308 the last of bug 326.)
5309 - Disable encrypted directory connections when we don't have a server
5310 descriptor for the destination. We'll get this working again in
5314 Changes in version 0.1.2.8-beta - 2007-02-26
5315 o Major bugfixes (crashes):
5316 - Stop crashing when the controller asks us to resetconf more than
5317 one config option at once. (Vidalia 0.0.11 does this.)
5318 - Fix a crash that happened on Win98 when we're given command-line
5319 arguments: don't try to load NT service functions from advapi32.dll
5320 except when we need them. (Bug introduced in 0.1.2.7-alpha;
5322 - Fix a longstanding obscure crash bug that could occur when
5323 we run out of DNS worker processes. (Resolves bug 390.)
5325 o Major bugfixes (hidden services):
5326 - Correctly detect whether hidden service descriptor downloads are
5327 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
5329 o Major bugfixes (accounting):
5330 - When we start during an accounting interval before it's time to wake
5331 up, remember to wake up at the correct time. (May fix bug 342.)
5333 o Minor bugfixes (controller):
5334 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
5335 clear the corresponding on_circuit variable, and remember later
5336 that we don't need to send a redundant CLOSED event. (Resolves part
5338 - Report events where a resolve succeeded or where we got a socks
5339 protocol error correctly, rather than calling both of them
5341 - Change reported stream target addresses to IP consistently when
5342 we finally get the IP from an exit node.
5343 - Send log messages to the controller even if they happen to be very
5346 o Minor bugfixes (other):
5347 - Display correct results when reporting which versions are
5348 recommended, and how recommended they are. (Resolves bug 383.)
5349 - Improve our estimates for directory bandwidth to be less random:
5350 guess that an unrecognized directory will have the average bandwidth
5351 from all known directories, not that it will have the average
5352 bandwidth from those directories earlier than it on the list.
5353 - If we start a server with ClientOnly 1, then set ClientOnly to 0
5354 and hup, stop triggering an assert based on an empty onion_key.
5355 - On platforms with no working mmap() equivalent, don't warn the
5356 user when cached-routers doesn't exist.
5357 - Warn the user when mmap() [or its equivalent] fails for some reason
5358 other than file-not-found.
5359 - Don't warn the user when cached-routers.new doesn't exist: that's
5360 perfectly fine when starting up for the first time.
5361 - When EntryNodes are configured, rebuild the guard list to contain,
5362 in order: the EntryNodes that were guards before; the rest of the
5363 EntryNodes; the nodes that were guards before.
5364 - Mask out all signals in sub-threads; only the libevent signal
5365 handler should be processing them. This should prevent some crashes
5366 on some machines using pthreads. (Patch from coderman.)
5367 - Fix switched arguments on memset in the implementation of
5368 tor_munmap() for systems with no mmap() call.
5369 - When Tor receives a router descriptor that it asked for, but
5370 no longer wants (because it has received fresh networkstatuses
5371 in the meantime), do not warn the user. Cache the descriptor if
5372 we're a cache; drop it if we aren't.
5373 - Make earlier entry guards _really_ get retried when the network
5375 - On a malformed DNS reply, always give an error to the corresponding
5377 - Build with recent libevents on platforms that do not define the
5378 nonstandard types "u_int8_t" and friends.
5380 o Minor features (controller):
5381 - Warn the user when an application uses the obsolete binary v0
5382 control protocol. We're planning to remove support for it during
5383 the next development series, so it's good to give people some
5385 - Add STREAM_BW events to report per-entry-stream bandwidth
5386 use. (Patch from Robert Hogan.)
5387 - Rate-limit SIGNEWNYM signals in response to controllers that
5388 impolitely generate them for every single stream. (Patch from
5389 mwenge; closes bug 394.)
5390 - Make REMAP stream events have a SOURCE (cache or exit), and
5391 make them generated in every case where we get a successful
5392 connected or resolved cell.
5394 o Minor bugfixes (performance):
5395 - Call router_have_min_dir_info half as often. (This is showing up in
5396 some profiles, but not others.)
5397 - When using GCC, make log_debug never get called at all, and its
5398 arguments never get evaluated, when no debug logs are configured.
5399 (This is showing up in some profiles, but not others.)
5402 - Remove some never-implemented options. Mark PathlenCoinWeight as
5404 - Implement proposal 106: Stop requiring clients to have well-formed
5405 certificates; stop checking nicknames in certificates. (Clients
5406 have certificates so that they can look like Tor servers, but in
5407 the future we might want to allow them to look like regular TLS
5408 clients instead. Nicknames in certificates serve no purpose other
5409 than making our protocol easier to recognize on the wire.)
5410 - Revise messages on handshake failure again to be even more clear about
5411 which are incoming connections and which are outgoing.
5412 - Discard any v1 directory info that's over 1 month old (for
5413 directories) or over 1 week old (for running-routers lists).
5414 - Do not warn when individual nodes in the configuration's EntryNodes,
5415 ExitNodes, etc are down: warn only when all possible nodes
5416 are down. (Fixes bug 348.)
5417 - Always remove expired routers and networkstatus docs before checking
5418 whether we have enough information to build circuits. (Fixes
5420 - Put a lower-bound on MaxAdvertisedBandwidth.
5423 Changes in version 0.1.2.7-alpha - 2007-02-06
5424 o Major bugfixes (rate limiting):
5425 - Servers decline directory requests much more aggressively when
5426 they're low on bandwidth. Otherwise they end up queueing more and
5427 more directory responses, which can't be good for latency.
5428 - But never refuse directory requests from local addresses.
5429 - Fix a memory leak when sending a 503 response for a networkstatus
5431 - Be willing to read or write on local connections (e.g. controller
5432 connections) even when the global rate limiting buckets are empty.
5433 - If our system clock jumps back in time, don't publish a negative
5434 uptime in the descriptor. Also, don't let the global rate limiting
5435 buckets go absurdly negative.
5436 - Flush local controller connection buffers periodically as we're
5437 writing to them, so we avoid queueing 4+ megabytes of data before
5440 o Major bugfixes (NT services):
5441 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
5442 command-line flag so that admins can override the default by saying
5443 "tor --service install --user "SomeUser"". This will not affect
5444 existing installed services. Also, warn the user that the service
5445 will look for its configuration file in the service user's
5446 %appdata% directory. (We can't do the 'hardwire the user's appdata
5447 directory' trick any more, since we may not have read access to that
5450 o Major bugfixes (other):
5451 - Previously, we would cache up to 16 old networkstatus documents
5452 indefinitely, if they came from nontrusted authorities. Now we
5453 discard them if they are more than 10 days old.
5454 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
5456 - Detect and reject malformed DNS responses containing circular
5458 - If exits are rare enough that we're not marking exits as guards,
5459 ignore exit bandwidth when we're deciding the required bandwidth
5461 - When we're handling a directory connection tunneled over Tor,
5462 don't fill up internal memory buffers with all the data we want
5463 to tunnel; instead, only add it if the OR connection that will
5464 eventually receive it has some room for it. (This can lead to
5465 slowdowns in tunneled dir connections; a better solution will have
5468 o Minor bugfixes (dns):
5469 - Add some defensive programming to eventdns.c in an attempt to catch
5470 possible memory-stomping bugs.
5471 - Detect and reject DNS replies containing IPv4 or IPv6 records with
5472 an incorrect number of bytes. (Previously, we would ignore the
5474 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
5475 in the correct order, and doesn't crash.
5476 - Free memory held in recently-completed DNS lookup attempts on exit.
5477 This was not a memory leak, but may have been hiding memory leaks.
5478 - Handle TTL values correctly on reverse DNS lookups.
5479 - Treat failure to parse resolv.conf as an error.
5481 o Minor bugfixes (other):
5482 - Fix crash with "tor --list-fingerprint" (reported by seeess).
5483 - When computing clock skew from directory HTTP headers, consider what
5484 time it was when we finished asking for the directory, not what
5486 - Expire socks connections if they spend too long waiting for the
5487 handshake to finish. Previously we would let them sit around for
5488 days, if the connecting application didn't close them either.
5489 - And if the socks handshake hasn't started, don't send a
5490 "DNS resolve socks failed" handshake reply; just close it.
5491 - Stop using C functions that OpenBSD's linker doesn't like.
5492 - Don't launch requests for descriptors unless we have networkstatuses
5493 from at least half of the authorities. This delays the first
5494 download slightly under pathological circumstances, but can prevent
5495 us from downloading a bunch of descriptors we don't need.
5496 - Do not log IPs with TLS failures for incoming TLS
5497 connections. (Fixes bug 382.)
5498 - If the user asks to use invalid exit nodes, be willing to use
5500 - Stop using the reserved ac_cv namespace in our configure script.
5501 - Call stat() slightly less often; use fstat() when possible.
5502 - Refactor the way we handle pending circuits when an OR connection
5503 completes or fails, in an attempt to fix a rare crash bug.
5504 - Only rewrite a conn's address based on X-Forwarded-For: headers
5505 if it's a parseable public IP address; and stop adding extra quotes
5506 to the resulting address.
5509 - Weight directory requests by advertised bandwidth. Now we can
5510 let servers enable write limiting but still allow most clients to
5511 succeed at their directory requests. (We still ignore weights when
5512 choosing a directory authority; I hope this is a feature.)
5515 - Create a new file ReleaseNotes which was the old ChangeLog. The
5516 new ChangeLog file now includes the summaries for all development
5518 - Check for addresses with invalid characters at the exit as well
5519 as at the client, and warn less verbosely when they fail. You can
5520 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
5521 - Adapt a patch from goodell to let the contrib/exitlist script
5522 take arguments rather than require direct editing.
5523 - Inform the server operator when we decide not to advertise a
5524 DirPort due to AccountingMax enabled or a low BandwidthRate. It
5525 was confusing Zax, so now we're hopefully more helpful.
5526 - Bring us one step closer to being able to establish an encrypted
5527 directory tunnel without knowing a descriptor first. Still not
5528 ready yet. As part of the change, now assume we can use a
5529 create_fast cell if we don't know anything about a router.
5530 - Allow exit nodes to use nameservers running on ports other than 53.
5531 - Servers now cache reverse DNS replies.
5532 - Add an --ignore-missing-torrc command-line option so that we can
5533 get the "use sensible defaults if the configuration file doesn't
5534 exist" behavior even when specifying a torrc location on the command
5537 o Minor features (controller):
5538 - Track reasons for OR connection failure; make these reasons
5539 available via the controller interface. (Patch from Mike Perry.)
5540 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
5541 can learn when clients are sending malformed hostnames to Tor.
5542 - Clean up documentation for controller status events.
5543 - Add a REMAP status to stream events to note that a stream's
5544 address has changed because of a cached address or a MapAddress
5548 Changes in version 0.1.2.6-alpha - 2007-01-09
5550 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
5551 connection handles more than 4 gigs in either direction, we crash.
5552 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
5553 advertised exit node, somebody might try to exit from us when
5554 we're bootstrapping and before we've built our descriptor yet.
5555 Refuse the connection rather than crashing.
5558 - Warn if we (as a server) find that we've resolved an address that we
5559 weren't planning to resolve.
5560 - Warn that using select() on any libevent version before 1.1 will be
5561 unnecessarily slow (even for select()).
5562 - Flush ERR-level controller status events just like we currently
5563 flush ERR-level log events, so that a Tor shutdown doesn't prevent
5564 the controller from learning about current events.
5566 o Minor features (more controller status events):
5567 - Implement EXTERNAL_ADDRESS server status event so controllers can
5568 learn when our address changes.
5569 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
5570 can learn when directories reject our descriptor.
5571 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
5572 can learn when a client application is speaking a non-socks protocol
5574 - Implement DANGEROUS_SOCKS client status event so controllers
5575 can learn when a client application is leaking DNS addresses.
5576 - Implement BUG general status event so controllers can learn when
5577 Tor is unhappy about its internal invariants.
5578 - Implement CLOCK_SKEW general status event so controllers can learn
5579 when Tor thinks the system clock is set incorrectly.
5580 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
5581 server status events so controllers can learn when their descriptors
5582 are accepted by a directory.
5583 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
5584 server status events so controllers can learn about Tor's progress in
5585 deciding whether it's reachable from the outside.
5586 - Implement BAD_LIBEVENT general status event so controllers can learn
5587 when we have a version/method combination in libevent that needs to
5589 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
5590 and DNS_USELESS server status events so controllers can learn
5591 about changes to DNS server status.
5593 o Minor features (directory):
5594 - Authorities no longer recommend exits as guards if this would shift
5595 too much load to the exit nodes.
5598 Changes in version 0.1.2.5-alpha - 2007-01-06
5600 - Enable write limiting as well as read limiting. Now we sacrifice
5601 capacity if we're pushing out lots of directory traffic, rather
5602 than overrunning the user's intended bandwidth limits.
5603 - Include TLS overhead when counting bandwidth usage; previously, we
5604 would count only the bytes sent over TLS, but not the bytes used
5606 - Support running the Tor service with a torrc not in the same
5607 directory as tor.exe and default to using the torrc located in
5608 the %appdata%\Tor\ of the user who installed the service. Patch
5610 - Servers now check for the case when common DNS requests are going to
5611 wildcarded addresses (i.e. all getting the same answer), and change
5612 their exit policy to reject *:* if it's happening.
5613 - Implement BEGIN_DIR cells, so we can connect to the directory
5614 server via TLS to do encrypted directory requests rather than
5615 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
5616 config options if you like.
5618 o Minor features (config and docs):
5619 - Start using the state file to store bandwidth accounting data:
5620 the bw_accounting file is now obsolete. We'll keep generating it
5621 for a while for people who are still using 0.1.2.4-alpha.
5622 - Try to batch changes to the state file so that we do as few
5623 disk writes as possible while still storing important things in
5625 - The state file and the bw_accounting file get saved less often when
5626 the AvoidDiskWrites config option is set.
5627 - Make PIDFile work on Windows (untested).
5628 - Add internal descriptions for a bunch of configuration options:
5629 accessible via controller interface and in comments in saved
5631 - Reject *:563 (NNTPS) in the default exit policy. We already reject
5632 NNTP by default, so this seems like a sensible addition.
5633 - Clients now reject hostnames with invalid characters. This should
5634 avoid some inadvertent info leaks. Add an option
5635 AllowNonRFC953Hostnames to disable this behavior, in case somebody
5636 is running a private network with hosts called @, !, and #.
5637 - Add a maintainer script to tell us which options are missing
5638 documentation: "make check-docs".
5639 - Add a new address-spec.txt document to describe our special-case
5640 addresses: .exit, .onion, and .noconnnect.
5642 o Minor features (DNS):
5643 - Ongoing work on eventdns infrastructure: now it has dns server
5644 and ipv6 support. One day Tor will make use of it.
5645 - Add client-side caching for reverse DNS lookups.
5646 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
5647 - When we change nameservers or IP addresses, reset and re-launch
5648 our tests for DNS hijacking.
5650 o Minor features (directory):
5651 - Authorities now specify server versions in networkstatus. This adds
5652 about 2% to the size of compressed networkstatus docs, and allows
5653 clients to tell which servers support BEGIN_DIR and which don't.
5654 The implementation is forward-compatible with a proposed future
5655 protocol version scheme not tied to Tor versions.
5656 - DirServer configuration lines now have an orport= option so
5657 clients can open encrypted tunnels to the authorities without
5658 having downloaded their descriptors yet. Enabled for moria1,
5659 moria2, tor26, and lefkada now in the default configuration.
5660 - Directory servers are more willing to send a 503 "busy" if they
5661 are near their write limit, especially for v1 directory requests.
5662 Now they can use their limited bandwidth for actual Tor traffic.
5663 - Clients track responses with status 503 from dirservers. After a
5664 dirserver has given us a 503, we try not to use it until an hour has
5665 gone by, or until we have no dirservers that haven't given us a 503.
5666 - When we get a 503 from a directory, and we're not a server, we don't
5667 count the failure against the total number of failures allowed
5668 for the thing we're trying to download.
5669 - Report X-Your-Address-Is correctly from tunneled directory
5670 connections; don't report X-Your-Address-Is when it's an internal
5671 address; and never believe reported remote addresses when they're
5673 - Protect against an unlikely DoS attack on directory servers.
5674 - Add a BadDirectory flag to network status docs so that authorities
5675 can (eventually) tell clients about caches they believe to be
5678 o Minor features (controller):
5679 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
5680 - Reimplement GETINFO so that info/names stays in sync with the
5682 - Implement "GETINFO fingerprint".
5683 - Implement "SETEVENTS GUARD" so controllers can get updates on
5684 entry guard status as it changes.
5686 o Minor features (clean up obsolete pieces):
5687 - Remove some options that have been deprecated since at least
5688 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
5689 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
5691 - We no longer look for identity and onion keys in "identity.key" and
5692 "onion.key" -- these were replaced by secret_id_key and
5693 secret_onion_key in 0.0.8pre1.
5694 - We no longer require unrecognized directory entries to be
5697 o Major bugfixes (security):
5698 - Stop sending the HttpProxyAuthenticator string to directory
5699 servers when directory connections are tunnelled through Tor.
5700 - Clients no longer store bandwidth history in the state file.
5701 - Do not log introduction points for hidden services if SafeLogging
5703 - When generating bandwidth history, round down to the nearest
5704 1k. When storing accounting data, round up to the nearest 1k.
5705 - When we're running as a server, remember when we last rotated onion
5706 keys, so that we will rotate keys once they're a week old even if
5707 we never stay up for a week ourselves.
5709 o Major bugfixes (other):
5710 - Fix a longstanding bug in eventdns that prevented the count of
5711 timed-out resolves from ever being reset. This bug caused us to
5712 give up on a nameserver the third time it timed out, and try it
5713 10 seconds later... and to give up on it every time it timed out
5715 - Take out the '5 second' timeout from the connection retry
5716 schedule. Now the first connect attempt will wait a full 10
5717 seconds before switching to a new circuit. Perhaps this will help
5718 a lot. Based on observations from Mike Perry.
5719 - Fix a bug on the Windows implementation of tor_mmap_file() that
5720 would prevent the cached-routers file from ever loading. Reported
5724 - Fix an assert failure when a directory authority sets
5725 AuthDirRejectUnlisted and then receives a descriptor from an
5726 unlisted router. Reported by seeess.
5727 - Avoid a double-free when parsing malformed DirServer lines.
5728 - Fix a bug when a BSD-style PF socket is first used. Patch from
5730 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
5731 to resolve an address at a given exit node even when they ask for
5733 - Servers no longer ever list themselves in their "family" line,
5734 even if configured to do so. This makes it easier to configure
5735 family lists conveniently.
5736 - When running as a server, don't fall back to 127.0.0.1 when no
5737 nameservers are configured in /etc/resolv.conf; instead, make the
5738 user fix resolv.conf or specify nameservers explicitly. (Resolves
5740 - Stop accepting certain malformed ports in configured exit policies.
5741 - Don't re-write the fingerprint file every restart, unless it has
5743 - Stop warning when a single nameserver fails: only warn when _all_ of
5744 our nameservers have failed. Also, when we only have one nameserver,
5745 raise the threshold for deciding that the nameserver is dead.
5746 - Directory authorities now only decide that routers are reachable
5747 if their identity keys are as expected.
5748 - When the user uses bad syntax in the Log config line, stop
5749 suggesting other bad syntax as a replacement.
5750 - Correctly detect ipv6 DNS capability on OpenBSD.
5752 o Minor bugfixes (controller):
5753 - Report the circuit number correctly in STREAM CLOSED events. Bug
5754 reported by Mike Perry.
5755 - Do not report bizarre values for results of accounting GETINFOs
5756 when the last second's write or read exceeds the allotted bandwidth.
5757 - Report "unrecognized key" rather than an empty string when the
5758 controller tries to fetch a networkstatus that doesn't exist.
5761 Changes in version 0.1.1.26 - 2006-12-14
5762 o Security bugfixes:
5763 - Stop sending the HttpProxyAuthenticator string to directory
5764 servers when directory connections are tunnelled through Tor.
5765 - Clients no longer store bandwidth history in the state file.
5766 - Do not log introduction points for hidden services if SafeLogging
5770 - Fix an assert failure when a directory authority sets
5771 AuthDirRejectUnlisted and then receives a descriptor from an
5772 unlisted router (reported by seeess).
5775 Changes in version 0.1.2.4-alpha - 2006-12-03
5777 - Add support for using natd; this allows FreeBSDs earlier than
5778 5.1.2 to have ipfw send connections through Tor without using
5779 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
5782 - Make all connections to addresses of the form ".noconnect"
5783 immediately get closed. This lets application/controller combos
5784 successfully test whether they're talking to the same Tor by
5785 watching for STREAM events.
5786 - Make cross.sh cross-compilation script work even when autogen.sh
5787 hasn't been run. (Patch from Michael Mohr.)
5788 - Statistics dumped by -USR2 now include a breakdown of public key
5789 operations, for profiling.
5792 - Fix a major leak when directory authorities parse their
5793 approved-routers list, a minor memory leak when we fail to pick
5794 an exit node, and a few rare leaks on errors.
5795 - Handle TransPort connections even when the server sends data before
5796 the client sends data. Previously, the connection would just hang
5797 until the client sent data. (Patch from tup based on patch from
5799 - Avoid assert failure when our cached-routers file is empty on
5803 - Don't log spurious warnings when we see a circuit close reason we
5804 don't recognize; it's probably just from a newer version of Tor.
5805 - Have directory authorities allow larger amounts of drift in uptime
5806 without replacing the server descriptor: previously, a server that
5807 restarted every 30 minutes could have 48 "interesting" descriptors
5809 - Start linking to the Tor specification and Tor reference manual
5810 correctly in the Windows installer.
5811 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5812 Tor/Privoxy we also uninstall Vidalia.
5813 - Resume building on Irix64, and fix a lot of warnings from its
5815 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
5816 when we're running as a client.
5819 Changes in version 0.1.1.25 - 2006-11-04
5821 - When a client asks us to resolve (rather than connect to)
5822 an address, and we have a cached answer, give them the cached
5823 answer. Previously, we would give them no answer at all.
5824 - We were building exactly the wrong circuits when we predict
5825 hidden service requirements, meaning Tor would have to build all
5826 its circuits on demand.
5827 - If none of our live entry guards have a high uptime, but we
5828 require a guard with a high uptime, try adding a new guard before
5829 we give up on the requirement. This patch should make long-lived
5830 connections more stable on average.
5831 - When testing reachability of our DirPort, don't launch new
5832 tests when there's already one in progress -- unreachable
5833 servers were stacking up dozens of testing streams.
5835 o Security bugfixes:
5836 - When the user sends a NEWNYM signal, clear the client-side DNS
5837 cache too. Otherwise we continue to act on previous information.
5840 - Avoid a memory corruption bug when creating a hash table for
5842 - Avoid possibility of controller-triggered crash when misusing
5843 certain commands from a v0 controller on platforms that do not
5844 handle printf("%s",NULL) gracefully.
5845 - Avoid infinite loop on unexpected controller input.
5846 - Don't log spurious warnings when we see a circuit close reason we
5847 don't recognize; it's probably just from a newer version of Tor.
5848 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5849 Tor/Privoxy we also uninstall Vidalia.
5852 Changes in version 0.1.2.3-alpha - 2006-10-29
5854 - Prepare for servers to publish descriptors less often: never
5855 discard a descriptor simply for being too old until either it is
5856 recommended by no authorities, or until we get a better one for
5857 the same router. Make caches consider retaining old recommended
5858 routers for even longer.
5859 - If most authorities set a BadExit flag for a server, clients
5860 don't think of it as a general-purpose exit. Clients only consider
5861 authorities that advertise themselves as listing bad exits.
5862 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
5863 headers for content, so that we can work better in the presence of
5864 caching HTTP proxies.
5865 - Allow authorities to list nodes as bad exits by fingerprint or by
5868 o Minor features, controller:
5869 - Add a REASON field to CIRC events; for backward compatibility, this
5870 field is sent only to controllers that have enabled the extended
5871 event format. Also, add additional reason codes to explain why
5872 a given circuit has been destroyed or truncated. (Patches from
5874 - Add a REMOTE_REASON field to extended CIRC events to tell the
5875 controller about why a remote OR told us to close a circuit.
5876 - Stream events also now have REASON and REMOTE_REASON fields,
5877 working much like those for circuit events.
5878 - There's now a GETINFO ns/... field so that controllers can ask Tor
5879 about the current status of a router.
5880 - A new event type "NS" to inform a controller when our opinion of
5881 a router's status has changed.
5882 - Add a GETINFO events/names and GETINFO features/names so controllers
5883 can tell which events and features are supported.
5884 - A new CLEARDNSCACHE signal to allow controllers to clear the
5885 client-side DNS cache without expiring circuits.
5887 o Security bugfixes:
5888 - When the user sends a NEWNYM signal, clear the client-side DNS
5889 cache too. Otherwise we continue to act on previous information.
5892 - Avoid sending junk to controllers or segfaulting when a controller
5893 uses EVENT_NEW_DESC with verbose nicknames.
5894 - Stop triggering asserts if the controller tries to extend hidden
5895 service circuits (reported by mwenge).
5896 - Avoid infinite loop on unexpected controller input.
5897 - When the controller does a "GETINFO network-status", tell it
5898 about even those routers whose descriptors are very old, and use
5899 long nicknames where appropriate.
5900 - Change NT service functions to be loaded on demand. This lets us
5901 build with MinGW without breaking Tor for Windows 98 users.
5902 - Do DirPort reachability tests less often, since a single test
5903 chews through many circuits before giving up.
5904 - In the hidden service example in torrc.sample, stop recommending
5905 esoteric and discouraged hidden service options.
5906 - When stopping an NT service, wait up to 10 sec for it to actually
5907 stop. (Patch from Matt Edman; resolves bug 295.)
5908 - Fix handling of verbose nicknames with ORCONN controller events:
5909 make them show up exactly when requested, rather than exactly when
5911 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
5912 printing a duplicate "$" in the keys we send (reported by mwenge).
5913 - Correctly set maximum connection limit on Cygwin. (This time
5915 - Try to detect Windows correctly when cross-compiling.
5916 - Detect the size of the routers file correctly even if it is
5917 corrupted (on systems without mmap) or not page-aligned (on systems
5918 with mmap). This bug was harmless.
5919 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
5920 to open a stream fails; now we do in more cases. This should
5921 make clients able to find a good exit faster in some cases, since
5922 unhandleable requests will now get an error rather than timing out.
5923 - Resolve two memory leaks when rebuilding the on-disk router cache
5924 (reported by fookoowa).
5925 - Clean up minor code warnings suggested by the MIPSpro C compiler,
5926 and reported by some Centos users.
5927 - Controller signals now work on non-Unix platforms that don't define
5928 SIGUSR1 and SIGUSR2 the way we expect.
5929 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
5930 values before failing, and always enables eventdns.
5931 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
5932 Try to fix this in configure.in by checking for most functions
5933 before we check for libevent.
5936 Changes in version 0.1.2.2-alpha - 2006-10-07
5938 - Make our async eventdns library on-by-default for Tor servers,
5939 and plan to deprecate the separate dnsworker threads.
5940 - Add server-side support for "reverse" DNS lookups (using PTR
5941 records so clients can determine the canonical hostname for a given
5942 IPv4 address). Only supported by servers using eventdns; servers
5943 now announce in their descriptors whether they support eventdns.
5944 - Specify and implement client-side SOCKS5 interface for reverse DNS
5945 lookups (see doc/socks-extensions.txt).
5946 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
5947 connect to directory servers through Tor. Previously, clients needed
5948 to find Tor exits to make private connections to directory servers.
5949 - Avoid choosing Exit nodes for entry or middle hops when the
5950 total bandwidth available from non-Exit nodes is much higher than
5951 the total bandwidth available from Exit nodes.
5952 - Workaround for name servers (like Earthlink's) that hijack failing
5953 DNS requests and replace the no-such-server answer with a "helpful"
5954 redirect to an advertising-driven search portal. Also work around
5955 DNS hijackers who "helpfully" decline to hijack known-invalid
5956 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
5957 lets you turn it off.
5958 - Send out a burst of long-range padding cells once we've established
5959 that we're reachable. Spread them over 4 circuits, so hopefully
5960 a few will be fast. This exercises our bandwidth and bootstraps
5961 us into the directory more quickly.
5963 o New/improved config options:
5964 - Add new config option "ResolvConf" to let the server operator
5965 choose an alternate resolve.conf file when using eventdns.
5966 - Add an "EnforceDistinctSubnets" option to control our "exclude
5967 servers on the same /16" behavior. It's still on by default; this
5968 is mostly for people who want to operate private test networks with
5969 all the machines on the same subnet.
5970 - If one of our entry guards is on the ExcludeNodes list, or the
5971 directory authorities don't think it's a good guard, treat it as
5972 if it were unlisted: stop using it as a guard, and throw it off
5973 the guards list if it stays that way for a long time.
5974 - Allow directory authorities to be marked separately as authorities
5975 for the v1 directory protocol, the v2 directory protocol, and
5976 as hidden service directories, to make it easier to retire old
5977 authorities. V1 authorities should set "HSAuthoritativeDir 1"
5978 to continue being hidden service authorities too.
5979 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
5981 o Minor features, controller:
5982 - Fix CIRC controller events so that controllers can learn the
5983 identity digests of non-Named servers used in circuit paths.
5984 - Let controllers ask for more useful identifiers for servers. Instead
5985 of learning identity digests for un-Named servers and nicknames
5986 for Named servers, the new identifiers include digest, nickname,
5987 and indication of Named status. Off by default; see control-spec.txt
5988 for more information.
5989 - Add a "getinfo address" controller command so it can display Tor's
5990 best guess to the user.
5991 - New controller event to alert the controller when our server
5992 descriptor has changed.
5993 - Give more meaningful errors on controller authentication failure.
5995 o Minor features, other:
5996 - When asked to resolve a hostname, don't use non-exit servers unless
5997 requested to do so. This allows servers with broken DNS to be
5998 useful to the network.
5999 - Divide eventdns log messages into warn and info messages.
6000 - Reserve the nickname "Unnamed" for routers that can't pick
6001 a hostname: any router can call itself Unnamed; directory
6002 authorities will never allocate Unnamed to any particular router;
6003 clients won't believe that any router is the canonical Unnamed.
6004 - Only include function names in log messages for info/debug messages.
6005 For notice/warn/err, the content of the message should be clear on
6006 its own, and printing the function name only confuses users.
6007 - Avoid some false positives during reachability testing: don't try
6008 to test via a server that's on the same /24 as us.
6009 - If we fail to build a circuit to an intended enclave, and it's
6010 not mandatory that we use that enclave, stop wanting it.
6011 - When eventdns is enabled, allow multithreaded builds on NetBSD and
6012 OpenBSD. (We had previously disabled threads on these platforms
6013 because they didn't have working thread-safe resolver functions.)
6015 o Major bugfixes, anonymity/security:
6016 - If a client asked for a server by name, and there's a named server
6017 in our network-status but we don't have its descriptor yet, we
6018 could return an unnamed server instead.
6019 - Fix NetBSD bug that could allow someone to force uninitialized RAM
6020 to be sent to a server's DNS resolver. This only affects NetBSD
6021 and other platforms that do not bounds-check tolower().
6022 - Reject (most) attempts to use Tor circuits with length one. (If
6023 many people start using Tor as a one-hop proxy, exit nodes become
6024 a more attractive target for compromise.)
6025 - Just because your DirPort is open doesn't mean people should be
6026 able to remotely teach you about hidden service descriptors. Now
6027 only accept rendezvous posts if you've got HSAuthoritativeDir set.
6029 o Major bugfixes, other:
6030 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
6031 - When a client asks the server to resolve (not connect to)
6032 an address, and it has a cached answer, give them the cached answer.
6033 Previously, the server would give them no answer at all.
6034 - Allow really slow clients to not hang up five minutes into their
6035 directory downloads (suggested by Adam J. Richter).
6036 - We were building exactly the wrong circuits when we anticipated
6037 hidden service requirements, meaning Tor would have to build all
6038 its circuits on demand.
6039 - Avoid crashing when we mmap a router cache file of size 0.
6040 - When testing reachability of our DirPort, don't launch new
6041 tests when there's already one in progress -- unreachable
6042 servers were stacking up dozens of testing streams.
6044 o Minor bugfixes, correctness:
6045 - If we're a directory mirror and we ask for "all" network status
6046 documents, we would discard status documents from authorities
6048 - Avoid a memory corruption bug when creating a hash table for
6050 - Avoid controller-triggered crash when misusing certain commands
6051 from a v0 controller on platforms that do not handle
6052 printf("%s",NULL) gracefully.
6053 - Don't crash when a controller sends a third argument to an
6054 "extendcircuit" request.
6055 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6056 response; fix error code when "getinfo dir/status/" fails.
6057 - Avoid crash when telling controller stream-status and a stream
6059 - Patch from Adam Langley to fix assert() in eventdns.c.
6060 - Fix a debug log message in eventdns to say "X resolved to Y"
6061 instead of "X resolved to X".
6062 - Make eventdns give strings for DNS errors, not just error numbers.
6063 - Track unreachable entry guards correctly: don't conflate
6064 'unreachable by us right now' with 'listed as down by the directory
6065 authorities'. With the old code, if a guard was unreachable by
6066 us but listed as running, it would clog our guard list forever.
6067 - Behave correctly in case we ever have a network with more than
6068 2GB/s total advertised capacity.
6069 - Make TrackExitHosts case-insensitive, and fix the behavior of
6070 ".suffix" TrackExitHosts items to avoid matching in the middle of
6072 - Finally fix the openssl warnings from newer gccs that believe that
6073 ignoring a return value is okay, but casting a return value and
6074 then ignoring it is a sign of madness.
6075 - Prevent the contrib/exitlist script from printing the same
6076 result more than once.
6077 - Patch from Steve Hildrey: Generate network status correctly on
6078 non-versioning dirservers.
6079 - Don't listen to the X-Your-Address-Is hint if you did the lookup
6080 via Tor; otherwise you'll think you're the exit node's IP address.
6082 o Minor bugfixes, performance:
6083 - Two small performance improvements on parsing descriptors.
6084 - Major performance improvement on inserting descriptors: change
6085 algorithm from O(n^2) to O(n).
6086 - Make the common memory allocation path faster on machines where
6087 malloc(0) returns a pointer.
6088 - Start remembering X-Your-Address-Is directory hints even if you're
6089 a client, so you can become a server more smoothly.
6090 - Avoid duplicate entries on MyFamily line in server descriptor.
6092 o Packaging, features:
6093 - Remove architecture from OS X builds. The official builds are
6094 now universal binaries.
6095 - The Debian package now uses --verify-config when (re)starting,
6096 to distinguish configuration errors from other errors.
6097 - Update RPMs to require libevent 1.1b.
6099 o Packaging, bugfixes:
6100 - Patches so Tor builds with MinGW on Windows.
6101 - Patches so Tor might run on Cygwin again.
6102 - Resume building on non-gcc compilers and ancient gcc. Resume
6103 building with the -O0 compile flag. Resume building cleanly on
6105 - Run correctly on OS X platforms with case-sensitive filesystems.
6106 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
6107 - Add autoconf checks so Tor can build on Solaris x86 again.
6110 - Documented (and renamed) ServerDNSSearchDomains and
6111 ServerDNSResolvConfFile options.
6112 - Be clearer that the *ListenAddress directives can be repeated
6116 Changes in version 0.1.1.24 - 2006-09-29
6118 - Allow really slow clients to not hang up five minutes into their
6119 directory downloads (suggested by Adam J. Richter).
6120 - Fix major performance regression from 0.1.0.x: instead of checking
6121 whether we have enough directory information every time we want to
6122 do something, only check when the directory information has changed.
6123 This should improve client CPU usage by 25-50%.
6124 - Don't crash if, after a server has been running for a while,
6125 it can't resolve its hostname.
6128 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6129 - Don't crash when the controller receives a third argument to an
6130 "extendcircuit" request.
6131 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6132 response; fix error code when "getinfo dir/status/" fails.
6133 - Fix configure.in to not produce broken configure files with
6134 more recent versions of autoconf. Thanks to Clint for his auto*
6136 - Fix security bug on NetBSD that could allow someone to force
6137 uninitialized RAM to be sent to a server's DNS resolver. This
6138 only affects NetBSD and other platforms that do not bounds-check
6140 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
6141 methods: these are known to be buggy.
6142 - If we're a directory mirror and we ask for "all" network status
6143 documents, we would discard status documents from authorities
6147 Changes in version 0.1.2.1-alpha - 2006-08-27
6149 - Add "eventdns" async dns library from Adam Langley, tweaked to
6150 build on OSX and Windows. Only enabled if you pass the
6151 --enable-eventdns argument to configure.
6152 - Allow servers with no hostname or IP address to learn their
6153 IP address by asking the directory authorities. This code only
6154 kicks in when you would normally have exited with a "no address"
6155 error. Nothing's authenticated, so use with care.
6156 - Rather than waiting a fixed amount of time between retrying
6157 application connections, we wait only 5 seconds for the first,
6158 10 seconds for the second, and 15 seconds for each retry after
6159 that. Hopefully this will improve the expected user experience.
6160 - Patch from Tup to add support for transparent AP connections:
6161 this basically bundles the functionality of trans-proxy-tor
6162 into the Tor mainline. Now hosts with compliant pf/netfilter
6163 implementations can redirect TCP connections straight to Tor
6164 without diverting through SOCKS. Needs docs.
6165 - Busy directory servers save lots of memory by spooling server
6166 descriptors, v1 directories, and v2 networkstatus docs to buffers
6167 as needed rather than en masse. Also mmap the cached-routers
6168 files, so we don't need to keep the whole thing in memory too.
6169 - Automatically avoid picking more than one node from the same
6170 /16 network when constructing a circuit.
6171 - Revise and clean up the torrc.sample that we ship with; add
6172 a section for BandwidthRate and BandwidthBurst.
6175 - Split circuit_t into origin_circuit_t and or_circuit_t, and
6176 split connection_t into edge, or, dir, control, and base structs.
6177 These will save quite a bit of memory on busy servers, and they'll
6178 also help us track down bugs in the code and bugs in the spec.
6179 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
6180 or later. Log when we are doing this, so we can diagnose it when
6181 it fails. (Also, recommend libevent 1.1b for kqueue and
6182 win32 methods; deprecate libevent 1.0b harder; make libevent
6183 recommendation system saner.)
6184 - Start being able to build universal binaries on OS X (thanks
6186 - Export the default exit policy via the control port, so controllers
6187 don't need to guess what it is / will be later.
6188 - Add a man page entry for ProtocolWarnings.
6189 - Add TestVia config option to the man page.
6190 - Remove even more protocol-related warnings from Tor server logs,
6191 such as bad TLS handshakes and malformed begin cells.
6192 - Stop fetching descriptors if you're not a dir mirror and you
6193 haven't tried to establish any circuits lately. [This currently
6194 causes some dangerous behavior, because when you start up again
6195 you'll use your ancient server descriptors.]
6196 - New DirPort behavior: if you have your dirport set, you download
6197 descriptors aggressively like a directory mirror, whether or not
6199 - Get rid of the router_retry_connections notion. Now routers
6200 no longer try to rebuild long-term connections to directory
6201 authorities, and directory authorities no longer try to rebuild
6202 long-term connections to all servers. We still don't hang up
6203 connections in these two cases though -- we need to look at it
6204 more carefully to avoid flapping, and we likely need to wait til
6205 0.1.1.x is obsolete.
6206 - Drop compatibility with obsolete Tors that permit create cells
6207 to have the wrong circ_id_type.
6208 - Re-enable per-connection rate limiting. Get rid of the "OP
6209 bandwidth" concept. Lay groundwork for "bandwidth classes" --
6210 separate global buckets that apply depending on what sort of conn
6212 - Start publishing one minute or so after we find our ORPort
6213 to be reachable. This will help reduce the number of descriptors
6214 we have for ourselves floating around, since it's quite likely
6215 other things (e.g. DirPort) will change during that minute too.
6216 - Fork the v1 directory protocol into its own spec document,
6217 and mark dir-spec.txt as the currently correct (v2) spec.
6220 - When we find our DirPort to be reachable, publish a new descriptor
6221 so we'll tell the world (reported by pnx).
6222 - Publish a new descriptor after we hup/reload. This is important
6223 if our config has changed such that we'll want to start advertising
6224 our DirPort now, etc.
6225 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6226 - When we have a state file we cannot parse, tell the user and
6227 move it aside. Now we avoid situations where the user starts
6228 Tor in 1904, Tor writes a state file with that timestamp in it,
6229 the user fixes her clock, and Tor refuses to start.
6230 - Fix configure.in to not produce broken configure files with
6231 more recent versions of autoconf. Thanks to Clint for his auto*
6233 - "tor --verify-config" now exits with -1(255) or 0 depending on
6234 whether the config options are bad or good.
6235 - Resolve bug 321 when using dnsworkers: append a period to every
6236 address we resolve at the exit node, so that we do not accidentally
6237 pick up local addresses, and so that failing searches are retried
6238 in the resolver search domains. (This is already solved for
6239 eventdns.) (This breaks Blossom servers for now.)
6240 - If we are using an exit enclave and we can't connect, e.g. because
6241 its webserver is misconfigured to not listen on localhost, then
6242 back off and try connecting from somewhere else before we fail.
6245 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
6246 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
6247 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
6248 when the IP address is mapped through MapAddress to a hostname.
6249 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6250 useless IPv6 DNS resolves.
6251 - Patch suggested by Karsten Loesing: respond to SIGNAL command
6252 before we execute the signal, in case the signal shuts us down.
6253 - Clean up AllowInvalidNodes man page entry.
6254 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
6255 - Add more asserts to track down an assert error on a windows Tor
6256 server with connection_add being called with socket == -1.
6257 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
6258 - Fix misleading log messages: an entry guard that is "unlisted",
6259 as well as not known to be "down" (because we've never heard
6260 of it), is not therefore "up".
6261 - Remove code to special-case "-cvs" ending, since it has not
6262 actually mattered since 0.0.9.
6263 - Make our socks5 handling more robust to broken socks clients:
6264 throw out everything waiting on the buffer in between socks
6265 handshake phases, since they can't possibly (so the theory
6266 goes) have predicted what we plan to respond to them.
6269 Changes in version 0.1.1.23 - 2006-07-30
6271 - Fast Tor servers, especially exit nodes, were triggering asserts
6272 due to a bug in handling the list of pending DNS resolves. Some
6273 bugs still remain here; we're hunting them.
6274 - Entry guards could crash clients by sending unexpected input.
6275 - More fixes on reachability testing: if you find yourself reachable,
6276 then don't ever make any client requests (so you stop predicting
6277 circuits), then hup or have your clock jump, then later your IP
6278 changes, you won't think circuits are working, so you won't try to
6279 test reachability, so you won't publish.
6282 - Avoid a crash if the controller does a resetconf firewallports
6283 and then a setconf fascistfirewall=1.
6284 - Avoid an integer underflow when the dir authority decides whether
6285 a router is stable: we might wrongly label it stable, and compute
6286 a slightly wrong median stability, when a descriptor is published
6288 - Fix a place where we might trigger an assert if we can't build our
6289 own server descriptor yet.
6292 Changes in version 0.1.1.22 - 2006-07-05
6294 - Fix a big bug that was causing servers to not find themselves
6295 reachable if they changed IP addresses. Since only 0.1.1.22+
6296 servers can do reachability testing correctly, now we automatically
6297 make sure to test via one of these.
6298 - Fix to allow clients and mirrors to learn directory info from
6299 descriptor downloads that get cut off partway through.
6300 - Directory authorities had a bug in deciding if a newly published
6301 descriptor was novel enough to make everybody want a copy -- a few
6302 servers seem to be publishing new descriptors many times a minute.
6304 - Fix a rare bug that was causing some servers to complain about
6305 "closing wedged cpuworkers" and skip some circuit create requests.
6306 - Make the Exit flag in directory status documents actually work.
6309 Changes in version 0.1.1.21 - 2006-06-10
6310 o Crash and assert fixes from 0.1.1.20:
6311 - Fix a rare crash on Tor servers that have enabled hibernation.
6312 - Fix a seg fault on startup for Tor networks that use only one
6313 directory authority.
6314 - Fix an assert from a race condition that occurs on Tor servers
6315 while exiting, where various threads are trying to log that they're
6316 exiting, and delete the logs, at the same time.
6317 - Make our unit tests pass again on certain obscure platforms.
6320 - Add support for building SUSE RPM packages.
6321 - Speed up initial bootstrapping for clients: if we are making our
6322 first ever connection to any entry guard, then don't mark it down
6324 - When only one Tor server in the network is labelled as a guard,
6325 and we've already picked him, we would cycle endlessly picking him
6326 again, being unhappy about it, etc. Now we specifically exclude
6327 current guards when picking a new guard.
6328 - Servers send create cells more reliably after the TLS connection
6329 is established: we were sometimes forgetting to send half of them
6330 when we had more than one pending.
6331 - If we get a create cell that asks us to extend somewhere, but the
6332 Tor server there doesn't match the expected digest, we now send
6333 a destroy cell back, rather than silently doing nothing.
6334 - Make options->RedirectExit work again.
6335 - Make cookie authentication for the controller work again.
6336 - Stop being picky about unusual characters in the arguments to
6337 mapaddress. It's none of our business.
6338 - Add a new config option "TestVia" that lets you specify preferred
6339 middle hops to use for test circuits. Perhaps this will let me
6340 debug the reachability problems better.
6342 o Log / documentation fixes:
6343 - If we're a server and some peer has a broken TLS certificate, don't
6344 log about it unless ProtocolWarnings is set, i.e., we want to hear
6345 about protocol violations by others.
6346 - Fix spelling of VirtualAddrNetwork in man page.
6347 - Add a better explanation at the top of the autogenerated torrc file
6348 about what happened to our old torrc.
6351 Changes in version 0.1.1.20 - 2006-05-23
6353 - Downgrade a log severity where servers complain that they're
6355 - Avoid a compile warning on FreeBSD.
6356 - Remove string size limit on NEWDESC messages; solve bug 291.
6357 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
6358 more thoroughly when we're running on windows.
6361 Changes in version 0.1.1.19-rc - 2006-05-03
6363 - Regenerate our local descriptor if it's dirty and we try to use
6364 it locally (e.g. if it changes during reachability detection).
6365 - If we setconf our ORPort to 0, we continued to listen on the
6366 old ORPort and receive connections.
6367 - Avoid a second warning about machine/limits.h on Debian
6369 - Be willing to add our own routerinfo into the routerlist.
6370 Now authorities will include themselves in their directories
6371 and network-statuses.
6372 - Stop trying to upload rendezvous descriptors to every
6373 directory authority: only try the v1 authorities.
6374 - Servers no longer complain when they think they're not
6375 registered with the directory authorities. There were too many
6377 - Backport dist-rpm changes so rpms can be built without errors.
6380 - Implement an option, VirtualAddrMask, to set which addresses
6381 get handed out in response to mapaddress requests. This works
6382 around a bug in tsocks where 127.0.0.0/8 is never socksified.
6385 Changes in version 0.1.1.18-rc - 2006-04-10
6387 - Work harder to download live network-statuses from all the
6388 directory authorities we know about. Improve the threshold
6389 decision logic so we're more robust to edge cases.
6390 - When fetching rendezvous descriptors, we were willing to ask
6391 v2 authorities too, which would always return 404.
6394 - Stop listing down or invalid nodes in the v1 directory. This will
6395 reduce its bulk by about 1/3, and reduce load on directory
6397 - When deciding whether a router is Fast or Guard-worthy, consider
6398 his advertised BandwidthRate and not just the BandwidthCapacity.
6399 - No longer ship INSTALL and README files -- they are useless now.
6400 - Force rpmbuild to behave and honor target_cpu.
6401 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6402 - Start to include translated versions of the tor-doc-*.html
6403 files, along with the screenshots. Still needs more work.
6404 - Start sending back 512 and 451 errors if mapaddress fails,
6405 rather than not sending anything back at all.
6406 - When we fail to bind or listen on an incoming or outgoing
6407 socket, we should close it before failing. otherwise we just
6408 leak it. (thanks to weasel for finding.)
6409 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
6410 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
6411 - Make NoPublish (even though deprecated) work again.
6412 - Fix a minor security flaw where a versioning auth dirserver
6413 could list a recommended version many times in a row to make
6414 clients more convinced that it's recommended.
6415 - Fix crash bug if there are two unregistered servers running
6416 with the same nickname, one of them is down, and you ask for
6417 them by nickname in your EntryNodes or ExitNodes. Also, try
6418 to pick the one that's running rather than an arbitrary one.
6419 - Fix an infinite loop we could hit if we go offline for too long.
6420 - Complain when we hit WSAENOBUFS on recv() or write() too.
6421 Perhaps this will help us hunt the bug.
6422 - If you're not a versioning dirserver, don't put the string
6423 "client-versions \nserver-versions \n" in your network-status.
6424 - Lower the minimum required number of file descriptors to 1000,
6425 so we can have some overhead for Valgrind on Linux, where the
6426 default ulimit -n is 1024.
6429 - Add tor.dizum.com as the fifth authoritative directory server.
6430 - Add a new config option FetchUselessDescriptors, off by default,
6431 for when you plan to run "exitlist" on your client and you want
6432 to know about even the non-running descriptors.
6435 Changes in version 0.1.1.17-rc - 2006-03-28
6437 - Clients and servers since 0.1.1.10-alpha have been expiring
6438 connections whenever they are idle for 5 minutes and they *do*
6439 have circuits on them. Oops. With this new version, clients will
6440 discard their previous entry guard choices and avoid choosing
6441 entry guards running these flawed versions.
6442 - Fix memory leak when uncompressing concatenated zlib streams. This
6443 was causing substantial leaks over time on Tor servers.
6444 - The v1 directory was including servers as much as 48 hours old,
6445 because that's how the new routerlist->routers works. Now only
6446 include them if they're 20 hours old or less.
6449 - Resume building on irix64, netbsd 2.0, etc.
6450 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
6452 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
6453 and it is confusing some users.
6454 - Mirrors stop caching the v1 directory so often.
6455 - Make the max number of old descriptors that a cache will hold
6456 rise with the number of directory authorities, so we can scale.
6457 - Change our win32 uname() hack to be more forgiving about what
6458 win32 versions it thinks it's found.
6461 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
6463 - When the controller's *setconf commands fail, collect an error
6464 message in a string and hand it back to the controller.
6465 - Make the v2 dir's "Fast" flag based on relative capacity, just
6466 like "Stable" is based on median uptime. Name everything in the
6467 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
6468 - Log server fingerprint on startup, so new server operators don't
6469 have to go hunting around their filesystem for it.
6470 - Return a robots.txt on our dirport to discourage google indexing.
6471 - Let the controller ask for GETINFO dir/status/foo so it can ask
6472 directly rather than connecting to the dir port. Only works when
6473 dirport is set for now.
6475 o New config options rather than constants in the code:
6476 - SocksTimeout: How long do we let a socks connection wait
6477 unattached before we fail it?
6478 - CircuitBuildTimeout: Cull non-open circuits that were born
6479 at least this many seconds ago.
6480 - CircuitIdleTimeout: Cull open clean circuits that were born
6481 at least this many seconds ago.
6484 Changes in version 0.1.1.16-rc - 2006-03-18
6485 o Bugfixes on 0.1.1.15-rc:
6486 - Fix assert when the controller asks to attachstream a connect-wait
6487 or resolve-wait stream.
6488 - Now do address rewriting when the controller asks us to attach
6489 to a particular circuit too. This will let Blossom specify
6490 "moria2.exit" without having to learn what moria2's IP address is.
6491 - Make the "tor --verify-config" command-line work again, so people
6492 can automatically check if their torrc will parse.
6493 - Authoritative dirservers no longer require an open connection from
6494 a server to consider him "reachable". We need this change because
6495 when we add new auth dirservers, old servers won't know not to
6497 - Let Tor build on Sun CC again.
6498 - Fix an off-by-one buffer size in dirserv.c that magically never
6499 hit our three authorities but broke sjmurdoch's own tor network.
6500 - If we as a directory mirror don't know of any v1 directory
6501 authorities, then don't try to cache any v1 directories.
6502 - Stop warning about unknown servers in our family when they are
6503 given as hex digests.
6504 - Stop complaining as quickly to the server operator that he
6505 hasn't registered his nickname/key binding.
6506 - Various cleanups so we can add new V2 Auth Dirservers.
6507 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
6508 reflect the updated flags in our v2 dir protocol.
6509 - Resume allowing non-printable characters for exit streams (both
6510 for connecting and for resolving). Now we tolerate applications
6511 that don't follow the RFCs. But continue to block malformed names
6514 o Bugfixes on 0.1.0.x:
6515 - Fix assert bug in close_logs(): when we close and delete logs,
6516 remove them all from the global "logfiles" list.
6517 - Fix minor integer overflow in calculating when we expect to use up
6518 our bandwidth allocation before hibernating.
6519 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
6520 there are multiple SSLs installed with different versions.
6521 - When we try to be a server and Address is not explicitly set and
6522 our hostname resolves to a private IP address, try to use an
6523 interface address if it has a public address. Now Windows machines
6524 that think of themselves as localhost can work by default.
6527 - Let the controller ask for GETINFO dir/server/foo so it can ask
6528 directly rather than connecting to the dir port.
6529 - Let the controller tell us about certain router descriptors
6530 that it doesn't want Tor to use in circuits. Implement
6531 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
6532 - New config option SafeSocks to reject all application connections
6533 using unsafe socks protocols. Defaults to off.
6536 Changes in version 0.1.1.15-rc - 2006-03-11
6537 o Bugfixes and cleanups:
6538 - When we're printing strings from the network, don't try to print
6539 non-printable characters. This protects us against shell escape
6540 sequence exploits, and also against attacks to fool humans into
6541 misreading their logs.
6542 - Fix a bug where Tor would fail to establish any connections if you
6543 left it off for 24 hours and then started it: we were happy with
6544 the obsolete network statuses, but they all referred to router
6545 descriptors that were too old to fetch, so we ended up with no
6546 valid router descriptors.
6547 - Fix a seg fault in the controller's "getinfo orconn-status"
6548 command while listing status on incoming handshaking connections.
6549 Introduce a status name "NEW" for these connections.
6550 - If we get a linelist or linelist_s config option from the torrc
6551 (e.g. ExitPolicy) and it has no value, warn and skip rather than
6552 silently resetting it to its default.
6553 - Don't abandon entry guards until they've been down or gone for
6555 - Cleaner and quieter log messages.
6558 - New controller signal NEWNYM that makes new application requests
6560 - Add a new circuit purpose 'controller' to let the controller ask
6561 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
6562 controller command to let you specify the purpose if you're
6563 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
6564 command to let you change a circuit's purpose after it's been
6566 - Accept "private:*" in routerdesc exit policies; not generated yet
6567 because older Tors do not understand it.
6568 - Add BSD-style contributed startup script "rc.subr" from Peter
6572 Changes in version 0.1.1.14-alpha - 2006-02-20
6573 o Bugfixes on 0.1.1.x:
6574 - Don't die if we ask for a stdout or stderr log (even implicitly)
6575 and we're set to RunAsDaemon -- just warn.
6576 - We still had a few bugs in the OR connection rotation code that
6577 caused directory servers to slowly aggregate connections to other
6578 fast Tor servers. This time for sure!
6579 - Make log entries on Win32 include the name of the function again.
6580 - We were treating a pair of exit policies if they were equal even
6581 if one said accept and the other said reject -- causing us to
6582 not always publish a new descriptor since we thought nothing
6584 - Retry pending server downloads as well as pending networkstatus
6585 downloads when we unexpectedly get a socks request.
6586 - We were ignoring the IS_FAST flag in the directory status,
6587 meaning we were willing to pick trivial-bandwidth nodes for "fast"
6589 - If the controller's SAVECONF command fails (e.g. due to file
6590 permissions), let the controller know that it failed.
6593 - If we're trying to be a Tor server and running Windows 95/98/ME
6594 as a server, explain that we'll likely crash.
6595 - When we're a server, a client asks for an old-style directory,
6596 and our write bucket is empty, don't give it to him. This way
6597 small servers can continue to serve the directory *sometimes*,
6598 without getting overloaded.
6599 - Compress exit policies even more -- look for duplicate lines
6601 - Clients now honor the "guard" flag in the router status when
6602 picking entry guards, rather than looking at is_fast or is_stable.
6603 - Retain unrecognized lines in $DATADIR/state file, so that we can
6604 be forward-compatible.
6605 - Generate 18.0.0.0/8 address policy format in descs when we can;
6606 warn when the mask is not reducible to a bit-prefix.
6607 - Let the user set ControlListenAddress in the torrc. This can be
6608 dangerous, but there are some cases (like a secured LAN) where it
6610 - Split ReachableAddresses into ReachableDirAddresses and
6611 ReachableORAddresses, so we can restrict Dir conns to port 80
6612 and OR conns to port 443.
6613 - Now we can target arch and OS in rpm builds (contributed by
6614 Phobos). Also make the resulting dist-rpm filename match the
6616 - New config options to help controllers: FetchServerDescriptors
6617 and FetchHidServDescriptors for whether to fetch server
6618 info and hidserv info or let the controller do it, and
6619 PublishServerDescriptor and PublishHidServDescriptors.
6620 - Also let the controller set the __AllDirActionsPrivate config
6621 option if you want all directory fetches/publishes to happen via
6622 Tor (it assumes your controller bootstraps your circuits).
6625 Changes in version 0.1.0.17 - 2006-02-17
6626 o Crash bugfixes on 0.1.0.x:
6627 - When servers with a non-zero DirPort came out of hibernation,
6628 sometimes they would trigger an assert.
6630 o Other important bugfixes:
6631 - On platforms that don't have getrlimit (like Windows), we were
6632 artificially constraining ourselves to a max of 1024
6633 connections. Now just assume that we can handle as many as 15000
6634 connections. Hopefully this won't cause other problems.
6636 o Backported features:
6637 - When we're a server, a client asks for an old-style directory,
6638 and our write bucket is empty, don't give it to him. This way
6639 small servers can continue to serve the directory *sometimes*,
6640 without getting overloaded.
6641 - Whenever you get a 503 in response to a directory fetch, try
6642 once more. This will become important once servers start sending
6643 503's whenever they feel busy.
6644 - Fetch a new directory every 120 minutes, not every 40 minutes.
6645 Now that we have hundreds of thousands of users running the old
6646 directory algorithm, it's starting to hurt a lot.
6647 - Bump up the period for forcing a hidden service descriptor upload
6648 from 20 minutes to 1 hour.
6651 Changes in version 0.1.1.13-alpha - 2006-02-09
6652 o Crashes in 0.1.1.x:
6653 - When you tried to setconf ORPort via the controller, Tor would
6654 crash. So people using TorCP to become a server were sad.
6655 - Solve (I hope) the stack-smashing bug that we were seeing on fast
6656 servers. The problem appears to be something do with OpenSSL's
6657 random number generation, or how we call it, or something. Let me
6658 know if the crashes continue.
6659 - Turn crypto hardware acceleration off by default, until we find
6660 somebody smart who can test it for us. (It appears to produce
6661 seg faults in at least some cases.)
6662 - Fix a rare assert error when we've tried all intro points for
6663 a hidden service and we try fetching the service descriptor again:
6664 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
6667 - Fix a major load balance bug: we were round-robining in 16 KB
6668 chunks, and servers with bandwidthrate of 20 KB, while downloading
6669 a 600 KB directory, would starve their other connections. Now we
6670 try to be a bit more fair.
6671 - Dir authorities and mirrors were never expiring the newest
6672 descriptor for each server, causing memory and directory bloat.
6673 - Fix memory-bloating and connection-bloating bug on servers: We
6674 were never closing any connection that had ever had a circuit on
6675 it, because we were checking conn->n_circuits == 0, yet we had a
6676 bug that let it go negative.
6677 - Make Tor work using squid as your http proxy again -- squid
6678 returns an error if you ask for a URL that's too long, and it uses
6679 a really generic error message. Plus, many people are behind a
6680 transparent squid so they don't even realize it.
6681 - On platforms that don't have getrlimit (like Windows), we were
6682 artificially constraining ourselves to a max of 1024
6683 connections. Now just assume that we can handle as many as 15000
6684 connections. Hopefully this won't cause other problems.
6685 - Add a new config option ExitPolicyRejectPrivate which defaults to
6686 1. This means all exit policies will begin with rejecting private
6687 addresses, unless the server operator explicitly turns it off.
6690 - Clients no longer download descriptors for non-running
6692 - Before we add new directory authorities, we should make it
6693 clear that only v1 authorities should receive/publish hidden
6694 service descriptors.
6697 - As soon as we've fetched some more directory info, immediately
6698 try to download more server descriptors. This way we don't have
6699 a 10 second pause during initial bootstrapping.
6700 - Remove even more loud log messages that the server operator can't
6702 - When we're running an obsolete or un-recommended version, make
6703 the log message more clear about what the problem is and what
6704 versions *are* still recommended.
6705 - Provide a more useful warn message when our onion queue gets full:
6706 the CPU is too slow or the exit policy is too liberal.
6707 - Don't warn when we receive a 503 from a dirserver/cache -- this
6708 will pave the way for them being able to refuse if they're busy.
6709 - When we fail to bind a listener, try to provide a more useful
6710 log message: e.g., "Is Tor already running?"
6711 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
6712 Goldberg can prove things about our handshake protocol more
6714 - MaxConn has been obsolete for a while now. Document the ConnLimit
6715 config option, which is a *minimum* number of file descriptors
6716 that must be available else Tor refuses to start.
6717 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
6718 if you log to syslog and want something other than LOG_DAEMON.
6719 - Make dirservers generate a separate "guard" flag to mean,
6720 "would make a good entry guard". Make clients parse it and vote
6721 on it. Not used by clients yet.
6722 - Implement --with-libevent-dir option to ./configure. Also, improve
6723 search techniques to find libevent, and use those for openssl too.
6724 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
6725 - Only start testing reachability once we've established a
6726 circuit. This will make startup on dirservers less noisy.
6727 - Don't try to upload hidden service descriptors until we have
6728 established a circuit.
6729 - Fix the controller's "attachstream 0" command to treat conn like
6730 it just connected, doing address remapping, handling .exit and
6731 .onion idioms, and so on. Now we're more uniform in making sure
6732 that the controller hears about new and closing connections.
6735 Changes in version 0.1.1.12-alpha - 2006-01-11
6736 o Bugfixes on 0.1.1.x:
6737 - The fix to close duplicate server connections was closing all
6738 Tor client connections if they didn't establish a circuit
6739 quickly enough. Oops.
6740 - Fix minor memory issue (double-free) that happened on exit.
6742 o Bugfixes on 0.1.0.x:
6743 - Tor didn't warn when it failed to open a log file.
6746 Changes in version 0.1.1.11-alpha - 2006-01-10
6747 o Crashes in 0.1.1.x:
6748 - Include all the assert/crash fixes from 0.1.0.16.
6749 - If you start Tor and then quit very quickly, there were some
6750 races that tried to free things that weren't allocated yet.
6751 - Fix a rare memory stomp if you're running hidden services.
6752 - Fix segfault when specifying DirServer in config without nickname.
6753 - Fix a seg fault when you finish connecting to a server but at
6754 that moment you dump his server descriptor.
6755 - Extendcircuit and Attachstream controller commands would
6756 assert/crash if you don't give them enough arguments.
6757 - Fix an assert error when we're out of space in the connection_list
6758 and we try to post a hidden service descriptor (reported by weasel).
6759 - If you specify a relative torrc path and you set RunAsDaemon in
6760 your torrc, then it chdir()'s to the new directory. If you HUP,
6761 it tries to load the new torrc location, fails, and exits.
6762 The fix: no longer allow a relative path to torrc using -f.
6765 - Implement "entry guards": automatically choose a handful of entry
6766 nodes and stick with them for all circuits. Only pick new guards
6767 when the ones you have are unsuitable, and if the old guards
6768 become suitable again, switch back. This will increase security
6769 dramatically against certain end-point attacks. The EntryNodes
6770 config option now provides some hints about which entry guards you
6771 want to use most; and StrictEntryNodes means to only use those.
6772 - New directory logic: download by descriptor digest, not by
6773 fingerprint. Caches try to download all listed digests from
6774 authorities; clients try to download "best" digests from caches.
6775 This avoids partitioning and isolating attacks better.
6776 - Make the "stable" router flag in network-status be the median of
6777 the uptimes of running valid servers, and make clients pay
6778 attention to the network-status flags. Thus the cutoff adapts
6779 to the stability of the network as a whole, making IRC, IM, etc
6780 connections more reliable.
6783 - Tor servers with dynamic IP addresses were needing to wait 18
6784 hours before they could start doing reachability testing using
6785 the new IP address and ports. This is because they were using
6786 the internal descriptor to learn what to test, yet they were only
6787 rebuilding the descriptor once they decided they were reachable.
6788 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
6789 to download certain server descriptors, throw them away, and then
6790 fetch them again after 30 minutes. Now mirrors throw away these
6791 server descriptors so clients can't get them.
6792 - We were leaving duplicate connections to other ORs open for a week,
6793 rather than closing them once we detect a duplicate. This only
6794 really affected authdirservers, but it affected them a lot.
6795 - Spread the authdirservers' reachability testing over the entire
6796 testing interval, so we don't try to do 500 TLS's at once every
6800 - If the network is down, and we try to connect to a conn because
6801 we have a circuit in mind, and we timeout (30 seconds) because the
6802 network never answers, we were expiring the circuit, but we weren't
6803 obsoleting the connection or telling the entry_guards functions.
6804 - Some Tor servers process billions of cells per day. These statistics
6805 need to be uint64_t's.
6806 - Check for integer overflows in more places, when adding elements
6807 to smartlists. This could possibly prevent a buffer overflow
6808 on malicious huge inputs. I don't see any, but I haven't looked
6810 - ReachableAddresses kept growing new "reject *:*" lines on every
6812 - When you "setconf log" via the controller, it should remove all
6813 logs. We were automatically adding back in a "log notice stdout".
6814 - Newly bootstrapped Tor networks couldn't establish hidden service
6815 circuits until they had nodes with high uptime. Be more tolerant.
6816 - We were marking servers down when they could not answer every piece
6817 of the directory request we sent them. This was far too harsh.
6818 - Fix the torify (tsocks) config file to not use Tor for localhost
6820 - Directory authorities now go to the proper authority when asking for
6821 a networkstatus, even when they want a compressed one.
6822 - Fix a harmless bug that was causing Tor servers to log
6823 "Got an end because of misc error, but we're not an AP. Closing."
6824 - Authorities were treating their own descriptor changes as cosmetic,
6825 meaning the descriptor available in the network-status and the
6826 descriptor that clients downloaded were different.
6827 - The OS X installer was adding a symlink for tor_resolve but
6828 the binary was called tor-resolve (reported by Thomas Hardly).
6829 - Workaround a problem with some http proxies where they refuse GET
6830 requests that specify "Content-Length: 0" (reported by Adrian).
6831 - Fix wrong log message when you add a "HiddenServiceNodes" config
6832 line without any HiddenServiceDir line (reported by Chris Thomas).
6835 - Write the TorVersion into the state file so we have a prayer of
6836 keeping forward and backward compatibility.
6837 - Revive the FascistFirewall config option rather than eliminating it:
6838 now it's a synonym for ReachableAddresses *:80,*:443.
6839 - Clients choose directory servers from the network status lists,
6840 not from their internal list of router descriptors. Now they can
6841 go to caches directly rather than needing to go to authorities
6843 - Directory authorities ignore router descriptors that have only
6844 cosmetic differences: do this for 0.1.0.x servers now too.
6845 - Add a new flag to network-status indicating whether the server
6846 can answer v2 directory requests too.
6847 - Authdirs now stop whining so loudly about bad descriptors that
6848 they fetch from other dirservers. So when there's a log complaint,
6849 it's for sure from a freshly uploaded descriptor.
6850 - Reduce memory requirements in our structs by changing the order
6852 - There used to be two ways to specify your listening ports in a
6853 server descriptor: on the "router" line and with a separate "ports"
6854 line. Remove support for the "ports" line.
6855 - New config option "AuthDirRejectUnlisted" for auth dirservers as
6856 a panic button: if we get flooded with unusable servers we can
6857 revert to only listing servers in the approved-routers file.
6858 - Auth dir servers can now mark a fingerprint as "!reject" or
6859 "!invalid" in the approved-routers file (as its nickname), to
6860 refuse descriptors outright or include them but marked as invalid.
6861 - Servers store bandwidth history across restarts/crashes.
6862 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
6863 get a better idea of why their circuits failed. Not used yet.
6864 - Directory mirrors now cache up to 16 unrecognized network-status
6865 docs. Now we can add new authdirservers and they'll be cached too.
6866 - When picking a random directory, prefer non-authorities if any
6868 - New controller option "getinfo desc/all-recent" to fetch the
6869 latest server descriptor for every router that Tor knows about.
6872 Changes in version 0.1.0.16 - 2006-01-02
6873 o Crash bugfixes on 0.1.0.x:
6874 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6875 corrupting the heap, losing FDs, or crashing when we need to resize
6876 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6877 - It turns out sparc64 platforms crash on unaligned memory access
6878 too -- so detect and avoid this.
6879 - Handle truncated compressed data correctly (by detecting it and
6881 - Fix possible-but-unlikely free(NULL) in control.c.
6882 - When we were closing connections, there was a rare case that
6883 stomped on memory, triggering seg faults and asserts.
6884 - Avoid potential infinite recursion when building a descriptor. (We
6885 don't know that it ever happened, but better to fix it anyway.)
6886 - We were neglecting to unlink marked circuits from soon-to-close OR
6887 connections, which caused some rare scribbling on freed memory.
6888 - Fix a memory stomping race bug when closing the joining point of two
6889 rendezvous circuits.
6890 - Fix an assert in time parsing found by Steven Murdoch.
6892 o Other bugfixes on 0.1.0.x:
6893 - When we're doing reachability testing, provide more useful log
6894 messages so the operator knows what to expect.
6895 - Do not check whether DirPort is reachable when we are suppressing
6896 advertising it because of hibernation.
6897 - When building with -static or on Solaris, we sometimes needed -ldl.
6898 - When we're deciding whether a stream has enough circuits around
6899 that can handle it, count the freshly dirty ones and not the ones
6900 that are so dirty they won't be able to handle it.
6901 - When we're expiring old circuits, we had a logic error that caused
6902 us to close new rendezvous circuits rather than old ones.
6903 - Give a more helpful log message when you try to change ORPort via
6904 the controller: you should upgrade Tor if you want that to work.
6905 - We were failing to parse Tor versions that start with "Tor ".
6906 - Tolerate faulty streams better: when a stream fails for reason
6907 exitpolicy, stop assuming that the router is lying about his exit
6908 policy. When a stream fails for reason misc, allow it to retry just
6909 as if it was resolvefailed. When a stream has failed three times,
6910 reset its failure count so we can try again and get all three tries.
6913 Changes in version 0.1.1.10-alpha - 2005-12-11
6914 o Correctness bugfixes on 0.1.0.x:
6915 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6916 corrupting the heap, losing FDs, or crashing when we need to resize
6917 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6918 - Stop doing the complex voodoo overkill checking for insecure
6919 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
6920 - When we were closing connections, there was a rare case that
6921 stomped on memory, triggering seg faults and asserts.
6922 - We were neglecting to unlink marked circuits from soon-to-close OR
6923 connections, which caused some rare scribbling on freed memory.
6924 - When we're deciding whether a stream has enough circuits around
6925 that can handle it, count the freshly dirty ones and not the ones
6926 that are so dirty they won't be able to handle it.
6927 - Recover better from TCP connections to Tor servers that are
6928 broken but don't tell you (it happens!); and rotate TLS
6929 connections once a week.
6930 - When we're expiring old circuits, we had a logic error that caused
6931 us to close new rendezvous circuits rather than old ones.
6932 - Fix a scary-looking but apparently harmless bug where circuits
6933 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
6934 servers, and never switch to state CIRCUIT_STATE_OPEN.
6935 - When building with -static or on Solaris, we sometimes needed to
6937 - Give a useful message when people run Tor as the wrong user,
6938 rather than telling them to start chowning random directories.
6939 - We were failing to inform the controller about new .onion streams.
6941 o Security bugfixes on 0.1.0.x:
6942 - Refuse server descriptors if the fingerprint line doesn't match
6943 the included identity key. Tor doesn't care, but other apps (and
6944 humans) might actually be trusting the fingerprint line.
6945 - We used to kill the circuit when we receive a relay command we
6946 don't recognize. Now we just drop it.
6947 - Start obeying our firewall options more rigorously:
6948 . If we can't get to a dirserver directly, try going via Tor.
6949 . Don't ever try to connect (as a client) to a place our
6950 firewall options forbid.
6951 . If we specify a proxy and also firewall options, obey the
6952 firewall options even when we're using the proxy: some proxies
6953 can only proxy to certain destinations.
6954 - Fix a bug found by Lasse Overlier: when we were making internal
6955 circuits (intended to be cannibalized later for rendezvous and
6956 introduction circuits), we were picking them so that they had
6957 useful exit nodes. There was no need for this, and it actually
6958 aids some statistical attacks.
6959 - Start treating internal circuits and exit circuits separately.
6960 It's important to keep them separate because internal circuits
6961 have their last hops picked like middle hops, rather than like
6962 exit hops. So exiting on them will break the user's expectations.
6964 o Bugfixes on 0.1.1.x:
6965 - Take out the mis-feature where we tried to detect IP address
6966 flapping for people with DynDNS, and chose not to upload a new
6967 server descriptor sometimes.
6968 - Try to be compatible with OpenSSL 0.9.6 again.
6969 - Log fix: when the controller is logging about .onion addresses,
6970 sometimes it didn't include the ".onion" part of the address.
6971 - Don't try to modify options->DirServers internally -- if the
6972 user didn't specify any, just add the default ones directly to
6973 the trusted dirserver list. This fixes a bug where people running
6974 controllers would use SETCONF on some totally unrelated config
6975 option, and Tor would start yelling at them about changing their
6977 - Let the controller's redirectstream command specify a port, in
6978 case the controller wants to change that too.
6979 - When we requested a pile of server descriptors, we sometimes
6980 accidentally launched a duplicate request for the first one.
6981 - Bugfix for trackhostexits: write down the fingerprint of the
6982 chosen exit, not its nickname, because the chosen exit might not
6984 - When parsing foo.exit, if foo is unknown, and we are leaving
6985 circuits unattached, set the chosen_exit field and leave the
6986 address empty. This matters because controllers got confused
6988 - Directory authorities no longer try to download server
6989 descriptors that they know they will reject.
6991 o Features and updates:
6992 - Replace balanced trees with hash tables: this should make stuff
6993 significantly faster.
6994 - Resume using the AES counter-mode implementation that we ship,
6995 rather than OpenSSL's. Ours is significantly faster.
6996 - Many other CPU and memory improvements.
6997 - Add a new config option FastFirstHopPK (on by default) so clients
6998 do a trivial crypto handshake for their first hop, since TLS has
6999 already taken care of confidentiality and authentication.
7000 - Add a new config option TestSocks so people can see if their
7001 applications are using socks4, socks4a, socks5-with-ip, or
7002 socks5-with-hostname. This way they don't have to keep mucking
7003 with tcpdump and wondering if something got cached somewhere.
7004 - Warn when listening on a public address for socks. I suspect a
7005 lot of people are setting themselves up as open socks proxies,
7006 and they have no idea that jerks on the Internet are using them,
7007 since they simply proxy the traffic into the Tor network.
7008 - Add "private:*" as an alias in configuration for policies. Now
7009 you can simplify your exit policy rather than needing to list
7010 every single internal or nonroutable network space.
7011 - Add a new controller event type that allows controllers to get
7012 all server descriptors that were uploaded to a router in its role
7013 as authoritative dirserver.
7014 - Start shipping socks-extensions.txt, tor-doc-unix.html,
7015 tor-doc-server.html, and stylesheet.css in the tarball.
7016 - Stop shipping tor-doc.html in the tarball.
7019 Changes in version 0.1.1.9-alpha - 2005-11-15
7020 o Usability improvements:
7021 - Start calling it FooListenAddress rather than FooBindAddress,
7022 since few of our users know what it means to bind an address
7024 - Reduce clutter in server logs. We're going to try to make
7025 them actually usable now. New config option ProtocolWarnings that
7026 lets you hear about how _other Tors_ are breaking the protocol. Off
7028 - Divide log messages into logging domains. Once we put some sort
7029 of interface on this, it will let people looking at more verbose
7030 log levels specify the topics they want to hear more about.
7031 - Make directory servers return better http 404 error messages
7032 instead of a generic "Servers unavailable".
7033 - Check for even more Windows version flags when writing the platform
7034 string in server descriptors, and note any we don't recognize.
7035 - Clean up more of the OpenSSL memory when exiting, so we can detect
7036 memory leaks better.
7037 - Make directory authorities be non-versioning, non-naming by
7038 default. Now we can add new directory servers without requiring
7039 their operators to pay close attention.
7040 - When logging via syslog, include the pid whenever we provide
7041 a log entry. Suggested by Todd Fries.
7043 o Performance improvements:
7044 - Directory servers now silently throw away new descriptors that
7045 haven't changed much if the timestamps are similar. We do this to
7046 tolerate older Tor servers that upload a new descriptor every 15
7047 minutes. (It seemed like a good idea at the time.)
7048 - Inline bottleneck smartlist functions; use fast versions by default.
7049 - Add a "Map from digest to void*" abstraction digestmap_t so we
7050 can do less hex encoding/decoding. Use it in router_get_by_digest()
7051 to resolve a performance bottleneck.
7052 - Allow tor_gzip_uncompress to extract as much as possible from
7053 truncated compressed data. Try to extract as many
7054 descriptors as possible from truncated http responses (when
7055 DIR_PURPOSE_FETCH_ROUTERDESC).
7056 - Make circ->onionskin a pointer, not a static array. moria2 was using
7057 125000 circuit_t's after it had been up for a few weeks, which
7058 translates to 20+ megs of wasted space.
7059 - The private half of our EDH handshake keys are now chosen out
7060 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
7062 o Security improvements:
7063 - Start making directory caches retain old routerinfos, so soon
7064 clients can start asking by digest of descriptor rather than by
7065 fingerprint of server.
7066 - Add half our entropy from RAND_poll in OpenSSL. This knows how
7067 to use egd (if present), openbsd weirdness (if present), vms/os2
7068 weirdness (if we ever port there), and more in the future.
7070 o Bugfixes on 0.1.0.x:
7071 - Do round-robin writes of at most 16 kB per write. This might be
7072 more fair on loaded Tor servers, and it might resolve our Windows
7073 crash bug. It might also slow things down.
7074 - Our TLS handshakes were generating a single public/private
7075 keypair for the TLS context, rather than making a new one for
7076 each new connections. Oops. (But we were still rotating them
7077 periodically, so it's not so bad.)
7078 - When we were cannibalizing a circuit with a particular exit
7079 node in mind, we weren't checking to see if that exit node was
7080 already present earlier in the circuit. Oops.
7081 - When a Tor server's IP changes (e.g. from a dyndns address),
7082 upload a new descriptor so clients will learn too.
7083 - Really busy servers were keeping enough circuits open on stable
7084 connections that they were wrapping around the circuit_id
7085 space. (It's only two bytes.) This exposed a bug where we would
7086 feel free to reuse a circuit_id even if it still exists but has
7087 been marked for close. Try to fix this bug. Some bug remains.
7088 - If we would close a stream early (e.g. it asks for a .exit that
7089 we know would refuse it) but the LeaveStreamsUnattached config
7090 option is set by the controller, then don't close it.
7092 o Bugfixes on 0.1.1.8-alpha:
7093 - Fix a big pile of memory leaks, some of them serious.
7094 - Do not try to download a routerdesc if we would immediately reject
7096 - Resume inserting a newline between all router descriptors when
7097 generating (old style) signed directories, since our spec says
7099 - When providing content-type application/octet-stream for
7100 server descriptors using .z, we were leaving out the
7101 content-encoding header. Oops. (Everything tolerated this just
7102 fine, but that doesn't mean we need to be part of the problem.)
7103 - Fix a potential seg fault in getconf and getinfo using version 1
7104 of the controller protocol.
7105 - Avoid crash: do not check whether DirPort is reachable when we
7106 are suppressing it because of hibernation.
7107 - Make --hash-password not crash on exit.
7110 Changes in version 0.1.1.8-alpha - 2005-10-07
7111 o New features (major):
7112 - Clients don't download or use the directory anymore. Now they
7113 download and use network-statuses from the trusted dirservers,
7114 and fetch individual server descriptors as needed from mirrors.
7115 See dir-spec.txt for all the gory details.
7116 - Be more conservative about whether to advertise our DirPort.
7117 The main change is to not advertise if we're running at capacity
7118 and either a) we could hibernate or b) our capacity is low and
7119 we're using a default DirPort.
7120 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
7122 o New features (minor):
7123 - Try to be smart about when to retry network-status and
7124 server-descriptor fetches. Still needs some tuning.
7125 - Stop parsing, storing, or using running-routers output (but
7126 mirrors still cache and serve it).
7127 - Consider a threshold of versioning dirservers (dirservers who have
7128 an opinion about which Tor versions are still recommended) before
7129 deciding whether to warn the user that he's obsolete.
7130 - Dirservers can now reject/invalidate by key and IP, with the
7131 config options "AuthDirInvalid" and "AuthDirReject". This is
7132 useful since currently we automatically list servers as running
7133 and usable even if we know they're jerks.
7134 - Provide dire warnings to any users who set DirServer; move it out
7135 of torrc.sample and into torrc.complete.
7136 - Add MyFamily to torrc.sample in the server section.
7137 - Add nicknames to the DirServer line, so we can refer to them
7138 without requiring all our users to memorize their IP addresses.
7139 - When we get an EOF or a timeout on a directory connection, note
7140 how many bytes of serverdesc we are dropping. This will help
7141 us determine whether it is smart to parse incomplete serverdesc
7143 - Add a new function to "change pseudonyms" -- that is, to stop
7144 using any currently-dirty circuits for new streams, so we don't
7145 link new actions to old actions. Currently it's only called on
7146 HUP (or SIGNAL RELOAD).
7147 - On sighup, if UseHelperNodes changed to 1, use new circuits.
7148 - Start using RAND_bytes rather than RAND_pseudo_bytes from
7149 OpenSSL. Also, reseed our entropy every hour, not just at
7150 startup. And entropy in 512-bit chunks, not 160-bit chunks.
7152 o Fixes on 0.1.1.7-alpha:
7153 - Nobody ever implemented EVENT_ADDRMAP for control protocol
7154 version 0, so don't let version 0 controllers ask for it.
7155 - If you requested something with too many newlines via the
7156 v1 controller protocol, you could crash tor.
7157 - Fix a number of memory leaks, including some pretty serious ones.
7158 - Re-enable DirPort testing again, so Tor servers will be willing
7159 to advertise their DirPort if it's reachable.
7160 - On TLS handshake, only check the other router's nickname against
7161 its expected nickname if is_named is set.
7163 o Fixes forward-ported from 0.1.0.15:
7164 - Don't crash when we don't have any spare file descriptors and we
7165 try to spawn a dns or cpu worker.
7166 - Make the numbers in read-history and write-history into uint64s,
7167 so they don't overflow and publish negatives in the descriptor.
7170 - For the OS X package's modified privoxy config file, comment
7171 out the "logfile" line so we don't log everything passed
7173 - We were whining about using socks4 or socks5-with-local-lookup
7174 even when it's an IP in the "virtual" range we designed exactly
7176 - We were leaking some memory every time the client changes IPs.
7177 - Never call free() on tor_malloc()d memory. This will help us
7178 use dmalloc to detect memory leaks.
7179 - Check for named servers when looking them up by nickname;
7180 warn when we'recalling a non-named server by its nickname;
7181 don't warn twice about the same name.
7182 - Try to list MyFamily elements by key, not by nickname, and warn
7183 if we've not heard of the server.
7184 - Make windows platform detection (uname equivalent) smarter.
7185 - It turns out sparc64 doesn't like unaligned access either.
7188 Changes in version 0.1.0.15 - 2005-09-23
7189 o Bugfixes on 0.1.0.x:
7190 - Reject ports 465 and 587 (spam targets) in default exit policy.
7191 - Don't crash when we don't have any spare file descriptors and we
7192 try to spawn a dns or cpu worker.
7193 - Get rid of IgnoreVersion undocumented config option, and make us
7194 only warn, never exit, when we're running an obsolete version.
7195 - Don't try to print a null string when your server finds itself to
7196 be unreachable and the Address config option is empty.
7197 - Make the numbers in read-history and write-history into uint64s,
7198 so they don't overflow and publish negatives in the descriptor.
7199 - Fix a minor memory leak in smartlist_string_remove().
7200 - We were only allowing ourselves to upload a server descriptor at
7201 most every 20 minutes, even if it changed earlier than that.
7202 - Clean up log entries that pointed to old URLs.
7205 Changes in version 0.1.1.7-alpha - 2005-09-14
7206 o Fixes on 0.1.1.6-alpha:
7207 - Exit servers were crashing when people asked them to make a
7208 connection to an address not in their exit policy.
7209 - Looking up a non-existent stream for a v1 control connection would
7211 - Fix a seg fault if we ask a dirserver for a descriptor by
7212 fingerprint but he doesn't know about him.
7213 - SETCONF was appending items to linelists, not clearing them.
7214 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
7215 out and refuse the setconf if it would fail.
7216 - Downgrade the dirserver log messages when whining about
7220 - Add Peter Palfrader's check-tor script to tor/contrib/
7221 It lets you easily check whether a given server (referenced by
7222 nickname) is reachable by you.
7223 - Numerous changes to move towards client-side v2 directories. Not
7227 - If the user gave tor an odd number of command-line arguments,
7228 we were silently ignoring the last one. Now we complain and fail.
7229 [This wins the oldest-bug prize -- this bug has been present since
7230 November 2002, as released in Tor 0.0.0.]
7231 - Do not use unaligned memory access on alpha, mips, or mipsel.
7232 It *works*, but is very slow, so we treat them as if it doesn't.
7233 - Retry directory requests if we fail to get an answer we like
7234 from a given dirserver (we were retrying before, but only if
7235 we fail to connect).
7236 - When writing the RecommendedVersions line, sort them first.
7237 - When the client asked for a rendezvous port that the hidden
7238 service didn't want to provide, we were sending an IP address
7239 back along with the end cell. Fortunately, it was zero. But stop
7241 - Correct "your server is reachable" log entries to indicate that
7242 it was self-testing that told us so.
7245 Changes in version 0.1.1.6-alpha - 2005-09-09
7246 o Fixes on 0.1.1.5-alpha:
7247 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
7248 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
7249 - Fix bug with tor_memmem finding a match at the end of the string.
7250 - Make unit tests run without segfaulting.
7251 - Resolve some solaris x86 compile warnings.
7252 - Handle duplicate lines in approved-routers files without warning.
7253 - Fix bug where as soon as a server refused any requests due to his
7254 exit policy (e.g. when we ask for localhost and he tells us that's
7255 127.0.0.1 and he won't do it), we decided he wasn't obeying his
7256 exit policy using him for any exits.
7257 - Only do openssl hardware accelerator stuff if openssl version is
7260 o New controller features/fixes:
7261 - Add a "RESETCONF" command so you can set config options like
7262 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7263 a config option in the torrc with no value, then it clears it
7264 entirely (rather than setting it to its default).
7265 - Add a "GETINFO config-file" to tell us where torrc is.
7266 - Avoid sending blank lines when GETINFO replies should be empty.
7267 - Add a QUIT command for the controller (for using it manually).
7268 - Fix a bug in SAVECONF that was adding default dirservers and
7269 other redundant entries to the torrc file.
7271 o Start on the new directory design:
7272 - Generate, publish, cache, serve new network-status format.
7273 - Publish individual descriptors (by fingerprint, by "all", and by
7275 - Publish client and server recommended versions separately.
7276 - Allow tor_gzip_uncompress() to handle multiple concatenated
7277 compressed strings. Serve compressed groups of router
7278 descriptors. The compression logic here could be more
7280 - Distinguish v1 authorities (all currently trusted directories)
7281 from v2 authorities (all trusted directories).
7282 - Change DirServers config line to note which dirs are v1 authorities.
7283 - Add configuration option "V1AuthoritativeDirectory 1" which
7284 moria1, moria2, and tor26 should set.
7285 - Remove option when getting directory cache to see whether they
7286 support running-routers; they all do now. Replace it with one
7287 to see whether caches support v2 stuff.
7290 - Dirservers now do their own external reachability testing of each
7291 Tor server, and only list them as running if they've been found to
7292 be reachable. We also send back warnings to the server's logs if
7293 it uploads a descriptor that we already believe is unreachable.
7294 - Implement exit enclaves: if we know an IP address for the
7295 destination, and there's a running Tor server at that address
7296 which allows exit to the destination, then extend the circuit to
7297 that exit first. This provides end-to-end encryption and end-to-end
7298 authentication. Also, if the user wants a .exit address or enclave,
7299 use 4 hops rather than 3, and cannibalize a general circ for it
7301 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
7302 controller. Also, rotate dns and cpu workers if the controller
7303 changes options that will affect them; and initialize the dns
7304 worker cache tree whether or not we start out as a server.
7305 - Only upload a new server descriptor when options change, 18
7306 hours have passed, uptime is reset, or bandwidth changes a lot.
7307 - Check [X-]Forwarded-For headers in HTTP requests when generating
7308 log messages. This lets people run dirservers (and caches) behind
7309 Apache but still know which IP addresses are causing warnings.
7311 o Config option changes:
7312 - Replace (Fascist)Firewall* config options with a new
7313 ReachableAddresses option that understands address policies.
7314 For example, "ReachableAddresses *:80,*:443"
7315 - Get rid of IgnoreVersion undocumented config option, and make us
7316 only warn, never exit, when we're running an obsolete version.
7317 - Make MonthlyAccountingStart config option truly obsolete now.
7320 - Reject ports 465 and 587 in the default exit policy, since
7321 people have started using them for spam too.
7322 - It turns out we couldn't bootstrap a network since we added
7323 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7324 has never gone down. Add an AssumeReachable config option to let
7325 servers and dirservers bootstrap. When we're trying to build a
7326 high-uptime or high-bandwidth circuit but there aren't enough
7327 suitable servers, try being less picky rather than simply failing.
7328 - Our logic to decide if the OR we connected to was the right guy
7329 was brittle and maybe open to a mitm for unverified routers.
7330 - We weren't cannibalizing circuits correctly for
7331 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7332 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7333 build those from scratch. This should make hidden services faster.
7334 - Predict required circuits better, with an eye toward making hidden
7335 services faster on the service end.
7336 - Retry streams if the exit node sends back a 'misc' failure. This
7337 should result in fewer random failures. Also, after failing
7338 from resolve failed or misc, reset the num failures, so we give
7339 it a fair shake next time we try.
7340 - Clean up the rendezvous warn log msgs, and downgrade some to info.
7341 - Reduce severity on logs about dns worker spawning and culling.
7342 - When we're shutting down and we do something like try to post a
7343 server descriptor or rendezvous descriptor, don't complain that
7344 we seem to be unreachable. Of course we are, we're shutting down.
7345 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7346 We don't use them yet, but maybe one day our DNS resolver will be
7347 able to discover them.
7348 - Make ContactInfo mandatory for authoritative directory servers.
7349 - Require server descriptors to list IPv4 addresses -- hostnames
7350 are no longer allowed. This also fixes some potential security
7351 problems with people providing hostnames as their address and then
7352 preferentially resolving them to partition users.
7353 - Change log line for unreachability to explicitly suggest /etc/hosts
7354 as the culprit. Also make it clearer what IP address and ports we're
7355 testing for reachability.
7356 - Put quotes around user-supplied strings when logging so users are
7357 more likely to realize if they add bad characters (like quotes)
7359 - Let auth dir servers start without specifying an Address config
7361 - Make unit tests (and other invocations that aren't the real Tor)
7362 run without launching listeners, creating subdirectories, and so on.
7365 Changes in version 0.1.1.5-alpha - 2005-08-08
7366 o Bugfixes included in 0.1.0.14.
7368 o Bugfixes on 0.1.0.x:
7369 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7370 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7371 it would silently using ignore the 6668.
7374 Changes in version 0.1.0.14 - 2005-08-08
7375 o Bugfixes on 0.1.0.x:
7376 - Fix the other half of the bug with crypto handshakes
7378 - Fix an assert trigger if you send a 'signal term' via the
7379 controller when it's listening for 'event info' messages.
7382 Changes in version 0.1.1.4-alpha - 2005-08-04
7383 o Bugfixes included in 0.1.0.13.
7386 - Improve tor_gettimeofday() granularity on windows.
7387 - Make clients regenerate their keys when their IP address changes.
7388 - Implement some more GETINFO goodness: expose helper nodes, config
7389 options, getinfo keys.
7392 Changes in version 0.1.0.13 - 2005-08-04
7393 o Bugfixes on 0.1.0.x:
7394 - Fix a critical bug in the security of our crypto handshakes.
7395 - Fix a size_t underflow in smartlist_join_strings2() that made
7396 it do bad things when you hand it an empty smartlist.
7397 - Fix Windows installer to ship Tor license (thanks to Aphex for
7398 pointing out this oversight) and put a link to the doc directory
7400 - Explicitly set no-unaligned-access for sparc: it turns out the
7401 new gcc's let you compile broken code, but that doesn't make it
7405 Changes in version 0.1.1.3-alpha - 2005-07-23
7406 o Bugfixes on 0.1.1.2-alpha:
7407 - Fix a bug in handling the controller's "post descriptor"
7409 - Fix several bugs in handling the controller's "extend circuit"
7411 - Fix a bug in handling the controller's "stream status" event.
7412 - Fix an assert failure if we have a controller listening for
7413 circuit events and we go offline.
7414 - Re-allow hidden service descriptors to publish 0 intro points.
7415 - Fix a crash when generating your hidden service descriptor if
7416 you don't have enough intro points already.
7418 o New features on 0.1.1.2-alpha:
7419 - New controller function "getinfo accounting", to ask how
7420 many bytes we've used in this time period.
7421 - Experimental support for helper nodes: a lot of the risk from
7422 a small static adversary comes because users pick new random
7423 nodes every time they rebuild a circuit. Now users will try to
7424 stick to the same small set of entry nodes if they can. Not
7425 enabled by default yet.
7427 o Bugfixes on 0.1.0.12:
7428 - If you're an auth dir server, always publish your dirport,
7429 even if you haven't yet found yourself to be reachable.
7430 - Fix a size_t underflow in smartlist_join_strings2() that made
7431 it do bad things when you hand it an empty smartlist.
7434 Changes in version 0.1.0.12 - 2005-07-18
7435 o New directory servers:
7436 - tor26 has changed IP address.
7438 o Bugfixes on 0.1.0.x:
7439 - Fix a possible double-free in tor_gzip_uncompress().
7440 - When --disable-threads is set, do not search for or link against
7442 - Don't trigger an assert if an authoritative directory server
7443 claims its dirport is 0.
7444 - Fix bug with removing Tor as an NT service: some people were
7445 getting "The service did not return an error." Thanks to Matt
7449 Changes in version 0.1.1.2-alpha - 2005-07-15
7450 o New directory servers:
7451 - tor26 has changed IP address.
7453 o Bugfixes on 0.1.0.x, crashes/leaks:
7454 - Port the servers-not-obeying-their-exit-policies fix from
7456 - Fix an fd leak in start_daemon().
7457 - On Windows, you can't always reopen a port right after you've
7458 closed it. So change retry_listeners() to only close and re-open
7459 ports that have changed.
7460 - Fix a possible double-free in tor_gzip_uncompress().
7462 o Bugfixes on 0.1.0.x, usability:
7463 - When tor_socketpair() fails in Windows, give a reasonable
7464 Windows-style errno back.
7465 - Let people type "tor --install" as well as "tor -install" when
7467 want to make it an NT service.
7468 - NT service patch from Matt Edman to improve error messages.
7469 - When the controller asks for a config option with an abbreviated
7470 name, give the full name in our response.
7471 - Correct the man page entry on TrackHostExitsExpire.
7472 - Looks like we were never delivering deflated (i.e. compressed)
7473 running-routers lists, even when asked. Oops.
7474 - When --disable-threads is set, do not search for or link against
7477 o Bugfixes on 0.1.1.x:
7478 - Fix a seg fault with autodetecting which controller version is
7482 - New hidden service descriptor format: put a version in it, and
7483 let people specify introduction/rendezvous points that aren't
7484 in "the directory" (which is subjective anyway).
7485 - Allow the DEBUG controller event to work again. Mark certain log
7486 entries as "don't tell this to controllers", so we avoid cycles.
7489 Changes in version 0.1.0.11 - 2005-06-30
7490 o Bugfixes on 0.1.0.x:
7491 - Fix major security bug: servers were disregarding their
7492 exit policies if clients behaved unexpectedly.
7493 - Make OS X init script check for missing argument, so we don't
7494 confuse users who invoke it incorrectly.
7495 - Fix a seg fault in "tor --hash-password foo".
7496 - The MAPADDRESS control command was broken.
7499 Changes in version 0.1.1.1-alpha - 2005-06-29
7501 - Make OS X init script check for missing argument, so we don't
7502 confuse users who invoke it incorrectly.
7503 - Fix a seg fault in "tor --hash-password foo".
7504 - Fix a possible way to DoS dirservers.
7505 - When we complain that your exit policy implicitly allows local or
7506 private address spaces, name them explicitly so operators can
7508 - Make the log message less scary when all the dirservers are
7509 temporarily unreachable.
7510 - We were printing the number of idle dns workers incorrectly when
7514 - Revised controller protocol (version 1) that uses ascii rather
7515 than binary. Add supporting libraries in python and java so you
7516 can use the controller from your applications without caring how
7518 - Spiffy new support for crypto hardware accelerators. Can somebody
7522 Changes in version 0.0.9.10 - 2005-06-16
7523 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
7524 - Refuse relay cells that claim to have a length larger than the
7525 maximum allowed. This prevents a potential attack that could read
7526 arbitrary memory (e.g. keys) from an exit server's process
7530 Changes in version 0.1.0.10 - 2005-06-14
7531 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
7532 libevent before 1.1a.
7535 Changes in version 0.1.0.9-rc - 2005-06-09
7537 - Reset buf->highwater every time buf_shrink() is called, not just on
7538 a successful shrink. This was causing significant memory bloat.
7539 - Fix buffer overflow when checking hashed passwords.
7540 - Security fix: if seeding the RNG on Win32 fails, quit.
7541 - Allow seeding the RNG on Win32 even when you're not running as
7543 - Disable threading on Solaris too. Something is wonky with it,
7544 cpuworkers, and reentrant libs.
7545 - Reenable the part of the code that tries to flush as soon as an
7546 OR outbuf has a full TLS record available. Perhaps this will make
7547 OR outbufs not grow as huge except in rare cases, thus saving lots
7548 of CPU time plus memory.
7549 - Reject malformed .onion addresses rather then passing them on as
7550 normal web requests.
7551 - Adapt patch from Adam Langley: fix possible memory leak in
7552 tor_lookup_hostname().
7553 - Initialize libevent later in the startup process, so the logs are
7554 already established by the time we start logging libevent warns.
7555 - Use correct errno on win32 if libevent fails.
7556 - Check and warn about known-bad/slow libevent versions.
7557 - Pay more attention to the ClientOnly config option.
7558 - Have torctl.in/tor.sh.in check for location of su binary (needed
7560 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
7561 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
7562 HttpProxyAuthenticator
7563 - Stop warning about sigpipes in the logs. We're going to
7564 pretend that getting these occassionally is normal and fine.
7565 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
7567 installer screens; and don't put stuff into StartupItems unless
7568 the user asks you to.
7569 - Require servers that use the default dirservers to have public IP
7570 addresses. We have too many servers that are configured with private
7571 IPs and their admins never notice the log entries complaining that
7572 their descriptors are being rejected.
7573 - Add OSX uninstall instructions. An actual uninstall script will
7577 Changes in version 0.1.0.8-rc - 2005-05-23
7579 - It turns out that kqueue on OS X 10.3.9 was causing kernel
7580 panics. Disable kqueue on all OS X Tors.
7581 - Fix RPM: remove duplicate line accidentally added to the rpm
7583 - Disable threads on openbsd too, since its gethostaddr is not
7585 - Tolerate libevent 0.8 since it still works, even though it's
7587 - Enable building on Red Hat 9.0 again.
7588 - Allow the middle hop of the testing circuit to be running any
7589 version, now that most of them have the bugfix to let them connect
7590 to unknown servers. This will allow reachability testing to work
7591 even when 0.0.9.7-0.0.9.9 become obsolete.
7592 - Handle relay cells with rh.length too large. This prevents
7593 a potential attack that could read arbitrary memory (maybe even
7594 keys) from the exit server's process.
7595 - We screwed up the dirport reachability testing when we don't yet
7596 have a cached version of the directory. Hopefully now fixed.
7597 - Clean up router_load_single_router() (used by the controller),
7598 so it doesn't seg fault on error.
7599 - Fix a minor memory leak when somebody establishes an introduction
7600 point at your Tor server.
7601 - If a socks connection ends because read fails, don't warn that
7602 you're not sending a socks reply back.
7605 - Add HttpProxyAuthenticator config option too, that works like
7606 the HttpsProxyAuthenticator config option.
7607 - Encode hashed controller passwords in hex instead of base64,
7608 to make it easier to write controllers.
7611 Changes in version 0.1.0.7-rc - 2005-05-17
7613 - Fix a bug in the OS X package installer that prevented it from
7614 installing on Tiger.
7615 - Fix a script bug in the OS X package installer that made it
7616 complain during installation.
7617 - Find libevent even if it's hiding in /usr/local/ and your
7618 CFLAGS and LDFLAGS don't tell you to look there.
7619 - Be able to link with libevent as a shared library (the default
7620 after 1.0d), even if it's hiding in /usr/local/lib and even
7621 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7622 assuming you're running gcc. Otherwise fail and give a useful
7624 - Fix a bug in the RPM packager: set home directory for _tor to
7625 something more reasonable when first installing.
7626 - Free a minor amount of memory that is still reachable on exit.
7629 Changes in version 0.1.0.6-rc - 2005-05-14
7631 - Implement --disable-threads configure option. Disable threads on
7632 netbsd by default, because it appears to have no reentrant resolver
7634 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
7635 release (1.1) detects and disables kqueue if it's broken.
7636 - Append default exit policy before checking for implicit internal
7637 addresses. Now we don't log a bunch of complaints on startup
7638 when using the default exit policy.
7639 - Some people were putting "Address " in their torrc, and they had
7640 a buggy resolver that resolved " " to 0.0.0.0. Oops.
7641 - If DataDir is ~/.tor, and that expands to /.tor, then default to
7642 LOCALSTATEDIR/tor instead.
7643 - Fix fragmented-message bug in TorControl.py.
7644 - Resolve a minor bug which would prevent unreachable dirports
7645 from getting suppressed in the published descriptor.
7646 - When the controller gave us a new descriptor, we weren't resolving
7647 it immediately, so Tor would think its address was 0.0.0.0 until
7648 we fetched a new directory.
7649 - Fix an uppercase/lowercase case error in suppressing a bogus
7650 libevent warning on some Linuxes.
7653 - Begin scrubbing sensitive strings from logs by default. Turn off
7654 the config option SafeLogging if you need to do debugging.
7655 - Switch to a new buffer management algorithm, which tries to avoid
7656 reallocing and copying quite as much. In first tests it looks like
7657 it uses *more* memory on average, but less cpu.
7658 - First cut at support for "create-fast" cells. Clients can use
7659 these when extending to their first hop, since the TLS already
7660 provides forward secrecy and authentication. Not enabled on
7662 - When dirservers refuse a router descriptor, we now log its
7663 contactinfo, platform, and the poster's IP address.
7664 - Call tor_free_all instead of connections_free_all after forking, to
7665 save memory on systems that need to fork.
7666 - Whine at you if you're a server and you don't set your contactinfo.
7667 - Implement --verify-config command-line option to check if your torrc
7668 is valid without actually launching Tor.
7669 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
7670 rather than just rejecting it.
7673 Changes in version 0.1.0.5-rc - 2005-04-27
7675 - Stop trying to print a null pointer if an OR conn fails because
7676 we didn't like its cert.
7678 - Switch our internal buffers implementation to use a ring buffer,
7679 to hopefully improve performance for fast servers a lot.
7680 - Add HttpsProxyAuthenticator support (basic auth only), based
7681 on patch from Adam Langley.
7682 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7683 the fast servers that have been joining lately.
7684 - Give hidden service accesses extra time on the first attempt,
7685 since 60 seconds is often only barely enough. This might improve
7687 - Improve performance for dirservers: stop re-parsing the whole
7688 directory every time you regenerate it.
7689 - Add more debugging info to help us find the weird dns freebsd
7690 pthreads bug; cleaner debug messages to help track future issues.
7693 Changes in version 0.0.9.9 - 2005-04-23
7694 o Bugfixes on 0.0.9.x:
7695 - If unofficial Tor clients connect and send weird TLS certs, our
7696 Tor server triggers an assert. This release contains a minimal
7697 backport from the broader fix that we put into 0.1.0.4-rc.
7700 Changes in version 0.1.0.4-rc - 2005-04-23
7702 - If unofficial Tor clients connect and send weird TLS certs, our
7703 Tor server triggers an assert. Stop asserting, and start handling
7704 TLS errors better in other situations too.
7705 - When the controller asks us to tell it about all the debug-level
7706 logs, it turns out we were generating debug-level logs while
7707 telling it about them, which turns into a bad loop. Now keep
7708 track of whether you're sending a debug log to the controller,
7709 and don't log when you are.
7710 - Fix the "postdescriptor" feature of the controller interface: on
7711 non-complete success, only say "done" once.
7713 - Clients are now willing to load balance over up to 2mB, not 1mB,
7714 of advertised bandwidth capacity.
7715 - Add a NoPublish config option, so you can be a server (e.g. for
7716 testing running Tor servers in other Tor networks) without
7717 publishing your descriptor to the primary dirservers.
7720 Changes in version 0.1.0.3-rc - 2005-04-08
7721 o Improvements on 0.1.0.2-rc:
7722 - Client now retries when streams end early for 'hibernating' or
7723 'resource limit' reasons, rather than failing them.
7724 - More automated handling for dirserver operators:
7725 - Automatically approve nodes running 0.1.0.2-rc or later,
7726 now that the the reachability detection stuff is working.
7727 - Now we allow two unverified servers with the same nickname
7728 but different keys. But if a nickname is verified, only that
7729 nickname+key are allowed.
7730 - If you're an authdirserver connecting to an address:port,
7731 and it's not the OR you were expecting, forget about that
7732 descriptor. If he *was* the one you were expecting, then forget
7733 about all other descriptors for that address:port.
7734 - Allow servers to publish descriptors from 12 hours in the future.
7735 Corollary: only whine about clock skew from the dirserver if
7736 he's a trusted dirserver (since now even verified servers could
7737 have quite wrong clocks).
7738 - Adjust maximum skew and age for rendezvous descriptors: let skew
7739 be 48 hours rather than 90 minutes.
7740 - Efficiency improvements:
7741 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7742 it much faster to look up a circuit for each relay cell.
7743 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7744 since they're eating our cpu on exit nodes.
7745 - Stop wasting time doing a case insensitive comparison for every
7746 dns name every time we do any lookup. Canonicalize the names to
7747 lowercase and be done with it.
7748 - Start sending 'truncated' cells back rather than destroy cells,
7749 if the circuit closes in front of you. This means we won't have
7750 to abandon partially built circuits.
7751 - Only warn once per nickname from add_nickname_list_to_smartlist
7752 per failure, so an entrynode or exitnode choice that's down won't
7754 - Put a note in the torrc about abuse potential with the default
7756 - Revise control spec and implementation to allow all log messages to
7757 be sent to controller with their severities intact (suggested by
7758 Matt Edman). Update TorControl to handle new log event types.
7759 - Provide better explanation messages when controller's POSTDESCRIPTOR
7761 - Stop putting nodename in the Platform string in server descriptors.
7762 It doesn't actually help, and it is confusing/upsetting some people.
7764 o Bugfixes on 0.1.0.2-rc:
7765 - We were printing the host mask wrong in exit policies in server
7766 descriptors. This isn't a critical bug though, since we were still
7767 obeying the exit policy internally.
7768 - Fix Tor when compiled with libevent but without pthreads: move
7769 connection_unregister() from _connection_free() to
7771 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
7772 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
7773 when we look through the connection array, we'll find any of the
7774 cpu/dnsworkers. This is no good.
7776 o Bugfixes on 0.0.9.8:
7777 - Fix possible bug on threading platforms (e.g. win32) which was
7778 leaking a file descriptor whenever a cpuworker or dnsworker died.
7779 - When using preferred entry or exit nodes, ignore whether the
7780 circuit wants uptime or capacity. They asked for the nodes, they
7782 - chdir() to your datadirectory at the *end* of the daemonize process,
7783 not the beginning. This was a problem because the first time you
7784 run tor, if your datadir isn't there, and you have runasdaemon set
7785 to 1, it will try to chdir to it before it tries to create it. Oops.
7786 - Handle changed router status correctly when dirserver reloads
7787 fingerprint file. We used to be dropping all unverified descriptors
7788 right then. The bug was hidden because we would immediately
7789 fetch a directory from another dirserver, which would include the
7790 descriptors we just dropped.
7791 - When we're connecting to an OR and he's got a different nickname/key
7792 than we were expecting, only complain loudly if we're an OP or a
7793 dirserver. Complaining loudly to the OR admins just confuses them.
7794 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
7795 artificially capped at 500kB.
7798 Changes in version 0.0.9.8 - 2005-04-07
7799 o Bugfixes on 0.0.9.x:
7800 - We have a bug that I haven't found yet. Sometimes, very rarely,
7801 cpuworkers get stuck in the 'busy' state, even though the cpuworker
7802 thinks of itself as idle. This meant that no new circuits ever got
7803 established. Here's a workaround to kill any cpuworker that's been
7804 busy for more than 100 seconds.
7807 Changes in version 0.1.0.2-rc - 2005-04-01
7808 o Bugfixes on 0.1.0.1-rc:
7809 - Fixes on reachability detection:
7810 - Don't check for reachability while hibernating.
7811 - If ORPort is reachable but DirPort isn't, still publish the
7812 descriptor, but zero out DirPort until it's found reachable.
7813 - When building testing circs for ORPort testing, use only
7814 high-bandwidth nodes, so fewer circuits fail.
7815 - Complain about unreachable ORPort separately from unreachable
7816 DirPort, so the user knows what's going on.
7817 - Make sure we only conclude ORPort reachability if we didn't
7818 initiate the conn. Otherwise we could falsely conclude that
7819 we're reachable just because we connected to the guy earlier
7820 and he used that same pipe to extend to us.
7821 - Authdirservers shouldn't do ORPort reachability detection,
7822 since they're in clique mode, so it will be rare to find a
7823 server not already connected to them.
7824 - When building testing circuits, always pick middle hops running
7825 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
7826 bug. (This is a kludge; it will go away when 0.0.9.x becomes
7828 - When we decide we're reachable, actually publish our descriptor
7830 - Fix bug in redirectstream in the controller.
7831 - Fix the state descriptor strings so logs don't claim edge streams
7832 are in a different state than they actually are.
7833 - Use recent libevent features when possible (this only really affects
7834 win32 and osx right now, because the new libevent with these
7835 features hasn't been released yet). Add code to suppress spurious
7837 - Prevent possible segfault in connection_close_unattached_ap().
7838 - Fix newlines on torrc in win32.
7839 - Improve error msgs when tor-resolve fails.
7841 o Improvements on 0.0.9.x:
7842 - New experimental script tor/contrib/ExerciseServer.py (needs more
7843 work) that uses the controller interface to build circuits and
7844 fetch pages over them. This will help us bootstrap servers that
7845 have lots of capacity but haven't noticed it yet.
7846 - New experimental script tor/contrib/PathDemo.py (needs more work)
7847 that uses the controller interface to let you choose whole paths
7849 "<hostname>.<path,separated by dots>.<length of path>.path"
7850 - When we've connected to an OR and handshaked but didn't like
7851 the result, we were closing the conn without sending destroy
7852 cells back for pending circuits. Now send those destroys.
7855 Changes in version 0.0.9.7 - 2005-04-01
7856 o Bugfixes on 0.0.9.x:
7857 - Fix another race crash bug (thanks to Glenn Fink for reporting).
7858 - Compare identity to identity, not to nickname, when extending to
7859 a router not already in the directory. This was preventing us from
7860 extending to unknown routers. Oops.
7861 - Make sure to create OS X Tor user in <500 range, so we aren't
7862 creating actual system users.
7863 - Note where connection-that-hasn't-sent-end was marked, and fix
7864 a few really loud instances of this harmless bug (it's fixed more
7868 Changes in version 0.1.0.1-rc - 2005-03-28
7870 - Add reachability testing. Your Tor server will automatically try
7871 to see if its ORPort and DirPort are reachable from the outside,
7872 and it won't upload its descriptor until it decides they are.
7873 - Handle unavailable hidden services better. Handle slow or busy
7874 hidden services better.
7875 - Add support for CONNECTing through https proxies, with "HttpsProxy"
7877 - New exit policy: accept most low-numbered ports, rather than
7878 rejecting most low-numbered ports.
7879 - More Tor controller support (still experimental). See
7880 http://tor.eff.org/doc/control-spec.txt for all the new features,
7881 including signals to emulate unix signals from any platform;
7882 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
7883 closestream; closecircuit; etc.
7884 - Make nt services work and start on startup on win32 (based on
7885 patch by Matt Edman).
7886 - Add a new AddressMap config directive to rewrite incoming socks
7887 addresses. This lets you, for example, declare an implicit
7888 required exit node for certain sites.
7889 - Add a new TrackHostExits config directive to trigger addressmaps
7890 for certain incoming socks addresses -- for sites that break when
7891 your exit keeps changing (based on patch by Mike Perry).
7892 - Redo the client-side dns cache so it's just an addressmap too.
7893 - Notice when our IP changes, and reset stats/uptime/reachability.
7894 - When an application is using socks5, give him the whole variety of
7895 potential socks5 responses (connect refused, host unreachable, etc),
7896 rather than just "success" or "failure".
7897 - A more sane version numbering system. See
7898 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
7899 - New contributed script "exitlist": a simple python script to
7900 parse directories and find Tor nodes that exit to listed
7902 - New contributed script "privoxy-tor-toggle" to toggle whether
7903 Privoxy uses Tor. Seems to be configured for Debian by default.
7904 - Report HTTP reasons to client when getting a response from directory
7905 servers -- so you can actually know what went wrong.
7906 - New config option MaxAdvertisedBandwidth which lets you advertise
7907 a low bandwidthrate (to not attract as many circuits) while still
7908 allowing a higher bandwidthrate in reality.
7910 o Robustness/stability fixes:
7911 - Make Tor use Niels Provos's libevent instead of its current
7912 poll-but-sometimes-select mess. This will let us use faster async
7913 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
7915 - pthread support now too. This was forced because when we forked,
7916 we ended up wasting a lot of duplicate ram over time. Also switch
7917 to foo_r versions of some library calls to allow reentry and
7919 - Better handling for heterogeneous / unreliable nodes:
7920 - Annotate circuits w/ whether they aim to contain high uptime nodes
7921 and/or high capacity nodes. When building circuits, choose
7923 - This means that every single node in an intro rend circuit,
7924 not just the last one, will have a minimum uptime.
7925 - New config option LongLivedPorts to indicate application streams
7926 that will want high uptime circuits.
7927 - Servers reset uptime when a dir fetch entirely fails. This
7928 hopefully reflects stability of the server's network connectivity.
7929 - If somebody starts his tor server in Jan 2004 and then fixes his
7930 clock, don't make his published uptime be a year.
7931 - Reset published uptime when you wake up from hibernation.
7932 - Introduce a notion of 'internal' circs, which are chosen without
7933 regard to the exit policy of the last hop. Intro and rendezvous
7934 circs must be internal circs, to avoid leaking information. Resolve
7935 and connect streams can use internal circs if they want.
7936 - New circuit pooling algorithm: make sure to have enough circs around
7937 to satisfy any predicted ports, and also make sure to have 2 internal
7938 circs around if we've required internal circs lately (and with high
7939 uptime if we've seen that lately too).
7940 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
7941 which describes how often we retry making new circuits if current
7942 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
7943 how long we're willing to make use of an already-dirty circuit.
7944 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
7945 circ as necessary, if there are any completed ones lying around
7946 when we try to launch one.
7947 - Make hidden services try to establish a rendezvous for 30 seconds,
7948 rather than for n (where n=3) attempts to build a circuit.
7949 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
7950 "ShutdownWaitLength".
7951 - Try to be more zealous about calling connection_edge_end when
7952 things go bad with edge conns in connection.c.
7953 - Revise tor-spec to add more/better stream end reasons.
7954 - Revise all calls to connection_edge_end to avoid sending "misc",
7955 and to take errno into account where possible.
7958 - Fix a race condition that can trigger an assert, when we have a
7959 pending create cell and an OR connection fails right then.
7960 - Fix several double-mark-for-close bugs, e.g. where we were finding
7961 a conn for a cell even if that conn is already marked for close.
7962 - Make sequence of log messages when starting on win32 with no config
7963 file more reasonable.
7964 - When choosing an exit node for a new non-internal circ, don't take
7965 into account whether it'll be useful for any pending x.onion
7966 addresses -- it won't.
7967 - Turn addr_policy_compare from a tristate to a quadstate; this should
7968 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
7969 for google.com" problem.
7970 - Make "platform" string in descriptor more accurate for Win32 servers,
7971 so it's not just "unknown platform".
7972 - Fix an edge case in parsing config options (thanks weasel).
7973 If they say "--" on the commandline, it's not an option.
7974 - Reject odd-looking addresses at the client (e.g. addresses that
7975 contain a colon), rather than having the server drop them because
7977 - tor-resolve requests were ignoring .exit if there was a working circuit
7978 they could use instead.
7979 - REUSEADDR on normal platforms means you can rebind to the port
7980 right after somebody else has let it go. But REUSEADDR on win32
7981 means to let you bind to the port _even when somebody else
7982 already has it bound_! So, don't do that on Win32.
7983 - Change version parsing logic: a version is "obsolete" if it is not
7984 recommended and (1) there is a newer recommended version in the
7985 same series, or (2) there are no recommended versions in the same
7986 series, but there are some recommended versions in a newer series.
7987 A version is "new" if it is newer than any recommended version in
7989 - Stop most cases of hanging up on a socks connection without sending
7993 - Require BandwidthRate to be at least 20kB/s for servers.
7994 - When a dirserver causes you to give a warn, mention which dirserver
7996 - New config option DirAllowPrivateAddresses for authdirservers.
7997 Now by default they refuse router descriptors that have non-IP or
7998 private-IP addresses.
7999 - Stop publishing socksport in the directory, since it's not
8000 actually meant to be public. For compatibility, publish a 0 there
8002 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
8003 smart" value, that is low for servers and high for clients.
8004 - If our clock jumps forward by 100 seconds or more, assume something
8005 has gone wrong with our network and abandon all not-yet-used circs.
8006 - Warn when exit policy implicitly allows local addresses.
8007 - If we get an incredibly skewed timestamp from a dirserver mirror
8008 that isn't a verified OR, don't warn -- it's probably him that's
8010 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
8011 cookies to disk and doesn't log each web request to disk. (Thanks
8012 to Brett Carrington for pointing this out.)
8013 - When a client asks us for a dir mirror and we don't have one,
8014 launch an attempt to get a fresh one.
8015 - If we're hibernating and we get a SIGINT, exit immediately.
8016 - Add --with-dmalloc ./configure option, to track memory leaks.
8017 - And try to free all memory on closing, so we can detect what
8019 - Cache local dns resolves correctly even when they're .exit
8021 - Give a better warning when some other server advertises an
8022 ORPort that is actually an apache running ssl.
8023 - Add "opt hibernating 1" to server descriptor to make it clearer
8024 whether the server is hibernating.
8027 Changes in version 0.0.9.6 - 2005-03-24
8028 o Bugfixes on 0.0.9.x (crashes and asserts):
8029 - Add new end stream reasons to maintainance branch. Fix bug where
8030 reason (8) could trigger an assert. Prevent bug from recurring.
8031 - Apparently win32 stat wants paths to not end with a slash.
8032 - Fix assert triggers in assert_cpath_layer_ok(), where we were
8033 blowing away the circuit that conn->cpath_layer points to, then
8034 checking to see if the circ is well-formed. Backport check to make
8035 sure we dont use the cpath on a closed connection.
8036 - Prevent circuit_resume_edge_reading_helper() from trying to package
8037 inbufs for marked-for-close streams.
8038 - Don't crash on hup if your options->address has become unresolvable.
8039 - Some systems (like OS X) sometimes accept() a connection and tell
8040 you the remote host is 0.0.0.0:0. If this happens, due to some
8041 other mis-features, we get confused; so refuse the conn for now.
8043 o Bugfixes on 0.0.9.x (other):
8044 - Fix harmless but scary "Unrecognized content encoding" warn message.
8045 - Add new stream error reason: TORPROTOCOL reason means "you are not
8046 speaking a version of Tor I understand; say bye-bye to your stream."
8047 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
8048 into the future, now that we are more tolerant of skew. This
8049 resolves a bug where a Tor server would refuse to cache a directory
8050 because all the directories it gets are too far in the future;
8051 yet the Tor server never logs any complaints about clock skew.
8052 - Mac packaging magic: make man pages useable, and do not overwrite
8053 existing torrc files.
8054 - Make OS X log happily to /var/log/tor/tor.log
8057 Changes in version 0.0.9.5 - 2005-02-22
8058 o Bugfixes on 0.0.9.x:
8059 - Fix an assert race at exit nodes when resolve requests fail.
8060 - Stop picking unverified dir mirrors--it only leads to misery.
8061 - Patch from Matt Edman to make NT services work better. Service
8062 support is still not compiled into the executable by default.
8063 - Patch from Dmitri Bely so the Tor service runs better under
8064 the win32 SYSTEM account.
8065 - Make tor-resolve actually work (?) on Win32.
8066 - Fix a sign bug when getrlimit claims to have 4+ billion
8067 file descriptors available.
8068 - Stop refusing to start when bandwidthburst == bandwidthrate.
8069 - When create cells have been on the onion queue more than five
8070 seconds, just send back a destroy and take them off the list.
8073 Changes in version 0.0.9.4 - 2005-02-03
8074 o Bugfixes on 0.0.9:
8075 - Fix an assert bug that took down most of our servers: when
8076 a server claims to have 1 GB of bandwidthburst, don't
8078 - Don't crash as badly if we have spawned the max allowed number
8079 of dnsworkers, or we're out of file descriptors.
8080 - Block more file-sharing ports in the default exit policy.
8081 - MaxConn is now automatically set to the hard limit of max
8082 file descriptors we're allowed (ulimit -n), minus a few for
8084 - Give a clearer message when servers need to raise their
8085 ulimit -n when they start running out of file descriptors.
8086 - SGI Compatibility patches from Jan Schaumann.
8087 - Tolerate a corrupt cached directory better.
8088 - When a dirserver hasn't approved your server, list which one.
8089 - Go into soft hibernation after 95% of the bandwidth is used,
8090 not 99%. This is especially important for daily hibernators who
8091 have a small accounting max. Hopefully it will result in fewer
8092 cut connections when the hard hibernation starts.
8093 - Load-balance better when using servers that claim more than
8094 800kB/s of capacity.
8095 - Make NT services work (experimental, only used if compiled in).
8098 Changes in version 0.0.9.3 - 2005-01-21
8099 o Bugfixes on 0.0.9:
8100 - Backport the cpu use fixes from main branch, so busy servers won't
8101 need as much processor time.
8102 - Work better when we go offline and then come back, or when we
8103 run Tor at boot before the network is up. We do this by
8104 optimistically trying to fetch a new directory whenever an
8105 application request comes in and we think we're offline -- the
8106 human is hopefully a good measure of when the network is back.
8107 - Backport some minimal hidserv bugfixes: keep rend circuits open as
8108 long as you keep using them; actually publish hidserv descriptors
8109 shortly after they change, rather than waiting 20-40 minutes.
8110 - Enable Mac startup script by default.
8111 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
8112 - When you update AllowUnverifiedNodes or FirewallPorts via the
8113 controller's setconf feature, we were always appending, never
8115 - When you update HiddenServiceDir via setconf, it was screwing up
8116 the order of reading the lines, making it fail.
8117 - Do not rewrite a cached directory back to the cache; otherwise we
8118 will think it is recent and not fetch a newer one on startup.
8119 - Workaround for webservers that lie about Content-Encoding: Tor
8120 now tries to autodetect compressed directories and compression
8121 itself. This lets us Proxypass dir fetches through apache.
8124 Changes in version 0.0.9.2 - 2005-01-04
8125 o Bugfixes on 0.0.9 (crashes and asserts):
8126 - Fix an assert on startup when the disk is full and you're logging
8128 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
8129 style address, then we'd crash.
8130 - Fix an assert trigger when the running-routers string we get from
8131 a dirserver is broken.
8132 - Make worker threads start and run on win32. Now win32 servers
8134 - Bandaid (not actually fix, but now it doesn't crash) an assert
8135 where the dns worker dies mysteriously and the main Tor process
8136 doesn't remember anything about the address it was resolving.
8138 o Bugfixes on 0.0.9 (Win32):
8139 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
8140 name out of the warning/assert messages.
8141 - Fix a superficial "unhandled error on read" bug on win32.
8142 - The win32 installer no longer requires a click-through for our
8143 license, since our Free Software license grants rights but does not
8145 - Win32: When connecting to a dirserver fails, try another one
8146 immediately. (This was already working for non-win32 Tors.)
8147 - Stop trying to parse $HOME on win32 when hunting for default
8149 - Make tor-resolve.c work on win32 by calling network_init().
8151 o Bugfixes on 0.0.9 (other):
8152 - Make 0.0.9.x build on Solaris again.
8153 - Due to a fencepost error, we were blowing away the \n when reporting
8154 confvalue items in the controller. So asking for multiple config
8155 values at once couldn't work.
8156 - When listing circuits that are pending on an opening OR connection,
8157 if we're an OR we were listing circuits that *end* at us as
8158 being pending on every listener, dns/cpu worker, etc. Stop that.
8159 - Dirservers were failing to create 'running-routers' or 'directory'
8160 strings if we had more than some threshold of routers. Fix them so
8161 they can handle any number of routers.
8162 - Fix a superficial "Duplicate mark for close" bug.
8163 - Stop checking for clock skew for OR connections, even for servers.
8164 - Fix a fencepost error that was chopping off the last letter of any
8165 nickname that is the maximum allowed nickname length.
8166 - Update URLs in log messages so they point to the new website.
8167 - Fix a potential problem in mangling server private keys while
8168 writing to disk (not triggered yet, as far as we know).
8169 - Include the licenses for other free software we include in Tor,
8170 now that we're shipping binary distributions more regularly.
8173 Changes in version 0.0.9.1 - 2004-12-15
8174 o Bugfixes on 0.0.9:
8175 - Make hibernation actually work.
8176 - Make HashedControlPassword config option work.
8177 - When we're reporting event circuit status to a controller,
8178 don't use the stream status code.
8181 Changes in version 0.0.9 - 2004-12-12
8183 - Clean up manpage and torrc.sample file.
8184 - Clean up severities and text of log warnings.
8186 - Make servers trigger an assert when they enter hibernation.
8189 Changes in version 0.0.9rc7 - 2004-12-08
8190 o Bugfixes on 0.0.9rc:
8191 - Fix a stack-trashing crash when an exit node begins hibernating.
8192 - Avoid looking at unallocated memory while considering which
8193 ports we need to build circuits to cover.
8194 - Stop a sigpipe: when an 'end' cell races with eof from the app,
8195 we shouldn't hold-open-until-flush if the eof arrived first.
8196 - Fix a bug with init_cookie_authentication() in the controller.
8197 - When recommending new-format log lines, if the upper bound is
8198 LOG_ERR, leave it implicit.
8200 o Bugfixes on 0.0.8.1:
8201 - Fix a whole slew of memory leaks.
8202 - Fix isspace() and friends so they still make Solaris happy
8203 but also so they don't trigger asserts on win32.
8204 - Fix parse_iso_time on platforms without strptime (eg win32).
8205 - win32: tolerate extra "readable" events better.
8206 - win32: when being multithreaded, leave parent fdarray open.
8207 - Make unit tests work on win32.
8210 Changes in version 0.0.9rc6 - 2004-12-06
8211 o Bugfixes on 0.0.9pre:
8212 - Clean up some more integer underflow opportunities (not exploitable
8214 - While hibernating, hup should not regrow our listeners.
8215 - Send an end to the streams we close when we hibernate, rather
8216 than just chopping them off.
8217 - React to eof immediately on non-open edge connections.
8219 o Bugfixes on 0.0.8.1:
8220 - Calculate timeout for waiting for a connected cell from the time
8221 we sent the begin cell, not from the time the stream started. If
8222 it took a long time to establish the circuit, we would time out
8223 right after sending the begin cell.
8224 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8225 of * as always matching, so we were picking reject *:* nodes as
8226 exit nodes too. Oops.
8229 - New circuit building strategy: keep a list of ports that we've
8230 used in the past 6 hours, and always try to have 2 circuits open
8231 or on the way that will handle each such port. Seed us with port
8232 80 so web users won't complain that Tor is "slow to start up".
8233 - Make kill -USR1 dump more useful stats about circuits.
8234 - When warning about retrying or giving up, print the address, so
8235 the user knows which one it's talking about.
8236 - If you haven't used a clean circuit in an hour, throw it away,
8237 just to be on the safe side. (This means after 6 hours a totally
8238 unused Tor client will have no circuits open.)
8241 Changes in version 0.0.9rc5 - 2004-12-01
8242 o Bugfixes on 0.0.8.1:
8243 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8244 - Let resolve conns retry/expire also, rather than sticking around
8246 - If we are using select, make sure we stay within FD_SETSIZE.
8248 o Bugfixes on 0.0.9pre:
8249 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
8250 but doesn't seem to be currently; thanks to Ilja van Sprundel for
8252 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
8253 instead. Impose minima and maxima for all *Period options; impose
8254 even tighter maxima for fetching if we are a caching dirserver.
8255 Clip rather than rejecting.
8256 - Fetch cached running-routers from servers that serve it (that is,
8257 authdirservers and servers running 0.0.9rc5-cvs or later.)
8260 - Accept *:706 (silc) in default exit policy.
8261 - Implement new versioning format for post 0.1.
8262 - Support "foo.nickname.exit" addresses, to let Alice request the
8263 address "foo" as viewed by exit node "nickname". Based on a patch
8265 - Make tor --version --version dump the cvs Id of every file.
8268 Changes in version 0.0.9rc4 - 2004-11-28
8269 o Bugfixes on 0.0.8.1:
8270 - Make windows sockets actually non-blocking (oops), and handle
8271 win32 socket errors better.
8273 o Bugfixes on 0.0.9rc1:
8274 - Actually catch the -USR2 signal.
8277 Changes in version 0.0.9rc3 - 2004-11-25
8278 o Bugfixes on 0.0.8.1:
8279 - Flush the log file descriptor after we print "Tor opening log file",
8280 so we don't see those messages days later.
8282 o Bugfixes on 0.0.9rc1:
8283 - Make tor-resolve work again.
8284 - Avoid infinite loop in tor-resolve if tor hangs up on it.
8285 - Fix an assert trigger for clients/servers handling resolves.
8288 Changes in version 0.0.9rc2 - 2004-11-24
8289 o Bugfixes on 0.0.9rc1:
8290 - I broke socks5 support while fixing the eof bug.
8291 - Allow unitless bandwidths and intervals; they default to bytes
8293 - New servers don't start out hibernating; they are active until
8294 they run out of bytes, so they have a better estimate of how
8295 long it takes, and so their operators can know they're working.
8298 Changes in version 0.0.9rc1 - 2004-11-23
8299 o Bugfixes on 0.0.8.1:
8300 - Finally fix a bug that's been plaguing us for a year:
8301 With high load, circuit package window was reaching 0. Whenever
8302 we got a circuit-level sendme, we were reading a lot on each
8303 socket, but only writing out a bit. So we would eventually reach
8304 eof. This would be noticed and acted on even when there were still
8305 bytes sitting in the inbuf.
8306 - When poll() is interrupted, we shouldn't believe the revents values.
8308 o Bugfixes on 0.0.9pre6:
8309 - Fix hibernate bug that caused pre6 to be broken.
8310 - Don't keep rephist info for routers that haven't had activity for
8311 24 hours. (This matters now that clients have keys, since we track
8313 - Never call close_temp_logs while validating log options.
8314 - Fix backslash-escaping on tor.sh.in and torctl.in.
8317 - Implement weekly/monthly/daily accounting: now you specify your
8318 hibernation properties by
8319 AccountingMax N bytes|KB|MB|GB|TB
8320 AccountingStart day|week|month [day] HH:MM
8321 Defaults to "month 1 0:00".
8322 - Let bandwidth and interval config options be specified as 5 bytes,
8323 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8324 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8325 get back to normal.)
8326 - If your requested entry or exit node has advertised bandwidth 0,
8328 - Be more greedy about filling up relay cells -- we try reading again
8329 once we've processed the stuff we read, in case enough has arrived
8330 to fill the last cell completely.
8331 - Apply NT service patch from Osamu Fujino. Still needs more work.
8334 Changes in version 0.0.9pre6 - 2004-11-15
8335 o Bugfixes on 0.0.8.1:
8336 - Fix assert failure on malformed socks4a requests.
8337 - Use identity comparison, not nickname comparison, to choose which
8338 half of circuit-ID-space each side gets to use. This is needed
8339 because sometimes we think of a router as a nickname, and sometimes
8340 as a hex ID, and we can't predict what the other side will do.
8341 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8342 write() call will fail and we handle it there.
8343 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8344 and smartlist_len, which are two major profiling offenders.
8346 o Bugfixes on 0.0.9pre5:
8347 - Fix a bug in read_all that was corrupting config files on windows.
8348 - When we're raising the max number of open file descriptors to
8349 'unlimited', don't log that we just raised it to '-1'.
8350 - Include event code with events, as required by control-spec.txt.
8351 - Don't give a fingerprint when clients do --list-fingerprint:
8352 it's misleading, because it will never be the same again.
8353 - Stop using strlcpy in tor_strndup, since it was slowing us
8355 - Remove warn on startup about missing cached-directory file.
8356 - Make kill -USR1 work again.
8357 - Hibernate if we start tor during the "wait for wakeup-time" phase
8358 of an accounting interval. Log our hibernation plans better.
8359 - Authoritative dirservers now also cache their directory, so they
8360 have it on start-up.
8363 - Fetch running-routers; cache running-routers; compress
8364 running-routers; serve compressed running-routers.z
8365 - Add NSI installer script contributed by J Doe.
8366 - Commit VC6 and VC7 workspace/project files.
8367 - Commit a tor.spec for making RPM files, with help from jbash.
8368 - Add contrib/torctl.in contributed by Glenn Fink.
8369 - Implement the control-spec's SAVECONF command, to write your
8370 configuration to torrc.
8371 - Get cookie authentication for the controller closer to working.
8372 - Include control-spec.txt in the tarball.
8373 - When set_conf changes our server descriptor, upload a new copy.
8374 But don't upload it too often if there are frequent changes.
8375 - Document authentication config in man page, and document signals
8377 - Clean up confusing parts of man page and torrc.sample.
8378 - Make expand_filename handle ~ and ~username.
8379 - Use autoconf to enable largefile support where necessary. Use
8380 ftello where available, since ftell can fail at 2GB.
8381 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8382 log more informatively.
8383 - Give a slightly more useful output for "tor -h".
8384 - Refuse application socks connections to port 0.
8385 - Check clock skew for verified servers, but allow unverified
8386 servers and clients to have any clock skew.
8387 - Break DirFetchPostPeriod into:
8388 - DirFetchPeriod for fetching full directory,
8389 - StatusFetchPeriod for fetching running-routers,
8390 - DirPostPeriod for posting server descriptor,
8391 - RendPostPeriod for posting hidden service descriptors.
8392 - Make sure the hidden service descriptors are at a random offset
8393 from each other, to hinder linkability.
8396 Changes in version 0.0.9pre5 - 2004-11-09
8397 o Bugfixes on 0.0.9pre4:
8398 - Fix a seg fault in unit tests (doesn't affect main program).
8399 - Fix an assert bug where a hidden service provider would fail if
8400 the first hop of his rendezvous circuit was down.
8401 - Hidden service operators now correctly handle version 1 style
8402 INTRODUCE1 cells (nobody generates them still, so not a critical
8404 - If do_hup fails, actually notice.
8405 - Handle more errnos from accept() without closing the listener.
8406 Some OpenBSD machines were closing their listeners because
8407 they ran out of file descriptors.
8408 - Send resolve cells to exit routers that are running a new
8409 enough version of the resolve code to work right.
8410 - Better handling of winsock includes on non-MSV win32 compilers.
8411 - Some people had wrapped their tor client/server in a script
8412 that would restart it whenever it died. This did not play well
8413 with our "shut down if your version is obsolete" code. Now people
8414 don't fetch a new directory if their local cached version is
8416 - Make our autogen.sh work on ksh as well as bash.
8419 - Hibernation: New config option "AccountingMaxKB" lets you
8420 set how many KBytes per month you want to allow your server to
8421 consume. Rather than spreading those bytes out evenly over the
8422 month, we instead hibernate for some of the month and pop up
8423 at a deterministic time, work until the bytes are consumed, then
8424 hibernate again. Config option "MonthlyAccountingStart" lets you
8425 specify which day of the month your billing cycle starts on.
8426 - Control interface: a separate program can now talk to your
8427 client/server over a socket, and get/set config options, receive
8428 notifications of circuits and streams starting/finishing/dying,
8429 bandwidth used, etc. The next step is to get some GUIs working.
8430 Let us know if you want to help out. See doc/control-spec.txt .
8431 - Ship a contrib/tor-control.py as an example script to interact
8432 with the control port.
8433 - "tor --hash-password zzyxz" will output a salted password for
8434 use in authenticating to the control interface.
8435 - New log format in config:
8436 "Log minsev[-maxsev] stdout|stderr|syslog" or
8437 "Log minsev[-maxsev] file /var/foo"
8440 - DirPolicy config option, to let people reject incoming addresses
8441 from their dirserver.
8442 - "tor --list-fingerprint" will list your identity key fingerprint
8444 - Add "pass" target for RedirectExit, to make it easier to break
8445 out of a sequence of RedirectExit rules.
8446 - Clients now generate a TLS cert too, in preparation for having
8447 them act more like real nodes.
8448 - Ship src/win32/ in the tarball, so people can use it to build.
8449 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8451 - New "router-status" line in directory, to better bind each verified
8452 nickname to its identity key.
8453 - Deprecate unofficial config option abbreviations, and abbreviations
8454 not on the command line.
8455 - Add a pure-C tor-resolve implementation.
8456 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8457 1024) file descriptors.
8459 o Code security improvements, inspired by Ilja:
8460 - Replace sprintf with snprintf. (I think they were all safe, but
8462 - Replace strcpy/strncpy with strlcpy in more places.
8463 - Avoid strcat; use snprintf or strlcat instead.
8464 - snprintf wrapper with consistent (though not C99) overflow behavior.
8467 Changes in version 0.0.9pre4 - 2004-10-17
8468 o Bugfixes on 0.0.9pre3:
8469 - If the server doesn't specify an exit policy, use the real default
8470 exit policy, not reject *:*.
8471 - Ignore fascistfirewall when uploading/downloading hidden service
8472 descriptors, since we go through Tor for those; and when using
8473 an HttpProxy, since we assume it can reach them all.
8474 - When looking for an authoritative dirserver, use only the ones
8475 configured at boot. Don't bother looking in the directory.
8476 - The rest of the fix for get_default_conf_file() on older win32.
8477 - Make 'Routerfile' config option obsolete.
8480 - New 'MyFamily nick1,...' config option for a server to
8481 specify other servers that shouldn't be used in the same circuit
8482 with it. Only believed if nick1 also specifies us.
8483 - New 'NodeFamily nick1,nick2,...' config option for a client to
8484 specify nodes that it doesn't want to use in the same circuit.
8485 - New 'Redirectexit pattern address:port' config option for a
8486 server to redirect exit connections, e.g. to a local squid.
8489 Changes in version 0.0.9pre3 - 2004-10-13
8490 o Bugfixes on 0.0.8.1:
8491 - Better torrc example lines for dirbindaddress and orbindaddress.
8492 - Improved bounds checking on parsed ints (e.g. config options and
8493 the ones we find in directories.)
8494 - Better handling of size_t vs int, so we're more robust on 64
8496 - Fix the rest of the bug where a newly started OR would appear
8497 as unverified even after we've added his fingerprint and hupped
8499 - Fix a bug from 0.0.7: when read() failed on a stream, we would
8500 close it without sending back an end. So 'connection refused'
8501 would simply be ignored and the user would get no response.
8503 o Bugfixes on 0.0.9pre2:
8504 - Serving the cached-on-disk directory to people is bad. We now
8505 provide no directory until we've fetched a fresh one.
8506 - Workaround for bug on windows where cached-directories get crlf
8508 - Make get_default_conf_file() work on older windows too.
8509 - If we write a *:* exit policy line in the descriptor, don't write
8510 any more exit policy lines.
8513 - Use only 0.0.9pre1 and later servers for resolve cells.
8514 - Make the dirservers file obsolete.
8515 - Include a dir-signing-key token in directories to tell the
8516 parsing entity which key is being used to sign.
8517 - Remove the built-in bulky default dirservers string.
8518 - New config option "Dirserver %s:%d [fingerprint]", which can be
8519 repeated as many times as needed. If no dirservers specified,
8520 default to moria1,moria2,tor26.
8521 - Make moria2 advertise a dirport of 80, so people behind firewalls
8522 will be able to get a directory.
8523 - Http proxy support
8524 - Dirservers translate requests for http://%s:%d/x to /x
8525 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8526 be routed through this host.
8527 - Clients ask for /tor/x rather than /x for new enough dirservers.
8528 This way we can one day coexist peacefully with apache.
8529 - Clients specify a "Host: %s%d" http header, to be compatible
8530 with more proxies, and so running squid on an exit node can work.
8533 Changes in version 0.0.8.1 - 2004-10-13
8535 - Fix a seg fault that can be triggered remotely for Tor
8536 clients/servers with an open dirport.
8537 - Fix a rare assert trigger, where routerinfos for entries in
8538 our cpath would expire while we're building the path.
8539 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8540 - Fix a rare seg fault for people running hidden services on
8541 intermittent connections.
8542 - Fix a bug in parsing opt keywords with objects.
8543 - Fix a stale pointer assert bug when a stream detaches and
8545 - Fix a string format vulnerability (probably not exploitable)
8546 in reporting stats locally.
8547 - Fix an assert trigger: sometimes launching circuits can fail
8548 immediately, e.g. because too many circuits have failed recently.
8549 - Fix a compile warning on 64 bit platforms.
8552 Changes in version 0.0.9pre2 - 2004-10-03
8554 - Make fetching a cached directory work for 64-bit platforms too.
8555 - Make zlib.h a required header, not an optional header.
8558 Changes in version 0.0.9pre1 - 2004-10-01
8560 - Stop using separate defaults for no-config-file and
8561 empty-config-file. Now you have to explicitly turn off SocksPort,
8562 if you don't want it open.
8563 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8564 - Improve man page to mention more of the 0.0.8 features.
8565 - Fix a rare seg fault for people running hidden services on
8566 intermittent connections.
8567 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8569 - Fix more dns related bugs: send back resolve_failed and end cells
8570 more reliably when the resolve fails, rather than closing the
8571 circuit and then trying to send the cell. Also attach dummy resolve
8572 connections to a circuit *before* calling dns_resolve(), to fix
8573 a bug where cached answers would never be sent in RESOLVED cells.
8574 - When we run out of disk space, or other log writing error, don't
8575 crash. Just stop logging to that log and continue.
8576 - We were starting to daemonize before we opened our logs, so if
8577 there were any problems opening logs, we would complain to stderr,
8578 which wouldn't work, and then mysteriously exit.
8579 - Fix a rare bug where sometimes a verified OR would connect to us
8580 before he'd uploaded his descriptor, which would cause us to
8581 assign conn->nickname as though he's unverified. Now we look through
8582 the fingerprint list to see if he's there.
8583 - Fix a rare assert trigger, where routerinfos for entries in
8584 our cpath would expire while we're building the path.
8587 - Clients can ask dirservers for /dir.z to get a compressed version
8588 of the directory. Only works for servers running 0.0.9, of course.
8589 - Make clients cache directories and use them to seed their router
8590 lists at startup. This means clients have a datadir again.
8591 - Configuration infrastructure support for warning on obsolete
8593 - Respond to content-encoding headers by trying to uncompress as
8595 - Reply with a deflated directory when a client asks for "dir.z".
8596 We could use allow-encodings instead, but allow-encodings isn't
8597 specified in HTTP 1.0.
8598 - Raise the max dns workers from 50 to 100.
8599 - Discourage people from setting their dirfetchpostperiod more often
8600 than once per minute.
8601 - Protect dirservers from overzealous descriptor uploading -- wait
8602 10 seconds after directory gets dirty, before regenerating.
8605 Changes in version 0.0.8 - 2004-08-25
8606 o Port it to SunOS 5.9 / Athena
8609 Changes in version 0.0.8rc2 - 2004-08-20
8610 o Make it compile on cygwin again.
8611 o When picking unverified routers, skip those with low uptime and/or
8612 low bandwidth, depending on what properties you care about.
8615 Changes in version 0.0.8rc1 - 2004-08-18
8616 o Changes from 0.0.7.3:
8618 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8619 don't put it into the client dns cache.
8620 - If a begin failed due to exit policy, but we believe the IP address
8621 should have been allowed, switch that router to exitpolicy reject *:*
8622 until we get our next directory.
8624 - Clients choose nodes proportional to advertised bandwidth.
8625 - Avoid using nodes with low uptime as introduction points.
8626 - Handle servers with dynamic IP addresses: don't replace
8627 options->Address with the resolved one at startup, and
8628 detect our address right before we make a routerinfo each time.
8629 - 'FascistFirewall' option to pick dirservers and ORs on specific
8630 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8631 which ports are open. (Defaults to 80,443)
8632 - Be more aggressive about trying to make circuits when the network
8633 has changed (e.g. when you unsuspend your laptop).
8634 - Check for time skew on http headers; report date in response to
8636 - If the entrynode config line has only one node, don't pick it as
8638 - Add strict{entry|exit}nodes config options. If set to 1, then
8639 we refuse to build circuits that don't include the specified entry
8641 - OutboundBindAddress config option, to bind to a specific
8642 IP address for outgoing connect()s.
8643 - End truncated log entries (e.g. directories) with "[truncated]".
8645 o Patches to 0.0.8preX:
8647 - Patches to compile and run on win32 again (maybe)?
8648 - Fix crash when looking for ~/.torrc with no $HOME set.
8649 - Fix a race bug in the unit tests.
8650 - Handle verified/unverified name collisions better when new
8651 routerinfo's arrive in a directory.
8652 - Sometimes routers were getting entered into the stats before
8653 we'd assigned their identity_digest. Oops.
8654 - Only pick and establish intro points after we've gotten a
8657 - AllowUnverifiedNodes config option to let circuits choose no-name
8658 routers in entry,middle,exit,introduction,rendezvous positions.
8659 Allow middle and rendezvous positions by default.
8660 - Add a man page for tor-resolve.
8663 Changes in version 0.0.7.3 - 2004-08-12
8664 o Stop dnsworkers from triggering an assert failure when you
8665 ask them to resolve the host "".
8668 Changes in version 0.0.8pre3 - 2004-08-09
8669 o Changes from 0.0.7.2:
8670 - Allow multiple ORs with same nickname in routerlist -- now when
8671 people give us one identity key for a nickname, then later
8672 another, we don't constantly complain until the first expires.
8673 - Remember used bandwidth (both in and out), and publish 15-minute
8674 snapshots for the past day into our descriptor.
8675 - You can now fetch $DIRURL/running-routers to get just the
8676 running-routers line, not the whole descriptor list. (But
8677 clients don't use this yet.)
8678 - When people mistakenly use Tor as an http proxy, point them
8679 at the tor-doc.html rather than the INSTALL.
8680 - Remove our mostly unused -- and broken -- hex_encode()
8681 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8682 for pointing out this bug.)
8683 - Rotate onion keys every 12 hours, not every 2 hours, so we have
8684 fewer problems with people using the wrong key.
8685 - Change the default exit policy to reject the default edonkey,
8686 kazaa, gnutella ports.
8687 - Add replace_file() to util.[ch] to handle win32's rename().
8689 o Changes from 0.0.8preX:
8690 - Fix two bugs in saving onion keys to disk when rotating, so
8691 hopefully we'll get fewer people using old onion keys.
8692 - Fix an assert error that was making SocksPolicy not work.
8693 - Be willing to expire routers that have an open dirport -- it's
8694 just the authoritative dirservers we want to not forget.
8695 - Reject tor-resolve requests for .onion addresses early, so we
8696 don't build a whole rendezvous circuit and then fail.
8697 - When you're warning a server that he's unverified, don't cry
8699 - Fix a race condition: don't try to extend onto a connection
8700 that's still handshaking.
8701 - For servers in clique mode, require the conn to be open before
8702 you'll choose it for your path.
8703 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
8704 end relay cell, etc.
8705 - Measure bandwidth capacity over the last 24 hours, not just 12
8706 - Bugfix: authoritative dirservers were making and signing a new
8707 directory for each client, rather than reusing the cached one.
8710 Changes in version 0.0.8pre2 - 2004-08-04
8711 o Changes from 0.0.7.2:
8713 - Check directory signature _before_ you decide whether you're
8714 you're running an obsolete version and should exit.
8715 - Check directory signature _before_ you parse the running-routers
8716 list to decide who's running or verified.
8717 - Bugfixes and features:
8718 - Check return value of fclose while writing to disk, so we don't
8719 end up with broken files when servers run out of disk space.
8720 - Log a warning if the user uses an unsafe socks variant, so people
8721 are more likely to learn about privoxy or socat.
8722 - Dirservers now include RFC1123-style dates in the HTTP headers,
8723 which one day we will use to better detect clock skew.
8725 o Changes from 0.0.8pre1:
8726 - Make it compile without warnings again on win32.
8727 - Log a warning if you're running an unverified server, to let you
8728 know you might want to get it verified.
8729 - Only pick a default nickname if you plan to be a server.
8732 Changes in version 0.0.8pre1 - 2004-07-23
8734 - Made our unit tests compile again on OpenBSD 3.5, and tor
8735 itself compile again on OpenBSD on a sparc64.
8736 - We were neglecting milliseconds when logging on win32, so
8737 everything appeared to happen at the beginning of each second.
8740 - 'Extend' relay cell payloads now include the digest of the
8741 intended next hop's identity key. Now we can verify that we're
8742 extending to the right router, and also extend to routers we
8743 hadn't heard of before.
8746 - Tor nodes can now act as relays (with an advertised ORPort)
8747 without being manually verified by the dirserver operators.
8748 - Uploaded descriptors of unverified routers are now accepted
8749 by the dirservers, and included in the directory.
8750 - Verified routers are listed by nickname in the running-routers
8751 list; unverified routers are listed as "$<fingerprint>".
8752 - We now use hash-of-identity-key in most places rather than
8753 nickname or addr:port, for improved security/flexibility.
8754 - To avoid Sybil attacks, paths still use only verified servers.
8755 But now we have a chance to play around with hybrid approaches.
8756 - Nodes track bandwidth usage to estimate capacity (not used yet).
8757 - ClientOnly option for nodes that never want to become servers.
8758 - Directory caching.
8759 - "AuthoritativeDir 1" option for the official dirservers.
8760 - Now other nodes (clients and servers) will cache the latest
8761 directory they've pulled down.
8762 - They can enable their DirPort to serve it to others.
8763 - Clients will pull down a directory from any node with an open
8764 DirPort, and check the signature/timestamp correctly.
8765 - Authoritative dirservers now fetch directories from other
8766 authdirservers, to stay better synced.
8767 - Running-routers list tells who's down also, along with noting
8768 if they're verified (listed by nickname) or unverified (listed
8770 - Allow dirservers to serve running-router list separately.
8771 This isn't used yet.
8772 - ORs connect-on-demand to other ORs
8773 - If you get an extend cell to an OR you're not connected to,
8774 connect, handshake, and forward the create cell.
8775 - The authoritative dirservers stay connected to everybody,
8776 and everybody stays connected to 0.0.7 servers, but otherwise
8777 clients/servers expire unused connections after 5 minutes.
8778 - When servers get a sigint, they delay 30 seconds (refusing new
8779 connections) then exit. A second sigint causes immediate exit.
8780 - File and name management:
8781 - Look for .torrc if no CONFDIR "torrc" is found.
8782 - If no datadir is defined, then choose, make, and secure ~/.tor
8784 - If torrc not found, exitpolicy reject *:*.
8785 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
8786 - If no nickname is defined, derive default from hostname.
8787 - Rename secret key files, e.g. identity.key -> secret_id_key,
8788 to discourage people from mailing their identity key to tor-ops.
8789 - Refuse to build a circuit before the directory has arrived --
8790 it won't work anyway, since you won't know the right onion keys
8792 - Try other dirservers immediately if the one you try is down. This
8793 should tolerate down dirservers better now.
8794 - Parse tor version numbers so we can do an is-newer-than check
8795 rather than an is-in-the-list check.
8796 - New socks command 'resolve', to let us shim gethostbyname()
8798 - A 'tor_resolve' script to access the socks resolve functionality.
8799 - A new socks-extensions.txt doc file to describe our
8800 interpretation and extensions to the socks protocols.
8801 - Add a ContactInfo option, which gets published in descriptor.
8802 - Publish OR uptime in descriptor (and thus in directory) too.
8803 - Write tor version at the top of each log file
8804 - New docs in the tarball:
8806 - Document that you should proxy your SSL traffic too.
8809 Changes in version 0.0.7.2 - 2004-07-07
8810 o A better fix for the 0.0.0.0 problem, that will hopefully
8811 eliminate the remaining related assertion failures.
8814 Changes in version 0.0.7.1 - 2004-07-04
8815 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
8816 since internally we use 0.0.0.0 to signify "not yet resolved".
8819 Changes in version 0.0.7 - 2004-06-07
8820 o Updated the man page to reflect the new features.
8823 Changes in version 0.0.7rc2 - 2004-06-06
8824 o Changes from 0.0.7rc1:
8825 - Make it build on Win32 again.
8826 o Changes from 0.0.6.2:
8827 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
8831 Changes in version 0.0.7rc1 - 2004-06-02
8833 - On sighup, we were adding another log without removing the first
8834 one. So log messages would get duplicated n times for n sighups.
8835 - Several cases of using a connection after we'd freed it. The
8836 problem was that connections that are pending resolve are in both
8837 the pending_resolve tree, and also the circuit's resolving_streams
8838 list. When you want to remove one, you must remove it from both.
8839 - Fix a double-mark-for-close where an end cell arrived for a
8840 resolving stream, and then the resolve failed.
8841 - Check directory signatures based on name of signer, not on whom
8842 we got the directory from. This will let us cache directories more
8845 - Crank up some of our constants to handle more users.
8848 Changes in version 0.0.7pre1 - 2004-06-02
8849 o Fixes for crashes and other obnoxious bugs:
8850 - Fix an epipe bug: sometimes when directory connections failed
8851 to connect, we would give them a chance to flush before closing
8853 - When we detached from a circuit because of resolvefailed, we
8854 would immediately try the same circuit twice more, and then
8855 give up on the resolve thinking we'd tried three different
8857 - Limit the number of intro circuits we'll attempt to build for a
8858 hidden service per 15-minute period.
8859 - Check recommended-software string *early*, before actually parsing
8860 the directory. Thus we can detect an obsolete version and exit,
8861 even if the new directory format doesn't parse.
8862 o Fixes for security bugs:
8863 - Remember which nodes are dirservers when you startup, and if a
8864 random OR enables his dirport, don't automatically assume he's
8865 a trusted dirserver.
8867 - Directory connections were asking the wrong poll socket to
8868 start writing, and not asking themselves to start writing.
8869 - When we detached from a circuit because we sent a begin but
8870 didn't get a connected, we would use it again the first time;
8871 but after that we would correctly switch to a different one.
8872 - Stop warning when the first onion decrypt attempt fails; they
8873 will sometimes legitimately fail now that we rotate keys.
8874 - Override unaligned-access-ok check when $host_cpu is ia64 or
8875 arm. Apparently they allow it but the kernel whines.
8876 - Dirservers try to reconnect periodically too, in case connections
8878 - Fix some memory leaks in directory servers.
8879 - Allow backslash in Win32 filenames.
8880 - Made Tor build complain-free on FreeBSD, hopefully without
8881 breaking other BSD builds. We'll see.
8883 - Doxygen markup on all functions and global variables.
8884 - Make directory functions update routerlist, not replace it. So
8885 now directory disagreements are not so critical a problem.
8886 - Remove the upper limit on number of descriptors in a dirserver's
8887 directory (not that we were anywhere close).
8888 - Allow multiple logfiles at different severity ranges.
8889 - Allow *BindAddress to specify ":port" rather than setting *Port
8890 separately. Allow multiple instances of each BindAddress config
8891 option, so you can bind to multiple interfaces if you want.
8892 - Allow multiple exit policy lines, which are processed in order.
8893 Now we don't need that huge line with all the commas in it.
8894 - Enable accept/reject policies on SOCKS connections, so you can bind
8895 to 0.0.0.0 but still control who can use your OP.
8898 Changes in version 0.0.6.2 - 2004-05-16
8899 o Our integrity-checking digest was checking only the most recent cell,
8900 not the previous cells like we'd thought.
8901 Thanks to Stefan Mark for finding the flaw!
8904 Changes in version 0.0.6.1 - 2004-05-06
8905 o Fix two bugs in our AES counter-mode implementation (this affected
8906 onion-level stream encryption, but not TLS-level). It turns
8907 out we were doing something much more akin to a 16-character
8908 polyalphabetic cipher. Oops.
8909 Thanks to Stefan Mark for finding the flaw!
8910 o Retire moria3 as a directory server, and add tor26 as a directory
8914 Changes in version 0.0.6 - 2004-05-02
8918 Changes in version 0.0.6rc4 - 2004-05-01
8919 o Update the built-in dirservers list to use the new directory format
8920 o Fix a rare seg fault: if a node offering a hidden service attempts
8921 to build a circuit to Alice's rendezvous point and fails before it
8922 reaches the last hop, it retries with a different circuit, but
8924 o Handle windows socket errors correctly.
8927 Changes in version 0.0.6rc3 - 2004-04-28
8928 o Don't expire non-general excess circuits (if we had enough
8929 circuits open, we were expiring rendezvous circuits -- even
8930 when they had a stream attached. oops.)
8931 o Fetch randomness from /dev/urandom better (not via fopen/fread)
8932 o Better debugging for tls errors
8933 o Some versions of openssl have an SSL_pending function that erroneously
8934 returns bytes when there is a non-application record pending.
8935 o Set Content-Type on the directory and hidserv descriptor.
8936 o Remove IVs from cipher code, since AES-ctr has none.
8937 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
8938 o We were using an array of length zero in a few places.
8939 o win32's gethostbyname can't resolve an IP to an IP.
8940 o win32's close can't close a socket.
8943 Changes in version 0.0.6rc2 - 2004-04-26
8944 o Fix a bug where we were closing tls connections intermittently.
8945 It turns out openssl keeps its errors around -- so if an error
8946 happens, and you don't ask about it, and then another openssl
8947 operation happens and succeeds, and you ask if there was an error,
8948 it tells you about the first error. Fun fun.
8949 o Fix a bug that's been lurking since 27 may 03 (!)
8950 When passing back a destroy cell, we would use the wrong circ id.
8951 'Mostly harmless', but still worth fixing.
8952 o Since we don't support truncateds much, don't bother sending them;
8953 just close the circ.
8954 o check for <machine/limits.h> so we build on NetBSD again (I hope).
8955 o don't crash if a conn that sent a begin has suddenly lost its circuit
8956 (this was quite rare).
8959 Changes in version 0.0.6rc1 - 2004-04-25
8960 o We now rotate link (tls context) keys and onion keys.
8961 o CREATE cells now include oaep padding, so you can tell
8962 if you decrypted them correctly.
8963 o Add bandwidthburst to server descriptor.
8964 o Directories now say which dirserver signed them.
8965 o Use a tor_assert macro that logs failed assertions too.
8968 Changes in version 0.0.6pre5 - 2004-04-18
8969 o changes from 0.0.6pre4:
8970 - make tor build on broken freebsd 5.2 installs
8971 - fix a failed assert when you try an intro point, get a nack, and try
8972 a second one and it works.
8973 - when alice uses a port that the hidden service doesn't accept,
8974 it now sends back an end cell (denied by exit policy). otherwise
8975 alice would just have to wait to time out.
8976 - fix another rare bug: when we had tried all the intro
8977 points for a hidden service, we fetched the descriptor
8978 again, but we left our introcirc thinking it had already
8979 sent an intro, so it kept waiting for a response...
8980 - bugfix: when you sleep your hidden-service laptop, as soon
8981 as it wakes up it tries to upload a service descriptor, but
8982 socketpair fails for some reason (localhost not up yet?).
8983 now we simply give up on that upload, and we'll try again later.
8984 i'd still like to find the bug though.
8985 - if an intro circ waiting for an ack dies before getting one, then
8987 - we were reusing stale service descriptors and refetching usable
8991 Changes in version 0.0.6pre4 - 2004-04-14
8992 o changes from 0.0.6pre3:
8993 - when bob fails to connect to the rendezvous point, and his
8994 circ didn't fail because of the rendezvous point itself, then
8995 he retries a couple of times
8996 - we expire introduction and rendezvous circs more thoroughly
8997 (sometimes they were hanging around forever)
8998 - we expire unattached rendezvous streams that have been around
8999 too long (they were sticking around forever).
9000 - fix a measly fencepost error that was crashing everybody with
9004 Changes in version 0.0.6pre3 - 2004-04-14
9005 o changes from 0.0.6pre2:
9006 - make hup work again
9007 - fix some memory leaks for dirservers
9008 - allow more skew in rendezvous descriptor timestamps, to help
9009 handle people like blanu who don't know what time it is
9010 - normal circs are 3 hops, but some rend/intro circs are 4, if
9011 the initiator doesn't get to choose the last hop
9012 - send acks for introductions, so alice can know whether to try
9014 - bob publishes intro points more correctly
9015 o changes from 0.0.5:
9016 - fix an assert trigger that's been plaguing us since the days
9017 of 0.0.2prexx (thanks weasel!)
9018 - retry stream correctly when we fail to connect because of
9019 exit-policy-reject (should try another) or can't-resolve-address
9020 (also should try another, because dns on random internet servers
9022 - when we hup a dirserver and we've *removed* a server from the
9023 approved-routers list, now we remove that server from the
9024 in-memory directories too
9027 Changes in version 0.0.6pre2 - 2004-04-08
9028 o We fixed our base32 implementation. Now it works on all architectures.
9031 Changes in version 0.0.6pre1 - 2004-04-08
9033 - Hidden services and rendezvous points are implemented. Go to
9034 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
9035 hidden services. (This only works via a socks4a proxy such as
9036 Privoxy, and currently it's quite slow.)
9039 Changes in version 0.0.5 - 2004-03-30
9043 Changes in version 0.0.5rc3 - 2004-03-29
9044 o Install torrc as torrc.sample -- we no longer clobber your
9046 o Re-enable recommendedversion checking (we broke it in rc2, oops)
9047 o Add in a 'notice' log level for things the operator should hear
9048 but that aren't warnings
9051 Changes in version 0.0.5rc2 - 2004-03-29
9052 o Hold socks connection open until reply is flushed (if possible)
9053 o Make exit nodes resolve IPs to IPs immediately, rather than asking
9054 the dns farm to do it.
9055 o Fix c99 aliasing warnings in rephist.c
9056 o Don't include server descriptors that are older than 24 hours in the
9058 o Give socks 'reject' replies their whole 15s to attempt to flush,
9059 rather than seeing the 60s timeout and assuming the flush had failed.
9060 o Clean automake droppings from the cvs repository
9063 Changes in version 0.0.5rc1 - 2004-03-28
9064 o Fix mangled-state bug in directory fetching (was causing sigpipes).
9065 o Only build circuits after we've fetched the directory: clients were
9066 using only the directory servers before they'd fetched a directory.
9067 This also means longer startup time; so it goes.
9068 o Fix an assert trigger where an OP would fail to handshake, and we'd
9069 expect it to have a nickname.
9070 o Work around a tsocks bug: do a socks reject when AP connection dies
9071 early, else tsocks goes into an infinite loop.
9074 Changes in version 0.0.4 - 2004-03-26
9075 o When connecting to a dirserver or OR and the network is down,
9079 Changes in version 0.0.3 - 2004-03-26
9080 o Warn and fail if server chose a nickname with illegal characters
9081 o Port to Solaris and Sparc:
9082 - include missing header fcntl.h
9083 - have autoconf find -lsocket -lnsl automatically
9084 - deal with hardware word alignment
9085 - make uname() work (solaris has a different return convention)
9086 - switch from using signal() to sigaction()
9087 o Preliminary work on reputation system:
9088 - Keep statistics on success/fail of connect attempts; they're published
9089 by kill -USR1 currently.
9090 - Add a RunTesting option to try to learn link state by creating test
9091 circuits, even when SocksPort is off.
9092 - Remove unused open circuits when there are too many.
9095 Changes in version 0.0.2 - 2004-03-19
9096 - Include strlcpy and strlcat for safer string ops
9097 - define INADDR_NONE so we compile (but still not run) on solaris
9100 Changes in version 0.0.2pre27 - 2004-03-14
9102 - Allow internal tor networks (we were rejecting internal IPs,
9103 now we allow them if they're set explicitly).
9104 - And fix a few endian issues.
9107 Changes in version 0.0.2pre26 - 2004-03-14
9109 - If a stream times out after 15s without a connected cell, don't
9110 try that circuit again: try a new one.
9111 - Retry streams at most 4 times. Then give up.
9112 - When a dirserver gets a descriptor from an unknown router, it
9113 logs its fingerprint (so the dirserver operator can choose to
9114 accept it even without mail from the server operator).
9115 - Inform unapproved servers when we reject their descriptors.
9116 - Make tor build on Windows again. It works as a client, who knows
9118 - Clearer instructions in the torrc for how to set up a server.
9119 - Be more efficient about reading fd's when our global token bucket
9120 (used for rate limiting) becomes empty.
9122 - Stop asserting that computers always go forward in time. It's
9124 - When we sent a cell (e.g. destroy) and then marked an OR connection
9125 expired, we might close it before finishing a flush if the other
9126 side isn't reading right then.
9127 - Don't allow dirservers to start if they haven't defined
9129 - We were caching transient dns failures. Oops.
9130 - Prevent servers from publishing an internal IP as their address.
9131 - Address a strcat vulnerability in circuit.c
9134 Changes in version 0.0.2pre25 - 2004-03-04
9136 - Put the OR's IP in its router descriptor, not its fqdn. That way
9137 we'll stop being stalled by gethostbyname for nodes with flaky dns,
9140 - If the user typed in an address that didn't resolve, the server
9144 Changes in version 0.0.2pre24 - 2004-03-03
9146 - Fix an assertion failure in dns.c, where we were trying to dequeue
9147 a pending dns resolve even if it wasn't pending
9148 - Fix a spurious socks5 warning about still trying to write after the
9149 connection is finished.
9150 - Hold certain marked_for_close connections open until they're finished
9151 flushing, rather than losing bytes by closing them too early.
9152 - Correctly report the reason for ending a stream
9153 - Remove some duplicate calls to connection_mark_for_close
9154 - Put switch_id and start_daemon earlier in the boot sequence, so it
9155 will actually try to chdir() to options.DataDirectory
9156 - Make 'make test' exit(1) if a test fails; fix some unit tests
9157 - Make tor fail when you use a config option it doesn't know about,
9158 rather than warn and continue.
9159 - Make --version work
9160 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
9163 Changes in version 0.0.2pre23 - 2004-02-29
9165 - Print a statement when the first circ is finished, so the user
9167 - If a relay cell is unrecognized at the end of the circuit,
9168 send back a destroy. (So attacks to mutate cells are more
9170 - New config option 'excludenodes' to avoid certain nodes for circuits.
9171 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
9172 so you can collect coredumps there.
9174 - Fix a bug in tls flushing where sometimes data got wedged and
9175 didn't flush until more data got sent. Hopefully this bug was
9176 a big factor in the random delays we were seeing.
9177 - Make 'connected' cells include the resolved IP, so the client
9178 dns cache actually gets populated.
9179 - Disallow changing from ORPort=0 to ORPort>0 on hup.
9180 - When we time-out on a stream and detach from the circuit, send an
9181 end cell down it first.
9182 - Only warn about an unknown router (in exitnodes, entrynodes,
9183 excludenodes) after we've fetched a directory.
9186 Changes in version 0.0.2pre22 - 2004-02-26
9188 - Servers publish less revealing uname information in descriptors.
9189 - More memory tracking and assertions, to crash more usefully when
9191 - If the default torrc isn't there, just use some default defaults.
9192 Plus provide an internal dirservers file if they don't have one.
9193 - When the user tries to use Tor as an http proxy, give them an http
9194 501 failure explaining that we're a socks proxy.
9195 - Dump a new router.desc on hup, to help confused people who change
9196 their exit policies and then wonder why router.desc doesn't reflect
9198 - Clean up the generic tor.sh init script that we ship with.
9200 - If the exit stream is pending on the resolve, and a destroy arrives,
9201 then the stream wasn't getting removed from the pending list. I
9202 think this was the one causing recent server crashes.
9203 - Use a more robust poll on OSX 10.3, since their poll is flaky.
9204 - When it couldn't resolve any dirservers, it was useless from then on.
9205 Now it reloads the RouterFile (or default dirservers) if it has no
9207 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
9208 many users don't even *have* a /usr/local/sbin/.
9211 Changes in version 0.0.2pre21 - 2004-02-18
9213 - There's a ChangeLog file that actually reflects the changelog.
9214 - There's a 'torify' wrapper script, with an accompanying
9215 tor-tsocks.conf, that simplifies the process of using tsocks for
9216 tor. It even has a man page.
9217 - The tor binary gets installed to sbin rather than bin now.
9218 - Retry streams where the connected cell hasn't arrived in 15 seconds
9219 - Clean up exit policy handling -- get the default out of the torrc,
9220 so we can update it without forcing each server operator to fix
9222 - Allow imaps and pop3s in default exit policy
9224 - Prevent picking middleman nodes as the last node in the circuit
9227 Changes in version 0.0.2pre20 - 2004-01-30
9229 - We now have a deb package, and it's in debian unstable. Go to
9231 - I've split the TotalBandwidth option into BandwidthRate (how many
9232 bytes per second you want to allow, long-term) and
9233 BandwidthBurst (how many bytes you will allow at once before the cap
9234 kicks in). This better token bucket approach lets you, say, set
9235 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
9236 performance while not exceeding your monthly bandwidth quota.
9237 - Push out a tls record's worth of data once you've got it, rather
9238 than waiting until you've read everything waiting to be read. This
9239 may improve performance by pipelining better. We'll see.
9240 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
9241 from failed circuits (if they haven't been connected yet) and attach
9243 - Expire old streams that haven't managed to connect. Some day we'll
9244 have them reattach to new circuits instead.
9247 - Fix several memory leaks that were causing servers to become bloated
9249 - Fix a few very rare assert triggers. A few more remain.
9250 - Setuid to User _before_ complaining about running as root.
9253 Changes in version 0.0.2pre19 - 2004-01-07
9255 - Fix deadlock condition in dns farm. We were telling a child to die by
9256 closing the parent's file descriptor to him. But newer children were
9257 inheriting the open file descriptor from the parent, and since they
9258 weren't closing it, the socket never closed, so the child never read
9259 eof, so he never knew to exit. Similarly, dns workers were holding
9260 open other sockets, leading to all sorts of chaos.
9261 - New cleaner daemon() code for forking and backgrounding.
9262 - If you log to a file, it now prints an entry at the top of the
9263 logfile so you know it's working.
9264 - The onionskin challenge length was 30 bytes longer than necessary.
9265 - Started to patch up the spec so it's not quite so out of date.
9268 Changes in version 0.0.2pre18 - 2004-01-02
9270 - Fix endian issues with the 'integrity' field in the relay header.
9271 - Fix a potential bug where connections in state
9272 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9275 Changes in version 0.0.2pre17 - 2003-12-30
9277 - Made --debuglogfile (or any second log file, actually) work.
9278 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9279 adversary could force us into an infinite loop.
9282 - Each onionskin handshake now includes a hash of the computed key,
9283 to prove the server's identity and help perfect forward secrecy.
9284 - Changed cell size from 256 to 512 bytes (working toward compatibility
9286 - Changed cell length to 2 bytes, and moved it to the relay header.
9287 - Implemented end-to-end integrity checking for the payloads of
9289 - Separated streamid from 'recognized' (otherwise circuits will get
9290 messed up when we try to have streams exit from the middle). We
9291 use the integrity-checking to confirm that a cell is addressed to
9293 - Randomize the initial circid and streamid values, so an adversary who
9294 breaks into a node can't learn how many circuits or streams have
9298 Changes in version 0.0.2pre16 - 2003-12-14
9300 - Fixed a bug that made HUP trigger an assert
9301 - Fixed a bug where a circuit that immediately failed wasn't being
9302 counted as a failed circuit in counting retries.
9305 - Now we close the circuit when we get a truncated cell: otherwise we're
9306 open to an anonymity attack where a bad node in the path truncates
9307 the circuit and then we open streams at him.
9308 - Add port ranges to exit policies
9309 - Add a conservative default exit policy
9310 - Warn if you're running tor as root
9311 - on HUP, retry OR connections and close/rebind listeners
9312 - options.EntryNodes: try these nodes first when picking the first node
9313 - options.ExitNodes: if your best choices happen to include any of
9314 your preferred exit nodes, you choose among just those preferred
9316 - options.ExcludedNodes: nodes that are never picked in path building
9319 Changes in version 0.0.2pre15 - 2003-12-03
9320 o Robustness and bugfixes:
9321 - Sometimes clients would cache incorrect DNS resolves, which would
9322 really screw things up.
9323 - An OP that goes offline would slowly leak all its sockets and stop
9325 - A wide variety of bugfixes in exit node selection, exit policy
9326 handling, and processing pending streams when a new circuit is
9328 - Pick nodes for a path only from those the directory says are up
9329 - Choose randomly from all running dirservers, not always the first one
9330 - Increase allowed http header size for directory fetch.
9331 - Stop writing to stderr (if we're daemonized it will be closed).
9332 - Enable -g always, so cores will be more useful to me.
9333 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9336 - Wrote a man page. It lists commonly used options.
9339 - Change default loglevel to warn.
9340 - Make PidFile default to null rather than littering in your CWD.
9341 - OnionRouter config option is now obsolete. Instead it just checks
9343 - Moved to a single unified torrc file for both clients and servers.
9346 Changes in version 0.0.2pre14 - 2003-11-29
9347 o Robustness and bugfixes:
9348 - Force the admin to make the DataDirectory himself
9349 - to get ownership/permissions right
9350 - so clients no longer make a DataDirectory and then never use it
9351 - fix bug where a client who was offline for 45 minutes would never
9352 pull down a directory again
9353 - fix (or at least hide really well) the dns assert bug that was
9354 causing server crashes
9355 - warnings and improved robustness wrt clockskew for certs
9356 - use the native daemon(3) to daemonize, when available
9357 - exit if bind() fails
9358 - exit if neither socksport nor orport is defined
9359 - include our own tor_timegm (Win32 doesn't have its own)
9360 - bugfix for win32 with lots of connections
9361 - fix minor bias in PRNG
9362 - make dirserver more robust to corrupt cached directory
9365 - Wrote the design document (woo)
9367 o Circuit building and exit policies:
9368 - Circuits no longer try to use nodes that the directory has told them
9370 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9371 bitcounts (18.0.0.0/8).
9372 - Make AP connections standby for a circuit if no suitable circuit
9373 exists, rather than failing
9374 - Circuits choose exit node based on addr/port, exit policies, and
9375 which AP connections are standing by
9376 - Bump min pathlen from 2 to 3
9377 - Relay end cells have a payload to describe why the stream ended.
9378 - If the stream failed because of exit policy, try again with a new
9380 - Clients have a dns cache to remember resolved addresses.
9381 - Notice more quickly when we have no working circuits
9384 - APPort is now called SocksPort
9385 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9387 - RecommendedVersions is now a config variable rather than
9388 hardcoded (for dirservers)
9389 - Reloads config on HUP
9390 - Usage info on -h or --help
9391 - If you set User and Group config vars, it'll setu/gid to them.
9394 Changes in version 0.0.2pre13 - 2003-10-19
9395 o General stability:
9396 - SSL_write no longer fails when it returns WANTWRITE and the number
9397 of bytes in the buf has changed by the next SSL_write call.
9398 - Fix segfault fetching directory when network is down
9399 - Fix a variety of minor memory leaks
9400 - Dirservers reload the fingerprints file on HUP, so I don't have
9401 to take down the network when I approve a new router
9402 - Default server config file has explicit Address line to specify fqdn
9405 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9406 - Make listener connections not ever alloc bufs
9408 o Autoconf improvements:
9409 - don't clobber an external CFLAGS in ./configure
9410 - Make install now works
9411 - create var/lib/tor on make install
9412 - autocreate a tor.sh initscript to help distribs
9413 - autocreate the torrc and sample-server-torrc with correct paths
9415 o Log files and Daemonizing now work:
9416 - If --DebugLogFile is specified, log to it at -l debug
9417 - If --LogFile is specified, use it instead of commandline
9418 - If --RunAsDaemon is set, tor forks and backgrounds on startup