1 Changes in version 0.2.2.19-alpha - 2010-11-21
3 - Resolve an incompatibility with openssl 0.9.8p and openssl 1.0.0b:
4 No longer set the tlsext_host_name extension on server SSL objects;
5 but continue to set it on client SSL objects. Our goal in setting
6 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7 bugfix on 0.2.1.1-alpha.
10 - Try harder not to exceed the maximum length of 50 KB when writing
11 statistics to extra-info descriptors. This bug was triggered by very
12 fast relays reporting exit-port, entry, and dirreq statistics.
13 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
14 - Publish a router descriptor even if generating an extra-info
15 descriptor fails. Previously we would not publish a router
16 descriptor without an extra-info descriptor; this can cause fast
17 exit relays collecting exit-port statistics to drop from the
18 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
21 Changes in version 0.2.2.18-alpha - 2010-11-16
23 - Do even more to reject (and not just ignore) annotations on
24 router descriptors received anywhere but from the cache. Previously
25 we would ignore such annotations at first, but cache them to disk
26 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
27 - Do not log messages to the controller while shrinking buffer
28 freelists. Doing so would sometimes make the controller connection
29 try to allocate a buffer chunk, which would mess up the internals
30 of the freelist and cause an assertion failure. Fixes bug 1125;
31 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
32 - Learn our external IP address when we're a relay or bridge, even if
33 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
34 where we introduced bridge relays that don't need to publish to
35 be useful. Fixes bug 2050.
36 - Maintain separate TLS contexts and certificates for incoming and
37 outgoing connections in bridge relays. Previously we would use the
38 same TLS contexts and certs for incoming and outgoing connections.
39 Bugfix on 0.2.0.3-alpha; addresses bug 988.
40 - Maintain separate identity keys for incoming and outgoing TLS
41 contexts in bridge relays. Previously we would use the same
42 identity keys for incoming and outgoing TLS contexts. Bugfix on
43 0.2.0.3-alpha; addresses the other half of bug 988.
44 - Avoid an assertion failure when we as an authority receive a
45 duplicate upload of a router descriptor that we already have,
46 but which we previously considered an obsolete descriptor.
47 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
48 - Avoid a crash bug triggered by looking at a dangling pointer while
49 setting the network status consensus. Found by Robert Ransom.
50 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
51 - Fix a logic error where servers that _didn't_ act as exits would
52 try to keep their server lists more aggressively up to date than
53 exits, when it was supposed to be the other way around. Bugfix
56 o Minor bugfixes (on Tor 0.2.1.x and earlier):
57 - When we're trying to guess whether we know our IP address as
58 a relay, we would log various ways that we failed to guess
59 our address, but never log that we ended up guessing it
60 successfully. Now add a log line to help confused and anxious
61 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
62 - Bring the logic that gathers routerinfos and assesses the
63 acceptability of circuits into line. This prevents a Tor OP from
64 getting locked in a cycle of choosing its local OR as an exit for a
65 path (due to a .exit request) and then rejecting the circuit because
66 its OR is not listed yet. It also prevents Tor clients from using an
67 OR running in the same instance as an exit (due to a .exit request)
68 if the OR does not meet the same requirements expected of an OR
69 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
70 - Correctly describe errors that occur when generating a TLS object.
71 Previously we would attribute them to a failure while generating a
72 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
74 - Enforce multiplicity rules when parsing annotations. Bugfix on
75 0.2.0.8-alpha. Found by piebeer.
76 - Fix warnings that newer versions of autoconf produced during
77 ./autogen.sh. These warnings appear to be harmless in our case,
78 but they were extremely verbose. Fixes bug 2020.
80 o Minor bugfixes (on Tor 0.2.2.x):
81 - Enable protection of small arrays whenever we build with gcc
82 hardening features, not only when also building with warnings
83 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
86 - Make hidden services work better in private Tor networks by not
87 requiring any uptime to join the hidden service descriptor
88 DHT. Implements ticket 2088.
89 - Rate-limit the "your application is giving Tor only an IP address"
90 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
91 - When AllowSingleHopExits is set, print a warning to explain to the
92 relay operator why most clients are avoiding her relay.
93 - Update to the November 1 2010 Maxmind GeoLite Country database.
95 o Code simplifications and refactoring:
96 - When we fixed bug 1038 we had to put in a restriction not to send
97 RELAY_EARLY cells on rend circuits. This was necessary as long
98 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
99 active. Now remove this obsolete check. Resolves bug 2081.
100 - Some options used different conventions for uppercasing of acronyms
101 when comparing manpage and source. Fix those in favor of the
102 manpage, as it makes sense to capitalize acronyms.
103 - Remove the torrc.complete file. It hasn't been kept up to date
104 and users will have better luck checking out the manpage.
105 - Remove the obsolete "NoPublish" option; it has been flagged
106 as obsolete and has produced a warning since 0.1.1.18-rc.
107 - Remove everything related to building the expert bundle for OS X.
108 It has confused many users, doesn't work right on OS X 10.6,
109 and is hard to get rid of once installed. Resolves bug 1274.
112 Changes in version 0.2.2.17-alpha - 2010-09-30
113 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
114 to use one-hop circuits (which can put the exit relays at higher risk,
115 plus unbalance the network); fixes a big bug in bandwidth accounting
116 for relays that want to limit their monthly bandwidth use; fixes a
117 big pile of bugs in how clients tolerate temporary network failure;
118 and makes our adaptive circuit build timeout feature (which improves
119 client performance if your network is fast while not breaking things
120 if your network is slow) better handle bad networks.
123 - Exit relays now try harder to block exit attempts from unknown
124 relays, to make it harder for people to use them as one-hop proxies
125 a la tortunnel. Controlled by the refuseunknownexits consensus
126 parameter (currently enabled), or you can override it on your
127 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
129 o Major bugfixes (0.2.1.x and earlier):
130 - Fix a bug in bandwidth accounting that could make us use twice
131 the intended bandwidth when our interval start changes due to
132 daylight saving time. Now we tolerate skew in stored vs computed
133 interval starts: if the start of the period changes by no more than
134 50% of the period's duration, we remember bytes that we transferred
135 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
136 - Always search the Windows system directory for system DLLs, and
137 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
138 - When you're using bridges and your network goes away and your
139 bridges get marked as down, recover when you attempt a new socks
140 connection (if the network is back), rather than waiting up to an
141 hour to try fetching new descriptors for your bridges. Bugfix on
142 0.2.0.3-alpha; fixes bug 1981.
144 o Major bugfixes (on 0.2.2.x):
145 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
147 - Fix a segfault that could happen when operating a bridge relay with
148 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
149 - The consensus bandwidth-weights (used by clients to choose fast
150 relays) entered an unexpected edge case in September where
151 Exits were much scarcer than Guards, resulting in bad weight
152 recommendations. Now we compute them using new constraints that
153 should succeed in all cases. Also alter directory authorities to
154 not include the bandwidth-weights line if they fail to produce
155 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
156 - When weighting bridges during path selection, we used to trust
157 the bandwidths they provided in their descriptor, only capping them
158 at 10MB/s. This turned out to be problematic for two reasons:
159 Bridges could claim to handle a lot more traffic then they
160 actually would, thus making more clients pick them and have a
161 pretty effective DoS attack. The other issue is that new bridges
162 that might not have a good estimate for their bw capacity yet
163 would not get used at all unless no other bridges are available
164 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
166 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
167 - Ignore cannibalized circuits when recording circuit build times.
168 This should provide for a minor performance improvement for hidden
169 service users using 0.2.2.14-alpha, and should remove two spurious
170 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
171 - Simplify the logic that causes us to decide if the network is
172 unavailable for purposes of recording circuit build times. If we
173 receive no cells whatsoever for the entire duration of a circuit's
174 full measured lifetime, the network is probably down. Also ignore
175 one-hop directory fetching circuit timeouts when calculating our
176 circuit build times. These changes should hopefully reduce the
177 cases where we see ridiculous circuit build timeouts for people
178 with spotty wireless connections. Fixes part of bug 1772; bugfix
180 - Prevent the circuit build timeout from becoming larger than
181 the maximum build time we have ever seen. Also, prevent the time
182 period for measurement circuits from becoming larger than twice that
183 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
186 - When we run out of directory information such that we can't build
187 circuits, but then get enough that we can build circuits, log when
188 we actually construct a circuit, so the user has a better chance of
189 knowing what's going on. Fixes bug 1362.
190 - Be more generous with how much bandwidth we'd use up (with
191 accounting enabled) before entering "soft hibernation". Previously,
192 we'd refuse new connections and circuits once we'd used up 95% of
193 our allotment. Now, we use up 95% of our allotment, AND make sure
194 that we have no more than 500MB (or 3 hours of expected traffic,
195 whichever is lower) remaining before we enter soft hibernation.
196 - If we've configured EntryNodes and our network goes away and/or all
197 our entrynodes get marked down, optimistically retry them all when
198 a new socks application request appears. Fixes bug 1882.
199 - Add some more defensive programming for architectures that can't
200 handle unaligned integer accesses. We don't know of any actual bugs
201 right now, but that's the best time to fix them. Fixes bug 1943.
202 - Support line continuations in the torrc config file. If a line
203 ends with a single backslash character, the newline is ignored, and
204 the configuration value is treated as continuing on the next line.
207 o Minor bugfixes (on 0.2.1.x and earlier):
208 - For bandwidth accounting, calculate our expected bandwidth rate
209 based on the time during which we were active and not in
210 soft-hibernation during the last interval. Previously, we were
211 also considering the time spent in soft-hibernation. If this
212 was a long time, we would wind up underestimating our bandwidth
213 by a lot, and skewing our wakeup time towards the start of the
214 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
216 o Minor bugfixes (on 0.2.2.x):
217 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
218 which were disabled by the circuit build timeout changes in
219 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
220 - Make sure we don't warn about missing bandwidth weights when
221 choosing bridges or other relays not in the consensus. Bugfix on
222 0.2.2.10-alpha; fixes bug 1805.
223 - In our logs, do not double-report signatures from unrecognized
224 authorities both as "from unknown authority" and "not
225 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
228 Changes in version 0.2.2.16-alpha - 2010-09-17
229 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
230 evident at exit relays), and also continues to resolve all the little
231 bugs that have been filling up trac lately.
233 o Major bugfixes (stream-level fairness):
234 - When receiving a circuit-level SENDME for a blocked circuit, try
235 to package cells fairly from all the streams that had previously
236 been blocked on that circuit. Previously, we had started with the
237 oldest stream, and allowed each stream to potentially exhaust
238 the circuit's package window. This gave older streams on any
239 given circuit priority over newer ones. Fixes bug 1937. Detected
240 originally by Camilo Viecco. This bug was introduced before the
241 first Tor release, in svn commit r152: it is the new winner of
242 the longest-lived bug prize.
243 - When the exit relay got a circuit-level sendme cell, it started
244 reading on the exit streams, even if had 500 cells queued in the
245 circuit queue already, so the circuit queue just grew and grew in
246 some cases. We fix this by not re-enabling reading on receipt of a
247 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
248 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
250 - Newly created streams were allowed to read cells onto circuits,
251 even if the circuit's cell queue was blocked and waiting to drain.
252 This created potential unfairness, as older streams would be
253 blocked, but newer streams would gladly fill the queue completely.
254 We add code to detect this situation and prevent any stream from
255 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
259 - Update to the September 1 2010 Maxmind GeoLite Country database.
260 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
261 not. This would lead to a cookie that is still not group readable.
262 Closes bug 1843. Suggested by katmagic.
263 - When logging a rate-limited warning, we now mention how many messages
264 got suppressed since the last warning.
265 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
266 do individual connection-level rate limiting of clients. The torrc
267 config options with the same names trump the consensus params, if
268 both are present. Replaces the old "bwconnrate" and "bwconnburst"
269 consensus params which were broken from 0.2.2.7-alpha through
270 0.2.2.14-alpha. Closes bug 1947.
271 - When a router changes IP address or port, authorities now launch
272 a new reachability test for it. Implements ticket 1899.
273 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
274 2 no signature, 4 required" messages about consensus signatures
275 easier to read, and make sure they get logged at the same severity
276 as the messages explaining which keys are which. Fixes bug 1290.
277 - Don't warn when we have a consensus that we can't verify because
278 of missing certificates, unless those certificates are ones
279 that we have been trying and failing to download. Fixes bug 1145.
280 - If you configure your bridge with a known identity fingerprint,
281 and the bridge authority is unreachable (as it is in at least
282 one country now), fall back to directly requesting the descriptor
283 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
285 - When building with --enable-gcc-warnings on OpenBSD, disable
286 warnings in system headers. This makes --enable-gcc-warnings
289 o Minor bugfixes (on 0.2.1.x and earlier):
290 - Authorities will now attempt to download consensuses if their
291 own efforts to make a live consensus have failed. This change
292 means authorities that restart will fetch a valid consensus, and
293 it means authorities that didn't agree with the current consensus
294 will still fetch and serve it if it has enough signatures. Bugfix
295 on 0.2.0.9-alpha; fixes bug 1300.
296 - Ensure DNS requests launched by "RESOLVE" commands from the
297 controller respect the __LeaveStreamsUnattached setconf options. The
298 same goes for requests launched via DNSPort or transparent
299 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
300 - Allow handshaking OR connections to take a full KeepalivePeriod
301 seconds to handshake. Previously, we would close them after
302 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
303 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
305 - Rate-limit "Failed to hand off onionskin" warnings.
306 - Never relay a cell for a circuit we have already destroyed.
307 Between marking a circuit as closeable and finally closing it,
308 it may have been possible for a few queued cells to get relayed,
309 even though they would have been immediately dropped by the next
310 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
311 - Never queue a cell for a circuit that's already been marked
313 - Never vote for a server as "Running" if we have a descriptor for
314 it claiming to be hibernating, and that descriptor was published
315 more recently than our last contact with the server. Bugfix on
316 0.2.0.3-alpha; fixes bug 911.
317 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
320 o Minor bugfixes (on 0.2.2.x):
321 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
322 down if a directory fetch fails and you've configured either
323 bridges or EntryNodes. The intent was to mark the relay as down
324 _unless_ you're using bridges or EntryNodes, since if you are
325 then you could quickly run out of entry points.
326 - Fix the Windows directory-listing code. A bug introduced in
327 0.2.2.14-alpha could make Windows directory servers forget to load
328 some of their cached v2 networkstatus files.
329 - Really allow clients to use relays as bridges. Fixes bug 1776;
330 bugfix on 0.2.2.15-alpha.
331 - Demote a warn to info that happens when the CellStatistics option
332 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
333 Reported by Moritz Bartl.
334 - On Windows, build correctly either with or without Unicode support.
335 This is necessary so that Tor can support fringe platforms like
336 Windows 98 (which has no Unicode), or Windows CE (which has no
337 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
340 - Add a unit test for cross-platform directory-listing code.
343 Changes in version 0.2.2.15-alpha - 2010-08-18
344 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
345 fixes a variety of other bugs that were preventing performance
346 experiments from moving forward, fixes several bothersome memory leaks,
347 and generally closes a lot of smaller bugs that have been filling up
351 - Stop assigning the HSDir flag to relays that disable their
352 DirPort (and thus will refuse to answer directory requests). This
353 fix should dramatically improve the reachability of hidden services:
354 hidden services and hidden service clients pick six HSDir relays
355 to store and retrieve the hidden service descriptor, and currently
356 about half of the HSDir relays will refuse to work. Bugfix on
357 0.2.0.10-alpha; fixes part of bug 1693.
358 - The PerConnBWRate and Burst config options, along with the
359 bwconnrate and bwconnburst consensus params, initialized each conn's
360 token bucket values only when the connection is established. Now we
361 update them if the config options change, and update them every time
362 we get a new consensus. Otherwise we can encounter an ugly edge
363 case where we initialize an OR conn to client-level bandwidth,
364 but then later the relay joins the consensus and we leave it
365 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
366 - Fix a regression that caused Tor to rebind its ports if it receives
367 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
370 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
371 should give us approximately 40-50% more Guard-flagged nodes,
372 improving the anonymity the Tor network can provide and also
373 decreasing the dropoff in throughput that relays experience when
374 they first get the Guard flag.
375 - Allow enabling or disabling the *Statistics config options while
379 - Update to the August 1 2010 Maxmind GeoLite Country database.
380 - Have the controller interface give a more useful message than
381 "Internal Error" in response to failed GETINFO requests.
382 - Warn when the same option is provided more than once in a torrc
383 file, on the command line, or in a single SETCONF statement, and
384 the option is one that only accepts a single line. Closes bug 1384.
385 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
386 Patch from mingw-san.
387 - Add support for the country code "{??}" in torrc options like
388 ExcludeNodes, to indicate all routers of unknown country. Closes
390 - Relays report the number of bytes spent on answering directory
391 requests in extra-info descriptors similar to {read,write}-history.
392 Implements enhancement 1790.
394 o Minor bugfixes (on 0.2.1.x and earlier):
395 - Complain if PublishServerDescriptor is given multiple arguments that
396 include 0 or 1. This configuration will be rejected in the future.
397 Bugfix on 0.2.0.1-alpha; closes bug 1107.
398 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
399 Bugfix on 0.2.0.13-alpha; closes bug 928.
400 - Change "Application request when we're believed to be offline."
401 notice to "Application request when we haven't used client
402 functionality lately.", to clarify that it's not an error. Bugfix
403 on 0.0.9.3; fixes bug 1222.
404 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
405 would return "551 Internal error" rather than "552 Unrecognized key
406 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
407 - Users can't configure a regular relay to be their bridge. It didn't
408 work because when Tor fetched the bridge descriptor, it found
409 that it already had it, and didn't realize that the purpose of the
410 descriptor had changed. Now we replace routers with a purpose other
411 than bridge with bridge descriptors when fetching them. Bugfix on
412 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
413 refetch the descriptor with router purpose 'general', disabling
415 - Fix a rare bug in rend_fn unit tests: we would fail a test when
416 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
417 on 0.2.0.10-alpha; fixes bug 1808.
418 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
419 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
420 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
421 Servers can start sending this code when enough clients recognize
422 it. Also update the spec to reflect this new reason. Bugfix on
423 0.1.0.1-rc; fixes part of bug 1793.
424 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
425 when we switch from being a public relay to a bridge. Otherwise
426 there will still be clients that see the relay in their consensus,
427 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
429 - Instead of giving an assertion failure on an internal mismatch
430 on estimated freelist size, just log a BUG warning and try later.
431 Mitigates but does not fix bug 1125.
432 - Fix an assertion failure that could occur in caches or bridge users
433 when using a very short voting interval on a testing network.
434 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
436 o Minor bugfixes (on 0.2.2.x):
437 - Alter directory authorities to always consider Exit-flagged nodes
438 as potential Guard nodes in their votes. The actual decision to
439 use Exits as Guards is done in the consensus bandwidth weights.
440 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
441 - When the controller is reporting the purpose of circuits that
442 didn't finish building before the circuit build timeout, it was
443 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
444 - Our libevent version parsing code couldn't handle versions like
445 1.4.14b-stable and incorrectly warned the user about using an
446 old and broken version of libevent. Treat 1.4.14b-stable like
447 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
449 - Don't use substitution references like $(VAR:MOD) when
450 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
451 '$(:x)' to 'x' rather than the empty string. This bites us in
452 doc/ when configured with --disable-asciidoc. Bugfix on
453 0.2.2.9-alpha; fixes bug 1773.
454 - Remove a spurious hidden service server-side log notice about
455 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
457 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
459 - Correctly report written bytes on linked connections. Found while
460 implementing 1790. Bugfix on 0.2.2.4-alpha.
461 - Fix three memory leaks: one in circuit_build_times_parse_state(),
462 one in dirvote_add_signatures_to_pending_consensus(), and one every
463 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
464 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
466 o Code simplifications and refactoring:
467 - Take a first step towards making or.h smaller by splitting out
468 function definitions for all source files in src/or/. Leave
469 structures and defines in or.h for now.
470 - Remove a bunch of unused function declarations as well as a block of
471 #if 0'd code from the unit tests. Closes bug 1824.
472 - New unit tests for exit-port history statistics; refactored exit
473 statistics code to be more easily tested.
474 - Remove the old debian/ directory from the main Tor distribution.
475 The official Tor-for-debian git repository lives at the URL
476 https://git.torproject.org/debian/tor.git
479 Changes in version 0.2.2.14-alpha - 2010-07-12
480 Tor 0.2.2.14-alpha greatly improves client-side handling of
481 circuit build timeouts, which are used to estimate speed and improve
482 performance. We also move to a much better GeoIP database, port Tor to
483 Windows CE, introduce new compile flags that improve code security,
484 add an eighth v3 directory authority, and address a lot of more
488 - Tor directory authorities no longer crash when started with a
489 cached-microdesc-consensus file in their data directory. Bugfix
490 on 0.2.2.6-alpha; fixes bug 1532.
491 - Treat an unset $HOME like an empty $HOME rather than triggering an
492 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
493 - Ignore negative and large circuit build timeout values that can
494 happen during a suspend or hibernate. These values caused various
495 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
496 - Alter calculation of Pareto distribution parameter 'Xm' for
497 Circuit Build Timeout learning to use the weighted average of the
498 top N=3 modes (because we have three entry guards). Considering
499 multiple modes should improve the timeout calculation in some cases,
500 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
502 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
503 right censored distribution model. This approach improves over the
504 synthetic timeout generation approach that was producing insanely
505 high timeout values. Now we calculate build timeouts using truncated
506 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
507 - Do not close circuits that are under construction when they reach
508 the circuit build timeout. Instead, leave them building (but do not
509 use them) for up until the time corresponding to the 95th percentile
510 on the Pareto CDF or 60 seconds, whichever is greater. This is done
511 to provide better data for the new Pareto model. This percentile
512 can be controlled by the consensus.
515 - Move to the June 2010 Maxmind GeoLite country db (rather than the
516 June 2009 ip-to-country GeoIP db) for our statistics that count
517 how many users relays are seeing from each country. Now we have
518 more accurate data for many African countries.
519 - Port Tor to build and run correctly on Windows CE systems, using
520 the wcecompat library. Contributed by Valerio Lupi.
521 - New "--enable-gcc-hardening" ./configure flag (off by default)
522 to turn on gcc compile time hardening options. It ensures
523 that signed ints have defined behavior (-fwrapv), enables
524 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
525 with canaries (-fstack-protector-all), turns on ASLR protection if
526 supported by the kernel (-fPIE, -pie), and adds additional security
527 related warnings. Verified to work on Mac OS X and Debian Lenny.
528 - New "--enable-linker-hardening" ./configure flag (off by default)
529 to turn on ELF specific hardening features (relro, now). This does
530 not work with Mac OS X or any other non-ELF binary format.
532 o New directory authorities:
533 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
537 - New config option "WarnUnsafeSocks 0" disables the warning that
538 occurs whenever Tor receives only an IP address instead of a
539 hostname. Setups that do DNS locally over Tor are fine, and we
540 shouldn't spam the logs in that case.
541 - Convert the HACKING file to asciidoc, and add a few new sections
542 to it, explaining how we use Git, how we make changelogs, and
543 what should go in a patch.
544 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
545 event, to give information on the current rate of circuit timeouts
546 over our stored history.
547 - Add ability to disable circuit build time learning via consensus
548 parameter and via a LearnCircuitBuildTimeout config option. Also
549 automatically disable circuit build time calculation if we are
550 either a AuthoritativeDirectory, or if we fail to write our state
551 file. Fixes bug 1296.
552 - More gracefully handle corrupt state files, removing asserts
553 in favor of saving a backup and resetting state.
554 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
558 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
560 - When a2x fails, mention that the user could disable manpages instead
561 of trying to fix their asciidoc installation.
562 - Where available, use Libevent 2.0's periodic timers so that our
563 once-per-second cleanup code gets called even more closely to
564 once per second than it would otherwise. Fixes bug 943.
565 - If you run a bridge that listens on multiple IP addresses, and
566 some user configures a bridge address that uses a different IP
567 address than your bridge writes in its router descriptor, and the
568 user doesn't specify an identity key, their Tor would discard the
569 descriptor because "it isn't one of our configured bridges", and
570 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
571 Bugfix on 0.2.0.3-alpha.
572 - If OpenSSL fails to make a duplicate of a private or public key, log
573 an error message and try to exit cleanly. May help with debugging
574 if bug 1209 ever remanifests.
575 - Save a couple bytes in memory allocation every time we escape
576 certain characters in a string. Patch from Florian Zumbiehl.
577 - Make it explicit that we don't cannibalize one-hop circuits. This
578 happens in the wild, but doesn't turn out to be a problem because
579 we fortunately don't use those circuits. Many thanks to outofwords
580 for the initial analysis and to swissknife who confirmed that
581 two-hop circuits are actually created.
582 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
583 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
584 - Eliminate a case where a circuit build time warning was displayed
585 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
588 Changes in version 0.2.1.26 - 2010-05-02
589 Tor 0.2.1.26 addresses the recent connection and memory overload
590 problems we've been seeing on relays, especially relays with their
591 DirPort open. If your relay has been crashing, or you turned it off
592 because it used too many resources, give this release a try.
594 This release also fixes yet another instance of broken OpenSSL libraries
595 that was causing some relays to drop out of the consensus.
598 - Teach relays to defend themselves from connection overload. Relays
599 now close idle circuits early if it looks like they were intended
600 for directory fetches. Relays are also more aggressive about closing
601 TLS connections that have no circuits on them. Such circuits are
602 unlikely to be re-used, and tens of thousands of them were piling
603 up at the fast relays, causing the relays to run out of sockets
604 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
605 their directory fetches over TLS).
606 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
607 that claim to be earlier than 0.9.8m, but which have in reality
608 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
609 behavior. Possible fix for some cases of bug 1346.
610 - Directory mirrors were fetching relay descriptors only from v2
611 directory authorities, rather than v3 authorities like they should.
612 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
613 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
616 - Finally get rid of the deprecated and now harmful notion of "clique
617 mode", where directory authorities maintain TLS connections to
621 - In the util/threads test, no longer free the test_mutex before all
622 worker threads have finished. Bugfix on 0.2.1.6-alpha.
623 - The master thread could starve the worker threads quite badly on
624 certain systems, causing them to run only partially in the allowed
625 window. This resulted in test failures. Now the master thread sleeps
626 occasionally for a few microseconds while the two worker-threads
627 compete for the mutex. Bugfix on 0.2.0.1-alpha.
630 Changes in version 0.2.2.13-alpha - 2010-04-24
631 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
632 problems we've been seeing on relays, especially relays with their
633 DirPort open. If your relay has been crashing, or you turned it off
634 because it used too many resources, give this release a try.
637 - Teach relays to defend themselves from connection overload. Relays
638 now close idle circuits early if it looks like they were intended
639 for directory fetches. Relays are also more aggressive about closing
640 TLS connections that have no circuits on them. Such circuits are
641 unlikely to be re-used, and tens of thousands of them were piling
642 up at the fast relays, causing the relays to run out of sockets
643 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
644 their directory fetches over TLS).
647 - Finally get rid of the deprecated and now harmful notion of "clique
648 mode", where directory authorities maintain TLS connections to
650 - Directory authorities now do an immediate reachability check as soon
651 as they hear about a new relay. This change should slightly reduce
652 the time between setting up a relay and getting listed as running
653 in the consensus. It should also improve the time between setting
654 up a bridge and seeing use by bridge users.
655 - Directory authorities no longer launch a TLS connection to every
656 relay as they startup. Now that we have 2k+ descriptors cached,
657 the resulting network hiccup is becoming a burden. Besides,
658 authorities already avoid voting about Running for the first half
659 hour of their uptime.
662 Changes in version 0.2.2.12-alpha - 2010-04-20
663 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
664 handle and vote on descriptors. It was causing relays to drop out of
668 - Many relays have been falling out of the consensus lately because
669 not enough authorities know about their descriptor for them to get
670 a majority of votes. When we deprecated the v2 directory protocol,
671 we got rid of the only way that v3 authorities can hear from each
672 other about other descriptors. Now authorities examine every v3
673 vote for new descriptors, and fetch them from that authority. Bugfix
675 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
676 and a warning in or.h related to bandwidth_weight_rule_t that
677 prevented clean compile on OS X. Fixes bug 1363; bugfix on
679 - Fix a segfault on relays when DirReqStatistics is enabled
680 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
684 - Demote a confusing TLS warning that relay operators might get when
685 someone tries to talk to their OrPort. It is neither the operator's
686 fault nor can they do anything about it. Fixes bug 1364; bugfix
690 Changes in version 0.2.2.11-alpha - 2010-04-15
691 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
692 libraries that was causing some relays to drop out of the consensus.
695 - Directory mirrors were fetching relay descriptors only from v2
696 directory authorities, rather than v3 authorities like they should.
697 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
698 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
699 - Fix a parsing error that made every possible value of
700 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
701 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
702 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
703 about the option without breaking older ones.
704 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
705 that claim to be earlier than 0.9.8m, but which have in reality
706 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
707 behavior. Possible fix for some cases of bug 1346.
710 - Experiment with a more aggressive approach to preventing clients
711 from making one-hop exit streams. Exit relays who want to try it
712 out can set "RefuseUnknownExits 1" in their torrc, and then look
713 for "Attempt by %s to open a stream" log messages. Let us know
715 - Add support for statically linking zlib by specifying
716 --enable-static-zlib, to go with our support for statically linking
717 openssl and libevent. Resolves bug 1358.
720 - Fix a segfault that happens whenever a Tor client that is using
721 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
723 - When we cleaned up the contrib/tor-exit-notice.html file, we left
724 out the first line. Fixes bug 1295.
725 - When building the manpage from a tarball, we required asciidoc, but
726 the asciidoc -> roff/html conversion was already done for the
727 tarball. Make 'make' complain only when we need asciidoc (either
728 because we're compiling directly from git, or because we altered
729 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
730 - When none of the directory authorities vote on any params, Tor
731 segfaulted when trying to make the consensus from the votes. We
732 didn't trigger the bug in practice, because authorities do include
733 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
736 - In the util/threads test, no longer free the test_mutex before all
737 worker threads have finished. Bugfix on 0.2.1.6-alpha.
738 - The master thread could starve the worker threads quite badly on
739 certain systems, causing them to run only partially in the allowed
740 window. This resulted in test failures. Now the master thread sleeps
741 occasionally for a few microseconds while the two worker-threads
742 compete for the mutex. Bugfix on 0.2.0.1-alpha.
745 Changes in version 0.2.2.10-alpha - 2010-03-07
746 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
747 could prevent relays from guessing their IP address correctly. It also
748 starts the groundwork for another client-side performance boost, since
749 currently we're not making efficient use of relays that have both the
750 Guard flag and the Exit flag.
753 - Fix a regression from our patch for bug 1244 that caused relays
754 to guess their IP address incorrectly if they didn't set Address
755 in their torrc and/or their address fails to resolve. Bugfix on
756 0.2.2.9-alpha; fixes bug 1269.
758 o Major features (performance):
759 - Directory authorities now compute consensus weightings that instruct
760 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
761 and no flag. Clients that use these weightings will distribute
762 network load more evenly across these different relay types. The
763 weightings are in the consensus so we can change them globally in
764 the future. Extra thanks to "outofwords" for finding some nasty
765 security bugs in the first implementation of this feature.
767 o Minor features (performance):
768 - Always perform router selections using weighted relay bandwidth,
769 even if we don't need a high capacity circuit at the time. Non-fast
770 circuits now only differ from fast ones in that they can use relays
771 not marked with the Fast flag. This "feature" could turn out to
772 be a horrible bug; we should investigate more before it goes into
776 - Allow disabling building of the manpages. Skipping the manpage
777 speeds up the build considerably.
779 o Minor bugfixes (on 0.2.2.x):
780 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
781 Bugfix on 0.2.2.9-alpha.
782 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
783 config option. Bugfix on 0.2.2.7-alpha.
784 - Ship the asciidoc-helper file in the tarball, so that people can
785 build from source if they want to, and touching the .1.txt files
786 doesn't break the build. Bugfix on 0.2.2.9-alpha.
788 o Minor bugfixes (on 0.2.1.x or earlier):
789 - Fix a dereference-then-NULL-check sequence when publishing
790 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
792 - Fix another dereference-then-NULL-check sequence. Bugfix on
793 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
794 - Make sure we treat potentially not NUL-terminated strings correctly.
795 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
797 o Code simplifications and refactoring:
798 - Fix some urls in the exit notice file and make it XHTML1.1 strict
799 compliant. Based on a patch from Christian Kujau.
800 - Don't use sed in asciidoc-helper anymore.
801 - Make the build process fail if asciidoc cannot be found and
802 building with asciidoc isn't disabled.
805 Changes in version 0.2.2.9-alpha - 2010-02-22
806 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
807 location of a directory authority, and cleans up a bunch of small bugs.
809 o Directory authority changes:
810 - Change IP address for dannenberg (v3 directory authority), and
811 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
812 service directory authority) from the list.
815 - Make Tor work again on the latest OS X: when deciding whether to
816 use strange flags to turn TLS renegotiation on, detect the OpenSSL
817 version at run-time, not compile time. We need to do this because
818 Apple doesn't update its dev-tools headers when it updates its
819 libraries in a security patch.
820 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
821 that could happen on 32-bit platforms with 64-bit time_t. Also fix
822 a memory leak when requesting a hidden service descriptor we've
823 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
825 - Authorities could be tricked into giving out the Exit flag to relays
826 that didn't allow exiting to any ports. This bug could screw
827 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
828 1238. Bug discovered by Martin Kowalczyk.
829 - When freeing a session key, zero it out completely. We only zeroed
830 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
831 patched by ekir. Fixes bug 1254.
834 - Fix static compilation by listing the openssl libraries in the right
835 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
836 - Resume handling .exit hostnames in a special way: originally we
837 stripped the .exit part and used the requested exit relay. In
838 0.2.2.1-alpha we stopped treating them in any special way, meaning
839 if you use a .exit address then Tor will pass it on to the exit
840 relay. Now we reject the .exit stream outright, since that behavior
841 might be more expected by the user. Found and diagnosed by Scott
842 Bennett and Downie on or-talk.
843 - Don't spam the controller with events when we have no file
844 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
845 for log messages was already solved from bug 748.)
846 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
848 - Make the DNSPort option work with libevent 2.x. Don't alter the
849 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
850 - Emit a GUARD DROPPED controller event for a case we missed.
851 - Make more fields in the controller protocol case-insensitive, since
852 control-spec.txt said they were.
853 - Refactor resolve_my_address() to not use gethostbyname() anymore.
854 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
855 - Fix a spec conformance issue: the network-status-version token
856 must be the first token in a v3 consensus or vote. Discovered by
857 parakeep. Bugfix on 0.2.0.3-alpha.
859 o Code simplifications and refactoring:
860 - Generate our manpage and HTML documentation using Asciidoc. This
861 change should make it easier to maintain the documentation, and
863 - Remove the --enable-iphone option. According to reports from Marco
864 Bonetti, Tor builds fine without any special tweaking on recent
866 - Removed some unnecessary files from the source distribution. The
867 AUTHORS file has now been merged into the people page on the
868 website. The roadmaps and design doc can now be found in the
869 projects directory in svn.
870 - Enabled various circuit build timeout constants to be controlled
871 by consensus parameters. Also set better defaults for these
872 parameters based on experimentation on broadband and simulated
876 - The 'EXTENDCIRCUIT' control port command can now be used with
877 a circ id of 0 and no path. This feature will cause Tor to build
878 a new 'fast' general purpose circuit using its own path selection
880 - Added a BUILDTIMEOUT_SET controller event to describe changes
881 to the circuit build timeout.
882 - Future-proof the controller protocol a bit by ignoring keyword
883 arguments we do not recognize.
884 - Expand homedirs passed to tor-checkkey. This should silence a
885 coverity complaint about passing a user-supplied string into
886 open() without checking it.
889 Changes in version 0.2.1.25 - 2010-03-16
890 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
891 prevent relays from guessing their IP address correctly. It also fixes
892 several minor potential security bugs.
895 - Fix a regression from our patch for bug 1244 that caused relays
896 to guess their IP address incorrectly if they didn't set Address
897 in their torrc and/or their address fails to resolve. Bugfix on
898 0.2.1.23; fixes bug 1269.
899 - When freeing a session key, zero it out completely. We only zeroed
900 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
901 patched by ekir. Fixes bug 1254.
904 - Fix a dereference-then-NULL-check sequence when publishing
905 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
907 - Fix another dereference-then-NULL-check sequence. Bugfix on
908 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
909 - Make sure we treat potentially not NUL-terminated strings correctly.
910 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
914 Changes in version 0.2.1.24 - 2010-02-21
915 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
919 - Work correctly out-of-the-box with even more vendor-patched versions
920 of OpenSSL. In particular, make it so Debian and OS X don't need
921 customized patches to run/build.
924 Changes in version 0.2.1.23 - 2010-02-13
925 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
926 again on the latest OS X, and updates the location of a directory
929 o Major bugfixes (performance):
930 - We were selecting our guards uniformly at random, and then weighting
931 which of our guards we'd use uniformly at random. This imbalance
932 meant that Tor clients were severely limited on throughput (and
933 probably latency too) by the first hop in their circuit. Now we
934 select guards weighted by currently advertised bandwidth. We also
935 automatically discard guards picked using the old algorithm. Fixes
936 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
939 - Make Tor work again on the latest OS X: when deciding whether to
940 use strange flags to turn TLS renegotiation on, detect the OpenSSL
941 version at run-time, not compile time. We need to do this because
942 Apple doesn't update its dev-tools headers when it updates its
943 libraries in a security patch.
944 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
945 that could happen on 32-bit platforms with 64-bit time_t. Also fix
946 a memory leak when requesting a hidden service descriptor we've
947 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
950 o Directory authority changes:
951 - Change IP address for dannenberg (v3 directory authority), and
952 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
953 service directory authority) from the list.
956 - Refactor resolve_my_address() to not use gethostbyname() anymore.
957 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
960 - Avoid a mad rush at the beginning of each month when each client
961 rotates half of its guards. Instead we spread the rotation out
962 throughout the month, but we still avoid leaving a precise timestamp
963 in the state file about when we first picked the guard. Improves
964 over the behavior introduced in 0.1.2.17.
967 Changes in version 0.2.2.8-alpha - 2010-01-26
968 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
969 causing bridge relays to disappear. If you're running a bridge,
973 - Fix a memory corruption bug on bridges that occured during the
974 inclusion of stats data in extra-info descriptors. Also fix the
975 interface for geoip_get_bridge_stats* to prevent similar bugs in
976 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
977 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
980 - Ignore OutboundBindAddress when connecting to localhost.
981 Connections to localhost need to come _from_ localhost, or else
982 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
986 Changes in version 0.2.2.7-alpha - 2010-01-19
987 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
988 as laying the groundwork for further relay-side performance fixes. It
989 also starts cleaning up client behavior with respect to the EntryNodes,
990 ExitNodes, and StrictNodes config options.
992 This release also rotates two directory authority keys, due to a
993 security breach of some of the Torproject servers.
995 o Directory authority changes:
996 - Rotate keys (both v3 identity and relay identity) for moria1
999 o Major features (performance):
1000 - We were selecting our guards uniformly at random, and then weighting
1001 which of our guards we'd use uniformly at random. This imbalance
1002 meant that Tor clients were severely limited on throughput (and
1003 probably latency too) by the first hop in their circuit. Now we
1004 select guards weighted by currently advertised bandwidth. We also
1005 automatically discard guards picked using the old algorithm. Fixes
1006 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
1007 - When choosing which cells to relay first, relays can now favor
1008 circuits that have been quiet recently, to provide lower latency
1009 for low-volume circuits. By default, relays enable or disable this
1010 feature based on a setting in the consensus. You can override
1011 this default by using the new "CircuitPriorityHalflife" config
1012 option. Design and code by Ian Goldberg, Can Tang, and Chris
1014 - Add separate per-conn write limiting to go with the per-conn read
1015 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
1016 but never per-conn write limits.
1017 - New consensus params "bwconnrate" and "bwconnburst" to let us
1018 rate-limit client connections as they enter the network. It's
1019 controlled in the consensus so we can turn it on and off for
1020 experiments. It's starting out off. Based on proposal 163.
1022 o Major features (relay selection options):
1023 - Switch to a StrictNodes config option, rather than the previous
1024 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
1025 "StrictExcludeNodes" option.
1026 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
1027 change during a config reload, mark and discard all our origin
1028 circuits. This fix should address edge cases where we change the
1029 config options and but then choose a circuit that we created before
1031 - If EntryNodes or ExitNodes are set, be more willing to use an
1032 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
1034 - Make EntryNodes config option much more aggressive even when
1035 StrictNodes is not set. Before it would prepend your requested
1036 entrynodes to your list of guard nodes, but feel free to use others
1037 after that. Now it chooses only from your EntryNodes if any of
1038 those are available, and only falls back to others if a) they're
1039 all down and b) StrictNodes is not set.
1040 - Now we refresh your entry guards from EntryNodes at each consensus
1041 fetch -- rather than just at startup and then they slowly rot as
1042 the network changes.
1045 - Stop bridge directory authorities from answering dbg-stability.txt
1046 directory queries, which would let people fetch a list of all
1047 bridge identities they track. Bugfix on 0.2.1.6-alpha.
1050 - Log a notice when we get a new control connection. Now it's easier
1051 for security-conscious users to recognize when a local application
1052 is knocking on their controller door. Suggested by bug 1196.
1053 - New config option "CircuitStreamTimeout" to override our internal
1054 timeout schedule for how many seconds until we detach a stream from
1055 a circuit and try a new circuit. If your network is particularly
1056 slow, you might want to set this to a number like 60.
1057 - New controller command "getinfo config-text". It returns the
1058 contents that Tor would write if you send it a SAVECONF command,
1059 so the controller can write the file to disk itself.
1060 - New options for SafeLogging to allow scrubbing only log messages
1061 generated while acting as a relay.
1062 - Ship the bridges spec file in the tarball too.
1063 - Avoid a mad rush at the beginning of each month when each client
1064 rotates half of its guards. Instead we spread the rotation out
1065 throughout the month, but we still avoid leaving a precise timestamp
1066 in the state file about when we first picked the guard. Improves
1067 over the behavior introduced in 0.1.2.17.
1069 o Minor bugfixes (compiling):
1070 - Fix compilation on OS X 10.3, which has a stub mlockall() but
1071 hides it. Bugfix on 0.2.2.6-alpha.
1072 - Fix compilation on Solaris by removing support for the
1073 DisableAllSwap config option. Solaris doesn't have an rlimit for
1074 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
1077 o Minor bugfixes (crashes):
1078 - Do not segfault when writing buffer stats when we haven't observed
1079 a single circuit to report about. Found by Fabian Lanze. Bugfix on
1081 - If we're in the pathological case where there's no exit bandwidth
1082 but there is non-exit bandwidth, or no guard bandwidth but there
1083 is non-guard bandwidth, don't crash during path selection. Bugfix
1085 - Fix an impossible-to-actually-trigger buffer overflow in relay
1086 descriptor generation. Bugfix on 0.1.0.15.
1088 o Minor bugfixes (privacy):
1089 - Fix an instance where a Tor directory mirror might accidentally
1090 log the IP address of a misbehaving Tor client. Bugfix on
1092 - Don't list Windows capabilities in relay descriptors. We never made
1093 use of them, and maybe it's a bad idea to publish them. Bugfix
1096 o Minor bugfixes (other):
1097 - Resolve an edge case in path weighting that could make us misweight
1098 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
1099 - Fix statistics on client numbers by country as seen by bridges that
1100 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
1101 intervals instead of variable 12-to-48-hour intervals.
1102 - After we free an internal connection structure, overwrite it
1103 with a different memory value than we use for overwriting a freed
1104 internal circuit structure. Should help with debugging. Suggested
1106 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
1110 - Remove the HSAuthorityRecordStats option that version 0 hidden
1111 service authorities could have used to track statistics of overall
1112 hidden service usage.
1115 Changes in version 0.2.1.22 - 2010-01-19
1116 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
1117 authorities -- it would tell you its whole history of bridge descriptors
1118 if you make the right directory request. This stable update also
1119 rotates two of the seven v3 directory authority keys and locations.
1121 o Directory authority changes:
1122 - Rotate keys (both v3 identity and relay identity) for moria1
1126 - Stop bridge directory authorities from answering dbg-stability.txt
1127 directory queries, which would let people fetch a list of all
1128 bridge identities they track. Bugfix on 0.2.1.6-alpha.
1131 Changes in version 0.2.1.21 - 2009-12-21
1132 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
1133 library. If you use Tor on Linux / Unix and you're getting SSL
1134 renegotiation errors, upgrading should help. We also recommend an
1135 upgrade if you're an exit relay.
1138 - Work around a security feature in OpenSSL 0.9.8l that prevents our
1139 handshake from working unless we explicitly tell OpenSSL that we
1140 are using SSL renegotiation safely. We are, of course, but OpenSSL
1141 0.9.8l won't work unless we say we are.
1142 - Avoid crashing if the client is trying to upload many bytes and the
1143 circuit gets torn down at the same time, or if the flip side
1144 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
1147 - Do not refuse to learn about authority certs and v2 networkstatus
1148 documents that are older than the latest consensus. This bug might
1149 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
1150 Spotted and fixed by xmux.
1151 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
1152 trigger platform-specific option misparsing case found by Coverity
1154 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
1155 trigger assert. Fixes bug 1173.
1158 Changes in version 0.2.2.6-alpha - 2009-11-19
1159 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
1160 support for the new lower-footprint "microdescriptor" directory design,
1161 future-proofing our consensus format against new hash functions or
1162 other changes, and an Android port. It also makes Tor compatible with
1163 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
1166 - Directory authorities can now create, vote on, and serve multiple
1167 parallel formats of directory data as part of their voting process.
1168 Partially implements Proposal 162: "Publish the consensus in
1170 - Directory authorities can now agree on and publish small summaries
1171 of router information that clients can use in place of regular
1172 server descriptors. This transition will eventually allow clients
1173 to use far less bandwidth for downloading information about the
1174 network. Begins the implementation of Proposal 158: "Clients
1175 download consensus + microdescriptors".
1176 - The directory voting system is now extensible to use multiple hash
1177 algorithms for signatures and resource selection. Newer formats
1178 are signed with SHA256, with a possibility for moving to a better
1179 hash algorithm in the future.
1180 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
1181 current and future memory pages via mlockall(). On supported
1182 platforms (modern Linux and probably BSD but not Windows or OS X),
1183 this should effectively disable any and all attempts to page out
1184 memory. This option requires that you start your Tor as root --
1185 if you use DisableAllSwap, please consider using the User option
1186 to properly reduce the privileges of your Tor.
1187 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
1188 to help Tor build correctly for Android phones.
1191 - Work around a security feature in OpenSSL 0.9.8l that prevents our
1192 handshake from working unless we explicitly tell OpenSSL that we
1193 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
1194 won't work unless we say we are.
1197 - Fix a crash bug when trying to initialize the evdns module in
1198 Libevent 2. Bugfix on 0.2.1.16-rc.
1199 - Stop logging at severity 'warn' when some other Tor client tries
1200 to establish a circuit with us using weak DH keys. It's a protocol
1201 violation, but that doesn't mean ordinary users need to hear about
1202 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
1203 - Do not refuse to learn about authority certs and v2 networkstatus
1204 documents that are older than the latest consensus. This bug might
1205 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
1206 Spotted and fixed by xmux.
1207 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
1208 - If all authorities restart at once right before a consensus vote,
1209 nobody will vote about "Running", and clients will get a consensus
1210 with no usable relays. Instead, authorities refuse to build a
1211 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
1212 - If your relay can't keep up with the number of incoming create
1213 cells, it would log one warning per failure into your logs. Limit
1214 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
1215 - Bridges now use "reject *:*" as their default exit policy. Bugfix
1216 on 0.2.0.3-alpha; fixes bug 1113.
1217 - Fix a memory leak on directory authorities during voting that was
1218 introduced in 0.2.2.1-alpha. Found via valgrind.
1221 Changes in version 0.2.1.20 - 2009-10-15
1222 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
1223 services at once, prepares for more performance improvements, and
1224 fixes a bunch of smaller bugs.
1226 The Windows and OS X bundles also include a more recent Vidalia,
1227 and switch from Privoxy to Polipo.
1229 The OS X installers are now drag and drop. It's best to un-install
1230 Tor/Vidalia and then install this new bundle, rather than upgrade. If
1231 you want to upgrade, you'll need to update the paths for Tor and Polipo
1232 in the Vidalia Settings window.
1235 - Send circuit or stream sendme cells when our window has decreased
1236 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1237 by Karsten when testing the "reduce circuit window" performance
1238 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1239 before the release of Tor 0.0.0. This is the new winner of the
1241 - Fix a remotely triggerable memory leak when a consensus document
1242 contains more than one signature from the same voter. Bugfix on
1244 - Avoid segfault in rare cases when finishing an introduction circuit
1245 as a client and finding out that we don't have an introduction key
1246 for it. Fixes bug 1073. Reported by Aaron Swartz.
1249 - Tor now reads the "circwindow" parameter out of the consensus,
1250 and uses that value for its circuit package window rather than the
1251 default of 1000 cells. Begins the implementation of proposal 168.
1253 o New directory authorities:
1254 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1256 - Move moria1 and tonga to alternate IP addresses.
1259 - Fix a signed/unsigned compile warning in 0.2.1.19.
1260 - Fix possible segmentation fault on directory authorities. Bugfix on
1262 - Fix an extremely rare infinite recursion bug that could occur if
1263 we tried to log a message after shutting down the log subsystem.
1264 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1265 - Fix an obscure bug where hidden services on 64-bit big-endian
1266 systems might mis-read the timestamp in v3 introduce cells, and
1267 refuse to connect back to the client. Discovered by "rotor".
1268 Bugfix on 0.2.1.6-alpha.
1269 - We were triggering a CLOCK_SKEW controller status event whenever
1270 we connect via the v2 connection protocol to any relay that has
1271 a wrong clock. Instead, we should only inform the controller when
1272 it's a trusted authority that claims our clock is wrong. Bugfix
1273 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1274 - We were telling the controller about CHECKING_REACHABILITY and
1275 REACHABILITY_FAILED status events whenever we launch a testing
1276 circuit or notice that one has failed. Instead, only tell the
1277 controller when we want to inform the user of overall success or
1278 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1280 - Don't warn when we're using a circuit that ends with a node
1281 excluded in ExcludeExitNodes, but the circuit is not used to access
1282 the outside world. This should help fix bug 1090. Bugfix on
1284 - Work around a small memory leak in some versions of OpenSSL that
1285 stopped the memory used by the hostname TLS extension from being
1289 - Add a "getinfo status/accepted-server-descriptor" controller
1290 command, which is the recommended way for controllers to learn
1291 whether our server descriptor has been successfully received by at
1292 least on directory authority. Un-recommend good-server-descriptor
1293 getinfo and status events until we have a better design for them.
1296 Changes in version 0.2.2.5-alpha - 2009-10-11
1297 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
1300 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
1302 o New directory authorities:
1303 - Move dizum to an alternate IP address.
1306 Changes in version 0.2.2.4-alpha - 2009-10-10
1307 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
1308 introduces a new unit test framework, shifts directry authority
1309 addresses around to reduce the impact from recent blocking events,
1310 and fixes a few smaller bugs.
1313 - Fix several more asserts in the circuit_build_times code, for
1314 example one that causes Tor to fail to start once we have
1315 accumulated 5000 build times in the state file. Bugfixes on
1316 0.2.2.2-alpha; fixes bug 1108.
1318 o New directory authorities:
1319 - Move moria1 and Tonga to alternate IP addresses.
1322 - Log SSL state transitions at debug level during handshake, and
1323 include SSL states in error messages. This may help debug future
1324 SSL handshake issues.
1325 - Add a new "Handshake" log domain for activities that happen
1326 during the TLS handshake.
1327 - Revert to the "June 3 2009" ip-to-country file. The September one
1328 seems to have removed most US IP addresses.
1329 - Directory authorities now reject Tor relays with versions less than
1330 0.1.2.14. This step cuts out four relays from the current network,
1331 none of which are very big.
1334 - Fix a couple of smaller issues with gathering statistics. Bugfixes
1336 - Fix two memory leaks in the error case of
1337 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
1338 - Don't count one-hop circuits when we're estimating how long it
1339 takes circuits to build on average. Otherwise we'll set our circuit
1340 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
1341 - Directory authorities no longer change their opinion of, or vote on,
1342 whether a router is Running, unless they have themselves been
1343 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
1346 o Code simplifications and refactoring:
1347 - Revise our unit tests to use the "tinytest" framework, so we
1348 can run tests in their own processes, have smarter setup/teardown
1349 code, and so on. The unit test code has moved to its own
1350 subdirectory, and has been split into multiple modules.
1353 Changes in version 0.2.2.3-alpha - 2009-09-23
1354 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
1357 - Fix an overzealous assert in our new circuit build timeout code.
1358 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
1361 - If the networkstatus consensus tells us that we should use a
1362 negative circuit package window, ignore it. Otherwise we'll
1363 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
1366 Changes in version 0.2.2.2-alpha - 2009-09-21
1367 Tor 0.2.2.2-alpha introduces our latest performance improvement for
1368 clients: Tor tracks the average time it takes to build a circuit, and
1369 avoids using circuits that take too long to build. For fast connections,
1370 this feature can cut your expected latency in half. For slow or flaky
1371 connections, it could ruin your Tor experience. Let us know if it does!
1374 - Tor now tracks how long it takes to build client-side circuits
1375 over time, and adapts its timeout to local network performance.
1376 Since a circuit that takes a long time to build will also provide
1377 bad performance, we get significant latency improvements by
1378 discarding the slowest 20% of circuits. Specifically, Tor creates
1379 circuits more aggressively than usual until it has enough data
1380 points for a good timeout estimate. Implements proposal 151.
1381 We are especially looking for reports (good and bad) from users with
1382 both EDGE and broadband connections that can move from broadband
1383 to EDGE and find out if the build-time data in the .tor/state gets
1384 reset without loss of Tor usability. You should also see a notice
1385 log message telling you that Tor has reset its timeout.
1386 - Directory authorities can now vote on arbitary integer values as
1387 part of the consensus process. This is designed to help set
1388 network-wide parameters. Implements proposal 167.
1389 - Tor now reads the "circwindow" parameter out of the consensus,
1390 and uses that value for its circuit package window rather than the
1391 default of 1000 cells. Begins the implementation of proposal 168.
1394 - Fix a remotely triggerable memory leak when a consensus document
1395 contains more than one signature from the same voter. Bugfix on
1399 - Fix an extremely rare infinite recursion bug that could occur if
1400 we tried to log a message after shutting down the log subsystem.
1401 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1402 - Fix parsing for memory or time units given without a space between
1403 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
1404 - A networkstatus vote must contain exactly one signature. Spec
1405 conformance issue. Bugfix on 0.2.0.3-alpha.
1406 - Fix an obscure bug where hidden services on 64-bit big-endian
1407 systems might mis-read the timestamp in v3 introduce cells, and
1408 refuse to connect back to the client. Discovered by "rotor".
1409 Bugfix on 0.2.1.6-alpha.
1410 - We were triggering a CLOCK_SKEW controller status event whenever
1411 we connect via the v2 connection protocol to any relay that has
1412 a wrong clock. Instead, we should only inform the controller when
1413 it's a trusted authority that claims our clock is wrong. Bugfix
1414 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1415 - We were telling the controller about CHECKING_REACHABILITY and
1416 REACHABILITY_FAILED status events whenever we launch a testing
1417 circuit or notice that one has failed. Instead, only tell the
1418 controller when we want to inform the user of overall success or
1419 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1421 - Don't warn when we're using a circuit that ends with a node
1422 excluded in ExcludeExitNodes, but the circuit is not used to access
1423 the outside world. This should help fix bug 1090, but more problems
1424 remain. Bugfix on 0.2.1.6-alpha.
1425 - Work around a small memory leak in some versions of OpenSSL that
1426 stopped the memory used by the hostname TLS extension from being
1428 - Make our 'torify' script more portable; if we have only one of
1429 'torsocks' or 'tsocks' installed, don't complain to the user;
1430 and explain our warning about tsocks better.
1433 - Add a "getinfo status/accepted-server-descriptor" controller
1434 command, which is the recommended way for controllers to learn
1435 whether our server descriptor has been successfully received by at
1436 least on directory authority. Un-recommend good-server-descriptor
1437 getinfo and status events until we have a better design for them.
1438 - Update to the "September 4 2009" ip-to-country file.
1441 Changes in version 0.2.2.1-alpha - 2009-08-26
1442 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
1443 Tor clients to bootstrap on networks where only port 80 is reachable,
1444 makes it more straightforward to support hardware crypto accelerators,
1445 and starts the groundwork for gathering stats safely at relays.
1448 - Start the process of disabling ".exit" address notation, since it
1449 can be used for a variety of esoteric application-level attacks
1450 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
1453 o New directory authorities:
1454 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1458 - New AccelName and AccelDir options add support for dynamic OpenSSL
1459 hardware crypto acceleration engines.
1460 - Tor now supports tunneling all of its outgoing connections over
1461 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
1462 configuration options. Code by Christopher Davis.
1465 - Send circuit or stream sendme cells when our window has decreased
1466 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1467 by Karsten when testing the "reduce circuit window" performance
1468 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1469 before the release of Tor 0.0.0. This is the new winner of the
1472 o New options for gathering stats safely:
1473 - Directories that set "DirReqStatistics 1" write statistics on
1474 directory request to disk every 24 hours. As compared to the
1475 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
1476 1) stats are written to disk exactly every 24 hours; 2) estimated
1477 shares of v2 and v3 requests are determined as mean values, not at
1478 the end of a measurement period; 3) unresolved requests are listed
1479 with country code '??'; 4) directories also measure download times.
1480 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
1481 number of exit streams and transferred bytes per port to disk every
1483 - Relays that set "CellStatistics 1" write statistics on how long
1484 cells spend in their circuit queues to disk every 24 hours.
1485 - Entry nodes that set "EntryStatistics 1" write statistics on the
1486 rough number and origins of connecting clients to disk every 24
1488 - Relays that write any of the above statistics to disk and set
1489 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
1490 their extra-info documents.
1493 - New --digests command-line switch to output the digests of the
1494 source files Tor was built with.
1495 - The "torify" script now uses torsocks where available.
1496 - The memarea code now uses a sentinel value at the end of each area
1497 to make sure nothing writes beyond the end of an area. This might
1498 help debug some conceivable causes of bug 930.
1499 - Time and memory units in the configuration file can now be set to
1500 fractional units. For example, "2.5 GB" is now a valid value for
1502 - Certain Tor clients (such as those behind check.torproject.org) may
1503 want to fetch the consensus in an extra early manner. To enable this
1504 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
1505 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
1506 as only certain clients who must have this information sooner should
1508 - Instead of adding the svn revision to the Tor version string, report
1509 the git commit (when we're building from a git checkout).
1512 - If any the v3 certs we download are unparseable, we should actually
1513 notice the failure so we don't retry indefinitely. Bugfix on
1514 0.2.0.x; reported by "rotator".
1515 - If the cached cert file is unparseable, warn but don't exit.
1516 - Fix possible segmentation fault on directory authorities. Bugfix on
1518 - When Tor fails to parse a descriptor of any kind, dump it to disk.
1519 Might help diagnosing bug 1051.
1521 o Deprecated and removed features:
1522 - The controller no longer accepts the old obsolete "addr-mappings/"
1523 or "unregistered-servers-" GETINFO values.
1524 - Hidden services no longer publish version 0 descriptors, and clients
1525 do not request or use version 0 descriptors. However, the old hidden
1526 service authorities still accept and serve version 0 descriptors
1527 when contacted by older hidden services/clients.
1528 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1529 always on; using them is necessary for correct forward-compatible
1531 - Remove support for .noconnect style addresses. Nobody was using
1532 them, and they provided another avenue for detecting Tor users
1533 via application-level web tricks.
1535 o Packaging changes:
1536 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
1537 installer bundles. See
1538 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
1539 for details of what's new in Vidalia 0.2.3.
1540 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
1541 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
1542 configuration file, rather than the old Privoxy.
1543 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
1544 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
1545 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
1546 better compatibility with OS X 10.6, aka Snow Leopard.
1547 - OS X Vidalia Bundle: The multi-package installer is now replaced
1548 by a simple drag and drop to the /Applications folder. This change
1549 occurred with the upgrade to Vidalia 0.2.3.
1552 Changes in version 0.2.1.19 - 2009-07-28
1553 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
1554 services on Tor 0.2.1.3-alpha through 0.2.1.18.
1557 - Make accessing hidden services on 0.2.1.x work right again.
1558 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
1559 part of patch provided by "optimist".
1562 - When a relay/bridge is writing out its identity key fingerprint to
1563 the "fingerprint" file and to its logs, write it without spaces. Now
1564 it will look like the fingerprints in our bridges documentation,
1565 and confuse fewer users.
1568 - Relays no longer publish a new server descriptor if they change
1569 their MaxAdvertisedBandwidth config option but it doesn't end up
1570 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
1571 fixes bug 1026. Patch from Sebastian.
1572 - Avoid leaking memory every time we get a create cell but we have
1573 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
1574 fixes bug 1034. Reported by BarkerJr.
1577 Changes in version 0.2.1.18 - 2009-07-24
1578 Tor 0.2.1.18 lays the foundations for performance improvements,
1579 adds status events to help users diagnose bootstrap problems, adds
1580 optional authentication/authorization for hidden services, fixes a
1581 variety of potential anonymity problems, and includes a huge pile of
1582 other features and bug fixes.
1585 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
1588 Changes in version 0.2.1.17-rc - 2009-07-07
1589 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
1590 candidate for the 0.2.1.x series. It lays the groundwork for further
1591 client performance improvements, and also fixes a big bug with directory
1592 authorities that were causing them to assign Guard and Stable flags
1595 The Windows bundles also finally include the geoip database that we
1596 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
1597 should actually install Torbutton rather than giving you a cryptic
1598 failure message (oops).
1601 - Clients now use the bandwidth values in the consensus, rather than
1602 the bandwidth values in each relay descriptor. This approach opens
1603 the door to more accurate bandwidth estimates once the directory
1604 authorities start doing active measurements. Implements more of
1608 - When Tor clients restart after 1-5 days, they discard all their
1609 cached descriptors as too old, but they still use the cached
1610 consensus document. This approach is good for robustness, but
1611 bad for performance: since they don't know any bandwidths, they
1612 end up choosing at random rather than weighting their choice by
1613 speed. Fixed by the above feature of putting bandwidths in the
1614 consensus. Bugfix on 0.2.0.x.
1615 - Directory authorities were neglecting to mark relays down in their
1616 internal histories if the relays fall off the routerlist without
1617 ever being found unreachable. So there were relays in the histories
1618 that haven't been seen for eight months, and are listed as being
1619 up for eight months. This wreaked havoc on the "median wfu"
1620 and "median mtbf" calculations, in turn making Guard and Stable
1621 flags very wrong, hurting network performance. Fixes bugs 696 and
1622 969. Bugfix on 0.2.0.6-alpha.
1625 - Serve the DirPortFrontPage page even when we have been approaching
1626 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
1627 - The control port would close the connection before flushing long
1628 replies, such as the network consensus, if a QUIT command was issued
1629 before the reply had completed. Now, the control port flushes all
1630 pending replies before closing the connection. Also fixed a spurious
1631 warning when a QUIT command is issued after a malformed or rejected
1632 AUTHENTICATE command, but before the connection was closed. Patch
1633 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
1634 - When we can't find an intro key for a v2 hidden service descriptor,
1635 fall back to the v0 hidden service descriptor and log a bug message.
1636 Workaround for bug 1024.
1637 - Fix a log message that did not respect the SafeLogging option.
1641 - If we're a relay and we change our IP address, be more verbose
1642 about the reason that made us change. Should help track down
1643 further bugs for relays on dynamic IP addresses.
1646 Changes in version 0.2.0.35 - 2009-06-24
1648 - Avoid crashing in the presence of certain malformed descriptors.
1649 Found by lark, and by automated fuzzing.
1650 - Fix an edge case where a malicious exit relay could convince a
1651 controller that the client's DNS question resolves to an internal IP
1652 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1655 - Finally fix the bug where dynamic-IP relays disappear when their
1656 IP address changes: directory mirrors were mistakenly telling
1657 them their old address if they asked via begin_dir, so they
1658 never got an accurate answer about their new address, so they
1659 just vanished after a day. For belt-and-suspenders, relays that
1660 don't set Address in their config now avoid using begin_dir for
1661 all direct connections. Should fix bugs 827, 883, and 900.
1662 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1663 that would occur on some exit nodes when DNS failures and timeouts
1664 occurred in certain patterns. Fix for bug 957.
1667 - When starting with a cache over a few days old, do not leak
1668 memory for the obsolete router descriptors in it. Bugfix on
1669 0.2.0.33; fixes bug 672.
1670 - Hidden service clients didn't use a cached service descriptor that
1671 was older than 15 minutes, but wouldn't fetch a new one either,
1672 because there was already one in the cache. Now, fetch a v2
1673 descriptor unless the same descriptor was added to the cache within
1674 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1677 Changes in version 0.2.1.16-rc - 2009-06-20
1678 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
1679 a bunch of minor bugs.
1682 - Fix an edge case where a malicious exit relay could convince a
1683 controller that the client's DNS question resolves to an internal IP
1684 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1686 o Major performance improvements (on 0.2.0.x):
1687 - Disable and refactor some debugging checks that forced a linear scan
1688 over the whole server-side DNS cache. These accounted for over 50%
1689 of CPU time on a relatively busy exit node's gprof profile. Found
1691 - Disable some debugging checks that appeared in exit node profile
1695 - Update to the "June 3 2009" ip-to-country file.
1696 - Do not have tor-resolve automatically refuse all .onion addresses;
1697 if AutomapHostsOnResolve is set in your torrc, this will work fine.
1699 o Minor bugfixes (on 0.2.0.x):
1700 - Log correct error messages for DNS-related network errors on
1702 - Fix a race condition that could cause crashes or memory corruption
1703 when running as a server with a controller listening for log
1705 - Avoid crashing when we have a policy specified in a DirPolicy or
1706 SocksPolicy or ReachableAddresses option with ports set on it,
1707 and we re-load the policy. May fix bug 996.
1708 - Hidden service clients didn't use a cached service descriptor that
1709 was older than 15 minutes, but wouldn't fetch a new one either,
1710 because there was already one in the cache. Now, fetch a v2
1711 descriptor unless the same descriptor was added to the cache within
1712 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1714 o Minor bugfixes (on 0.2.1.x):
1715 - Don't warn users about low port and hibernation mix when they
1716 provide a *ListenAddress directive to fix that. Bugfix on
1718 - When switching back and forth between bridge mode, do not start
1719 gathering GeoIP data until two hours have passed.
1720 - Do not complain that the user has requested an excluded node as
1721 an exit when the node is not really an exit. This could happen
1722 because the circuit was for testing, or an introduction point.
1726 Changes in version 0.2.1.15-rc - 2009-05-25
1727 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
1728 series. It fixes a major bug on fast exit relays, as well as a variety
1731 o Major bugfixes (on 0.2.0.x):
1732 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1733 that would occur on some exit nodes when DNS failures and timeouts
1734 occurred in certain patterns. Fix for bug 957.
1736 o Minor bugfixes (on 0.2.0.x):
1737 - Actually return -1 in the error case for read_bandwidth_usage().
1738 Harmless bug, since we currently don't care about the return value
1739 anywhere. Bugfix on 0.2.0.9-alpha.
1740 - Provide a more useful log message if bug 977 (related to buffer
1741 freelists) ever reappears, and do not crash right away.
1742 - Fix an assertion failure on 64-bit platforms when we allocated
1743 memory right up to the end of a memarea, then realigned the memory
1744 one step beyond the end. Fixes a possible cause of bug 930.
1745 - Protect the count of open sockets with a mutex, so we can't
1746 corrupt it when two threads are closing or opening sockets at once.
1747 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
1748 - Don't allow a bridge to publish its router descriptor to a
1749 non-bridge directory authority. Fixes part of bug 932.
1750 - When we change to or from being a bridge, reset our counts of
1751 client usage by country. Fixes bug 932.
1752 - Fix a bug that made stream bandwidth get misreported to the
1754 - Stop using malloc_usable_size() to use more area than we had
1755 actually allocated: it was safe, but made valgrind really unhappy.
1756 - Fix a memory leak when v3 directory authorities load their keys
1757 and cert from disk. Bugfix on 0.2.0.1-alpha.
1759 o Minor bugfixes (on 0.2.1.x):
1760 - Fix use of freed memory when deciding to mark a non-addable
1761 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
1764 Changes in version 0.2.1.14-rc - 2009-04-12
1765 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
1766 series. It begins fixing some major performance problems, and also
1767 finally addresses the bug that was causing relays on dynamic IP
1768 addresses to fall out of the directory.
1771 - Clients replace entry guards that were chosen more than a few months
1772 ago. This change should significantly improve client performance,
1773 especially once more people upgrade, since relays that have been
1774 a guard for a long time are currently overloaded.
1776 o Major bugfixes (on 0.2.0):
1777 - Finally fix the bug where dynamic-IP relays disappear when their
1778 IP address changes: directory mirrors were mistakenly telling
1779 them their old address if they asked via begin_dir, so they
1780 never got an accurate answer about their new address, so they
1781 just vanished after a day. For belt-and-suspenders, relays that
1782 don't set Address in their config now avoid using begin_dir for
1783 all direct connections. Should fix bugs 827, 883, and 900.
1784 - Relays were falling out of the networkstatus consensus for
1785 part of a day if they changed their local config but the
1786 authorities discarded their new descriptor as "not sufficiently
1787 different". Now directory authorities accept a descriptor as changed
1788 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
1790 - Avoid crashing in the presence of certain malformed descriptors.
1791 Found by lark, and by automated fuzzing.
1794 - When generating circuit events with verbose nicknames for
1795 controllers, try harder to look up nicknames for routers on a
1796 circuit. (Previously, we would look in the router descriptors we had
1797 for nicknames, but not in the consensus.) Partial fix for bug 941.
1798 - If the bridge config line doesn't specify a port, assume 443.
1799 This makes bridge lines a bit smaller and easier for users to
1801 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
1802 bytes (aka 20KB/s), to match our documentation. Also update
1803 directory authorities so they always assign the Fast flag to relays
1804 with 20KB/s of capacity. Now people running relays won't suddenly
1805 find themselves not seeing any use, if the network gets faster
1807 - Update to the "April 3 2009" ip-to-country file.
1810 - Avoid trying to print raw memory to the logs when we decide to
1811 give up on downloading a given relay descriptor. Bugfix on
1813 - In tor-resolve, when the Tor client to use is specified by
1814 <hostname>:<port>, actually use the specified port rather than
1815 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
1816 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
1817 - When starting with a cache over a few days old, do not leak
1818 memory for the obsolete router descriptors in it. Bugfix on
1820 - Avoid double-free on list of successfully uploaded hidden
1821 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
1822 - Change memarea_strndup() implementation to work even when
1823 duplicating a string at the end of a page. This bug was
1824 harmless for now, but could have meant crashes later. Fix by
1825 lark. Bugfix on 0.2.1.1-alpha.
1826 - Limit uploaded directory documents to be 16M rather than 500K.
1827 The directory authorities were refusing v3 consensus votes from
1828 other authorities, since the votes are now 504K. Fixes bug 959;
1829 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
1830 - Directory authorities should never send a 503 "busy" response to
1831 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
1835 Changes in version 0.2.1.13-alpha - 2009-03-09
1836 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
1837 cleanups. We're finally getting close to a release candidate.
1840 - Correctly update the list of which countries we exclude as
1841 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
1842 lark. Bugfix on 0.2.1.6-alpha.
1844 o Minor bugfixes (on 0.2.0.x and earlier):
1845 - Automatically detect MacOSX versions earlier than 10.4.0, and
1846 disable kqueue from inside Tor when running with these versions.
1847 We previously did this from the startup script, but that was no
1848 help to people who didn't use the startup script. Resolves bug 863.
1849 - When we had picked an exit node for a connection, but marked it as
1850 "optional", and it turned out we had no onion key for the exit,
1851 stop wanting that exit and try again. This situation may not
1852 be possible now, but will probably become feasible with proposal
1853 158. Spotted by rovv. Fixes another case of bug 752.
1854 - Clients no longer cache certificates for authorities they do not
1855 recognize. Bugfix on 0.2.0.9-alpha.
1856 - When we can't transmit a DNS request due to a network error, retry
1857 it after a while, and eventually transmit a failing response to
1858 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
1859 - If the controller claimed responsibility for a stream, but that
1860 stream never finished making its connection, it would live
1861 forever in circuit_wait state. Now we close it after SocksTimeout
1862 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
1863 - Drop begin cells to a hidden service if they come from the middle
1864 of a circuit. Patch from lark.
1865 - When we erroneously receive two EXTEND cells for the same circuit
1866 ID on the same connection, drop the second. Patch from lark.
1867 - Fix a crash that occurs on exit nodes when a nameserver request
1868 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
1869 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
1871 - Do not assume that a stack-allocated character array will be
1872 64-bit aligned on platforms that demand that uint64_t access is
1873 aligned. Possible fix for bug 604.
1874 - Parse dates and IPv4 addresses in a locale- and libc-independent
1875 manner, to avoid platform-dependent behavior on malformed input.
1876 - Build correctly when configured to build outside the main source
1877 path. Patch from Michael Gold.
1878 - We were already rejecting relay begin cells with destination port
1879 of 0. Now also reject extend cells with destination port or address
1880 of 0. Suggested by lark.
1882 o Minor bugfixes (on 0.2.1.x):
1883 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
1884 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
1885 - If we're an exit node, scrub the IP address to which we are exiting
1886 in the logs. Bugfix on 0.2.1.8-alpha.
1889 - On Linux, use the prctl call to re-enable core dumps when the user
1891 - New controller event NEWCONSENSUS that lists the networkstatus
1892 lines for every recommended relay. Now controllers like Torflow
1893 can keep up-to-date on which relays they should be using.
1894 - Update to the "February 26 2009" ip-to-country file.
1897 Changes in version 0.2.0.34 - 2009-02-08
1898 Tor 0.2.0.34 features several more security-related fixes. You should
1899 upgrade, especially if you run an exit relay (remote crash) or a
1900 directory authority (remote infinite loop), or you're on an older
1901 (pre-XP) or not-recently-patched Windows (remote exploit).
1903 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
1904 have many known flaws, and nobody should be using them. You should
1905 upgrade. If you're using a Linux or BSD and its packages are obsolete,
1906 stop using those packages and upgrade anyway.
1909 - Fix an infinite-loop bug on handling corrupt votes under certain
1910 circumstances. Bugfix on 0.2.0.8-alpha.
1911 - Fix a temporary DoS vulnerability that could be performed by
1912 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1913 - Avoid a potential crash on exit nodes when processing malformed
1914 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
1915 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1916 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1919 - Fix compilation on systems where time_t is a 64-bit integer.
1920 Patch from Matthias Drochner.
1921 - Don't consider expiring already-closed client connections. Fixes
1922 bug 893. Bugfix on 0.0.2pre20.
1925 Changes in version 0.2.1.12-alpha - 2009-02-08
1926 Tor 0.2.1.12-alpha features several more security-related fixes. You
1927 should upgrade, especially if you run an exit relay (remote crash) or
1928 a directory authority (remote infinite loop), or you're on an older
1929 (pre-XP) or not-recently-patched Windows (remote exploit). It also
1930 includes a big pile of minor bugfixes and cleanups.
1933 - Fix an infinite-loop bug on handling corrupt votes under certain
1934 circumstances. Bugfix on 0.2.0.8-alpha.
1935 - Fix a temporary DoS vulnerability that could be performed by
1936 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1937 - Avoid a potential crash on exit nodes when processing malformed
1938 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
1941 - Let controllers actually ask for the "clients_seen" event for
1942 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
1943 reported by Matt Edman.
1944 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
1946 - Fix a bug in address parsing that was preventing bridges or hidden
1947 service targets from being at IPv6 addresses.
1948 - Solve a bug that kept hardware crypto acceleration from getting
1949 enabled when accounting was turned on. Fixes bug 907. Bugfix on
1951 - Remove a bash-ism from configure.in to build properly on non-Linux
1952 platforms. Bugfix on 0.2.1.1-alpha.
1953 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
1954 headers. Bugfix on 0.2.0.10-alpha.
1955 - Don't consider expiring already-closed client connections. Fixes
1956 bug 893. Bugfix on 0.0.2pre20.
1957 - Fix another interesting corner-case of bug 891 spotted by rovv:
1958 Previously, if two hosts had different amounts of clock drift, and
1959 one of them created a new connection with just the wrong timing,
1960 the other might decide to deprecate the new connection erroneously.
1961 Bugfix on 0.1.1.13-alpha.
1962 - Resolve a very rare crash bug that could occur when the user forced
1963 a nameserver reconfiguration during the middle of a nameserver
1964 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
1965 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
1966 Bugfix on 0.2.1.7-alpha.
1967 - If we're using bridges and our network goes away, be more willing
1968 to forgive our bridges and try again when we get an application
1969 request. Bugfix on 0.2.0.x.
1972 - Support platforms where time_t is 64 bits long. (Congratulations,
1973 NetBSD!) Patch from Matthias Drochner.
1974 - Add a 'getinfo status/clients-seen' controller command, in case
1975 controllers want to hear clients_seen events but connect late.
1978 - Disable GCC's strict alias optimization by default, to avoid the
1979 likelihood of its introducing subtle bugs whenever our code violates
1980 the letter of C99's alias rules.
1983 Changes in version 0.2.0.33 - 2009-01-21
1984 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
1985 useful to users. It also finally fixes a bug where a relay or client
1986 that's been off for many days would take a long time to bootstrap.
1988 This update also fixes an important security-related bug reported by
1989 Ilja van Sprundel. You should upgrade. (We'll send out more details
1990 about the bug once people have had some time to upgrade.)
1993 - Fix a heap-corruption bug that may be remotely triggerable on
1994 some platforms. Reported by Ilja van Sprundel.
1997 - When a stream at an exit relay is in state "resolving" or
1998 "connecting" and it receives an "end" relay cell, the exit relay
1999 would silently ignore the end cell and not close the stream. If
2000 the client never closes the circuit, then the exit relay never
2001 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
2003 - When sending CREATED cells back for a given circuit, use a 64-bit
2004 connection ID to find the right connection, rather than an addr:port
2005 combination. Now that we can have multiple OR connections between
2006 the same ORs, it is no longer possible to use addr:port to uniquely
2007 identify a connection.
2008 - Bridge relays that had DirPort set to 0 would stop fetching
2009 descriptors shortly after startup, and then briefly resume
2010 after a new bandwidth test and/or after publishing a new bridge
2011 descriptor. Bridge users that try to bootstrap from them would
2012 get a recent networkstatus but would get descriptors from up to
2013 18 hours earlier, meaning most of the descriptors were obsolete
2014 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
2015 - Prevent bridge relays from serving their 'extrainfo' document
2016 to anybody who asks, now that extrainfo docs include potentially
2017 sensitive aggregated client geoip summaries. Bugfix on
2019 - If the cached networkstatus consensus is more than five days old,
2020 discard it rather than trying to use it. In theory it could be
2021 useful because it lists alternate directory mirrors, but in practice
2022 it just means we spend many minutes trying directory mirrors that
2023 are long gone from the network. Also discard router descriptors as
2024 we load them if they are more than five days old, since the onion
2025 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
2028 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2029 could make gcc generate non-functional binary search code. Bugfix
2031 - Build correctly on platforms without socklen_t.
2032 - Compile without warnings on solaris.
2033 - Avoid potential crash on internal error during signature collection.
2034 Fixes bug 864. Patch from rovv.
2035 - Correct handling of possible malformed authority signing key
2036 certificates with internal signature types. Fixes bug 880.
2037 Bugfix on 0.2.0.3-alpha.
2038 - Fix a hard-to-trigger resource leak when logging credential status.
2040 - When we can't initialize DNS because the network is down, do not
2041 automatically stop Tor from starting. Instead, we retry failed
2042 dns_init() every 10 minutes, and change the exit policy to reject
2043 *:* until one succeeds. Fixes bug 691.
2044 - Use 64 bits instead of 32 bits for connection identifiers used with
2045 the controller protocol, to greatly reduce risk of identifier reuse.
2046 - When we're choosing an exit node for a circuit, and we have
2047 no pending streams, choose a good general exit rather than one that
2048 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2049 - Fix another case of assuming, when a specific exit is requested,
2050 that we know more than the user about what hosts it allows.
2051 Fixes one case of bug 752. Patch from rovv.
2052 - Clip the MaxCircuitDirtiness config option to a minimum of 10
2053 seconds. Warn the user if lower values are given in the
2054 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
2055 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
2056 user if lower values are given in the configuration. Bugfix on
2057 0.1.1.17-rc. Patch by Sebastian.
2058 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
2059 the cache because we already had a v0 descriptor with the same ID.
2060 Bugfix on 0.2.0.18-alpha.
2061 - Fix a race condition when freeing keys shared between main thread
2062 and CPU workers that could result in a memory leak. Bugfix on
2063 0.1.0.1-rc. Fixes bug 889.
2064 - Send a valid END cell back when a client tries to connect to a
2065 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2066 840. Patch from rovv.
2067 - Check which hops rendezvous stream cells are associated with to
2068 prevent possible guess-the-streamid injection attacks from
2069 intermediate hops. Fixes another case of bug 446. Based on patch
2071 - If a broken client asks a non-exit router to connect somewhere,
2072 do not even do the DNS lookup before rejecting the connection.
2073 Fixes another case of bug 619. Patch from rovv.
2074 - When a relay gets a create cell it can't decrypt (e.g. because it's
2075 using the wrong onion key), we were dropping it and letting the
2076 client time out. Now actually answer with a destroy cell. Fixes
2077 bug 904. Bugfix on 0.0.2pre8.
2079 o Minor bugfixes (hidden services):
2080 - Do not throw away existing introduction points on SIGHUP. Bugfix on
2081 0.0.6pre1. Patch by Karsten. Fixes bug 874.
2084 - Report the case where all signatures in a detached set are rejected
2085 differently than the case where there is an error handling the
2087 - When we realize that another process has modified our cached
2088 descriptors, print out a more useful error message rather than
2089 triggering an assertion. Fixes bug 885. Patch from Karsten.
2090 - Implement the 0x20 hack to better resist DNS poisoning: set the
2091 case on outgoing DNS requests randomly, and reject responses that do
2092 not match the case correctly. This logic can be disabled with the
2093 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
2094 of servers that do not reliably preserve case in replies. See
2095 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2097 - Check DNS replies for more matching fields to better resist DNS
2099 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2100 compress cells, which are basically all encrypted, compressed, or
2104 Changes in version 0.2.1.11-alpha - 2009-01-20
2105 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
2106 week it will take a long time to bootstrap again" bug. It also fixes
2107 an important security-related bug reported by Ilja van Sprundel. You
2108 should upgrade. (We'll send out more details about the bug once people
2109 have had some time to upgrade.)
2112 - Fix a heap-corruption bug that may be remotely triggerable on
2113 some platforms. Reported by Ilja van Sprundel.
2116 - Discard router descriptors as we load them if they are more than
2117 five days old. Otherwise if Tor is off for a long time and then
2118 starts with cached descriptors, it will try to use the onion
2119 keys in those obsolete descriptors when building circuits. Bugfix
2120 on 0.2.0.x. Fixes bug 887.
2123 - Try to make sure that the version of Libevent we're running with
2124 is binary-compatible with the one we built with. May address bug
2126 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
2127 for bug 905. Bugfix on 0.2.1.7-alpha.
2128 - Add a new --enable-local-appdata configuration switch to change
2129 the default location of the datadir on win32 from APPDATA to
2130 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
2131 entirely. Patch from coderman.
2134 - Make outbound DNS packets respect the OutboundBindAddress setting.
2135 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
2136 - When our circuit fails at the first hop (e.g. we get a destroy
2137 cell back), avoid using that OR connection anymore, and also
2138 tell all the one-hop directory requests waiting for it that they
2139 should fail. Bugfix on 0.2.1.3-alpha.
2140 - In the torify(1) manpage, mention that tsocks will leak your
2144 Changes in version 0.2.1.10-alpha - 2009-01-06
2145 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
2146 would make the bridge relay not so useful if it had DirPort set to 0,
2147 and one that could let an attacker learn a little bit of information
2148 about the bridge's users), and a bug that would cause your Tor relay
2149 to ignore a circuit create request it can't decrypt (rather than reply
2150 with an error). It also fixes a wide variety of other bugs.
2153 - If the cached networkstatus consensus is more than five days old,
2154 discard it rather than trying to use it. In theory it could
2155 be useful because it lists alternate directory mirrors, but in
2156 practice it just means we spend many minutes trying directory
2157 mirrors that are long gone from the network. Helps bug 887 a bit;
2159 - Bridge relays that had DirPort set to 0 would stop fetching
2160 descriptors shortly after startup, and then briefly resume
2161 after a new bandwidth test and/or after publishing a new bridge
2162 descriptor. Bridge users that try to bootstrap from them would
2163 get a recent networkstatus but would get descriptors from up to
2164 18 hours earlier, meaning most of the descriptors were obsolete
2165 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
2166 - Prevent bridge relays from serving their 'extrainfo' document
2167 to anybody who asks, now that extrainfo docs include potentially
2168 sensitive aggregated client geoip summaries. Bugfix on
2172 - New controller event "clients_seen" to report a geoip-based summary
2173 of which countries we've seen clients from recently. Now controllers
2174 like Vidalia can show bridge operators that they're actually making
2176 - Build correctly against versions of OpenSSL 0.9.8 or later built
2177 without support for deprecated functions.
2178 - Update to the "December 19 2008" ip-to-country file.
2180 o Minor bugfixes (on 0.2.0.x):
2181 - Authorities now vote for the Stable flag for any router whose
2182 weighted MTBF is at least 5 days, regardless of the mean MTBF.
2183 - Do not remove routers as too old if we do not have any consensus
2184 document. Bugfix on 0.2.0.7-alpha.
2185 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
2186 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
2187 - When an exit relay resolves a stream address to a local IP address,
2188 do not just keep retrying that same exit relay over and
2189 over. Instead, just close the stream. Addresses bug 872. Bugfix
2190 on 0.2.0.32. Patch from rovv.
2191 - If a hidden service sends us an END cell, do not consider
2192 retrying the connection; just close it. Patch from rovv.
2193 - When we made bridge authorities stop serving bridge descriptors over
2194 unencrypted links, we also broke DirPort reachability testing for
2195 bridges. So bridges with a non-zero DirPort were printing spurious
2196 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
2197 - When a relay gets a create cell it can't decrypt (e.g. because it's
2198 using the wrong onion key), we were dropping it and letting the
2199 client time out. Now actually answer with a destroy cell. Fixes
2200 bug 904. Bugfix on 0.0.2pre8.
2201 - Squeeze 2-5% out of client performance (according to oprofile) by
2202 improving the implementation of some policy-manipulation functions.
2204 o Minor bugfixes (on 0.2.1.x):
2205 - Make get_interface_address() function work properly again; stop
2206 guessing the wrong parts of our address as our address.
2207 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
2208 send on that circuit. Otherwise we might violate the proposal-110
2209 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
2211 - When we're sending non-EXTEND cells to the first hop in a circuit,
2212 for example to use an encrypted directory connection, we don't need
2213 to use RELAY_EARLY cells: the first hop knows what kind of cell
2214 it is, and nobody else can even see the cell type. Conserving
2215 RELAY_EARLY cells makes it easier to cannibalize circuits like
2217 - Stop logging nameserver addresses in reverse order.
2218 - If we are retrying a directory download slowly over and over, do
2219 not automatically give up after the 254th failure. Bugfix on
2221 - Resume reporting accurate "stream end" reasons to the local control
2222 port. They were lost in the changes for Proposal 148. Bugfix on
2225 o Deprecated and removed features:
2226 - The old "tor --version --version" command, which would print out
2227 the subversion "Id" of most of the source files, is now removed. It
2228 turned out to be less useful than we'd expected, and harder to
2231 o Code simplifications and refactoring:
2232 - Change our header file guard macros to be less likely to conflict
2233 with system headers. Adam Langley noticed that we were conflicting
2234 with log.h on Android.
2235 - Tool-assisted documentation cleanup. Nearly every function or
2236 static variable in Tor should have its own documentation now.
2239 Changes in version 0.2.1.9-alpha - 2008-12-25
2240 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
2242 o New directory authorities:
2243 - gabelmoo (the authority run by Karsten Loesing) now has a new
2247 - Never use a connection with a mismatched address to extend a
2248 circuit, unless that connection is canonical. A canonical
2249 connection is one whose address is authenticated by the router's
2250 identity key, either in a NETINFO cell or in a router descriptor.
2251 - Avoid a possible memory corruption bug when receiving hidden service
2252 descriptors. Bugfix on 0.2.1.6-alpha.
2255 - Fix a logic error that would automatically reject all but the first
2256 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
2257 part of bug 813/868. Bug spotted by coderman.
2258 - When a stream at an exit relay is in state "resolving" or
2259 "connecting" and it receives an "end" relay cell, the exit relay
2260 would silently ignore the end cell and not close the stream. If
2261 the client never closes the circuit, then the exit relay never
2262 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
2264 - When we can't initialize DNS because the network is down, do not
2265 automatically stop Tor from starting. Instead, retry failed
2266 dns_init() every 10 minutes, and change the exit policy to reject
2267 *:* until one succeeds. Fixes bug 691.
2270 - Give a better error message when an overzealous init script says
2271 "sudo -u username tor --user username". Makes Bug 882 easier for
2273 - When a directory authority gives us a new guess for our IP address,
2274 log which authority we used. Hopefully this will help us debug
2275 the recent complaints about bad IP address guesses.
2276 - Detect svn revision properly when we're using git-svn.
2277 - Try not to open more than one descriptor-downloading connection
2278 to an authority at once. This should reduce load on directory
2279 authorities. Fixes bug 366.
2280 - Add cross-certification to newly generated certificates, so that
2281 a signing key is enough information to look up a certificate.
2282 Partial implementation of proposal 157.
2283 - Start serving certificates by <identity digest, signing key digest>
2284 pairs. Partial implementation of proposal 157.
2285 - Clients now never report any stream end reason except 'MISC'.
2286 Implements proposal 148.
2287 - On platforms with a maximum syslog string length, truncate syslog
2288 messages to that length ourselves, rather than relying on the
2289 system to do it for us.
2290 - Optimize out calls to time(NULL) that occur for every IO operation,
2291 or for every cell. On systems where time() is a slow syscall,
2292 this fix will be slightly helpful.
2293 - Exit servers can now answer resolve requests for ip6.arpa addresses.
2294 - When we download a descriptor that we then immediately (as
2295 a directory authority) reject, do not retry downloading it right
2296 away. Should save some bandwidth on authorities. Fix for bug
2297 888. Patch by Sebastian Hahn.
2298 - When a download gets us zero good descriptors, do not notify
2299 Tor that new directory information has arrived.
2300 - Avoid some nasty corner cases in the logic for marking connections
2301 as too old or obsolete or noncanonical for circuits. Partial
2304 o Minor features (controller):
2305 - New CONSENSUS_ARRIVED event to note when a new consensus has
2306 been fetched and validated.
2307 - When we realize that another process has modified our cached
2308 descriptors file, print out a more useful error message rather
2309 than triggering an assertion. Fixes bug 885. Patch from Karsten.
2310 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
2311 controllers to prevent SIGHUP from reloading the
2312 configuration. Fixes bug 856.
2315 - Resume using the correct "REASON=" stream when telling the
2316 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
2317 - When a canonical connection appears later in our internal list
2318 than a noncanonical one for a given OR ID, always use the
2319 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
2321 - Clip the MaxCircuitDirtiness config option to a minimum of 10
2322 seconds. Warn the user if lower values are given in the
2323 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
2324 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
2325 user if lower values are given in the configuration. Bugfix on
2326 0.1.1.17-rc. Patch by Sebastian.
2327 - Fix a race condition when freeing keys shared between main thread
2328 and CPU workers that could result in a memory leak. Bugfix on
2329 0.1.0.1-rc. Fixes bug 889.
2331 o Minor bugfixes (hidden services):
2332 - Do not throw away existing introduction points on SIGHUP (bugfix on
2333 0.0.6pre1); also, do not stall hidden services because we're
2334 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
2335 by John Brooks. Patch by Karsten. Fixes bug 874.
2336 - Fix a memory leak when we decline to add a v2 rendezvous
2337 descriptor to the cache because we already had a v0 descriptor
2338 with the same ID. Bugfix on 0.2.0.18-alpha.
2340 o Deprecated and removed features:
2341 - RedirectExits has been removed. It was deprecated since
2343 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
2344 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
2345 - Cell pools are now always enabled; --disable-cell-pools is ignored.
2347 o Code simplifications and refactoring:
2348 - Rename the confusing or_is_obsolete field to the more appropriate
2349 is_bad_for_new_circs, and move it to or_connection_t where it
2351 - Move edge-only flags from connection_t to edge_connection_t: not
2352 only is this better coding, but on machines of plausible alignment,
2353 it should save 4-8 bytes per connection_t. "Every little bit helps."
2354 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
2355 for consistency; keep old option working for backward compatibility.
2356 - Simplify the code for finding connections to use for a circuit.
2359 Changes in version 0.2.1.8-alpha - 2008-12-08
2360 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
2361 builds better on unusual platforms like Solaris and old OS X, and
2362 fixes a variety of other issues.
2365 - New DirPortFrontPage option that takes an html file and publishes
2366 it as "/" on the DirPort. Now relay operators can provide a
2367 disclaimer without needing to set up a separate webserver. There's
2368 a sample disclaimer in contrib/tor-exit-notice.html.
2371 - When the client is choosing entry guards, now it selects at most
2372 one guard from a given relay family. Otherwise we could end up with
2373 all of our entry points into the network run by the same operator.
2374 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
2377 - Fix a DOS opportunity during the voting signature collection process
2378 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2379 - Fix a possible segfault when establishing an exit connection. Bugfix
2383 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
2385 - Made Tor a little less aggressive about deleting expired
2386 certificates. Partial fix for bug 854.
2387 - Stop doing unaligned memory access that generated bus errors on
2388 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
2389 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
2390 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
2391 - Make USR2 log-level switch take effect immediately. Bugfix on
2393 - If one win32 nameserver fails to get added, continue adding the
2394 rest, and don't automatically fail.
2395 - Use fcntl() for locking when flock() is not available. Should fix
2396 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
2397 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2398 could make gcc generate non-functional binary search code. Bugfix
2400 - Build correctly on platforms without socklen_t.
2401 - Avoid potential crash on internal error during signature collection.
2402 Fixes bug 864. Patch from rovv.
2403 - Do not use C's stdio library for writing to log files. This will
2404 improve logging performance by a minute amount, and will stop
2405 leaking fds when our disk is full. Fixes bug 861.
2406 - Stop erroneous use of O_APPEND in cases where we did not in fact
2407 want to re-seek to the end of a file before every last write().
2408 - Correct handling of possible malformed authority signing key
2409 certificates with internal signature types. Fixes bug 880. Bugfix
2411 - Fix a hard-to-trigger resource leak when logging credential status.
2415 - Directory mirrors no longer fetch the v1 directory or
2416 running-routers files. They are obsolete, and nobody asks for them
2417 anymore. This is the first step to making v1 authorities obsolete.
2419 o Minor features (controller):
2420 - Return circuit purposes in response to GETINFO circuit-status. Fixes
2424 Changes in version 0.2.0.32 - 2008-11-20
2425 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
2426 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2427 a smaller security flaw that might allow an attacker to access local
2428 services, further improves hidden service performance, and fixes a
2429 variety of other issues.
2432 - The "User" and "Group" config options did not clear the
2433 supplementary group entries for the Tor process. The "User" option
2434 is now more robust, and we now set the groups to the specified
2435 user's primary group. The "Group" option is now ignored. For more
2436 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2437 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2438 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
2439 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2440 consistently obeyed: if an exit relay refuses a stream because its
2441 exit policy doesn't allow it, we would remember what IP address
2442 the relay said the destination address resolves to, even if it's
2443 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2446 - Fix a DOS opportunity during the voting signature collection process
2447 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2449 o Major bugfixes (hidden services):
2450 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2451 we were failing the whole hidden service request when the v0
2452 descriptor fetch fails, even if the v2 fetch is still pending and
2453 might succeed. Similarly, if the last v2 fetch fails, we were
2454 failing the whole hidden service request even if a v0 fetch is
2455 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2456 - When extending a circuit to a hidden service directory to upload a
2457 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2458 requests failed, because the router descriptor has not been
2459 downloaded yet. In these cases, do not attempt to upload the
2460 rendezvous descriptor, but wait until the router descriptor is
2461 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
2462 descriptor from a hidden service directory for which the router
2463 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
2467 - Fix several infrequent memory leaks spotted by Coverity.
2468 - When testing for libevent functions, set the LDFLAGS variable
2469 correctly. Found by Riastradh.
2470 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2471 bootstrapping with tunneled directory connections. Bugfix on
2472 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2473 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2474 and we know that server B rejects most-but-not all connections to
2475 port 80, we would previously reject the connection. Now, we assume
2476 the user knows what they were asking for. Fixes bug 752. Bugfix
2477 on 0.0.9rc5. Diagnosed by BarkerJr.
2478 - If we overrun our per-second write limits a little, count this as
2479 having used up our write allocation for the second, and choke
2480 outgoing directory writes. Previously, we had only counted this when
2481 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
2482 Bugfix on 0.2.0.x (??).
2483 - Remove the old v2 directory authority 'lefkada' from the default
2484 list. It has been gone for many months.
2485 - Stop doing unaligned memory access that generated bus errors on
2486 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
2487 - Make USR2 log-level switch take effect immediately. Bugfix on
2490 o Minor bugfixes (controller):
2491 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
2492 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
2495 Changes in version 0.2.1.7-alpha - 2008-11-08
2496 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
2497 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2498 a smaller security flaw that might allow an attacker to access local
2499 services, adds better defense against DNS poisoning attacks on exit
2500 relays, further improves hidden service performance, and fixes a
2501 variety of other issues.
2504 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2505 consistently obeyed: if an exit relay refuses a stream because its
2506 exit policy doesn't allow it, we would remember what IP address
2507 the relay said the destination address resolves to, even if it's
2508 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2509 - The "User" and "Group" config options did not clear the
2510 supplementary group entries for the Tor process. The "User" option
2511 is now more robust, and we now set the groups to the specified
2512 user's primary group. The "Group" option is now ignored. For more
2513 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2514 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2515 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
2516 - Do not use or believe expired v3 authority certificates. Patch
2517 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
2520 - Now NodeFamily and MyFamily config options allow spaces in
2521 identity fingerprints, so it's easier to paste them in.
2522 Suggested by Lucky Green.
2523 - Implement the 0x20 hack to better resist DNS poisoning: set the
2524 case on outgoing DNS requests randomly, and reject responses that do
2525 not match the case correctly. This logic can be disabled with the
2526 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
2527 of servers that do not reliably preserve case in replies. See
2528 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2530 - Preserve case in replies to DNSPort requests in order to support
2531 the 0x20 hack for resisting DNS poisoning attacks.
2533 o Hidden service performance improvements:
2534 - When the client launches an introduction circuit, retry with a
2535 new circuit after 30 seconds rather than 60 seconds.
2536 - Launch a second client-side introduction circuit in parallel
2537 after a delay of 15 seconds (based on work by Christian Wilms).
2538 - Hidden services start out building five intro circuits rather
2539 than three, and when the first three finish they publish a service
2540 descriptor using those. Now we publish our service descriptor much
2541 faster after restart.
2544 - Minor fix in the warning messages when you're having problems
2545 bootstrapping; also, be more forgiving of bootstrap problems when
2546 we're still making incremental progress on a given bootstrap phase.
2547 - When we're choosing an exit node for a circuit, and we have
2548 no pending streams, choose a good general exit rather than one that
2549 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2550 - Send a valid END cell back when a client tries to connect to a
2551 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2552 840. Patch from rovv.
2553 - If a broken client asks a non-exit router to connect somewhere,
2554 do not even do the DNS lookup before rejecting the connection.
2555 Fixes another case of bug 619. Patch from rovv.
2556 - Fix another case of assuming, when a specific exit is requested,
2557 that we know more than the user about what hosts it allows.
2558 Fixes another case of bug 752. Patch from rovv.
2559 - Check which hops rendezvous stream cells are associated with to
2560 prevent possible guess-the-streamid injection attacks from
2561 intermediate hops. Fixes another case of bug 446. Based on patch
2563 - Avoid using a negative right-shift when comparing 32-bit
2564 addresses. Possible fix for bug 845 and bug 811.
2565 - Make the assert_circuit_ok() function work correctly on circuits that
2566 have already been marked for close.
2567 - Fix read-off-the-end-of-string error in unit tests when decoding
2568 introduction points.
2569 - Fix uninitialized size field for memory area allocation: may improve
2570 memory performance during directory parsing.
2571 - Treat duplicate certificate fetches as failures, so that we do
2572 not try to re-fetch an expired certificate over and over and over.
2573 - Do not say we're fetching a certificate when we'll in fact skip it
2574 because of a pending download.
2577 Changes in version 0.2.1.6-alpha - 2008-09-30
2578 Tor 0.2.1.6-alpha further improves performance and robustness of
2579 hidden services, starts work on supporting per-country relay selection,
2580 and fixes a variety of smaller issues.
2583 - Implement proposal 121: make it possible to build hidden services
2584 that only certain clients are allowed to connect to. This is
2585 enforced at several points, so that unauthorized clients are unable
2586 to send INTRODUCE cells to the service, or even (depending on the
2587 type of authentication) to learn introduction points. This feature
2588 raises the bar for certain kinds of active attacks against hidden
2589 services. Code by Karsten Loesing.
2590 - Relays now store and serve v2 hidden service descriptors by default,
2591 i.e., the new default value for HidServDirectoryV2 is 1. This is
2592 the last step in proposal 114, which aims to make hidden service
2593 lookups more reliable.
2594 - Start work to allow node restrictions to include country codes. The
2595 syntax to exclude nodes in a country with country code XX is
2596 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
2597 refinement to decide what config options should take priority if
2598 you ask to both use a particular node and exclude it.
2599 - Allow ExitNodes list to include IP ranges and country codes, just
2600 like the Exclude*Nodes lists. Patch from Robert Hogan.
2603 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
2604 Tor to fail to start if you had it configured to use a bridge
2605 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
2606 - When extending a circuit to a hidden service directory to upload a
2607 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2608 requests failed, because the router descriptor had not been
2609 downloaded yet. In these cases, we now wait until the router
2610 descriptor is downloaded, and then retry. Likewise, clients
2611 now skip over a hidden service directory if they don't yet have
2612 its router descriptor, rather than futilely requesting it and
2613 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
2615 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2616 we were failing the whole hidden service request when the v0
2617 descriptor fetch fails, even if the v2 fetch is still pending and
2618 might succeed. Similarly, if the last v2 fetch fails, we were
2619 failing the whole hidden service request even if a v0 fetch is
2620 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2621 - DNS replies need to have names matching their requests, but
2622 these names should be in the questions section, not necessarily
2623 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
2626 - Update to the "September 1 2008" ip-to-country file.
2627 - Allow ports 465 and 587 in the default exit policy again. We had
2628 rejected them in 0.1.0.15, because back in 2005 they were commonly
2629 misconfigured and ended up as spam targets. We hear they are better
2630 locked down these days.
2631 - Use a lockfile to make sure that two Tor processes are not
2632 simultaneously running with the same datadir.
2633 - Serve the latest v3 networkstatus consensus via the control
2634 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2635 - Better logging about stability/reliability calculations on directory
2637 - Drop the requirement to have an open dir port for storing and
2638 serving v2 hidden service descriptors.
2639 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2640 help debug WFU and MTBF calculations.
2641 - Implement most of Proposal 152: allow specialized servers to permit
2642 single-hop circuits, and clients to use those servers to build
2643 single-hop circuits when using a specialized controller. Patch
2644 from Josh Albrecht. Resolves feature request 768.
2645 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2646 people find host:port too confusing.
2647 - Make TrackHostExit mappings expire a while after their last use, not
2648 after their creation. Patch from Robert Hogan.
2649 - Provide circuit purposes along with circuit events to the controller.
2652 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
2654 - Fixed some memory leaks -- some quite frequent, some almost
2655 impossible to trigger -- based on results from Coverity.
2656 - When testing for libevent functions, set the LDFLAGS variable
2657 correctly. Found by Riastradh.
2658 - Fix an assertion bug in parsing policy-related options; possible fix
2660 - Catch and report a few more bootstrapping failure cases when Tor
2661 fails to establish a TCP connection. Cleanup on 0.2.1.x.
2662 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2663 bootstrapping with tunneled directory connections. Bugfix on
2664 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2665 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2666 and we know that server B rejects most-but-not all connections to
2667 port 80, we would previously reject the connection. Now, we assume
2668 the user knows what they were asking for. Fixes bug 752. Bugfix
2669 on 0.0.9rc5. Diagnosed by BarkerJr.
2670 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2671 service directories if they have no advertised dir port. Bugfix
2673 - If we overrun our per-second write limits a little, count this as
2674 having used up our write allocation for the second, and choke
2675 outgoing directory writes. Previously, we had only counted this when
2676 we had met our limits precisely. Fixes bug 824. Patch by rovv.
2677 Bugfix on 0.2.0.x (??).
2678 - Avoid a "0 divided by 0" calculation when calculating router uptime
2679 at directory authorities. Bugfix on 0.2.0.8-alpha.
2680 - Make DNS resolved controller events into "CLOSED", not
2681 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2683 - Fix a bug where an unreachable relay would establish enough
2684 reachability testing circuits to do a bandwidth test -- if
2685 we already have a connection to the middle hop of the testing
2686 circuit, then it could establish the last hop by using the existing
2687 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2688 circuits no longer use entry guards in 0.2.1.3-alpha.
2689 - If we have correct permissions on $datadir, we complain to stdout
2690 and fail to start. But dangerous permissions on
2691 $datadir/cached-status/ would cause us to open a log and complain
2692 there. Now complain to stdout and fail to start in both cases. Fixes
2693 bug 820, reported by seeess.
2694 - Remove the old v2 directory authority 'lefkada' from the default
2695 list. It has been gone for many months.
2697 o Code simplifications and refactoring:
2698 - Revise the connection_new functions so that a more typesafe variant
2699 exists. This will work better with Coverity, and let us find any
2700 actual mistakes we're making here.
2701 - Refactor unit testing logic so that dmalloc can be used sensibly
2702 with unit tests to check for memory leaks.
2703 - Move all hidden-service related fields from connection and circuit
2704 structure to substructures: this way they won't eat so much memory.
2707 Changes in version 0.2.0.31 - 2008-09-03
2708 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
2709 a big bug we're seeing where in rare cases traffic from one Tor stream
2710 gets mixed into another stream, and fixes a variety of smaller issues.
2713 - Make sure that two circuits can never exist on the same connection
2714 with the same circuit ID, even if one is marked for close. This
2715 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
2716 - Relays now reject risky extend cells: if the extend cell includes
2717 a digest of all zeroes, or asks to extend back to the relay that
2718 sent the extend cell, tear down the circuit. Ideas suggested
2720 - If not enough of our entry guards are available so we add a new
2721 one, we might use the new one even if it overlapped with the
2722 current circuit's exit relay (or its family). Anonymity bugfix
2723 pointed out by rovv.
2726 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2727 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2728 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2729 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2730 - Pick size of default geoip filename string correctly on windows.
2731 Fixes bug 806. Bugfix on 0.2.0.30.
2732 - Make the autoconf script accept the obsolete --with-ssl-dir
2733 option as an alias for the actually-working --with-openssl-dir
2734 option. Fix the help documentation to recommend --with-openssl-dir.
2735 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2736 - When using the TransPort option on OpenBSD, and using the User
2737 option to change UID and drop privileges, make sure to open
2738 /dev/pf before dropping privileges. Fixes bug 782. Patch from
2739 Christopher Davis. Bugfix on 0.1.2.1-alpha.
2740 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2741 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2742 on the client side when connecting to a hidden service. Bugfix
2743 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2744 - When closing an application-side connection because its circuit is
2745 getting torn down, generate the stream event correctly. Bugfix on
2746 0.1.2.x. Anonymous patch.
2749 Changes in version 0.2.1.5-alpha - 2008-08-31
2750 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
2751 in a lot of the infrastructure for adding authorization to hidden
2752 services, lays the groundwork for having clients read their load
2753 balancing information out of the networkstatus consensus rather than
2754 the individual router descriptors, addresses two potential anonymity
2755 issues, and fixes a variety of smaller issues.
2758 - Convert many internal address representations to optionally hold
2760 - Generate and accept IPv6 addresses in many protocol elements.
2761 - Make resolver code handle nameservers located at ipv6 addresses.
2762 - Begin implementation of proposal 121 ("Client authorization for
2763 hidden services"): configure hidden services with client
2764 authorization, publish descriptors for them, and configure
2765 authorization data for hidden services at clients. The next
2766 step is to actually access hidden services that perform client
2768 - More progress toward proposal 141: Network status consensus
2769 documents and votes now contain bandwidth information for each
2770 router and a summary of that router's exit policy. Eventually this
2771 will be used by clients so that they do not have to download every
2772 known descriptor before building circuits.
2774 o Major bugfixes (on 0.2.0.x and before):
2775 - When sending CREATED cells back for a given circuit, use a 64-bit
2776 connection ID to find the right connection, rather than an addr:port
2777 combination. Now that we can have multiple OR connections between
2778 the same ORs, it is no longer possible to use addr:port to uniquely
2779 identify a connection.
2780 - Relays now reject risky extend cells: if the extend cell includes
2781 a digest of all zeroes, or asks to extend back to the relay that
2782 sent the extend cell, tear down the circuit. Ideas suggested
2784 - If not enough of our entry guards are available so we add a new
2785 one, we might use the new one even if it overlapped with the
2786 current circuit's exit relay (or its family). Anonymity bugfix
2787 pointed out by rovv.
2790 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2791 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2792 - When using the TransPort option on OpenBSD, and using the User
2793 option to change UID and drop privileges, make sure to open /dev/pf
2794 before dropping privileges. Fixes bug 782. Patch from Christopher
2795 Davis. Bugfix on 0.1.2.1-alpha.
2796 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2797 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2798 - Add a missing safe_str() call for a debug log message.
2799 - Use 64 bits instead of 32 bits for connection identifiers used with
2800 the controller protocol, to greatly reduce risk of identifier reuse.
2801 - Make the autoconf script accept the obsolete --with-ssl-dir
2802 option as an alias for the actually-working --with-openssl-dir
2803 option. Fix the help documentation to recommend --with-openssl-dir.
2804 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2807 - Rate-limit too-many-sockets messages: when they happen, they happen
2808 a lot. Resolves bug 748.
2809 - Resist DNS poisoning a little better by making sure that names in
2810 answer sections match.
2811 - Print the SOCKS5 error message string as well as the error code
2812 when a tor-resolve request fails. Patch from Jacob.
2815 Changes in version 0.2.1.4-alpha - 2008-08-04
2816 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
2819 - The address part of exit policies was not correctly written
2820 to router descriptors. This generated router descriptors that failed
2821 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
2823 - Tor triggered a false assert when extending a circuit to a relay
2824 but we already have a connection open to that relay. Noticed by
2825 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
2828 - Fix a hidden service logging bug: in some edge cases, the router
2829 descriptor of a previously picked introduction point becomes
2830 obsolete and we need to give up on it rather than continually
2831 complaining that it has become obsolete. Observed by xiando. Bugfix
2835 - Take out the TestVia config option, since it was a workaround for
2836 a bug that was fixed in Tor 0.1.1.21.
2839 Changes in version 0.2.1.3-alpha - 2008-08-03
2840 Tor 0.2.1.3-alpha implements most of the pieces to prevent
2841 infinite-length circuit attacks (see proposal 110); fixes a bug that
2842 might cause exit relays to corrupt streams they send back; allows
2843 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
2844 ExcludeExitNodes config options; and fixes a big pile of bugs.
2846 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
2847 - Send a bootstrap problem "warn" event on the first problem if the
2848 reason is NO_ROUTE (that is, our network is down).
2851 - Implement most of proposal 110: The first K cells to be sent
2852 along a circuit are marked as special "early" cells; only K "early"
2853 cells will be allowed. Once this code is universal, we can block
2854 certain kinds of DOS attack by requiring that EXTEND commands must
2855 be sent using an "early" cell.
2858 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2859 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2860 on the client side when connecting to a hidden service. Bugfix
2861 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2862 - Ensure that two circuits can never exist on the same connection
2863 with the same circuit ID, even if one is marked for close. This
2864 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
2867 - When relays do their initial bandwidth measurement, don't limit
2868 to just our entry guards for the test circuits. Otherwise we tend
2869 to have multiple test circuits going through a single entry guard,
2870 which makes our bandwidth test less accurate. Fixes part of bug 654;
2871 patch contributed by Josh Albrecht.
2872 - Add an ExcludeExitNodes option so users can list a set of nodes
2873 that should be be excluded from the exit node position, but
2874 allowed elsewhere. Implements proposal 151.
2875 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
2876 ExcludeNodes and ExcludeExitNodes lists.
2877 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2878 be more efficient. Formerly it was quadratic in the number of
2879 servers; now it should be linear. Fixes bug 509.
2880 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2881 and n_conn_id_digest fields into a separate structure that's
2882 only needed when the circuit has not yet attached to an n_conn.
2885 - Change the contrib/tor.logrotate script so it makes the new
2886 logs as "_tor:_tor" rather than the default, which is generally
2887 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
2888 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2889 warnings (occasionally), but it can also cause the compiler to
2890 eliminate error-checking code. Suggested by Peter Gutmann.
2891 - When a hidden service is giving up on an introduction point candidate
2892 that was not included in the last published rendezvous descriptor,
2893 don't reschedule publication of the next descriptor. Fixes bug 763.
2895 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2896 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2897 and nobody claims to be using them. Fixes bug 754. Bugfix on
2898 0.1.0.1-rc. Patch from Christian Wilms.
2899 - Fix a small alignment and memory-wasting bug on buffer chunks.
2902 o Minor bugfixes (controller):
2903 - When closing an application-side connection because its circuit
2904 is getting torn down, generate the stream event correctly.
2905 Bugfix on 0.1.2.x. Anonymous patch.
2908 - Remove all backward-compatibility code to support relays running
2909 versions of Tor so old that they no longer work at all on the
2913 Changes in version 0.2.0.30 - 2008-07-15
2915 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2916 warnings (occasionally), but it can also cause the compiler to
2917 eliminate error-checking code. Suggested by Peter Gutmann.
2920 Changes in version 0.2.0.29-rc - 2008-07-08
2921 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
2922 hidden-service performance bugs, and fixes a bunch of smaller bugs.
2925 - If you have more than one bridge but don't know their keys,
2926 you would only launch a request for the descriptor of the first one
2927 on your list. (Tor considered launching requests for the others, but
2928 found that it already had a connection on the way for $0000...0000
2929 so it didn't open another.) Bugfix on 0.2.0.x.
2930 - If you have more than one bridge but don't know their keys, and the
2931 connection to one of the bridges failed, you would cancel all
2932 pending bridge connections. (After all, they all have the same
2933 digest.) Bugfix on 0.2.0.x.
2934 - When a hidden service was trying to establish an introduction point,
2935 and Tor had built circuits preemptively for such purposes, we
2936 were ignoring all the preemptive circuits and launching a new one
2937 instead. Bugfix on 0.2.0.14-alpha.
2938 - When a hidden service was trying to establish an introduction point,
2939 and Tor *did* manage to reuse one of the preemptively built
2940 circuits, it didn't correctly remember which one it used,
2941 so it asked for another one soon after, until there were no
2942 more preemptive circuits, at which point it launched one from
2943 scratch. Bugfix on 0.0.9.x.
2944 - Make directory servers include the X-Your-Address-Is: http header in
2945 their responses even for begin_dir conns. Now clients who only
2946 ever use begin_dir connections still have a way to learn their IP
2947 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
2950 - Fix a macro/CPP interaction that was confusing some compilers:
2951 some GCCs don't like #if/#endif pairs inside macro arguments.
2953 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
2954 Fixes bug 704; fix from Steven Murdoch.
2955 - When opening /dev/null in finish_daemonize(), do not pass the
2956 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
2957 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
2958 - Correctly detect transparent proxy support on Linux hosts that
2959 require in.h to be included before netfilter_ipv4.h. Patch
2961 - Disallow session resumption attempts during the renegotiation
2962 stage of the v2 handshake protocol. Clients should never be trying
2963 session resumption at this point, but apparently some did, in
2964 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
2965 found by Geoff Goodell.
2968 Changes in version 0.2.1.2-alpha - 2008-06-20
2969 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
2970 make it easier to set up your own private Tor network; fixes several
2971 big bugs with using more than one bridge relay; fixes a big bug with
2972 offering hidden services quickly after Tor starts; and uses a better
2973 API for reporting potential bootstrapping problems to the controller.
2976 - New TestingTorNetwork config option to allow adjustment of
2977 previously constant values that, while reasonable, could slow
2978 bootstrapping. Implements proposal 135. Patch from Karsten.
2981 - If you have more than one bridge but don't know their digests,
2982 you would only learn a request for the descriptor of the first one
2983 on your list. (Tor considered launching requests for the others, but
2984 found that it already had a connection on the way for $0000...0000
2985 so it didn't open another.) Bugfix on 0.2.0.x.
2986 - If you have more than one bridge but don't know their digests,
2987 and the connection to one of the bridges failed, you would cancel
2988 all pending bridge connections. (After all, they all have the
2989 same digest.) Bugfix on 0.2.0.x.
2990 - When establishing a hidden service, introduction points that
2991 originate from cannibalized circuits are completely ignored and not
2992 included in rendezvous service descriptors. This might be another
2993 reason for delay in making a hidden service available. Bugfix
2994 from long ago (0.0.9.x?)
2997 - Allow OpenSSL to use dynamic locks if it wants.
2998 - When building a consensus, do not include routers that are down.
2999 This will cut down 30% to 40% on consensus size. Implements
3001 - In directory authorities' approved-routers files, allow
3002 fingerprints with or without space.
3003 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
3004 controller can query our current bootstrap state in case it attaches
3005 partway through and wants to catch up.
3006 - Send an initial "Starting" bootstrap status event, so we have a
3007 state to start out in.
3010 - Asking for a conditional consensus at .../consensus/<fingerprints>
3011 would crash a dirserver if it did not already have a
3012 consensus. Bugfix on 0.2.1.1-alpha.
3013 - Clean up some macro/CPP interactions: some GCC versions don't like
3014 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
3017 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
3018 - Directory authorities shouldn't complain about bootstrapping
3019 problems just because they do a lot of reachability testing and
3020 some of the connection attempts fail.
3021 - Start sending "count" and "recommendation" key/value pairs in
3022 bootstrap problem status events, so the controller can hear about
3023 problems even before Tor decides they're worth reporting for sure.
3024 - If you're using bridges, generate "bootstrap problem" warnings
3025 as soon as you run out of working bridges, rather than waiting
3026 for ten failures -- which will never happen if you have less than
3028 - If we close our OR connection because there's been a circuit
3029 pending on it for too long, we were telling our bootstrap status
3030 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
3033 Changes in version 0.2.1.1-alpha - 2008-06-13
3034 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
3035 were making the Tor process bloat especially on Linux; makes our TLS
3036 handshake blend in better; sends "bootstrap phase" status events to
3037 the controller, so it can keep the user informed of progress (and
3038 problems) fetching directory information and establishing circuits;
3039 and adds a variety of smaller features.
3042 - More work on making our TLS handshake blend in: modify the list
3043 of ciphers advertised by OpenSSL in client mode to even more
3044 closely resemble a common web browser. We cheat a little so that
3045 we can advertise ciphers that the locally installed OpenSSL doesn't
3047 - Start sending "bootstrap phase" status events to the controller,
3048 so it can keep the user informed of progress fetching directory
3049 information and establishing circuits. Also inform the controller
3050 if we think we're stuck at a particular bootstrap phase. Implements
3052 - Resume using OpenSSL's RAND_poll() for better (and more portable)
3053 cross-platform entropy collection again. We used to use it, then
3054 stopped using it because of a bug that could crash systems that
3055 called RAND_poll when they had a lot of fds open. It looks like the
3056 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
3057 at startup, and to call RAND_poll() when we reseed later only if
3058 we have a non-buggy OpenSSL version.
3061 - When we choose to abandon a new entry guard because we think our
3062 older ones might be better, close any circuits pending on that
3063 new entry guard connection. This fix should make us recover much
3064 faster when our network is down and then comes back. Bugfix on
3065 0.1.2.8-beta; found by lodger.
3067 o Memory fixes and improvements:
3068 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
3069 to avoid unused RAM in buffer chunks and memory pools.
3070 - Speed up parsing and cut down on memory fragmentation by using
3071 stack-style allocations for parsing directory objects. Previously,
3072 this accounted for over 40% of allocations from within Tor's code
3073 on a typical directory cache.
3074 - Use a Bloom filter rather than a digest-based set to track which
3075 descriptors we need to keep around when we're cleaning out old
3076 router descriptors. This speeds up the computation significantly,
3077 and may reduce fragmentation.
3078 - Reduce the default smartlist size from 32 to 16; it turns out that
3079 most smartlists hold around 8-12 elements tops.
3080 - Make dumpstats() log the fullness and size of openssl-internal
3082 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
3083 patch to their OpenSSL, turn it on to save memory on servers. This
3084 patch will (with any luck) get included in a mainline distribution
3086 - Never use OpenSSL compression: it wastes RAM and CPU trying to
3087 compress cells, which are basically all encrypted, compressed,
3091 - Stop reloading the router list from disk for no reason when we
3092 run out of reachable directory mirrors. Once upon a time reloading
3093 it would set the 'is_running' flag back to 1 for them. It hasn't
3094 done that for a long time.
3095 - In very rare situations new hidden service descriptors were
3096 published earlier than 30 seconds after the last change to the
3097 service. (We currently think that a hidden service descriptor
3098 that's been stable for 30 seconds is worth publishing.)
3101 - Allow separate log levels to be configured for different logging
3102 domains. For example, this allows one to log all notices, warnings,
3103 or errors, plus all memory management messages of level debug or
3104 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
3105 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
3106 and stop using a warning that had become unfixably verbose under
3108 - New --hush command-line option similar to --quiet. While --quiet
3109 disables all logging to the console on startup, --hush limits the
3110 output to messages of warning and error severity.
3111 - Servers support a new URL scheme for consensus downloads that
3112 allows the client to specify which authorities are trusted.
3113 The server then only sends the consensus if the client will trust
3114 it. Otherwise a 404 error is sent back. Clients use this
3115 new scheme when the server supports it (meaning it's running
3116 0.2.1.1-alpha or later). Implements proposal 134.
3117 - New configure/torrc options (--enable-geoip-stats,
3118 DirRecordUsageByCountry) to record how many IPs we've served
3119 directory info to in each country code, how many status documents
3120 total we've sent to each country code, and what share of the total
3121 directory requests we should expect to see.
3122 - Use the TLS1 hostname extension to more closely resemble browser
3124 - Lots of new unit tests.
3125 - Add a macro to implement the common pattern of iterating through
3126 two parallel lists in lockstep.
3129 Changes in version 0.2.0.28-rc - 2008-06-13
3130 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
3131 performance bug, and fixes a bunch of smaller bugs.
3134 - Fix a bug where, when we were choosing the 'end stream reason' to
3135 put in our relay end cell that we send to the exit relay, Tor
3136 clients on Windows were sometimes sending the wrong 'reason'. The
3137 anonymity problem is that exit relays may be able to guess whether
3138 the client is running Windows, thus helping partition the anonymity
3139 set. Down the road we should stop sending reasons to exit relays,
3140 or otherwise prevent future versions of this bug.
3143 - While setting up a hidden service, some valid introduction circuits
3144 were overlooked and abandoned. This might be the reason for
3145 the long delay in making a hidden service available. Bugfix on
3149 - Update to the "June 9 2008" ip-to-country file.
3150 - Run 'make test' as part of 'make dist', so we stop releasing so
3151 many development snapshots that fail their unit tests.
3154 - When we're checking if we have enough dir info for each relay
3155 to begin establishing circuits, make sure that we actually have
3156 the descriptor listed in the consensus, not just any descriptor.
3158 - Bridge relays no longer print "xx=0" in their extrainfo document
3159 for every single country code in the geoip db. Bugfix on
3161 - Only warn when we fail to load the geoip file if we were planning to
3162 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
3163 - If we change our MaxAdvertisedBandwidth and then reload torrc,
3164 Tor won't realize it should publish a new relay descriptor. Fixes
3165 bug 688, reported by mfr. Bugfix on 0.1.2.x.
3166 - When we haven't had any application requests lately, don't bother
3167 logging that we have expired a bunch of descriptors. Bugfix
3169 - Make relay cells written on a connection count as non-padding when
3170 tracking how long a connection has been in use. Bugfix on
3171 0.2.0.1-alpha. Spotted by lodger.
3172 - Fix unit tests in 0.2.0.27-rc.
3173 - Fix compile on Windows.
3176 Changes in version 0.2.0.27-rc - 2008-06-03
3177 Tor 0.2.0.27-rc adds a few features we left out of the earlier
3178 release candidates. In particular, we now include an IP-to-country
3179 GeoIP database, so controllers can easily look up what country a
3180 given relay is in, and so bridge relays can give us some sanitized
3181 summaries about which countries are making use of bridges. (See proposal
3182 126-geoip-fetching.txt for details.)
3185 - Include an IP-to-country GeoIP file in the tarball, so bridge
3186 relays can report sanitized summaries of the usage they're seeing.
3189 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
3190 Robert Hogan. Fixes the first part of bug 681.
3191 - Make bridge authorities never serve extrainfo docs.
3192 - Add support to detect Libevent versions in the 1.4.x series
3194 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
3195 - Include a new contrib/tor-exit-notice.html file that exit relay
3196 operators can put on their website to help reduce abuse queries.
3199 - When tunneling an encrypted directory connection, and its first
3200 circuit fails, do not leave it unattached and ask the controller
3201 to deal. Fixes the second part of bug 681.
3202 - Make bridge authorities correctly expire old extrainfo documents
3206 Changes in version 0.2.0.26-rc - 2008-05-13
3207 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
3208 in Debian's OpenSSL packages. All users running any 0.2.0.x version
3209 should upgrade, whether they're running Debian or not.
3211 o Major security fixes:
3212 - Use new V3 directory authority keys on the tor26, gabelmoo, and
3213 moria1 V3 directory authorities. The old keys were generated with
3214 a vulnerable version of Debian's OpenSSL package, and must be
3215 considered compromised. Other authorities' keys were not generated
3216 with an affected version of OpenSSL.
3219 - List authority signatures as "unrecognized" based on DirServer
3220 lines, not on cert cache. Bugfix on 0.2.0.x.
3223 - Add a new V3AuthUseLegacyKey option to make it easier for
3224 authorities to change their identity keys if they have to.
3227 Changes in version 0.2.0.25-rc - 2008-04-23
3228 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
3231 - Remember to initialize threading before initializing logging.
3232 Otherwise, many BSD-family implementations will crash hard on
3233 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
3236 - Authorities correctly free policies on bad servers on
3237 exit. Fixes bug 672. Bugfix on 0.2.0.x.
3240 Changes in version 0.2.0.24-rc - 2008-04-22
3241 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
3242 v3 directory authority, makes relays with dynamic IP addresses and no
3243 DirPort notice more quickly when their IP address changes, fixes a few
3244 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
3246 o New directory authorities:
3247 - Take lefkada out of the list of v3 directory authorities, since
3248 it has been down for months.
3249 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
3253 - Detect address changes more quickly on non-directory mirror
3254 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
3256 o Minor features (security):
3257 - Reject requests for reverse-dns lookup of names that are in
3258 a private address space. Patch from lodger.
3259 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
3262 o Minor bugfixes (crashes):
3263 - Avoid a rare assert that can trigger when Tor doesn't have much
3264 directory information yet and it tries to fetch a v2 hidden
3265 service descriptor. Fixes bug 651, reported by nwf.
3266 - Initialize log mutex before initializing dmalloc. Otherwise,
3267 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
3268 - Use recursive pthread mutexes in order to avoid deadlock when
3269 logging debug-level messages to a controller. Bug spotted by nwf,
3270 bugfix on 0.2.0.16-alpha.
3272 o Minor bugfixes (resource management):
3273 - Keep address policies from leaking memory: start their refcount
3274 at 1, not 2. Bugfix on 0.2.0.16-alpha.
3275 - Free authority certificates on exit, so they don't look like memory
3276 leaks. Bugfix on 0.2.0.19-alpha.
3277 - Free static hashtables for policy maps and for TLS connections on
3278 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
3279 - Avoid allocating extra space when computing consensuses on 64-bit
3280 platforms. Bug spotted by aakova.
3282 o Minor bugfixes (misc):
3283 - Do not read the configuration file when we've only been told to
3284 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
3285 based on patch from Sebastian Hahn.
3286 - Exit relays that are used as a client can now reach themselves
3287 using the .exit notation, rather than just launching an infinite
3288 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
3289 - When attempting to open a logfile fails, tell us why.
3290 - Fix a dumb bug that was preventing us from knowing that we should
3291 preemptively build circuits to handle expected directory requests.
3292 Fixes bug 660. Bugfix on 0.1.2.x.
3293 - Warn less verbosely about clock skew from netinfo cells from
3294 untrusted sources. Fixes bug 663.
3295 - Make controller stream events for DNS requests more consistent,
3296 by adding "new stream" events for DNS requests, and removing
3297 spurious "stream closed" events" for cached reverse resolves.
3298 Patch from mwenge. Fixes bug 646.
3299 - Correctly notify one-hop connections when a circuit build has
3300 failed. Possible fix for bug 669. Found by lodger.
3303 Changes in version 0.2.0.23-rc - 2008-03-24
3304 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
3305 makes bootstrapping faster if the first directory mirror you contact
3306 is down. The bundles also include the new Vidalia 0.1.2 release.
3309 - When a tunneled directory request is made to a directory server
3310 that's down, notice after 30 seconds rather than 120 seconds. Also,
3311 fail any begindir streams that are pending on it, so they can
3312 retry elsewhere. This was causing multi-minute delays on bootstrap.
3315 Changes in version 0.2.0.22-rc - 2008-03-18
3316 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
3317 enables encrypted directory connections by default for non-relays, fixes
3318 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
3319 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
3322 - Enable encrypted directory connections by default for non-relays,
3323 so censor tools that block Tor directory connections based on their
3324 plaintext patterns will no longer work. This means Tor works in
3325 certain censored countries by default again.
3328 - Make sure servers always request certificates from clients during
3329 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
3330 - Do not enter a CPU-eating loop when a connection is closed in
3331 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
3332 diagnosed by lodger; bugfix on 0.2.0.20-rc.
3333 - Fix assertion failure that could occur when a blocked circuit
3334 became unblocked, and it had pending client DNS requests. Bugfix
3335 on 0.2.0.1-alpha. Fixes bug 632.
3337 o Minor bugfixes (on 0.1.2.x):
3338 - Generate "STATUS_SERVER" events rather than misspelled
3339 "STATUS_SEVER" events. Caught by mwenge.
3340 - When counting the number of bytes written on a TLS connection,
3341 look at the BIO actually used for writing to the network, not
3342 at the BIO used (sometimes) to buffer data for the network.
3343 Looking at different BIOs could result in write counts on the
3344 order of ULONG_MAX. Fixes bug 614.
3345 - On Windows, correctly detect errors when listing the contents of
3346 a directory. Fix from lodger.
3348 o Minor bugfixes (on 0.2.0.x):
3349 - Downgrade "sslv3 alert handshake failure" message to INFO.
3350 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
3351 left BandwidthRate and BandwidthBurst at the default, we would be
3352 silently limited by those defaults. Now raise them to match the
3353 RelayBandwidth* values.
3354 - Fix the SVK version detection logic to work correctly on a branch.
3355 - Make --enable-openbsd-malloc work correctly on Linux with alpha
3356 CPUs. Fixes bug 625.
3357 - Logging functions now check that the passed severity is sane.
3358 - Use proper log levels in the testsuite call of
3359 get_interface_address6().
3360 - When using a nonstandard malloc, do not use the platform values for
3361 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
3362 - Make the openbsd malloc code use 8k pages on alpha CPUs and
3364 - Detect mismatched page sizes when using --enable-openbsd-malloc.
3365 - Avoid double-marked-for-close warning when certain kinds of invalid
3366 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
3367 for bug 617. Bugfix on 0.2.0.1-alpha.
3368 - Make sure that the "NULL-means-reject *:*" convention is followed by
3369 all the policy manipulation functions, avoiding some possible crash
3370 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
3371 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
3372 actually works, and doesn't warn about every single reverse lookup.
3373 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
3376 - Only log guard node status when guard node status has changed.
3377 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
3378 make "INFO" 75% less verbose.
3381 Changes in version 0.2.0.21-rc - 2008-03-02
3382 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
3383 makes Tor work well with Vidalia again, fixes a rare assert bug,
3384 and fixes a pair of more minor bugs. The bundles also include Vidalia
3385 0.1.0 and Torbutton 1.1.16.
3388 - The control port should declare that it requires password auth
3389 when HashedControlSessionPassword is set too. Patch from Matt Edman;
3390 bugfix on 0.2.0.20-rc. Fixes bug 615.
3391 - Downgrade assert in connection_buckets_decrement() to a log message.
3392 This may help us solve bug 614, and in any case will make its
3393 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
3394 - We were sometimes miscounting the number of bytes read from the
3395 network, causing our rate limiting to not be followed exactly.
3396 Bugfix on 0.2.0.16-alpha. Reported by lodger.
3399 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
3400 OpenSSL versions should have been working fine. Diagnosis and patch
3401 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
3402 Bugfix on 0.2.0.20-rc.
3405 Changes in version 0.2.0.20-rc - 2008-02-24
3406 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
3407 makes more progress towards normalizing Tor's TLS handshake, makes
3408 hidden services work better again, helps relays bootstrap if they don't
3409 know their IP address, adds optional support for linking in openbsd's
3410 allocator or tcmalloc, allows really fast relays to scale past 15000
3411 sockets, and fixes a bunch of minor bugs reported by Veracode.
3414 - Enable the revised TLS handshake based on the one designed by
3415 Steven Murdoch in proposal 124, as revised in proposal 130. It
3416 includes version negotiation for OR connections as described in
3417 proposal 105. The new handshake is meant to be harder for censors
3418 to fingerprint, and it adds the ability to detect certain kinds of
3419 man-in-the-middle traffic analysis attacks. The version negotiation
3420 feature will allow us to improve Tor's link protocol more safely
3422 - Choose which bridge to use proportional to its advertised bandwidth,
3423 rather than uniformly at random. This should speed up Tor for
3424 bridge users. Also do this for people who set StrictEntryNodes.
3425 - When a TrackHostExits-chosen exit fails too many times in a row,
3426 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
3429 - Resolved problems with (re-)fetching hidden service descriptors.
3430 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
3432 - If we only ever used Tor for hidden service lookups or posts, we
3433 would stop building circuits and start refusing connections after
3434 24 hours, since we falsely believed that Tor was dormant. Reported
3435 by nwf; bugfix on 0.1.2.x.
3436 - Servers that don't know their own IP address should go to the
3437 authorities for their first directory fetch, even if their DirPort
3438 is off or if they don't know they're reachable yet. This will help
3439 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
3440 - When counting the number of open sockets, count not only the number
3441 of sockets we have received from the socket() call, but also
3442 the number we've gotten from accept() and socketpair(). This bug
3443 made us fail to count all sockets that we were using for incoming
3444 connections. Bugfix on 0.2.0.x.
3445 - Fix code used to find strings within buffers, when those strings
3446 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
3447 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
3448 - Add a new __HashedControlSessionPassword option for controllers
3449 to use for one-off session password hashes that shouldn't get
3450 saved to disk by SAVECONF --- Vidalia users were accumulating a
3451 pile of HashedControlPassword lines in their torrc files, one for
3452 each time they had restarted Tor and then clicked Save. Make Tor
3453 automatically convert "HashedControlPassword" to this new option but
3454 only when it's given on the command line. Partial fix for bug 586.
3456 o Minor features (performance):
3457 - Tune parameters for cell pool allocation to minimize amount of
3459 - Add OpenBSD malloc code from phk as an optional malloc
3460 replacement on Linux: some glibc libraries do very poorly
3461 with Tor's memory allocation patterns. Pass
3462 --enable-openbsd-malloc to get the replacement malloc code.
3463 - Add a --with-tcmalloc option to the configure script to link
3464 against tcmalloc (if present). Does not yet search for
3465 non-system include paths.
3466 - Stop imposing an arbitrary maximum on the number of file descriptors
3467 used for busy servers. Bug reported by Olaf Selke; patch from
3470 o Minor features (other):
3471 - When SafeLogging is disabled, log addresses along with all TLS
3473 - When building with --enable-gcc-warnings, check for whether Apple's
3474 warning "-Wshorten-64-to-32" is available.
3475 - Add a --passphrase-fd argument to the tor-gencert command for
3478 o Minor bugfixes (memory leaks and code problems):
3479 - We were leaking a file descriptor if Tor started with a zero-length
3480 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
3481 - Detect size overflow in zlib code. Reported by Justin Ferguson and
3483 - We were comparing the raw BridgePassword entry with a base64'ed
3484 version of it, when handling a "/tor/networkstatus-bridges"
3485 directory request. Now compare correctly. Noticed by Veracode.
3486 - Recover from bad tracked-since value in MTBF-history file.
3488 - Alter the code that tries to recover from unhandled write
3489 errors, to not try to flush onto a socket that's given us
3490 unhandled errors. Bugfix on 0.1.2.x.
3491 - Make Unix controlsockets work correctly on OpenBSD. Patch from
3492 tup. Bugfix on 0.2.0.3-alpha.
3494 o Minor bugfixes (other):
3495 - If we have an extra-info document for our server, always make
3496 it available on the control port, even if we haven't gotten
3497 a copy of it from an authority yet. Patch from mwenge.
3498 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
3499 - Directory mirrors no longer include a guess at the client's IP
3500 address if the connection appears to be coming from the same /24
3501 network; it was producing too many wrong guesses.
3502 - Make the new hidden service code respect the SafeLogging setting.
3503 Bugfix on 0.2.0.x. Patch from Karsten.
3504 - When starting as an authority, do not overwrite all certificates
3505 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
3506 - If we're trying to flush the last bytes on a connection (for
3507 example, when answering a directory request), reset the
3508 time-to-give-up timeout every time we manage to write something
3509 on the socket. Bugfix on 0.1.2.x.
3510 - Change the behavior of "getinfo status/good-server-descriptor"
3511 so it doesn't return failure when any authority disappears.
3512 - Even though the man page said that "TrackHostExits ." should
3513 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
3514 - Report TLS "zero return" case as a "clean close" and "IO error"
3515 as a "close". Stop calling closes "unexpected closes": existing
3516 Tors don't use SSL_close(), so having a connection close without
3517 the TLS shutdown handshake is hardly unexpected.
3518 - Send NAMESERVER_STATUS messages for a single failed nameserver
3521 o Code simplifications and refactoring:
3522 - Remove the tor_strpartition function: its logic was confused,
3523 and it was only used for one thing that could be implemented far
3527 Changes in version 0.2.0.19-alpha - 2008-02-09
3528 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
3529 handshake, makes path selection for relays more secure and IP address
3530 guessing more robust, and generally fixes a lot of bugs in preparation
3531 for calling the 0.2.0 branch stable.
3534 - Do not include recognizeable strings in the commonname part of
3535 Tor's x509 certificates.
3538 - If we're a relay, avoid picking ourselves as an introduction point,
3539 a rendezvous point, or as the final hop for internal circuits. Bug
3540 reported by taranis and lodger. Bugfix on 0.1.2.x.
3541 - Patch from "Andrew S. Lists" to catch when we contact a directory
3542 mirror at IP address X and he says we look like we're coming from
3543 IP address X. Bugfix on 0.1.2.x.
3545 o Minor features (security):
3546 - Be more paranoid about overwriting sensitive memory on free(),
3547 as a defensive programming tactic to ensure forward secrecy.
3549 o Minor features (directory authority):
3550 - Actually validate the options passed to AuthDirReject,
3551 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
3552 - Reject router descriptors with out-of-range bandwidthcapacity or
3553 bandwidthburst values.
3555 o Minor features (controller):
3556 - Reject controller commands over 1MB in length. This keeps rogue
3557 processes from running us out of memory.
3559 o Minor features (misc):
3560 - Give more descriptive well-formedness errors for out-of-range
3561 hidden service descriptor/protocol versions.
3562 - Make memory debugging information describe more about history
3563 of cell allocation, so we can help reduce our memory use.
3565 o Deprecated features (controller):
3566 - The status/version/num-versioning and status/version/num-concurring
3567 GETINFO options are no longer useful in the v3 directory protocol:
3568 treat them as deprecated, and warn when they're used.
3571 - When our consensus networkstatus has been expired for a while, stop
3572 being willing to build circuits using it. Fixes bug 401. Bugfix
3574 - Directory caches now fetch certificates from all authorities
3575 listed in a networkstatus consensus, even when they do not
3576 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
3577 - When connecting to a bridge without specifying its key, insert
3578 the connection into the identity-to-connection map as soon as
3579 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
3580 - Detect versions of OS X where malloc_good_size() is present in the
3581 library but never actually declared. Resolves bug 587. Bugfix
3583 - Stop incorrectly truncating zlib responses to directory authority
3584 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
3585 - Stop recommending that every server operator send mail to tor-ops.
3586 Resolves bug 597. Bugfix on 0.1.2.x.
3587 - Don't trigger an assert if we start a directory authority with a
3588 private IP address (like 127.0.0.1).
3589 - Avoid possible failures when generating a directory with routers
3590 with over-long versions strings, or too many flags set. Bugfix
3592 - If an attempt to launch a DNS resolve request over the control
3593 port fails because we have overrun the limit on the number of
3594 connections, tell the controller that the request has failed.
3595 - Avoid using too little bandwidth when our clock skips a few
3596 seconds. Bugfix on 0.1.2.x.
3597 - Fix shell error when warning about missing packages in configure
3598 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
3599 - Do not become confused when receiving a spurious VERSIONS-like
3600 cell from a confused v1 client. Bugfix on 0.2.0.x.
3601 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
3602 introduction points for a hidden service have failed. Patch from
3603 Karsten Loesing. Bugfix on 0.2.0.x.
3605 o Code simplifications and refactoring:
3606 - Remove some needless generality from cpuworker code, for improved
3608 - Stop overloading the circuit_t.onionskin field for both "onionskin
3609 from a CREATE cell that we are waiting for a cpuworker to be
3610 assigned" and "onionskin from an EXTEND cell that we are going to
3611 send to an OR as soon as we are connected". Might help with bug 600.
3612 - Add an in-place version of aes_crypt() so that we can avoid doing a
3613 needless memcpy() call on each cell payload.
3616 Changes in version 0.2.0.18-alpha - 2008-01-25
3617 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
3618 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
3619 that can warn or reject connections to ports generally associated with
3620 vulnerable-plaintext protocols.
3622 o New directory authorities:
3623 - Set up dannenberg (run by CCC) as the sixth v3 directory
3627 - Fix a major memory leak when attempting to use the v2 TLS
3628 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
3629 - We accidentally enabled the under-development v2 TLS handshake
3630 code, which was causing log entries like "TLS error while
3631 renegotiating handshake". Disable it again. Resolves bug 590.
3632 - We were computing the wrong Content-Length: header for directory
3633 responses that need to be compressed on the fly, causing clients
3634 asking for those items to always fail. Bugfix on 0.2.0.x; partially
3638 - Avoid going directly to the directory authorities even if you're a
3639 relay, if you haven't found yourself reachable yet or if you've
3640 decided not to advertise your dirport yet. Addresses bug 556.
3641 - If we've gone 12 hours since our last bandwidth check, and we
3642 estimate we have less than 50KB bandwidth capacity but we could
3643 handle more, do another bandwidth test.
3644 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3645 Tor can warn and/or refuse connections to ports commonly used with
3646 vulnerable-plaintext protocols. Currently we warn on ports 23,
3647 109, 110, and 143, but we don't reject any.
3650 - When we setconf ClientOnly to 1, close any current OR and Dir
3651 listeners. Reported by mwenge.
3652 - When we get a consensus that's been signed by more people than
3653 we expect, don't log about it; it's not a big deal. Reported
3657 - Don't answer "/tor/networkstatus-bridges" directory requests if
3658 the request isn't encrypted.
3659 - Make "ClientOnly 1" config option disable directory ports too.
3660 - Patches from Karsten Loesing to make v2 hidden services more
3661 robust: work even when there aren't enough HSDir relays available;
3662 retry when a v2 rend desc fetch fails; but don't retry if we
3663 already have a usable v0 rend desc.
3666 Changes in version 0.2.0.17-alpha - 2008-01-17
3667 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
3670 - Make the tor-gencert man page get included correctly in the tarball.
3673 Changes in version 0.2.0.16-alpha - 2008-01-17
3674 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
3675 Loesing, and generally cleans up a lot of features and minor bugs.
3677 o New directory authorities:
3678 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
3681 o Major performance improvements:
3682 - Switch our old ring buffer implementation for one more like that
3683 used by free Unix kernels. The wasted space in a buffer with 1mb
3684 of data will now be more like 8k than 1mb. The new implementation
3685 also avoids realloc();realloc(); patterns that can contribute to
3686 memory fragmentation.
3689 - Configuration files now accept C-style strings as values. This
3690 helps encode characters not allowed in the current configuration
3691 file format, such as newline or #. Addresses bug 557.
3692 - Although we fixed bug 539 (where servers would send HTTP status 503
3693 responses _and_ send a body too), there are still servers out
3694 there that haven't upgraded. Therefore, make clients parse such
3695 bodies when they receive them.
3696 - When we're not serving v2 directory information, there is no reason
3697 to actually keep any around. Remove the obsolete files and directory
3698 on startup if they are very old and we aren't going to serve them.
3700 o Minor performance improvements:
3701 - Reference-count and share copies of address policy entries; only 5%
3702 of them were actually distinct.
3703 - Never walk through the list of logs if we know that no log is
3704 interested in a given message.
3707 - When an authority has not signed a consensus, do not try to
3708 download a nonexistent "certificate with key 00000000". Bugfix
3709 on 0.2.0.x. Fixes bug 569.
3710 - Fix a rare assert error when we're closing one of our threads:
3711 use a mutex to protect the list of logs, so we never write to the
3712 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
3713 bug 575, which is kind of the revenge of bug 222.
3714 - Patch from Karsten Loesing to complain less at both the client
3715 and the relay when a relay used to have the HSDir flag but doesn't
3716 anymore, and we try to upload a hidden service descriptor.
3717 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
3719 - Do not try to download missing certificates until we have tried
3720 to check our fallback consensus. Fixes bug 583.
3721 - Make bridges round reported GeoIP stats info up to the nearest
3722 estimate, not down. Now we can distinguish between "0 people from
3723 this country" and "1 person from this country".
3724 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
3725 - Avoid possible segfault if key generation fails in
3726 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
3727 - Avoid segfault in the case where a badly behaved v2 versioning
3728 directory sends a signed networkstatus with missing client-versions.
3730 - Avoid segfaults on certain complex invocations of
3731 router_get_by_hexdigest(). Bugfix on 0.1.2.
3732 - Correct bad index on array access in parse_http_time(). Bugfix
3734 - Fix possible bug in vote generation when server versions are present
3735 but client versions are not.
3736 - Fix rare bug on REDIRECTSTREAM control command when called with no
3737 port set: it could erroneously report an error when none had
3739 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
3740 compressing large objects and find ourselves with more than 4k
3741 left over. Bugfix on 0.2.0.
3742 - Fix a small memory leak when setting up a hidden service.
3743 - Fix a few memory leaks that could in theory happen under bizarre
3745 - Fix an assert if we post a general-purpose descriptor via the
3746 control port but that descriptor isn't mentioned in our current
3747 network consensus. Bug reported by Jon McLachlan; bugfix on
3750 o Minor features (controller):
3751 - Get NS events working again. Patch from tup.
3752 - The GETCONF command now escapes and quotes configuration values
3753 that don't otherwise fit into the torrc file.
3754 - The SETCONF command now handles quoted values correctly.
3756 o Minor features (directory authorities):
3757 - New configuration options to override default maximum number of
3758 servers allowed on a single IP address. This is important for
3759 running a test network on a single host.
3760 - Actually implement the -s option to tor-gencert.
3761 - Add a manual page for tor-gencert.
3763 o Minor features (bridges):
3764 - Bridge authorities no longer serve bridge descriptors over
3765 unencrypted connections.
3767 o Minor features (other):
3768 - Add hidden services and DNSPorts to the list of things that make
3769 Tor accept that it has running ports. Change starting Tor with no
3770 ports from a fatal error to a warning; we might change it back if
3771 this turns out to confuse anybody. Fixes bug 579.
3774 Changes in version 0.1.2.19 - 2008-01-17
3775 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3776 exit policy a little bit more conservative so it's safer to run an
3777 exit relay on a home system, and fixes a variety of smaller issues.
3780 - Exit policies now reject connections that are addressed to a
3781 relay's public (external) IP address too, unless
3782 ExitPolicyRejectPrivate is turned off. We do this because too
3783 many relays are running nearby to services that trust them based
3787 - When the clock jumps forward a lot, do not allow the bandwidth
3788 buckets to become negative. Fixes bug 544.
3789 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3790 on every successful resolve. Reported by Mike Perry.
3791 - Purge old entries from the "rephist" database and the hidden
3792 service descriptor database even when DirPort is zero.
3793 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3794 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3795 crashing or mis-answering these requests.
3796 - When we decide to send a 503 response to a request for servers, do
3797 not then also send the server descriptors: this defeats the whole
3798 purpose. Fixes bug 539.
3801 - Changing the ExitPolicyRejectPrivate setting should cause us to
3802 rebuild our server descriptor.
3803 - Fix handling of hex nicknames when answering controller requests for
3804 networkstatus by name, or when deciding whether to warn about
3805 unknown routers in a config option. (Patch from mwenge.)
3806 - Fix a couple of hard-to-trigger autoconf problems that could result
3807 in really weird results on platforms whose sys/types.h files define
3808 nonstandard integer types.
3809 - Don't try to create the datadir when running --verify-config or
3810 --hash-password. Resolves bug 540.
3811 - If we were having problems getting a particular descriptor from the
3812 directory caches, and then we learned about a new descriptor for
3813 that router, we weren't resetting our failure count. Reported
3815 - Although we fixed bug 539 (where servers would send HTTP status 503
3816 responses _and_ send a body too), there are still servers out there
3817 that haven't upgraded. Therefore, make clients parse such bodies
3818 when they receive them.
3819 - Run correctly on systems where rlim_t is larger than unsigned long.
3820 This includes some 64-bit systems.
3821 - Run correctly on platforms (like some versions of OS X 10.5) where
3822 the real limit for number of open files is OPEN_FILES, not rlim_max
3823 from getrlimit(RLIMIT_NOFILES).
3824 - Avoid a spurious free on base64 failure.
3825 - Avoid segfaults on certain complex invocations of
3826 router_get_by_hexdigest().
3827 - Fix rare bug on REDIRECTSTREAM control command when called with no
3828 port set: it could erroneously report an error when none had
3832 Changes in version 0.2.0.15-alpha - 2007-12-25
3833 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
3834 features added in 0.2.0.13-alpha.
3837 - Fix several remotely triggerable asserts based on DirPort requests
3838 for a v2 or v3 networkstatus object before we were prepared. This
3839 was particularly bad for 0.2.0.13 and later bridge relays, who
3840 would never have a v2 networkstatus and would thus always crash
3841 when used. Bugfixes on 0.2.0.x.
3842 - Estimate the v3 networkstatus size more accurately, rather than
3843 estimating it at zero bytes and giving it artificially high priority
3844 compared to other directory requests. Bugfix on 0.2.0.x.
3847 - Fix configure.in logic for cross-compilation.
3848 - When we load a bridge descriptor from the cache, and it was
3849 previously unreachable, mark it as retriable so we won't just
3850 ignore it. Also, try fetching a new copy immediately. Bugfixes
3852 - The bridge GeoIP stats were counting other relays, for example
3853 self-reachability and authority-reachability tests.
3856 - Support compilation to target iPhone; patch from cjacker huang.
3857 To build for iPhone, pass the --enable-iphone option to configure.
3860 Changes in version 0.2.0.14-alpha - 2007-12-23
3862 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
3863 without a datadirectory from a previous Tor install. Reported
3865 - Fix a crash when we fetch a descriptor that turns out to be
3866 unexpected (it used to be in our networkstatus when we started
3867 fetching it, but it isn't in our current networkstatus), and we
3868 aren't using bridges. Bugfix on 0.2.0.x.
3869 - Fix a crash when accessing hidden services: it would work the first
3870 time you use a given introduction point for your service, but
3871 on subsequent requests we'd be using garbage memory. Fixed by
3872 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
3873 - Fix a crash when we load a bridge descriptor from disk but we don't
3874 currently have a Bridge line for it in our torrc. Bugfix on
3878 - If bridge authorities set BridgePassword, they will serve a
3879 snapshot of known bridge routerstatuses from their DirPort to
3880 anybody who knows that password. Unset by default.
3883 - Make the unit tests build again.
3884 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
3885 - Make PublishServerDescriptor default to 1, so the default doesn't
3886 have to change as we invent new directory protocol versions.
3887 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
3888 be included unless sys/time.h is already included. Fixes
3889 bug 553. Bugfix on 0.2.0.x.
3890 - If we receive a general-purpose descriptor and then receive an
3891 identical bridge-purpose descriptor soon after, don't discard
3892 the next one as a duplicate.
3895 - If BridgeRelay is set to 1, then the default for
3896 PublishServerDescriptor is now "bridge" rather than "v2,v3".
3897 - If the user sets RelayBandwidthRate but doesn't set
3898 RelayBandwidthBurst, then make them equal rather than erroring out.
3901 Changes in version 0.2.0.13-alpha - 2007-12-21
3902 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
3903 Goodell, fixes many more bugs, and adds a lot of infrastructure for
3906 o New directory authorities:
3907 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
3911 - Only update guard status (usable / not usable) once we have
3912 enough directory information. This was causing us to always pick
3913 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
3914 causing us to discard all our guards on startup if we hadn't been
3915 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
3916 - Purge old entries from the "rephist" database and the hidden
3917 service descriptor databases even when DirPort is zero. Bugfix
3919 - We were ignoring our RelayBandwidthRate for the first 30 seconds
3920 after opening a circuit -- even a relayed circuit. Bugfix on
3922 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3923 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3924 crashing or mis-answering these types of requests.
3925 - Relays were publishing their server descriptor to v1 and v2
3926 directory authorities, but they didn't try publishing to v3-only
3927 authorities. Fix this; and also stop publishing to v1 authorities.
3929 - When we were reading router descriptors from cache, we were ignoring
3930 the annotations -- so for example we were reading in bridge-purpose
3931 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
3932 - When we decided to send a 503 response to a request for servers, we
3933 were then also sending the server descriptors: this defeats the
3934 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
3937 - Bridge relays now behave like clients with respect to time
3938 intervals for downloading new consensus documents -- otherwise they
3939 stand out. Bridge users now wait until the end of the interval,
3940 so their bridge relay will be sure to have a new consensus document.
3941 - Three new config options (AlternateDirAuthority,
3942 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3943 user selectively replace the default directory authorities by type,
3944 rather than the all-or-nothing replacement that DirServer offers.
3945 - Tor can now be configured to read a GeoIP file from disk in one
3946 of two formats. This can be used by controllers to map IP addresses
3947 to countries. Eventually, it may support exit-by-country.
3948 - When possible, bridge relays remember which countries users
3949 are coming from, and report aggregate information in their
3950 extra-info documents, so that the bridge authorities can learn
3951 where Tor is blocked.
3952 - Bridge directory authorities now do reachability testing on the
3953 bridges they know. They provide router status summaries to the
3954 controller via "getinfo ns/purpose/bridge", and also dump summaries
3955 to a file periodically.
3956 - Stop fetching directory info so aggressively if your DirPort is
3957 on but your ORPort is off; stop fetching v2 dir info entirely.
3958 You can override these choices with the new FetchDirInfoEarly
3962 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
3963 consensus documents when there are too many relays at a single
3964 IP address. Now clear it in v2 network status documents too, and
3965 also clear it in routerinfo_t when the relay is no longer listed
3966 in the relevant networkstatus document.
3967 - Don't crash if we get an unexpected value for the
3968 PublishServerDescriptor config option. Reported by Matt Edman;
3969 bugfix on 0.2.0.9-alpha.
3970 - Our new v2 hidden service descriptor format allows descriptors
3971 that have no introduction points. But Tor crashed when we tried
3972 to build a descriptor with no intro points (and it would have
3973 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
3975 - Fix building with dmalloc 5.5.2 with glibc.
3976 - Reject uploaded descriptors and extrainfo documents if they're
3977 huge. Otherwise we'll cache them all over the network and it'll
3978 clog everything up. Reported by Aljosha Judmayer.
3979 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
3980 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
3981 - When the DANGEROUS_VERSION controller status event told us we're
3982 running an obsolete version, it used the string "OLD" to describe
3983 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3984 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
3985 - If we can't expand our list of entry guards (e.g. because we're
3986 using bridges or we have StrictEntryNodes set), don't mark relays
3987 down when they fail a directory request. Otherwise we're too quick
3988 to mark all our entry points down. Bugfix on 0.1.2.x.
3989 - Fix handling of hex nicknames when answering controller requests for
3990 networkstatus by name, or when deciding whether to warn about unknown
3991 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
3992 - Fix a couple of hard-to-trigger autoconf problems that could result
3993 in really weird results on platforms whose sys/types.h files define
3994 nonstandard integer types. Bugfix on 0.1.2.x.
3995 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
3996 - Don't crash on name lookup when we have no current consensus. Fixes
3997 bug 538; bugfix on 0.2.0.x.
3998 - Only Tors that want to mirror the v2 directory info should
3999 create the "cached-status" directory in their datadir. (All Tors
4000 used to create it.) Bugfix on 0.2.0.9-alpha.
4001 - Directory authorities should only automatically download Extra Info
4002 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
4005 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
4006 consumers. (We already do this on HUP.)
4007 - Authorities and caches fetch the v2 networkstatus documents
4008 less often, now that v3 is encouraged.
4009 - Add a new config option BridgeRelay that specifies you want to
4010 be a bridge relay. Right now the only difference is that it makes
4011 you answer begin_dir requests, and it makes you cache dir info,
4012 even if your DirPort isn't on.
4013 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
4014 ask about source, timestamp of arrival, purpose, etc. We need
4015 something like this to help Vidalia not do GeoIP lookups on bridge
4017 - Allow multiple HashedControlPassword config lines, to support
4018 multiple controller passwords.
4019 - Authorities now decide whether they're authoritative for a given
4020 router based on the router's purpose.
4021 - New config options AuthDirBadDir and AuthDirListBadDirs for
4022 authorities to mark certain relays as "bad directories" in the
4023 networkstatus documents. Also supports the "!baddir" directive in
4024 the approved-routers file.
4027 Changes in version 0.2.0.12-alpha - 2007-11-16
4028 This twelfth development snapshot fixes some more build problems as
4029 well as a few minor bugs.
4032 - Make it build on OpenBSD again. Patch from tup.
4033 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
4034 package-building for Red Hat, OS X, etc.
4036 o Minor bugfixes (on 0.1.2.x):
4037 - Changing the ExitPolicyRejectPrivate setting should cause us to
4038 rebuild our server descriptor.
4040 o Minor bugfixes (on 0.2.0.x):
4041 - When we're lacking a consensus, don't try to perform rendezvous
4042 operations. Reported by Karsten Loesing.
4043 - Fix a small memory leak whenever we decide against using a
4044 newly picked entry guard. Reported by Mike Perry.
4045 - When authorities detected more than two relays running on the same
4046 IP address, they were clearing all the status flags but forgetting
4047 to clear the "hsdir" flag. So clients were being told that a
4048 given relay was the right choice for a v2 hsdir lookup, yet they
4049 never had its descriptor because it was marked as 'not running'
4051 - If we're trying to fetch a bridge descriptor and there's no way
4052 the bridge authority could help us (for example, we don't know
4053 a digest, or there is no bridge authority), don't be so eager to
4054 fall back to asking the bridge authority.
4055 - If we're using bridges or have strictentrynodes set, and our
4056 chosen exit is in the same family as all our bridges/entry guards,
4057 then be flexible about families.
4060 - When we negotiate a v2 link-layer connection (not yet implemented),
4061 accept RELAY_EARLY cells and turn them into RELAY cells if we've
4062 negotiated a v1 connection for their next step. Initial code for
4066 Changes in version 0.2.0.11-alpha - 2007-11-12
4067 This eleventh development snapshot fixes some build problems with
4068 the previous snapshot. It also includes a more secure-by-default exit
4069 policy for relays, fixes an enormous memory leak for exit relays, and
4070 fixes another bug where servers were falling out of the directory list.
4073 - Exit policies now reject connections that are addressed to a
4074 relay's public (external) IP address too, unless
4075 ExitPolicyRejectPrivate is turned off. We do this because too
4076 many relays are running nearby to services that trust them based
4077 on network address. Bugfix on 0.1.2.x.
4080 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
4081 on every successful resolve. Reported by Mike Perry; bugfix
4083 - On authorities, never downgrade to old router descriptors simply
4084 because they're listed in the consensus. This created a catch-22
4085 where we wouldn't list a new descriptor because there was an
4086 old one in the consensus, and we couldn't get the new one in the
4087 consensus because we wouldn't list it. Possible fix for bug 548.
4088 Also, this might cause bug 543 to appear on authorities; if so,
4089 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
4091 o Packaging fixes on 0.2.0.10-alpha:
4092 - We were including instructions about what to do with the
4093 src/config/fallback-consensus file, but we weren't actually
4094 including it in the tarball. Disable all of that for now.
4097 - Allow people to say PreferTunnelledDirConns rather than
4098 PreferTunneledDirConns, for those alternate-spellers out there.
4101 - Don't reevaluate all the information from our consensus document
4102 just because we've downloaded a v2 networkstatus that we intend
4103 to cache. Fixes bug 545; bugfix on 0.2.0.x.
4106 Changes in version 0.2.0.10-alpha - 2007-11-10
4107 This tenth development snapshot adds a third v3 directory authority
4108 run by Mike Perry, adds most of Karsten Loesing's new hidden service
4109 descriptor format, fixes a bad crash bug and new bridge bugs introduced
4110 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
4111 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
4112 addresses many more minor issues.
4114 o New directory authorities:
4115 - Set up ides (run by Mike Perry) as the third v3 directory authority.
4118 - Allow tunnelled directory connections to ask for an encrypted
4119 "begin_dir" connection or an anonymized "uses a full Tor circuit"
4120 connection independently. Now we can make anonymized begin_dir
4121 connections for (e.g.) more secure hidden service posting and
4123 - More progress on proposal 114: code from Karsten Loesing to
4124 implement new hidden service descriptor format.
4125 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
4126 accommodate the growing number of servers that use the default
4127 and are reaching it.
4128 - Directory authorities use a new formula for selecting which nodes
4129 to advertise as Guards: they must be in the top 7/8 in terms of
4130 how long we have known about them, and above the median of those
4131 nodes in terms of weighted fractional uptime.
4132 - Make "not enough dir info yet" warnings describe *why* Tor feels
4133 it doesn't have enough directory info yet.
4136 - Stop servers from crashing if they set a Family option (or
4137 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
4139 - Make bridge users work again -- the move to v3 directories in
4140 0.2.0.9-alpha had introduced a number of bugs that made bridges
4141 no longer work for clients.
4142 - When the clock jumps forward a lot, do not allow the bandwidth
4143 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
4145 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
4146 - When the consensus lists a router descriptor that we previously were
4147 mirroring, but that we considered non-canonical, reload the
4148 descriptor as canonical. This fixes bug 543 where Tor servers
4149 would start complaining after a few days that they don't have
4150 enough directory information to build a circuit.
4151 - Consider replacing the current consensus when certificates arrive
4152 that make the pending consensus valid. Previously, we were only
4153 considering replacement when the new certs _didn't_ help.
4154 - Fix an assert error on startup if we didn't already have the
4155 consensus and certs cached in our datadirectory: we were caching
4156 the consensus in consensus_waiting_for_certs but then free'ing it
4158 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
4159 Request) if we need more v3 certs but we've already got pending
4160 requests for all of them.
4161 - Correctly back off from failing certificate downloads. Fixes
4163 - Authorities don't vote on the Running flag if they have been running
4164 for less than 30 minutes themselves. Fixes bug 547, where a newly
4165 started authority would vote that everyone was down.
4168 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
4169 it, it had no AES, and it hasn't seen any security patches since
4173 - Clients now hold circuitless TLS connections open for 1.5 times
4174 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
4175 rebuild a new circuit over them within that timeframe. Previously,
4176 they held them open only for KeepalivePeriod (5 minutes).
4177 - Use "If-Modified-Since" to avoid retrieving consensus
4178 networkstatuses that we already have.
4179 - When we have no consensus, check FallbackNetworkstatusFile (defaults
4180 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
4181 we start knowing some directory caches.
4182 - When we receive a consensus from the future, warn about skew.
4183 - Improve skew reporting: try to give the user a better log message
4184 about how skewed they are, and how much this matters.
4185 - When we have a certificate for an authority, believe that
4186 certificate's claims about the authority's IP address.
4187 - New --quiet command-line option to suppress the default console log.
4188 Good in combination with --hash-password.
4189 - Authorities send back an X-Descriptor-Not-New header in response to
4190 an accepted-but-discarded descriptor upload. Partially implements
4192 - Make the log message for "tls error. breaking." more useful.
4193 - Better log messages about certificate downloads, to attempt to
4194 track down the second incarnation of bug 546.
4196 o Minor features (bridges):
4197 - If bridge users set UpdateBridgesFromAuthority, but the digest
4198 they ask for is a 404 from the bridge authority, they now fall
4199 back to trying the bridge directly.
4200 - Bridges now use begin_dir to publish their server descriptor to
4201 the bridge authority, even when they haven't set TunnelDirConns.
4203 o Minor features (controller):
4204 - When reporting clock skew, and we know that the clock is _at least
4205 as skewed_ as some value, but we don't know the actual value,
4206 report the value as a "minimum skew."
4209 - Update linux-tor-prio.sh script to allow QoS based on the uid of
4210 the Tor process. Patch from Marco Bonetti with tweaks from Mike
4214 - Refuse to start if both ORPort and UseBridges are set. Bugfix
4215 on 0.2.0.x, suggested by Matt Edman.
4216 - Don't stop fetching descriptors when FetchUselessDescriptors is
4217 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
4218 reported by tup and ioerror.
4219 - Better log message on vote from unknown authority.
4220 - Don't log "Launching 0 request for 0 router" message.
4222 o Minor bugfixes (memory leaks):
4223 - Stop leaking memory every time we parse a v3 certificate. Bugfix
4225 - Stop leaking memory every time we load a v3 certificate. Bugfix
4226 on 0.2.0.1-alpha. Fixes bug 536.
4227 - Stop leaking a cached networkstatus on exit. Bugfix on
4229 - Stop leaking voter information every time we free a consensus.
4230 Bugfix on 0.2.0.3-alpha.
4231 - Stop leaking signed data every time we check a voter signature.
4232 Bugfix on 0.2.0.3-alpha.
4233 - Stop leaking a signature every time we fail to parse a consensus or
4234 a vote. Bugfix on 0.2.0.3-alpha.
4235 - Stop leaking v2_download_status_map on shutdown. Bugfix on
4237 - Stop leaking conn->nickname every time we make a connection to a
4238 Tor relay without knowing its expected identity digest (e.g. when
4239 using bridges). Bugfix on 0.2.0.3-alpha.
4241 - Minor bugfixes (portability):
4242 - Run correctly on platforms where rlim_t is larger than unsigned
4243 long, and/or where the real limit for number of open files is
4244 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
4245 particular, these may be needed for OS X 10.5.
4248 Changes in version 0.1.2.18 - 2007-10-28
4249 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
4250 hidden service introduction that were causing huge delays, and a big
4251 bug that was causing some servers to disappear from the network status
4252 lists for a few hours each day.
4254 o Major bugfixes (crashes):
4255 - If a connection is shut down abruptly because of something that
4256 happened inside connection_flushed_some(), do not call
4257 connection_finished_flushing(). Should fix bug 451:
4258 "connection_stop_writing: Assertion conn->write_event failed"
4259 Bugfix on 0.1.2.7-alpha.
4260 - Fix possible segfaults in functions called from
4261 rend_process_relay_cell().
4263 o Major bugfixes (hidden services):
4264 - Hidden services were choosing introduction points uniquely by
4265 hexdigest, but when constructing the hidden service descriptor
4266 they merely wrote the (potentially ambiguous) nickname.
4267 - Clients now use the v2 intro format for hidden service
4268 connections: they specify their chosen rendezvous point by identity
4269 digest rather than by (potentially ambiguous) nickname. These
4270 changes could speed up hidden service connections dramatically.
4272 o Major bugfixes (other):
4273 - Stop publishing a new server descriptor just because we get a
4274 HUP signal. This led (in a roundabout way) to some servers getting
4275 dropped from the networkstatus lists for a few hours each day.
4276 - When looking for a circuit to cannibalize, consider family as well
4277 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4278 circuit cannibalization).
4279 - When a router wasn't listed in a new networkstatus, we were leaving
4280 the flags for that router alone -- meaning it remained Named,
4281 Running, etc -- even though absence from the networkstatus means
4282 that it shouldn't be considered to exist at all anymore. Now we
4283 clear all the flags for routers that fall out of the networkstatus
4284 consensus. Fixes bug 529.
4287 - Don't try to access (or alter) the state file when running
4288 --list-fingerprint or --verify-config or --hash-password. Resolves
4290 - When generating information telling us how to extend to a given
4291 router, do not try to include the nickname if it is
4292 absent. Resolves bug 467.
4293 - Fix a user-triggerable segfault in expand_filename(). (There isn't
4294 a way to trigger this remotely.)
4295 - When sending a status event to the controller telling it that an
4296 OR address is reachable, set the port correctly. (Previously we
4297 were reporting the dir port.)
4298 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4299 command. Bugfix on 0.1.2.17.
4300 - When loading bandwidth history, do not believe any information in
4301 the future. Fixes bug 434.
4302 - When loading entry guard information, do not believe any information
4304 - When we have our clock set far in the future and generate an
4305 onion key, then re-set our clock to be correct, we should not stop
4306 the onion key from getting rotated.
4307 - On some platforms, accept() can return a broken address. Detect
4308 this more quietly, and deal accordingly. Fixes bug 483.
4309 - It's not actually an error to find a non-pending entry in the DNS
4310 cache when canceling a pending resolve. Don't log unless stuff
4311 is fishy. Resolves bug 463.
4312 - Don't reset trusted dir server list when we set a configuration
4313 option. Patch from Robert Hogan.
4314 - Don't try to create the datadir when running --verify-config or
4315 --hash-password. Resolves bug 540.
4318 Changes in version 0.2.0.9-alpha - 2007-10-24
4319 This ninth development snapshot switches clients to the new v3 directory
4320 system; allows servers to be listed in the network status even when they
4321 have the same nickname as a registered server; and fixes many other
4322 bugs including a big one that was causing some servers to disappear
4323 from the network status lists for a few hours each day.
4325 o Major features (directory system):
4326 - Clients now download v3 consensus networkstatus documents instead
4327 of v2 networkstatus documents. Clients and caches now base their
4328 opinions about routers on these consensus documents. Clients only
4329 download router descriptors listed in the consensus.
4330 - Authorities now list servers who have the same nickname as
4331 a different named server, but list them with a new flag,
4332 "Unnamed". Now we can list servers that happen to pick the same
4333 nickname as a server that registered two years ago and then
4334 disappeared. Partially implements proposal 122.
4335 - If the consensus lists a router as "Unnamed", the name is assigned
4336 to a different router: do not identify the router by that name.
4337 Partially implements proposal 122.
4338 - Authorities can now come to a consensus on which method to use to
4339 compute the consensus. This gives us forward compatibility.
4342 - Stop publishing a new server descriptor just because we HUP or
4343 when we find our DirPort to be reachable but won't actually publish
4344 it. New descriptors without any real changes are dropped by the
4345 authorities, and can screw up our "publish every 18 hours" schedule.
4347 - When a router wasn't listed in a new networkstatus, we were leaving
4348 the flags for that router alone -- meaning it remained Named,
4349 Running, etc -- even though absence from the networkstatus means
4350 that it shouldn't be considered to exist at all anymore. Now we
4351 clear all the flags for routers that fall out of the networkstatus
4352 consensus. Fixes bug 529; bugfix on 0.1.2.x.
4353 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
4354 extrainfo documents and then discard them immediately for not
4355 matching the latest router. Bugfix on 0.2.0.1-alpha.
4357 o Minor features (v3 directory protocol):
4358 - Allow tor-gencert to generate a new certificate without replacing
4360 - Allow certificates to include an address.
4361 - When we change our directory-cache settings, reschedule all voting
4362 and download operations.
4363 - Reattempt certificate downloads immediately on failure, as long as
4364 we haven't failed a threshold number of times yet.
4365 - Delay retrying consensus downloads while we're downloading
4366 certificates to verify the one we just got. Also, count getting a
4367 consensus that we already have (or one that isn't valid) as a failure,
4368 and count failing to get the certificates after 20 minutes as a
4370 - Build circuits and download descriptors even if our consensus is a
4371 little expired. (This feature will go away once authorities are
4374 o Minor features (router descriptor cache):
4375 - If we find a cached-routers file that's been sitting around for more
4376 than 28 days unmodified, then most likely it's a leftover from
4377 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
4379 - When we (as a cache) download a descriptor because it was listed
4380 in a consensus, remember when the consensus was supposed to expire,
4381 and don't expire the descriptor until then.
4383 o Minor features (performance):
4384 - Call routerlist_remove_old_routers() much less often. This should
4385 speed startup, especially on directory caches.
4386 - Don't try to launch new descriptor downloads quite so often when we
4387 already have enough directory information to build circuits.
4388 - Base64 decoding was actually showing up on our profile when parsing
4389 the initial descriptor file; switch to an in-process all-at-once
4390 implementation that's about 3.5x times faster than calling out to
4393 o Minor features (compilation):
4394 - Detect non-ASCII platforms (if any still exist) and refuse to
4395 build there: some of our code assumes that 'A' is 65 and so on.
4397 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
4398 - Make the "next period" votes into "current period" votes immediately
4399 after publishing the consensus; avoid a heisenbug that made them
4400 stick around indefinitely.
4401 - When we discard a vote as a duplicate, do not report this as
4403 - Treat missing v3 keys or certificates as an error when running as a
4404 v3 directory authority.
4405 - When we're configured to be a v3 authority, but we're only listed
4406 as a non-v3 authority in our DirServer line for ourself, correct
4408 - If an authority doesn't have a qualified hostname, just put
4409 its address in the vote. This fixes the problem where we referred to
4410 "moria on moria:9031."
4411 - Distinguish between detached signatures for the wrong period, and
4412 detached signatures for a divergent vote.
4413 - Fix a small memory leak when computing a consensus.
4414 - When there's no concensus, we were forming a vote every 30
4415 minutes, but writing the "valid-after" line in our vote based
4416 on our configured V3AuthVotingInterval: so unless the intervals
4417 matched up, we immediately rejected our own vote because it didn't
4418 start at the voting interval that caused us to construct a vote.
4420 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
4421 - Delete unverified-consensus when the real consensus is set.
4422 - Consider retrying a consensus networkstatus fetch immediately
4423 after one fails: don't wait 60 seconds to notice.
4424 - When fetching a consensus as a cache, wait until a newer consensus
4425 should exist before trying to replace the current one.
4426 - Use a more forgiving schedule for retrying failed consensus
4427 downloads than for other types.
4429 o Minor bugfixes (other directory issues):
4430 - Correct the implementation of "download votes by digest." Bugfix on
4432 - Authorities no longer send back "400 you're unreachable please fix
4433 it" errors to Tor servers that aren't online all the time. We're
4434 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
4436 o Minor bugfixes (controller):
4437 - Don't reset trusted dir server list when we set a configuration
4438 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
4439 - Respond to INT and TERM SIGNAL commands before we execute the
4440 signal, in case the signal shuts us down. We had a patch in
4441 0.1.2.1-alpha that tried to do this by queueing the response on
4442 the connection's buffer before shutting down, but that really
4443 isn't the same thing at all. Bug located by Matt Edman.
4445 o Minor bugfixes (misc):
4446 - Correctly check for bad options to the "PublishServerDescriptor"
4447 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
4448 - Stop leaking memory on failing case of base32_decode, and make
4449 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
4450 - Don't try to download extrainfo documents when we're trying to
4451 fetch enough directory info to build a circuit: having enough
4452 info should get priority. Bugfix on 0.2.0.x.
4453 - Don't complain that "your server has not managed to confirm that its
4454 ports are reachable" if we haven't been able to build any circuits
4455 yet. Bug found by spending four hours without a v3 consensus. Bugfix
4457 - Detect the reason for failing to mmap a descriptor file we just
4458 wrote, and give a more useful log message. Fixes bug 533. Bugfix
4461 o Code simplifications and refactoring:
4462 - Remove support for the old bw_accounting file: we've been storing
4463 bandwidth accounting information in the state file since
4464 0.1.2.5-alpha. This may result in bandwidth accounting errors
4465 if you try to upgrade from 0.1.1.x or earlier, or if you try to
4466 downgrade to 0.1.1.x or earlier.
4467 - New convenience code to locate a file within the DataDirectory.
4468 - Move non-authority functionality out of dirvote.c.
4469 - Refactor the arguments for router_pick_{directory_|trusteddir}server
4470 so that they all take the same named flags.
4473 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
4474 Unix users an easy way to script their Tor process (e.g. by
4475 adjusting bandwidth based on the time of the day).
4478 Changes in version 0.2.0.8-alpha - 2007-10-12
4479 This eighth development snapshot fixes a crash bug that's been bothering
4480 us since February 2007, lets bridge authorities store a list of bridge
4481 descriptors they've seen, gets v3 directory voting closer to working,
4482 starts caching v3 directory consensus documents on directory mirrors,
4483 and fixes a variety of smaller issues including some minor memory leaks.
4485 o Major features (router descriptor cache):
4486 - Store routers in a file called cached-descriptors instead of in
4487 cached-routers. Initialize cached-descriptors from cached-routers
4488 if the old format is around. The new format allows us to store
4489 annotations along with descriptors.
4490 - Use annotations to record the time we received each descriptor, its
4491 source, and its purpose.
4492 - Disable the SETROUTERPURPOSE controller command: it is now
4494 - Controllers should now specify cache=no or cache=yes when using
4495 the +POSTDESCRIPTOR command.
4496 - Bridge authorities now write bridge descriptors to disk, meaning
4497 we can export them to other programs and begin distributing them
4500 o Major features (directory authorities):
4501 - When a v3 authority is missing votes or signatures, it now tries
4503 - Directory authorities track weighted fractional uptime as well as
4504 weighted mean-time-between failures. WFU is suitable for deciding
4505 whether a node is "usually up", while MTBF is suitable for deciding
4506 whether a node is "likely to stay up." We need both, because
4507 "usually up" is a good requirement for guards, while "likely to
4508 stay up" is a good requirement for long-lived connections.
4510 o Major features (v3 directory system):
4511 - Caches now download v3 network status documents as needed,
4512 and download the descriptors listed in them.
4513 - All hosts now attempt to download and keep fresh v3 authority
4514 certificates, and re-attempt after failures.
4515 - More internal-consistency checks for vote parsing.
4517 o Major bugfixes (crashes):
4518 - If a connection is shut down abruptly because of something that
4519 happened inside connection_flushed_some(), do not call
4520 connection_finished_flushing(). Should fix bug 451. Bugfix on
4523 o Major bugfixes (performance):
4524 - Fix really bad O(n^2) performance when parsing a long list of
4525 routers: Instead of searching the entire list for an "extra-info "
4526 string which usually wasn't there, once for every routerinfo
4527 we read, just scan lines forward until we find one we like.
4529 - When we add data to a write buffer in response to the data on that
4530 write buffer getting low because of a flush, do not consider the
4531 newly added data as a candidate for immediate flushing, but rather
4532 make it wait until the next round of writing. Otherwise, we flush
4533 and refill recursively, and a single greedy TLS connection can
4534 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
4536 o Minor features (v3 authority system):
4537 - Add more ways for tools to download the votes that lead to the
4539 - Send a 503 when low on bandwidth and a vote, consensus, or
4540 certificate is requested.
4541 - If-modified-since is now implemented properly for all kinds of
4542 certificate requests.
4544 o Minor bugfixes (network statuses):
4545 - Tweak the implementation of proposal 109 slightly: allow at most
4546 two Tor servers on the same IP address, except if it's the location
4547 of a directory authority, in which case allow five. Bugfix on
4550 o Minor bugfixes (controller):
4551 - When sending a status event to the controller telling it that an
4552 OR address is reachable, set the port correctly. (Previously we
4553 were reporting the dir port.) Bugfix on 0.1.2.x.
4555 o Minor bugfixes (v3 directory system):
4556 - Fix logic to look up a cert by its signing key digest. Bugfix on
4558 - Only change the reply to a vote to "OK" if it's not already
4559 set. This gets rid of annoying "400 OK" log messages, which may
4560 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
4561 - When we get a valid consensus, recompute the voting schedule.
4562 - Base the valid-after time of a vote on the consensus voting
4563 schedule, not on our preferred schedule.
4564 - Make the return values and messages from signature uploads and
4565 downloads more sensible.
4566 - Fix a memory leak when serving votes and consensus documents, and
4567 another when serving certificates.
4569 o Minor bugfixes (performance):
4570 - Use a slightly simpler string hashing algorithm (copying Python's
4571 instead of Java's) and optimize our digest hashing algorithm to take
4572 advantage of 64-bit platforms and to remove some possibly-costly
4574 - Fix a minor memory leak whenever we parse guards from our state
4575 file. Bugfix on 0.2.0.7-alpha.
4576 - Fix a minor memory leak whenever we write out a file. Bugfix on
4578 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4579 command. Bugfix on 0.2.0.5-alpha.
4581 o Minor bugfixes (portability):
4582 - On some platforms, accept() can return a broken address. Detect
4583 this more quietly, and deal accordingly. Fixes bug 483.
4584 - Stop calling tor_strlower() on uninitialized memory in some cases.
4585 Bugfix in 0.2.0.7-alpha.
4587 o Minor bugfixes (usability):
4588 - Treat some 403 responses from directory servers as INFO rather than
4589 WARN-severity events.
4590 - It's not actually an error to find a non-pending entry in the DNS
4591 cache when canceling a pending resolve. Don't log unless stuff is
4592 fishy. Resolves bug 463.
4594 o Minor bugfixes (anonymity):
4595 - Never report that we've used more bandwidth than we're willing to
4596 relay: it leaks how much non-relay traffic we're using. Resolves
4598 - When looking for a circuit to cannibalize, consider family as well
4599 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4600 circuit cannibalization).
4602 o Code simplifications and refactoring:
4603 - Make a bunch of functions static. Remove some dead code.
4604 - Pull out about a third of the really big routerlist.c; put it in a
4605 new module, networkstatus.c.
4606 - Merge the extra fields in local_routerstatus_t back into
4607 routerstatus_t: we used to need one routerstatus_t for each
4608 authority's opinion, plus a local_routerstatus_t for the locally
4609 computed consensus opinion. To save space, we put the locally
4610 modified fields into local_routerstatus_t, and only the common
4611 stuff into routerstatus_t. But once v3 directories are in use,
4612 clients and caches will no longer need to hold authority opinions;
4613 thus, the rationale for keeping the types separate is now gone.
4614 - Make the code used to reschedule and reattempt downloads more
4616 - Turn all 'Are we a directory server/mirror?' logic into a call to
4618 - Remove the code to generate the oldest (v1) directory format.
4619 The code has been disabled since 0.2.0.5-alpha.
4622 Changes in version 0.2.0.7-alpha - 2007-09-21
4623 This seventh development snapshot makes bridges work again, makes bridge
4624 authorities work for the first time, fixes two huge performance flaws
4625 in hidden services, and fixes a variety of minor issues.
4627 o New directory authorities:
4628 - Set up moria1 and tor26 as the first v3 directory authorities. See
4629 doc/spec/dir-spec.txt for details on the new directory design.
4631 o Major bugfixes (crashes):
4632 - Fix possible segfaults in functions called from
4633 rend_process_relay_cell(). Bugfix on 0.1.2.x.
4635 o Major bugfixes (bridges):
4636 - Fix a bug that made servers send a "404 Not found" in response to
4637 attempts to fetch their server descriptor. This caused Tor servers
4638 to take many minutes to establish reachability for their DirPort,
4639 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
4640 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
4641 users configure that and specify a bridge with an identity
4642 fingerprint, now they will lookup the bridge descriptor at the
4643 default bridge authority via a one-hop tunnel, but once circuits
4644 are established they will switch to a three-hop tunnel for later
4645 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
4647 o Major bugfixes (hidden services):
4648 - Hidden services were choosing introduction points uniquely by
4649 hexdigest, but when constructing the hidden service descriptor
4650 they merely wrote the (potentially ambiguous) nickname.
4651 - Clients now use the v2 intro format for hidden service
4652 connections: they specify their chosen rendezvous point by identity
4653 digest rather than by (potentially ambiguous) nickname. Both
4654 are bugfixes on 0.1.2.x, and they could speed up hidden service
4655 connections dramatically. Thanks to Karsten Loesing.
4657 o Minor features (security):
4658 - As a client, do not believe any server that tells us that an
4659 address maps to an internal address space.
4660 - Make it possible to enable HashedControlPassword and
4661 CookieAuthentication at the same time.
4663 o Minor features (guard nodes):
4664 - Tag every guard node in our state file with the version that
4665 we believe added it, or with our own version if we add it. This way,
4666 if a user temporarily runs an old version of Tor and then switches
4667 back to a new one, she doesn't automatically lose her guards.
4669 o Minor features (speed):
4670 - When implementing AES counter mode, update only the portions of the
4671 counter buffer that need to change, and don't keep separate
4672 network-order and host-order counters when they are the same (i.e.,
4673 on big-endian hosts.)
4675 o Minor features (controller):
4676 - Accept LF instead of CRLF on controller, since some software has a
4677 hard time generating real Internet newlines.
4678 - Add GETINFO values for the server status events
4679 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
4683 - Routers no longer include bandwidth-history lines in their
4684 descriptors; this information is already available in extra-info
4685 documents, and including it in router descriptors took up 60%
4686 (!) of compressed router descriptor downloads. Completes
4687 implementation of proposal 104.
4688 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
4689 and TorControl.py, as they use the old v0 controller protocol,
4690 and are obsoleted by TorFlow anyway.
4691 - Drop support for v1 rendezvous descriptors, since we never used
4692 them anyway, and the code has probably rotted by now. Based on
4693 patch from Karsten Loesing.
4694 - On OSX, stop warning the user that kqueue support in libevent is
4695 "experimental", since it seems to have worked fine for ages.
4698 - When generating information telling us how to extend to a given
4699 router, do not try to include the nickname if it is absent. Fixes
4700 bug 467. Bugfix on 0.2.0.3-alpha.
4701 - Fix a user-triggerable (but not remotely-triggerable) segfault
4702 in expand_filename(). Bugfix on 0.1.2.x.
4703 - Fix a memory leak when freeing incomplete requests from DNSPort.
4704 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
4705 - Don't try to access (or alter) the state file when running
4706 --list-fingerprint or --verify-config or --hash-password. (Resolves
4707 bug 499.) Bugfix on 0.1.2.x.
4708 - Servers used to decline to publish their DirPort if their
4709 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
4710 were below a threshold. Now they only look at BandwidthRate and
4711 RelayBandwidthRate. Bugfix on 0.1.2.x.
4712 - Remove an optimization in the AES counter-mode code that assumed
4713 that the counter never exceeded 2^68. When the counter can be set
4714 arbitrarily as an IV (as it is by Karsten's new hidden services
4715 code), this assumption no longer holds. Bugfix on 0.1.2.x.
4716 - Resume listing "AUTHORITY" flag for authorities in network status.
4717 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
4719 o Code simplifications and refactoring:
4720 - Revamp file-writing logic so we don't need to have the entire
4721 contents of a file in memory at once before we write to disk. Tor,
4723 - Turn "descriptor store" into a full-fledged type.
4724 - Move all NT services code into a separate source file.
4725 - Unify all code that computes medians, percentile elements, etc.
4726 - Get rid of a needless malloc when parsing address policies.
4729 Changes in version 0.1.2.17 - 2007-08-30
4730 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
4731 X bundles. Vidalia 0.0.14 makes authentication required for the
4732 ControlPort in the default configuration, which addresses important
4733 security risks. Everybody who uses Vidalia (or another controller)
4736 In addition, this Tor update fixes major load balancing problems with
4737 path selection, which should speed things up a lot once many people
4740 o Major bugfixes (security):
4741 - We removed support for the old (v0) control protocol. It has been
4742 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
4743 become more of a headache than it's worth.
4745 o Major bugfixes (load balancing):
4746 - When choosing nodes for non-guard positions, weight guards
4747 proportionally less, since they already have enough load. Patch
4749 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4750 will allow fast Tor servers to get more attention.
4751 - When we're upgrading from an old Tor version, forget our current
4752 guards and pick new ones according to the new weightings. These
4753 three load balancing patches could raise effective network capacity
4754 by a factor of four. Thanks to Mike Perry for measurements.
4756 o Major bugfixes (stream expiration):
4757 - Expire not-yet-successful application streams in all cases if
4758 they've been around longer than SocksTimeout. Right now there are
4759 some cases where the stream will live forever, demanding a new
4760 circuit every 15 seconds. Fixes bug 454; reported by lodger.
4762 o Minor features (controller):
4763 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4764 is valid before any authentication has been received. It tells
4765 a controller what kind of authentication is expected, and what
4766 protocol is spoken. Implements proposal 119.
4768 o Minor bugfixes (performance):
4769 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
4770 greatly speeding up loading cached-routers from disk on startup.
4771 - Disable sentinel-based debugging for buffer code: we squashed all
4772 the bugs that this was supposed to detect a long time ago, and now
4773 its only effect is to change our buffer sizes from nice powers of
4774 two (which platform mallocs tend to like) to values slightly over
4775 powers of two (which make some platform mallocs sad).
4777 o Minor bugfixes (misc):
4778 - If exit bandwidth ever exceeds one third of total bandwidth, then
4779 use the correct formula to weight exit nodes when choosing paths.
4780 Based on patch from Mike Perry.
4781 - Choose perfectly fairly among routers when choosing by bandwidth and
4782 weighting by fraction of bandwidth provided by exits. Previously, we
4783 would choose with only approximate fairness, and correct ourselves
4784 if we ran off the end of the list.
4785 - If we require CookieAuthentication but we fail to write the
4786 cookie file, we would warn but not exit, and end up in a state
4787 where no controller could authenticate. Now we exit.
4788 - If we require CookieAuthentication, stop generating a new cookie
4789 every time we change any piece of our config.
4790 - Refuse to start with certain directory authority keys, and
4791 encourage people using them to stop.
4792 - Terminate multi-line control events properly. Original patch
4794 - Fix a minor memory leak when we fail to find enough suitable
4795 servers to choose a circuit.
4796 - Stop leaking part of the descriptor when we run into a particularly
4797 unparseable piece of it.
4800 Changes in version 0.2.0.6-alpha - 2007-08-26
4801 This sixth development snapshot features a new Vidalia version in the
4802 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
4803 the ControlPort in the default configuration, which addresses important
4806 In addition, this snapshot fixes major load balancing problems
4807 with path selection, which should speed things up a lot once many
4808 people have upgraded. The directory authorities also use a new
4809 mean-time-between-failure approach to tracking which servers are stable,
4810 rather than just looking at the most recent uptime.
4812 o New directory authorities:
4813 - Set up Tonga as the default bridge directory authority.
4816 - Directory authorities now track servers by weighted
4817 mean-times-between-failures. When we have 4 or more days of data,
4818 use measured MTBF rather than declared uptime to decide whether
4819 to call a router Stable. Implements proposal 108.
4821 o Major bugfixes (load balancing):
4822 - When choosing nodes for non-guard positions, weight guards
4823 proportionally less, since they already have enough load. Patch
4825 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4826 will allow fast Tor servers to get more attention.
4827 - When we're upgrading from an old Tor version, forget our current
4828 guards and pick new ones according to the new weightings. These
4829 three load balancing patches could raise effective network capacity
4830 by a factor of four. Thanks to Mike Perry for measurements.
4832 o Major bugfixes (descriptor parsing):
4833 - Handle unexpected whitespace better in malformed descriptors. Bug
4834 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
4837 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
4838 GETINFO for Torstat to use until it can switch to using extrainfos.
4839 - Optionally (if built with -DEXPORTMALLINFO) export the output
4840 of mallinfo via http, as tor/mallinfo.txt. Only accessible
4844 - Do not intermix bridge routers with controller-added
4845 routers. (Bugfix on 0.2.0.x)
4846 - Do not fail with an assert when accept() returns an unexpected
4847 address family. Addresses but does not wholly fix bug 483. (Bugfix
4849 - Let directory authorities startup even when they can't generate
4850 a descriptor immediately, e.g. because they don't know their
4852 - Stop putting the authentication cookie in a file called "0"
4853 in your working directory if you don't specify anything for the
4854 new CookieAuthFile option. Reported by Matt Edman.
4855 - Make it possible to read the PROTOCOLINFO response in a way that
4856 conforms to our control-spec. Reported by Matt Edman.
4857 - Fix a minor memory leak when we fail to find enough suitable
4858 servers to choose a circuit. Bugfix on 0.1.2.x.
4859 - Stop leaking part of the descriptor when we run into a particularly
4860 unparseable piece of it. Bugfix on 0.1.2.x.
4861 - Unmap the extrainfo cache file on exit.
4864 Changes in version 0.2.0.5-alpha - 2007-08-19
4865 This fifth development snapshot fixes compilation on Windows again;
4866 fixes an obnoxious client-side bug that slowed things down and put
4867 extra load on the network; gets us closer to using the v3 directory
4868 voting scheme; makes it easier for Tor controllers to use cookie-based
4869 authentication; and fixes a variety of other bugs.
4872 - Version 1 directories are no longer generated in full. Instead,
4873 authorities generate and serve "stub" v1 directories that list
4874 no servers. This will stop Tor versions 0.1.0.x and earlier from
4875 working, but (for security reasons) nobody should be running those
4878 o Major bugfixes (compilation, 0.2.0.x):
4879 - Try to fix Win32 compilation again: improve checking for IPv6 types.
4880 - Try to fix MSVC compilation: build correctly on platforms that do
4881 not define s6_addr16 or s6_addr32.
4882 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
4885 o Major bugfixes (stream expiration):
4886 - Expire not-yet-successful application streams in all cases if
4887 they've been around longer than SocksTimeout. Right now there are
4888 some cases where the stream will live forever, demanding a new
4889 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
4892 o Minor features (directory servers):
4893 - When somebody requests a list of statuses or servers, and we have
4894 none of those, return a 404 rather than an empty 200.
4896 o Minor features (directory voting):
4897 - Store v3 consensus status consensuses on disk, and reload them
4900 o Minor features (security):
4901 - Warn about unsafe ControlPort configurations.
4902 - Refuse to start with certain directory authority keys, and
4903 encourage people using them to stop.
4905 o Minor features (controller):
4906 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4907 is valid before any authentication has been received. It tells
4908 a controller what kind of authentication is expected, and what
4909 protocol is spoken. Implements proposal 119.
4910 - New config option CookieAuthFile to choose a new location for the
4911 cookie authentication file, and config option
4912 CookieAuthFileGroupReadable to make it group-readable.
4914 o Minor features (unit testing):
4915 - Add command-line arguments to unit-test executable so that we can
4916 invoke any chosen test from the command line rather than having
4917 to run the whole test suite at once; and so that we can turn on
4918 logging for the unit tests.
4920 o Minor bugfixes (on 0.1.2.x):
4921 - If we require CookieAuthentication but we fail to write the
4922 cookie file, we would warn but not exit, and end up in a state
4923 where no controller could authenticate. Now we exit.
4924 - If we require CookieAuthentication, stop generating a new cookie
4925 every time we change any piece of our config.
4926 - When loading bandwidth history, do not believe any information in
4927 the future. Fixes bug 434.
4928 - When loading entry guard information, do not believe any information
4930 - When we have our clock set far in the future and generate an
4931 onion key, then re-set our clock to be correct, we should not stop
4932 the onion key from getting rotated.
4933 - Clean up torrc sample config file.
4934 - Do not automatically run configure from autogen.sh. This
4935 non-standard behavior tended to annoy people who have built other
4938 o Minor bugfixes (on 0.2.0.x):
4939 - Fix a bug with AutomapHostsOnResolve that would always cause
4940 the second request to fail. Bug reported by Kate. Bugfix on
4942 - Fix a bug in ADDRMAP controller replies that would sometimes
4943 try to print a NULL. Patch from tup.
4944 - Read v3 directory authority keys from the right location.
4945 - Numerous bugfixes to directory voting code.
4948 Changes in version 0.1.2.16 - 2007-08-01
4949 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
4950 remote attacker in certain situations to rewrite the user's torrc
4951 configuration file. This can completely compromise anonymity of users
4952 in most configurations, including those running the Vidalia bundles,
4953 TorK, etc. Or worse.
4955 o Major security fixes:
4956 - Close immediately after missing authentication on control port;
4957 do not allow multiple authentication attempts.
4960 Changes in version 0.2.0.4-alpha - 2007-08-01
4961 This fourth development snapshot fixes a critical security vulnerability
4962 for most users, specifically those running Vidalia, TorK, etc. Everybody
4963 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
4965 o Major security fixes:
4966 - Close immediately after missing authentication on control port;
4967 do not allow multiple authentication attempts.
4969 o Major bugfixes (compilation):
4970 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
4973 o Minor features (performance):
4974 - Be even more aggressive about releasing RAM from small
4975 empty buffers. Thanks to our free-list code, this shouldn't be too
4976 performance-intensive.
4977 - Disable sentinel-based debugging for buffer code: we squashed all
4978 the bugs that this was supposed to detect a long time ago, and
4979 now its only effect is to change our buffer sizes from nice
4980 powers of two (which platform mallocs tend to like) to values
4981 slightly over powers of two (which make some platform mallocs sad).
4982 - Log malloc statistics from mallinfo() on platforms where it
4986 Changes in version 0.2.0.3-alpha - 2007-07-29
4987 This third development snapshot introduces new experimental
4988 blocking-resistance features and a preliminary version of the v3
4989 directory voting design, and includes many other smaller features
4993 - The first pieces of our "bridge" design for blocking-resistance
4994 are implemented. People can run bridge directory authorities;
4995 people can run bridges; and people can configure their Tor clients
4996 with a set of bridges to use as the first hop into the Tor network.
4997 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
4999 - Create listener connections before we setuid to the configured
5000 User and Group. Now non-Windows users can choose port values
5001 under 1024, start Tor as root, and have Tor bind those ports
5002 before it changes to another UID. (Windows users could already
5004 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
5005 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
5006 on "vserver" accounts. (Patch from coderman.)
5007 - Be even more aggressive about separating local traffic from relayed
5008 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
5010 o Major features (experimental):
5011 - First cut of code for "v3 dir voting": directory authorities will
5012 vote on a common network status document rather than each publishing
5013 their own opinion. This code needs more testing and more corner-case
5014 handling before it's ready for use.
5017 - Directory authorities now call routers Fast if their bandwidth is
5018 at least 100KB/s, and consider their bandwidth adequate to be a
5019 Guard if it is at least 250KB/s, no matter the medians. This fix
5020 complements proposal 107. [Bugfix on 0.1.2.x]
5021 - Directory authorities now never mark more than 3 servers per IP as
5022 Valid and Running. (Implements proposal 109, by Kevin Bauer and
5024 - Minor change to organizationName and commonName generation
5025 procedures in TLS certificates during Tor handshakes, to invalidate
5026 some earlier censorware approaches. This is not a long-term
5027 solution, but applying it will give us a bit of time to look into
5028 the epidemiology of countermeasures as they spread.
5030 o Major bugfixes (directory):
5031 - Rewrite directory tokenization code to never run off the end of
5032 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
5034 o Minor features (controller):
5035 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
5036 match requests to applications. (Patch from Robert Hogan.)
5037 - Report address and port correctly on connections to DNSPort. (Patch
5039 - Add a RESOLVE command to launch hostname lookups. (Original patch
5041 - Add GETINFO status/enough-dir-info to let controllers tell whether
5042 Tor has downloaded sufficient directory information. (Patch
5044 - You can now use the ControlSocket option to tell Tor to listen for
5045 controller connections on Unix domain sockets on systems that
5046 support them. (Patch from Peter Palfrader.)
5047 - STREAM NEW events are generated for DNSPort requests and for
5048 tunneled directory connections. (Patch from Robert Hogan.)
5049 - New "GETINFO address-mappings/*" command to get address mappings
5050 with expiry information. "addr-mappings/*" is now deprecated.
5053 o Minor features (misc):
5054 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
5056 - The tor-gencert tool for v3 directory authorities now creates all
5057 files as readable to the file creator only, and write-protects
5058 the authority identity key.
5059 - When dumping memory usage, list bytes used in buffer memory
5061 - When running with dmalloc, dump more stats on hup and on exit.
5062 - Directory authorities now fail quickly and (relatively) harmlessly
5063 if they generate a network status document that is somehow
5066 o Traffic load balancing improvements:
5067 - If exit bandwidth ever exceeds one third of total bandwidth, then
5068 use the correct formula to weight exit nodes when choosing paths.
5069 (Based on patch from Mike Perry.)
5070 - Choose perfectly fairly among routers when choosing by bandwidth and
5071 weighting by fraction of bandwidth provided by exits. Previously, we
5072 would choose with only approximate fairness, and correct ourselves
5073 if we ran off the end of the list. [Bugfix on 0.1.2.x]
5075 o Performance improvements:
5076 - Be more aggressive with freeing buffer RAM or putting it on the
5078 - Use Critical Sections rather than Mutexes for synchronizing threads
5079 on win32; Mutexes are heavier-weight, and designed for synchronizing
5082 o Deprecated and removed features:
5083 - RedirectExits is now deprecated.
5084 - Stop allowing address masks that do not correspond to bit prefixes.
5085 We have warned about these for a really long time; now it's time
5086 to reject them. (Patch from croup.)
5088 o Minor bugfixes (directory):
5089 - Fix another crash bug related to extra-info caching. (Bug found by
5090 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
5091 - Directories no longer return a "304 not modified" when they don't
5092 have the networkstatus the client asked for. Also fix a memory
5093 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
5094 - We had accidentally labelled 0.1.2.x directory servers as not
5095 suitable for begin_dir requests, and had labelled no directory
5096 servers as suitable for uploading extra-info documents. [Bugfix
5099 o Minor bugfixes (dns):
5100 - Fix a crash when DNSPort is set more than once. (Patch from Robert
5101 Hogan.) [Bugfix on 0.2.0.2-alpha]
5102 - Add DNSPort connections to the global connection list, so that we
5103 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
5105 - Fix a dangling reference that could lead to a crash when DNSPort is
5106 changed or closed (Patch from Robert Hogan.) [Bugfix on
5109 o Minor bugfixes (controller):
5110 - Provide DNS expiry times in GMT, not in local time. For backward
5111 compatibility, ADDRMAP events only provide GMT expiry in an extended
5112 field. "GETINFO address-mappings" always does the right thing.
5113 - Use CRLF line endings properly in NS events.
5114 - Terminate multi-line control events properly. (Original patch
5115 from tup.) [Bugfix on 0.1.2.x-alpha]
5116 - Do not include spaces in SOURCE_ADDR fields in STREAM
5117 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
5120 Changes in version 0.1.2.15 - 2007-07-17
5121 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
5122 problems, fixes compilation on BSD, and fixes a variety of other
5123 bugs. Everybody should upgrade.
5125 o Major bugfixes (compilation):
5126 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
5128 o Major bugfixes (crashes):
5129 - Try even harder not to dereference the first character after
5130 an mmap(). Reported by lodger.
5131 - Fix a crash bug in directory authorities when we re-number the
5132 routerlist while inserting a new router.
5133 - When the cached-routers file is an even multiple of the page size,
5134 don't run off the end and crash. (Fixes bug 455; based on idea
5136 - Fix eventdns.c behavior on Solaris: It is critical to include
5137 orconfig.h _before_ sys/types.h, so that we can get the expected
5138 definition of _FILE_OFFSET_BITS.
5140 o Major bugfixes (security):
5141 - Fix a possible buffer overrun when using BSD natd support. Bug
5143 - When sending destroy cells from a circuit's origin, don't include
5144 the reason for tearing down the circuit. The spec says we didn't,
5145 and now we actually don't. Reported by lodger.
5146 - Keep streamids from different exits on a circuit separate. This
5147 bug may have allowed other routers on a given circuit to inject
5148 cells into streams. Reported by lodger; fixes bug 446.
5149 - If there's a never-before-connected-to guard node in our list,
5150 never choose any guards past it. This way we don't expand our
5151 guard list unless we need to.
5153 o Minor bugfixes (guard nodes):
5154 - Weight guard selection by bandwidth, so that low-bandwidth nodes
5155 don't get overused as guards.
5157 o Minor bugfixes (directory):
5158 - Correctly count the number of authorities that recommend each
5159 version. Previously, we were under-counting by 1.
5160 - Fix a potential crash bug when we load many server descriptors at
5161 once and some of them make others of them obsolete. Fixes bug 458.
5163 o Minor bugfixes (hidden services):
5164 - Stop tearing down the whole circuit when the user asks for a
5165 connection to a port that the hidden service didn't configure.
5168 o Minor bugfixes (misc):
5169 - On Windows, we were preventing other processes from reading
5170 cached-routers while Tor was running. Reported by janbar.
5171 - Fix a possible (but very unlikely) bug in picking routers by
5172 bandwidth. Add a log message to confirm that it is in fact
5173 unlikely. Patch from lodger.
5174 - Backport a couple of memory leak fixes.
5175 - Backport miscellaneous cosmetic bugfixes.
5178 Changes in version 0.2.0.2-alpha - 2007-06-02
5179 o Major bugfixes on 0.2.0.1-alpha:
5180 - Fix an assertion failure related to servers without extra-info digests.
5181 Resolves bugs 441 and 442.
5183 o Minor features (directory):
5184 - Support "If-Modified-Since" when answering HTTP requests for
5185 directories, running-routers documents, and network-status documents.
5186 (There's no need to support it for router descriptors, since those
5187 are downloaded by descriptor digest.)
5189 o Minor build issues:
5190 - Clear up some MIPSPro compiler warnings.
5191 - When building from a tarball on a machine that happens to have SVK
5192 installed, report the micro-revision as whatever version existed
5193 in the tarball, not as "x".
5196 Changes in version 0.2.0.1-alpha - 2007-06-01
5197 This early development snapshot provides new features for people running
5198 Tor as both a client and a server (check out the new RelayBandwidth
5199 config options); lets Tor run as a DNS proxy; and generally moves us
5200 forward on a lot of fronts.
5202 o Major features, server usability:
5203 - New config options RelayBandwidthRate and RelayBandwidthBurst:
5204 a separate set of token buckets for relayed traffic. Right now
5205 relayed traffic is defined as answers to directory requests, and
5206 OR connections that don't have any local circuits on them.
5208 o Major features, client usability:
5209 - A client-side DNS proxy feature to replace the need for
5210 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
5211 for DNS requests on port 9999, use the Tor network to resolve them
5212 anonymously, and send the reply back like a regular DNS server.
5213 The code still only implements a subset of DNS.
5214 - Make PreferTunneledDirConns and TunnelDirConns work even when
5215 we have no cached directory info. This means Tor clients can now
5216 do all of their connections protected by TLS.
5218 o Major features, performance and efficiency:
5219 - Directory authorities accept and serve "extra info" documents for
5220 routers. These documents contain fields from router descriptors
5221 that aren't usually needed, and that use a lot of excess
5222 bandwidth. Once these fields are removed from router descriptors,
5223 the bandwidth savings should be about 60%. [Partially implements
5225 - Servers upload extra-info documents to any authority that accepts
5226 them. Authorities (and caches that have been configured to download
5227 extra-info documents) download them as needed. [Partially implements
5229 - Change the way that Tor buffers data that it is waiting to write.
5230 Instead of queueing data cells in an enormous ring buffer for each
5231 client->OR or OR->OR connection, we now queue cells on a separate
5232 queue for each circuit. This lets us use less slack memory, and
5233 will eventually let us be smarter about prioritizing different kinds
5235 - Use memory pools to allocate cells with better speed and memory
5236 efficiency, especially on platforms where malloc() is inefficient.
5237 - Stop reading on edge connections when their corresponding circuit
5238 buffers are full; start again as the circuits empty out.
5240 o Major features, other:
5241 - Add an HSAuthorityRecordStats option that hidden service authorities
5242 can use to track statistics of overall hidden service usage without
5243 logging information that would be very useful to an attacker.
5244 - Start work implementing multi-level keys for directory authorities:
5245 Add a standalone tool to generate key certificates. (Proposal 103.)
5248 - Directory authorities now call routers Stable if they have an
5249 uptime of at least 30 days, even if that's not the median uptime
5250 in the network. Implements proposal 107, suggested by Kevin Bauer
5253 o Minor fixes (resource management):
5254 - Count the number of open sockets separately from the number
5255 of active connection_t objects. This will let us avoid underusing
5256 our allocated connection limit.
5257 - We no longer use socket pairs to link an edge connection to an
5258 anonymous directory connection or a DirPort test connection.
5259 Instead, we track the link internally and transfer the data
5260 in-process. This saves two sockets per "linked" connection (at the
5261 client and at the server), and avoids the nasty Windows socketpair()
5263 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
5264 for every single inactive connection_t. Free items from the
5265 4k/16k-buffer free lists when they haven't been used for a while.
5267 o Minor features (build):
5268 - Make autoconf search for libevent, openssl, and zlib consistently.
5269 - Update deprecated macros in configure.in.
5270 - When warning about missing headers, tell the user to let us
5271 know if the compile succeeds anyway, so we can downgrade the
5273 - Include the current subversion revision as part of the version
5274 string: either fetch it directly if we're in an SVN checkout, do
5275 some magic to guess it if we're in an SVK checkout, or use
5276 the last-detected version if we're building from a .tar.gz.
5277 Use this version consistently in log messages.
5279 o Minor features (logging):
5280 - Always prepend "Bug: " to any log message about a bug.
5281 - Put a platform string (e.g. "Linux i686") in the startup log
5282 message, so when people paste just their logs, we know if it's
5283 OpenBSD or Windows or what.
5284 - When logging memory usage, break down memory used in buffers by
5287 o Minor features (directory system):
5288 - New config option V2AuthoritativeDirectory that all directory
5289 authorities should set. This will let future authorities choose
5290 not to serve V2 directory information.
5291 - Directory authorities allow multiple router descriptors and/or extra
5292 info documents to be uploaded in a single go. This will make
5293 implementing proposal 104 simpler.
5295 o Minor features (controller):
5296 - Add a new config option __DisablePredictedCircuits designed for
5297 use by the controller, when we don't want Tor to build any circuits
5299 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
5300 so we can exit from the middle of the circuit.
5301 - Implement "getinfo status/circuit-established".
5302 - Implement "getinfo status/version/..." so a controller can tell
5303 whether the current version is recommended, and whether any versions
5304 are good, and how many authorities agree. (Patch from shibz.)
5306 o Minor features (hidden services):
5307 - Allow multiple HiddenServicePort directives with the same virtual
5308 port; when they occur, the user is sent round-robin to one
5309 of the target ports chosen at random. Partially fixes bug 393 by
5310 adding limited ad-hoc round-robining.
5312 o Minor features (other):
5314 - Add a new AutomapHostsOnResolve option: when it is enabled, any
5315 resolve request for hosts matching a given pattern causes Tor to
5316 generate an internal virtual address mapping for that host. This
5317 allows DNSPort to work sensibly with hidden service users. By
5318 default, .exit and .onion addresses are remapped; the list of
5319 patterns can be reconfigured with AutomapHostsSuffixes.
5320 - Add an "-F" option to tor-resolve to force a resolve for a .onion
5321 address. Thanks to the AutomapHostsOnResolve option, this is no
5322 longer a completely silly thing to do.
5323 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
5324 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
5325 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
5326 minus 1 byte: the actual maximum declared bandwidth.
5329 - Removed support for the old binary "version 0" controller protocol.
5330 This has been deprecated since 0.1.1, and warnings have been issued
5331 since 0.1.2. When we encounter a v0 control message, we now send
5332 back an error and close the connection.
5333 - Remove the old "dns worker" server DNS code: it hasn't been default
5334 since 0.1.2.2-alpha, and all the servers seem to be using the new
5337 o Minor bugfixes (portability):
5338 - Even though Windows is equally happy with / and \ as path separators,
5339 try to use \ consistently on Windows and / consistently on Unix: it
5340 makes the log messages nicer.
5341 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
5342 - Read resolv.conf files correctly on platforms where read() returns
5343 partial results on small file reads.
5345 o Minor bugfixes (directory):
5346 - Correctly enforce that elements of directory objects do not appear
5347 more often than they are allowed to appear.
5348 - When we are reporting the DirServer line we just parsed, we were
5349 logging the second stanza of the key fingerprint, not the first.
5351 o Minor bugfixes (logging):
5352 - When we hit an EOF on a log (probably because we're shutting down),
5353 don't try to remove the log from the list: just mark it as
5354 unusable. (Bulletproofs against bug 222.)
5356 o Minor bugfixes (other):
5357 - In the exitlist script, only consider the most recently published
5358 server descriptor for each server. Also, when the user requests
5359 a list of servers that _reject_ connections to a given address,
5360 explicitly exclude the IPs that also have servers that accept
5361 connections to that address. (Resolves bug 405.)
5362 - Stop allowing hibernating servers to be "stable" or "fast".
5363 - On Windows, we were preventing other processes from reading
5364 cached-routers while Tor was running. (Reported by janbar)
5365 - Make the NodeFamilies config option work. (Reported by
5366 lodger -- it has never actually worked, even though we added it
5368 - Check return values from pthread_mutex functions.
5369 - Don't save non-general-purpose router descriptors to the disk cache,
5370 because we have no way of remembering what their purpose was when
5372 - Add even more asserts to hunt down bug 417.
5373 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
5374 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
5375 Add a log message to confirm that it is in fact unlikely.
5377 o Minor bugfixes (controller):
5378 - Make 'getinfo fingerprint' return a 551 error if we're not a
5379 server, so we match what the control spec claims we do. Reported
5381 - Fix a typo in an error message when extendcircuit fails that
5382 caused us to not follow the \r\n-based delimiter protocol. Reported
5385 o Code simplifications and refactoring:
5386 - Stop passing around circuit_t and crypt_path_t pointers that are
5387 implicit in other procedure arguments.
5388 - Drop the old code to choke directory connections when the
5389 corresponding OR connections got full: thanks to the cell queue
5390 feature, OR conns don't get full any more.
5391 - Make dns_resolve() handle attaching connections to circuits
5392 properly, so the caller doesn't have to.
5393 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
5394 - Keep the connection array as a dynamic smartlist_t, rather than as
5395 a fixed-sized array. This is important, as the number of connections
5396 is becoming increasingly decoupled from the number of sockets.
5399 Changes in version 0.1.2.14 - 2007-05-25
5400 Tor 0.1.2.14 changes the addresses of two directory authorities (this
5401 change especially affects those who serve or use hidden services),
5402 and fixes several other crash- and security-related bugs.
5404 o Directory authority changes:
5405 - Two directory authorities (moria1 and moria2) just moved to new
5406 IP addresses. This change will particularly affect those who serve
5407 or use hidden services.
5409 o Major bugfixes (crashes):
5410 - If a directory server runs out of space in the connection table
5411 as it's processing a begin_dir request, it will free the exit stream
5412 but leave it attached to the circuit, leading to unpredictable
5413 behavior. (Reported by seeess, fixes bug 425.)
5414 - Fix a bug in dirserv_remove_invalid() that would cause authorities
5415 to corrupt memory under some really unlikely scenarios.
5416 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
5417 - Avoid segfaults when reading from mmaped descriptor file. (Reported
5420 o Major bugfixes (security):
5421 - When choosing an entry guard for a circuit, avoid using guards
5422 that are in the same family as the chosen exit -- not just guards
5423 that are exactly the chosen exit. (Reported by lodger.)
5425 o Major bugfixes (resource management):
5426 - If a directory authority is down, skip it when deciding where to get
5427 networkstatus objects or descriptors. Otherwise we keep asking
5428 every 10 seconds forever. Fixes bug 384.
5429 - Count it as a failure if we fetch a valid network-status but we
5430 don't want to keep it. Otherwise we'll keep fetching it and keep
5431 not wanting to keep it. Fixes part of bug 422.
5432 - If all of our dirservers have given us bad or no networkstatuses
5433 lately, then stop hammering them once per minute even when we
5434 think they're failed. Fixes another part of bug 422.
5437 - Actually set the purpose correctly for descriptors inserted with
5439 - When we have k non-v2 authorities in our DirServer config,
5440 we ignored the last k authorities in the list when updating our
5442 - Correctly back-off from requesting router descriptors that we are
5443 having a hard time downloading.
5444 - Read resolv.conf files correctly on platforms where read() returns
5445 partial results on small file reads.
5446 - Don't rebuild the entire router store every time we get 32K of
5447 routers: rebuild it when the journal gets very large, or when
5448 the gaps in the store get very large.
5451 - When routers publish SVN revisions in their router descriptors,
5452 authorities now include those versions correctly in networkstatus
5454 - Warn when using a version of libevent before 1.3b to run a server on
5455 OSX or BSD: these versions interact badly with userspace threads.
5458 Changes in version 0.1.2.13 - 2007-04-24
5459 This release features some major anonymity fixes, such as safer path
5460 selection; better client performance; faster bootstrapping, better
5461 address detection, and better DNS support for servers; write limiting as
5462 well as read limiting to make servers easier to run; and a huge pile of
5463 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
5465 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
5466 of the Freenode IRC network, remembering his patience and vision for
5467 free speech on the Internet.
5470 - Fix a memory leak when we ask for "all" networkstatuses and we
5471 get one we don't recognize.
5472 - Add more asserts to hunt down bug 417.
5473 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
5476 Changes in version 0.1.2.12-rc - 2007-03-16
5478 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
5479 directory information requested inside Tor connections (i.e. via
5480 begin_dir cells). It only triggered when the same connection was
5481 serving other data at the same time. Reported by seeess.
5484 - When creating a circuit via the controller, send a 'launched'
5485 event when we're done, so we follow the spec better.
5488 Changes in version 0.1.2.11-rc - 2007-03-15
5489 o Minor bugfixes (controller), reported by daejees:
5490 - Correct the control spec to match how the code actually responds
5491 to 'getinfo addr-mappings/*'.
5492 - The control spec described a GUARDS event, but the code
5493 implemented a GUARD event. Standardize on GUARD, but let people
5497 Changes in version 0.1.2.10-rc - 2007-03-07
5498 o Major bugfixes (Windows):
5499 - Do not load the NT services library functions (which may not exist)
5500 just to detect if we're a service trying to shut down. Now we run
5501 on Win98 and friends again.
5503 o Minor bugfixes (other):
5504 - Clarify a couple of log messages.
5505 - Fix a misleading socks5 error number.
5508 Changes in version 0.1.2.9-rc - 2007-03-02
5509 o Major bugfixes (Windows):
5510 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
5511 of the usual GCC "%llu". This prevents a bug when saving 64-bit
5512 int configuration values: the high-order 32 bits would get
5513 truncated. In particular, we were being bitten by the default
5514 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
5515 and maybe also bug 397.)
5517 o Minor bugfixes (performance):
5518 - Use OpenSSL's AES implementation on platforms where it's faster.
5519 This could save us as much as 10% CPU usage.
5521 o Minor bugfixes (server):
5522 - Do not rotate onion key immediately after setting it for the first
5525 o Minor bugfixes (directory authorities):
5526 - Stop calling servers that have been hibernating for a long time
5527 "stable". Also, stop letting hibernating or obsolete servers affect
5528 uptime and bandwidth cutoffs.
5529 - Stop listing hibernating servers in the v1 directory.
5531 o Minor bugfixes (hidden services):
5532 - Upload hidden service descriptors slightly less often, to reduce
5533 load on authorities.
5535 o Minor bugfixes (other):
5536 - Fix an assert that could trigger if a controller quickly set then
5537 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
5538 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
5540 - Fix a potential race condition in the rpm installer. Found by
5542 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
5543 of 2 as indicating that the server is completely bad; it sometimes
5544 means that the server is just bad for the request in question. (may fix
5545 the last of bug 326.)
5546 - Disable encrypted directory connections when we don't have a server
5547 descriptor for the destination. We'll get this working again in
5551 Changes in version 0.1.2.8-beta - 2007-02-26
5552 o Major bugfixes (crashes):
5553 - Stop crashing when the controller asks us to resetconf more than
5554 one config option at once. (Vidalia 0.0.11 does this.)
5555 - Fix a crash that happened on Win98 when we're given command-line
5556 arguments: don't try to load NT service functions from advapi32.dll
5557 except when we need them. (Bug introduced in 0.1.2.7-alpha;
5559 - Fix a longstanding obscure crash bug that could occur when
5560 we run out of DNS worker processes. (Resolves bug 390.)
5562 o Major bugfixes (hidden services):
5563 - Correctly detect whether hidden service descriptor downloads are
5564 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
5566 o Major bugfixes (accounting):
5567 - When we start during an accounting interval before it's time to wake
5568 up, remember to wake up at the correct time. (May fix bug 342.)
5570 o Minor bugfixes (controller):
5571 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
5572 clear the corresponding on_circuit variable, and remember later
5573 that we don't need to send a redundant CLOSED event. (Resolves part
5575 - Report events where a resolve succeeded or where we got a socks
5576 protocol error correctly, rather than calling both of them
5578 - Change reported stream target addresses to IP consistently when
5579 we finally get the IP from an exit node.
5580 - Send log messages to the controller even if they happen to be very
5583 o Minor bugfixes (other):
5584 - Display correct results when reporting which versions are
5585 recommended, and how recommended they are. (Resolves bug 383.)
5586 - Improve our estimates for directory bandwidth to be less random:
5587 guess that an unrecognized directory will have the average bandwidth
5588 from all known directories, not that it will have the average
5589 bandwidth from those directories earlier than it on the list.
5590 - If we start a server with ClientOnly 1, then set ClientOnly to 0
5591 and hup, stop triggering an assert based on an empty onion_key.
5592 - On platforms with no working mmap() equivalent, don't warn the
5593 user when cached-routers doesn't exist.
5594 - Warn the user when mmap() [or its equivalent] fails for some reason
5595 other than file-not-found.
5596 - Don't warn the user when cached-routers.new doesn't exist: that's
5597 perfectly fine when starting up for the first time.
5598 - When EntryNodes are configured, rebuild the guard list to contain,
5599 in order: the EntryNodes that were guards before; the rest of the
5600 EntryNodes; the nodes that were guards before.
5601 - Mask out all signals in sub-threads; only the libevent signal
5602 handler should be processing them. This should prevent some crashes
5603 on some machines using pthreads. (Patch from coderman.)
5604 - Fix switched arguments on memset in the implementation of
5605 tor_munmap() for systems with no mmap() call.
5606 - When Tor receives a router descriptor that it asked for, but
5607 no longer wants (because it has received fresh networkstatuses
5608 in the meantime), do not warn the user. Cache the descriptor if
5609 we're a cache; drop it if we aren't.
5610 - Make earlier entry guards _really_ get retried when the network
5612 - On a malformed DNS reply, always give an error to the corresponding
5614 - Build with recent libevents on platforms that do not define the
5615 nonstandard types "u_int8_t" and friends.
5617 o Minor features (controller):
5618 - Warn the user when an application uses the obsolete binary v0
5619 control protocol. We're planning to remove support for it during
5620 the next development series, so it's good to give people some
5622 - Add STREAM_BW events to report per-entry-stream bandwidth
5623 use. (Patch from Robert Hogan.)
5624 - Rate-limit SIGNEWNYM signals in response to controllers that
5625 impolitely generate them for every single stream. (Patch from
5626 mwenge; closes bug 394.)
5627 - Make REMAP stream events have a SOURCE (cache or exit), and
5628 make them generated in every case where we get a successful
5629 connected or resolved cell.
5631 o Minor bugfixes (performance):
5632 - Call router_have_min_dir_info half as often. (This is showing up in
5633 some profiles, but not others.)
5634 - When using GCC, make log_debug never get called at all, and its
5635 arguments never get evaluated, when no debug logs are configured.
5636 (This is showing up in some profiles, but not others.)
5639 - Remove some never-implemented options. Mark PathlenCoinWeight as
5641 - Implement proposal 106: Stop requiring clients to have well-formed
5642 certificates; stop checking nicknames in certificates. (Clients
5643 have certificates so that they can look like Tor servers, but in
5644 the future we might want to allow them to look like regular TLS
5645 clients instead. Nicknames in certificates serve no purpose other
5646 than making our protocol easier to recognize on the wire.)
5647 - Revise messages on handshake failure again to be even more clear about
5648 which are incoming connections and which are outgoing.
5649 - Discard any v1 directory info that's over 1 month old (for
5650 directories) or over 1 week old (for running-routers lists).
5651 - Do not warn when individual nodes in the configuration's EntryNodes,
5652 ExitNodes, etc are down: warn only when all possible nodes
5653 are down. (Fixes bug 348.)
5654 - Always remove expired routers and networkstatus docs before checking
5655 whether we have enough information to build circuits. (Fixes
5657 - Put a lower-bound on MaxAdvertisedBandwidth.
5660 Changes in version 0.1.2.7-alpha - 2007-02-06
5661 o Major bugfixes (rate limiting):
5662 - Servers decline directory requests much more aggressively when
5663 they're low on bandwidth. Otherwise they end up queueing more and
5664 more directory responses, which can't be good for latency.
5665 - But never refuse directory requests from local addresses.
5666 - Fix a memory leak when sending a 503 response for a networkstatus
5668 - Be willing to read or write on local connections (e.g. controller
5669 connections) even when the global rate limiting buckets are empty.
5670 - If our system clock jumps back in time, don't publish a negative
5671 uptime in the descriptor. Also, don't let the global rate limiting
5672 buckets go absurdly negative.
5673 - Flush local controller connection buffers periodically as we're
5674 writing to them, so we avoid queueing 4+ megabytes of data before
5677 o Major bugfixes (NT services):
5678 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
5679 command-line flag so that admins can override the default by saying
5680 "tor --service install --user "SomeUser"". This will not affect
5681 existing installed services. Also, warn the user that the service
5682 will look for its configuration file in the service user's
5683 %appdata% directory. (We can't do the 'hardwire the user's appdata
5684 directory' trick any more, since we may not have read access to that
5687 o Major bugfixes (other):
5688 - Previously, we would cache up to 16 old networkstatus documents
5689 indefinitely, if they came from nontrusted authorities. Now we
5690 discard them if they are more than 10 days old.
5691 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
5693 - Detect and reject malformed DNS responses containing circular
5695 - If exits are rare enough that we're not marking exits as guards,
5696 ignore exit bandwidth when we're deciding the required bandwidth
5698 - When we're handling a directory connection tunneled over Tor,
5699 don't fill up internal memory buffers with all the data we want
5700 to tunnel; instead, only add it if the OR connection that will
5701 eventually receive it has some room for it. (This can lead to
5702 slowdowns in tunneled dir connections; a better solution will have
5705 o Minor bugfixes (dns):
5706 - Add some defensive programming to eventdns.c in an attempt to catch
5707 possible memory-stomping bugs.
5708 - Detect and reject DNS replies containing IPv4 or IPv6 records with
5709 an incorrect number of bytes. (Previously, we would ignore the
5711 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
5712 in the correct order, and doesn't crash.
5713 - Free memory held in recently-completed DNS lookup attempts on exit.
5714 This was not a memory leak, but may have been hiding memory leaks.
5715 - Handle TTL values correctly on reverse DNS lookups.
5716 - Treat failure to parse resolv.conf as an error.
5718 o Minor bugfixes (other):
5719 - Fix crash with "tor --list-fingerprint" (reported by seeess).
5720 - When computing clock skew from directory HTTP headers, consider what
5721 time it was when we finished asking for the directory, not what
5723 - Expire socks connections if they spend too long waiting for the
5724 handshake to finish. Previously we would let them sit around for
5725 days, if the connecting application didn't close them either.
5726 - And if the socks handshake hasn't started, don't send a
5727 "DNS resolve socks failed" handshake reply; just close it.
5728 - Stop using C functions that OpenBSD's linker doesn't like.
5729 - Don't launch requests for descriptors unless we have networkstatuses
5730 from at least half of the authorities. This delays the first
5731 download slightly under pathological circumstances, but can prevent
5732 us from downloading a bunch of descriptors we don't need.
5733 - Do not log IPs with TLS failures for incoming TLS
5734 connections. (Fixes bug 382.)
5735 - If the user asks to use invalid exit nodes, be willing to use
5737 - Stop using the reserved ac_cv namespace in our configure script.
5738 - Call stat() slightly less often; use fstat() when possible.
5739 - Refactor the way we handle pending circuits when an OR connection
5740 completes or fails, in an attempt to fix a rare crash bug.
5741 - Only rewrite a conn's address based on X-Forwarded-For: headers
5742 if it's a parseable public IP address; and stop adding extra quotes
5743 to the resulting address.
5746 - Weight directory requests by advertised bandwidth. Now we can
5747 let servers enable write limiting but still allow most clients to
5748 succeed at their directory requests. (We still ignore weights when
5749 choosing a directory authority; I hope this is a feature.)
5752 - Create a new file ReleaseNotes which was the old ChangeLog. The
5753 new ChangeLog file now includes the summaries for all development
5755 - Check for addresses with invalid characters at the exit as well
5756 as at the client, and warn less verbosely when they fail. You can
5757 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
5758 - Adapt a patch from goodell to let the contrib/exitlist script
5759 take arguments rather than require direct editing.
5760 - Inform the server operator when we decide not to advertise a
5761 DirPort due to AccountingMax enabled or a low BandwidthRate. It
5762 was confusing Zax, so now we're hopefully more helpful.
5763 - Bring us one step closer to being able to establish an encrypted
5764 directory tunnel without knowing a descriptor first. Still not
5765 ready yet. As part of the change, now assume we can use a
5766 create_fast cell if we don't know anything about a router.
5767 - Allow exit nodes to use nameservers running on ports other than 53.
5768 - Servers now cache reverse DNS replies.
5769 - Add an --ignore-missing-torrc command-line option so that we can
5770 get the "use sensible defaults if the configuration file doesn't
5771 exist" behavior even when specifying a torrc location on the command
5774 o Minor features (controller):
5775 - Track reasons for OR connection failure; make these reasons
5776 available via the controller interface. (Patch from Mike Perry.)
5777 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
5778 can learn when clients are sending malformed hostnames to Tor.
5779 - Clean up documentation for controller status events.
5780 - Add a REMAP status to stream events to note that a stream's
5781 address has changed because of a cached address or a MapAddress
5785 Changes in version 0.1.2.6-alpha - 2007-01-09
5787 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
5788 connection handles more than 4 gigs in either direction, we crash.
5789 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
5790 advertised exit node, somebody might try to exit from us when
5791 we're bootstrapping and before we've built our descriptor yet.
5792 Refuse the connection rather than crashing.
5795 - Warn if we (as a server) find that we've resolved an address that we
5796 weren't planning to resolve.
5797 - Warn that using select() on any libevent version before 1.1 will be
5798 unnecessarily slow (even for select()).
5799 - Flush ERR-level controller status events just like we currently
5800 flush ERR-level log events, so that a Tor shutdown doesn't prevent
5801 the controller from learning about current events.
5803 o Minor features (more controller status events):
5804 - Implement EXTERNAL_ADDRESS server status event so controllers can
5805 learn when our address changes.
5806 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
5807 can learn when directories reject our descriptor.
5808 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
5809 can learn when a client application is speaking a non-socks protocol
5811 - Implement DANGEROUS_SOCKS client status event so controllers
5812 can learn when a client application is leaking DNS addresses.
5813 - Implement BUG general status event so controllers can learn when
5814 Tor is unhappy about its internal invariants.
5815 - Implement CLOCK_SKEW general status event so controllers can learn
5816 when Tor thinks the system clock is set incorrectly.
5817 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
5818 server status events so controllers can learn when their descriptors
5819 are accepted by a directory.
5820 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
5821 server status events so controllers can learn about Tor's progress in
5822 deciding whether it's reachable from the outside.
5823 - Implement BAD_LIBEVENT general status event so controllers can learn
5824 when we have a version/method combination in libevent that needs to
5826 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
5827 and DNS_USELESS server status events so controllers can learn
5828 about changes to DNS server status.
5830 o Minor features (directory):
5831 - Authorities no longer recommend exits as guards if this would shift
5832 too much load to the exit nodes.
5835 Changes in version 0.1.2.5-alpha - 2007-01-06
5837 - Enable write limiting as well as read limiting. Now we sacrifice
5838 capacity if we're pushing out lots of directory traffic, rather
5839 than overrunning the user's intended bandwidth limits.
5840 - Include TLS overhead when counting bandwidth usage; previously, we
5841 would count only the bytes sent over TLS, but not the bytes used
5843 - Support running the Tor service with a torrc not in the same
5844 directory as tor.exe and default to using the torrc located in
5845 the %appdata%\Tor\ of the user who installed the service. Patch
5847 - Servers now check for the case when common DNS requests are going to
5848 wildcarded addresses (i.e. all getting the same answer), and change
5849 their exit policy to reject *:* if it's happening.
5850 - Implement BEGIN_DIR cells, so we can connect to the directory
5851 server via TLS to do encrypted directory requests rather than
5852 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
5853 config options if you like.
5855 o Minor features (config and docs):
5856 - Start using the state file to store bandwidth accounting data:
5857 the bw_accounting file is now obsolete. We'll keep generating it
5858 for a while for people who are still using 0.1.2.4-alpha.
5859 - Try to batch changes to the state file so that we do as few
5860 disk writes as possible while still storing important things in
5862 - The state file and the bw_accounting file get saved less often when
5863 the AvoidDiskWrites config option is set.
5864 - Make PIDFile work on Windows (untested).
5865 - Add internal descriptions for a bunch of configuration options:
5866 accessible via controller interface and in comments in saved
5868 - Reject *:563 (NNTPS) in the default exit policy. We already reject
5869 NNTP by default, so this seems like a sensible addition.
5870 - Clients now reject hostnames with invalid characters. This should
5871 avoid some inadvertent info leaks. Add an option
5872 AllowNonRFC953Hostnames to disable this behavior, in case somebody
5873 is running a private network with hosts called @, !, and #.
5874 - Add a maintainer script to tell us which options are missing
5875 documentation: "make check-docs".
5876 - Add a new address-spec.txt document to describe our special-case
5877 addresses: .exit, .onion, and .noconnnect.
5879 o Minor features (DNS):
5880 - Ongoing work on eventdns infrastructure: now it has dns server
5881 and ipv6 support. One day Tor will make use of it.
5882 - Add client-side caching for reverse DNS lookups.
5883 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
5884 - When we change nameservers or IP addresses, reset and re-launch
5885 our tests for DNS hijacking.
5887 o Minor features (directory):
5888 - Authorities now specify server versions in networkstatus. This adds
5889 about 2% to the size of compressed networkstatus docs, and allows
5890 clients to tell which servers support BEGIN_DIR and which don't.
5891 The implementation is forward-compatible with a proposed future
5892 protocol version scheme not tied to Tor versions.
5893 - DirServer configuration lines now have an orport= option so
5894 clients can open encrypted tunnels to the authorities without
5895 having downloaded their descriptors yet. Enabled for moria1,
5896 moria2, tor26, and lefkada now in the default configuration.
5897 - Directory servers are more willing to send a 503 "busy" if they
5898 are near their write limit, especially for v1 directory requests.
5899 Now they can use their limited bandwidth for actual Tor traffic.
5900 - Clients track responses with status 503 from dirservers. After a
5901 dirserver has given us a 503, we try not to use it until an hour has
5902 gone by, or until we have no dirservers that haven't given us a 503.
5903 - When we get a 503 from a directory, and we're not a server, we don't
5904 count the failure against the total number of failures allowed
5905 for the thing we're trying to download.
5906 - Report X-Your-Address-Is correctly from tunneled directory
5907 connections; don't report X-Your-Address-Is when it's an internal
5908 address; and never believe reported remote addresses when they're
5910 - Protect against an unlikely DoS attack on directory servers.
5911 - Add a BadDirectory flag to network status docs so that authorities
5912 can (eventually) tell clients about caches they believe to be
5915 o Minor features (controller):
5916 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
5917 - Reimplement GETINFO so that info/names stays in sync with the
5919 - Implement "GETINFO fingerprint".
5920 - Implement "SETEVENTS GUARD" so controllers can get updates on
5921 entry guard status as it changes.
5923 o Minor features (clean up obsolete pieces):
5924 - Remove some options that have been deprecated since at least
5925 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
5926 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
5928 - We no longer look for identity and onion keys in "identity.key" and
5929 "onion.key" -- these were replaced by secret_id_key and
5930 secret_onion_key in 0.0.8pre1.
5931 - We no longer require unrecognized directory entries to be
5934 o Major bugfixes (security):
5935 - Stop sending the HttpProxyAuthenticator string to directory
5936 servers when directory connections are tunnelled through Tor.
5937 - Clients no longer store bandwidth history in the state file.
5938 - Do not log introduction points for hidden services if SafeLogging
5940 - When generating bandwidth history, round down to the nearest
5941 1k. When storing accounting data, round up to the nearest 1k.
5942 - When we're running as a server, remember when we last rotated onion
5943 keys, so that we will rotate keys once they're a week old even if
5944 we never stay up for a week ourselves.
5946 o Major bugfixes (other):
5947 - Fix a longstanding bug in eventdns that prevented the count of
5948 timed-out resolves from ever being reset. This bug caused us to
5949 give up on a nameserver the third time it timed out, and try it
5950 10 seconds later... and to give up on it every time it timed out
5952 - Take out the '5 second' timeout from the connection retry
5953 schedule. Now the first connect attempt will wait a full 10
5954 seconds before switching to a new circuit. Perhaps this will help
5955 a lot. Based on observations from Mike Perry.
5956 - Fix a bug on the Windows implementation of tor_mmap_file() that
5957 would prevent the cached-routers file from ever loading. Reported
5961 - Fix an assert failure when a directory authority sets
5962 AuthDirRejectUnlisted and then receives a descriptor from an
5963 unlisted router. Reported by seeess.
5964 - Avoid a double-free when parsing malformed DirServer lines.
5965 - Fix a bug when a BSD-style PF socket is first used. Patch from
5967 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
5968 to resolve an address at a given exit node even when they ask for
5970 - Servers no longer ever list themselves in their "family" line,
5971 even if configured to do so. This makes it easier to configure
5972 family lists conveniently.
5973 - When running as a server, don't fall back to 127.0.0.1 when no
5974 nameservers are configured in /etc/resolv.conf; instead, make the
5975 user fix resolv.conf or specify nameservers explicitly. (Resolves
5977 - Stop accepting certain malformed ports in configured exit policies.
5978 - Don't re-write the fingerprint file every restart, unless it has
5980 - Stop warning when a single nameserver fails: only warn when _all_ of
5981 our nameservers have failed. Also, when we only have one nameserver,
5982 raise the threshold for deciding that the nameserver is dead.
5983 - Directory authorities now only decide that routers are reachable
5984 if their identity keys are as expected.
5985 - When the user uses bad syntax in the Log config line, stop
5986 suggesting other bad syntax as a replacement.
5987 - Correctly detect ipv6 DNS capability on OpenBSD.
5989 o Minor bugfixes (controller):
5990 - Report the circuit number correctly in STREAM CLOSED events. Bug
5991 reported by Mike Perry.
5992 - Do not report bizarre values for results of accounting GETINFOs
5993 when the last second's write or read exceeds the allotted bandwidth.
5994 - Report "unrecognized key" rather than an empty string when the
5995 controller tries to fetch a networkstatus that doesn't exist.
5998 Changes in version 0.1.1.26 - 2006-12-14
5999 o Security bugfixes:
6000 - Stop sending the HttpProxyAuthenticator string to directory
6001 servers when directory connections are tunnelled through Tor.
6002 - Clients no longer store bandwidth history in the state file.
6003 - Do not log introduction points for hidden services if SafeLogging
6007 - Fix an assert failure when a directory authority sets
6008 AuthDirRejectUnlisted and then receives a descriptor from an
6009 unlisted router (reported by seeess).
6012 Changes in version 0.1.2.4-alpha - 2006-12-03
6014 - Add support for using natd; this allows FreeBSDs earlier than
6015 5.1.2 to have ipfw send connections through Tor without using
6016 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
6019 - Make all connections to addresses of the form ".noconnect"
6020 immediately get closed. This lets application/controller combos
6021 successfully test whether they're talking to the same Tor by
6022 watching for STREAM events.
6023 - Make cross.sh cross-compilation script work even when autogen.sh
6024 hasn't been run. (Patch from Michael Mohr.)
6025 - Statistics dumped by -USR2 now include a breakdown of public key
6026 operations, for profiling.
6029 - Fix a major leak when directory authorities parse their
6030 approved-routers list, a minor memory leak when we fail to pick
6031 an exit node, and a few rare leaks on errors.
6032 - Handle TransPort connections even when the server sends data before
6033 the client sends data. Previously, the connection would just hang
6034 until the client sent data. (Patch from tup based on patch from
6036 - Avoid assert failure when our cached-routers file is empty on
6040 - Don't log spurious warnings when we see a circuit close reason we
6041 don't recognize; it's probably just from a newer version of Tor.
6042 - Have directory authorities allow larger amounts of drift in uptime
6043 without replacing the server descriptor: previously, a server that
6044 restarted every 30 minutes could have 48 "interesting" descriptors
6046 - Start linking to the Tor specification and Tor reference manual
6047 correctly in the Windows installer.
6048 - Add Vidalia to the OS X uninstaller script, so when we uninstall
6049 Tor/Privoxy we also uninstall Vidalia.
6050 - Resume building on Irix64, and fix a lot of warnings from its
6052 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
6053 when we're running as a client.
6056 Changes in version 0.1.1.25 - 2006-11-04
6058 - When a client asks us to resolve (rather than connect to)
6059 an address, and we have a cached answer, give them the cached
6060 answer. Previously, we would give them no answer at all.
6061 - We were building exactly the wrong circuits when we predict
6062 hidden service requirements, meaning Tor would have to build all
6063 its circuits on demand.
6064 - If none of our live entry guards have a high uptime, but we
6065 require a guard with a high uptime, try adding a new guard before
6066 we give up on the requirement. This patch should make long-lived
6067 connections more stable on average.
6068 - When testing reachability of our DirPort, don't launch new
6069 tests when there's already one in progress -- unreachable
6070 servers were stacking up dozens of testing streams.
6072 o Security bugfixes:
6073 - When the user sends a NEWNYM signal, clear the client-side DNS
6074 cache too. Otherwise we continue to act on previous information.
6077 - Avoid a memory corruption bug when creating a hash table for
6079 - Avoid possibility of controller-triggered crash when misusing
6080 certain commands from a v0 controller on platforms that do not
6081 handle printf("%s",NULL) gracefully.
6082 - Avoid infinite loop on unexpected controller input.
6083 - Don't log spurious warnings when we see a circuit close reason we
6084 don't recognize; it's probably just from a newer version of Tor.
6085 - Add Vidalia to the OS X uninstaller script, so when we uninstall
6086 Tor/Privoxy we also uninstall Vidalia.
6089 Changes in version 0.1.2.3-alpha - 2006-10-29
6091 - Prepare for servers to publish descriptors less often: never
6092 discard a descriptor simply for being too old until either it is
6093 recommended by no authorities, or until we get a better one for
6094 the same router. Make caches consider retaining old recommended
6095 routers for even longer.
6096 - If most authorities set a BadExit flag for a server, clients
6097 don't think of it as a general-purpose exit. Clients only consider
6098 authorities that advertise themselves as listing bad exits.
6099 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
6100 headers for content, so that we can work better in the presence of
6101 caching HTTP proxies.
6102 - Allow authorities to list nodes as bad exits by fingerprint or by
6105 o Minor features, controller:
6106 - Add a REASON field to CIRC events; for backward compatibility, this
6107 field is sent only to controllers that have enabled the extended
6108 event format. Also, add additional reason codes to explain why
6109 a given circuit has been destroyed or truncated. (Patches from
6111 - Add a REMOTE_REASON field to extended CIRC events to tell the
6112 controller about why a remote OR told us to close a circuit.
6113 - Stream events also now have REASON and REMOTE_REASON fields,
6114 working much like those for circuit events.
6115 - There's now a GETINFO ns/... field so that controllers can ask Tor
6116 about the current status of a router.
6117 - A new event type "NS" to inform a controller when our opinion of
6118 a router's status has changed.
6119 - Add a GETINFO events/names and GETINFO features/names so controllers
6120 can tell which events and features are supported.
6121 - A new CLEARDNSCACHE signal to allow controllers to clear the
6122 client-side DNS cache without expiring circuits.
6124 o Security bugfixes:
6125 - When the user sends a NEWNYM signal, clear the client-side DNS
6126 cache too. Otherwise we continue to act on previous information.
6129 - Avoid sending junk to controllers or segfaulting when a controller
6130 uses EVENT_NEW_DESC with verbose nicknames.
6131 - Stop triggering asserts if the controller tries to extend hidden
6132 service circuits (reported by mwenge).
6133 - Avoid infinite loop on unexpected controller input.
6134 - When the controller does a "GETINFO network-status", tell it
6135 about even those routers whose descriptors are very old, and use
6136 long nicknames where appropriate.
6137 - Change NT service functions to be loaded on demand. This lets us
6138 build with MinGW without breaking Tor for Windows 98 users.
6139 - Do DirPort reachability tests less often, since a single test
6140 chews through many circuits before giving up.
6141 - In the hidden service example in torrc.sample, stop recommending
6142 esoteric and discouraged hidden service options.
6143 - When stopping an NT service, wait up to 10 sec for it to actually
6144 stop. (Patch from Matt Edman; resolves bug 295.)
6145 - Fix handling of verbose nicknames with ORCONN controller events:
6146 make them show up exactly when requested, rather than exactly when
6148 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
6149 printing a duplicate "$" in the keys we send (reported by mwenge).
6150 - Correctly set maximum connection limit on Cygwin. (This time
6152 - Try to detect Windows correctly when cross-compiling.
6153 - Detect the size of the routers file correctly even if it is
6154 corrupted (on systems without mmap) or not page-aligned (on systems
6155 with mmap). This bug was harmless.
6156 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
6157 to open a stream fails; now we do in more cases. This should
6158 make clients able to find a good exit faster in some cases, since
6159 unhandleable requests will now get an error rather than timing out.
6160 - Resolve two memory leaks when rebuilding the on-disk router cache
6161 (reported by fookoowa).
6162 - Clean up minor code warnings suggested by the MIPSpro C compiler,
6163 and reported by some Centos users.
6164 - Controller signals now work on non-Unix platforms that don't define
6165 SIGUSR1 and SIGUSR2 the way we expect.
6166 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
6167 values before failing, and always enables eventdns.
6168 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
6169 Try to fix this in configure.in by checking for most functions
6170 before we check for libevent.
6173 Changes in version 0.1.2.2-alpha - 2006-10-07
6175 - Make our async eventdns library on-by-default for Tor servers,
6176 and plan to deprecate the separate dnsworker threads.
6177 - Add server-side support for "reverse" DNS lookups (using PTR
6178 records so clients can determine the canonical hostname for a given
6179 IPv4 address). Only supported by servers using eventdns; servers
6180 now announce in their descriptors whether they support eventdns.
6181 - Specify and implement client-side SOCKS5 interface for reverse DNS
6182 lookups (see doc/socks-extensions.txt).
6183 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
6184 connect to directory servers through Tor. Previously, clients needed
6185 to find Tor exits to make private connections to directory servers.
6186 - Avoid choosing Exit nodes for entry or middle hops when the
6187 total bandwidth available from non-Exit nodes is much higher than
6188 the total bandwidth available from Exit nodes.
6189 - Workaround for name servers (like Earthlink's) that hijack failing
6190 DNS requests and replace the no-such-server answer with a "helpful"
6191 redirect to an advertising-driven search portal. Also work around
6192 DNS hijackers who "helpfully" decline to hijack known-invalid
6193 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
6194 lets you turn it off.
6195 - Send out a burst of long-range padding cells once we've established
6196 that we're reachable. Spread them over 4 circuits, so hopefully
6197 a few will be fast. This exercises our bandwidth and bootstraps
6198 us into the directory more quickly.
6200 o New/improved config options:
6201 - Add new config option "ResolvConf" to let the server operator
6202 choose an alternate resolve.conf file when using eventdns.
6203 - Add an "EnforceDistinctSubnets" option to control our "exclude
6204 servers on the same /16" behavior. It's still on by default; this
6205 is mostly for people who want to operate private test networks with
6206 all the machines on the same subnet.
6207 - If one of our entry guards is on the ExcludeNodes list, or the
6208 directory authorities don't think it's a good guard, treat it as
6209 if it were unlisted: stop using it as a guard, and throw it off
6210 the guards list if it stays that way for a long time.
6211 - Allow directory authorities to be marked separately as authorities
6212 for the v1 directory protocol, the v2 directory protocol, and
6213 as hidden service directories, to make it easier to retire old
6214 authorities. V1 authorities should set "HSAuthoritativeDir 1"
6215 to continue being hidden service authorities too.
6216 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
6218 o Minor features, controller:
6219 - Fix CIRC controller events so that controllers can learn the
6220 identity digests of non-Named servers used in circuit paths.
6221 - Let controllers ask for more useful identifiers for servers. Instead
6222 of learning identity digests for un-Named servers and nicknames
6223 for Named servers, the new identifiers include digest, nickname,
6224 and indication of Named status. Off by default; see control-spec.txt
6225 for more information.
6226 - Add a "getinfo address" controller command so it can display Tor's
6227 best guess to the user.
6228 - New controller event to alert the controller when our server
6229 descriptor has changed.
6230 - Give more meaningful errors on controller authentication failure.
6232 o Minor features, other:
6233 - When asked to resolve a hostname, don't use non-exit servers unless
6234 requested to do so. This allows servers with broken DNS to be
6235 useful to the network.
6236 - Divide eventdns log messages into warn and info messages.
6237 - Reserve the nickname "Unnamed" for routers that can't pick
6238 a hostname: any router can call itself Unnamed; directory
6239 authorities will never allocate Unnamed to any particular router;
6240 clients won't believe that any router is the canonical Unnamed.
6241 - Only include function names in log messages for info/debug messages.
6242 For notice/warn/err, the content of the message should be clear on
6243 its own, and printing the function name only confuses users.
6244 - Avoid some false positives during reachability testing: don't try
6245 to test via a server that's on the same /24 as us.
6246 - If we fail to build a circuit to an intended enclave, and it's
6247 not mandatory that we use that enclave, stop wanting it.
6248 - When eventdns is enabled, allow multithreaded builds on NetBSD and
6249 OpenBSD. (We had previously disabled threads on these platforms
6250 because they didn't have working thread-safe resolver functions.)
6252 o Major bugfixes, anonymity/security:
6253 - If a client asked for a server by name, and there's a named server
6254 in our network-status but we don't have its descriptor yet, we
6255 could return an unnamed server instead.
6256 - Fix NetBSD bug that could allow someone to force uninitialized RAM
6257 to be sent to a server's DNS resolver. This only affects NetBSD
6258 and other platforms that do not bounds-check tolower().
6259 - Reject (most) attempts to use Tor circuits with length one. (If
6260 many people start using Tor as a one-hop proxy, exit nodes become
6261 a more attractive target for compromise.)
6262 - Just because your DirPort is open doesn't mean people should be
6263 able to remotely teach you about hidden service descriptors. Now
6264 only accept rendezvous posts if you've got HSAuthoritativeDir set.
6266 o Major bugfixes, other:
6267 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
6268 - When a client asks the server to resolve (not connect to)
6269 an address, and it has a cached answer, give them the cached answer.
6270 Previously, the server would give them no answer at all.
6271 - Allow really slow clients to not hang up five minutes into their
6272 directory downloads (suggested by Adam J. Richter).
6273 - We were building exactly the wrong circuits when we anticipated
6274 hidden service requirements, meaning Tor would have to build all
6275 its circuits on demand.
6276 - Avoid crashing when we mmap a router cache file of size 0.
6277 - When testing reachability of our DirPort, don't launch new
6278 tests when there's already one in progress -- unreachable
6279 servers were stacking up dozens of testing streams.
6281 o Minor bugfixes, correctness:
6282 - If we're a directory mirror and we ask for "all" network status
6283 documents, we would discard status documents from authorities
6285 - Avoid a memory corruption bug when creating a hash table for
6287 - Avoid controller-triggered crash when misusing certain commands
6288 from a v0 controller on platforms that do not handle
6289 printf("%s",NULL) gracefully.
6290 - Don't crash when a controller sends a third argument to an
6291 "extendcircuit" request.
6292 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6293 response; fix error code when "getinfo dir/status/" fails.
6294 - Avoid crash when telling controller stream-status and a stream
6296 - Patch from Adam Langley to fix assert() in eventdns.c.
6297 - Fix a debug log message in eventdns to say "X resolved to Y"
6298 instead of "X resolved to X".
6299 - Make eventdns give strings for DNS errors, not just error numbers.
6300 - Track unreachable entry guards correctly: don't conflate
6301 'unreachable by us right now' with 'listed as down by the directory
6302 authorities'. With the old code, if a guard was unreachable by
6303 us but listed as running, it would clog our guard list forever.
6304 - Behave correctly in case we ever have a network with more than
6305 2GB/s total advertised capacity.
6306 - Make TrackExitHosts case-insensitive, and fix the behavior of
6307 ".suffix" TrackExitHosts items to avoid matching in the middle of
6309 - Finally fix the openssl warnings from newer gccs that believe that
6310 ignoring a return value is okay, but casting a return value and
6311 then ignoring it is a sign of madness.
6312 - Prevent the contrib/exitlist script from printing the same
6313 result more than once.
6314 - Patch from Steve Hildrey: Generate network status correctly on
6315 non-versioning dirservers.
6316 - Don't listen to the X-Your-Address-Is hint if you did the lookup
6317 via Tor; otherwise you'll think you're the exit node's IP address.
6319 o Minor bugfixes, performance:
6320 - Two small performance improvements on parsing descriptors.
6321 - Major performance improvement on inserting descriptors: change
6322 algorithm from O(n^2) to O(n).
6323 - Make the common memory allocation path faster on machines where
6324 malloc(0) returns a pointer.
6325 - Start remembering X-Your-Address-Is directory hints even if you're
6326 a client, so you can become a server more smoothly.
6327 - Avoid duplicate entries on MyFamily line in server descriptor.
6329 o Packaging, features:
6330 - Remove architecture from OS X builds. The official builds are
6331 now universal binaries.
6332 - The Debian package now uses --verify-config when (re)starting,
6333 to distinguish configuration errors from other errors.
6334 - Update RPMs to require libevent 1.1b.
6336 o Packaging, bugfixes:
6337 - Patches so Tor builds with MinGW on Windows.
6338 - Patches so Tor might run on Cygwin again.
6339 - Resume building on non-gcc compilers and ancient gcc. Resume
6340 building with the -O0 compile flag. Resume building cleanly on
6342 - Run correctly on OS X platforms with case-sensitive filesystems.
6343 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
6344 - Add autoconf checks so Tor can build on Solaris x86 again.
6347 - Documented (and renamed) ServerDNSSearchDomains and
6348 ServerDNSResolvConfFile options.
6349 - Be clearer that the *ListenAddress directives can be repeated
6353 Changes in version 0.1.1.24 - 2006-09-29
6355 - Allow really slow clients to not hang up five minutes into their
6356 directory downloads (suggested by Adam J. Richter).
6357 - Fix major performance regression from 0.1.0.x: instead of checking
6358 whether we have enough directory information every time we want to
6359 do something, only check when the directory information has changed.
6360 This should improve client CPU usage by 25-50%.
6361 - Don't crash if, after a server has been running for a while,
6362 it can't resolve its hostname.
6365 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6366 - Don't crash when the controller receives a third argument to an
6367 "extendcircuit" request.
6368 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6369 response; fix error code when "getinfo dir/status/" fails.
6370 - Fix configure.in to not produce broken configure files with
6371 more recent versions of autoconf. Thanks to Clint for his auto*
6373 - Fix security bug on NetBSD that could allow someone to force
6374 uninitialized RAM to be sent to a server's DNS resolver. This
6375 only affects NetBSD and other platforms that do not bounds-check
6377 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
6378 methods: these are known to be buggy.
6379 - If we're a directory mirror and we ask for "all" network status
6380 documents, we would discard status documents from authorities
6384 Changes in version 0.1.2.1-alpha - 2006-08-27
6386 - Add "eventdns" async dns library from Adam Langley, tweaked to
6387 build on OSX and Windows. Only enabled if you pass the
6388 --enable-eventdns argument to configure.
6389 - Allow servers with no hostname or IP address to learn their
6390 IP address by asking the directory authorities. This code only
6391 kicks in when you would normally have exited with a "no address"
6392 error. Nothing's authenticated, so use with care.
6393 - Rather than waiting a fixed amount of time between retrying
6394 application connections, we wait only 5 seconds for the first,
6395 10 seconds for the second, and 15 seconds for each retry after
6396 that. Hopefully this will improve the expected user experience.
6397 - Patch from Tup to add support for transparent AP connections:
6398 this basically bundles the functionality of trans-proxy-tor
6399 into the Tor mainline. Now hosts with compliant pf/netfilter
6400 implementations can redirect TCP connections straight to Tor
6401 without diverting through SOCKS. Needs docs.
6402 - Busy directory servers save lots of memory by spooling server
6403 descriptors, v1 directories, and v2 networkstatus docs to buffers
6404 as needed rather than en masse. Also mmap the cached-routers
6405 files, so we don't need to keep the whole thing in memory too.
6406 - Automatically avoid picking more than one node from the same
6407 /16 network when constructing a circuit.
6408 - Revise and clean up the torrc.sample that we ship with; add
6409 a section for BandwidthRate and BandwidthBurst.
6412 - Split circuit_t into origin_circuit_t and or_circuit_t, and
6413 split connection_t into edge, or, dir, control, and base structs.
6414 These will save quite a bit of memory on busy servers, and they'll
6415 also help us track down bugs in the code and bugs in the spec.
6416 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
6417 or later. Log when we are doing this, so we can diagnose it when
6418 it fails. (Also, recommend libevent 1.1b for kqueue and
6419 win32 methods; deprecate libevent 1.0b harder; make libevent
6420 recommendation system saner.)
6421 - Start being able to build universal binaries on OS X (thanks
6423 - Export the default exit policy via the control port, so controllers
6424 don't need to guess what it is / will be later.
6425 - Add a man page entry for ProtocolWarnings.
6426 - Add TestVia config option to the man page.
6427 - Remove even more protocol-related warnings from Tor server logs,
6428 such as bad TLS handshakes and malformed begin cells.
6429 - Stop fetching descriptors if you're not a dir mirror and you
6430 haven't tried to establish any circuits lately. [This currently
6431 causes some dangerous behavior, because when you start up again
6432 you'll use your ancient server descriptors.]
6433 - New DirPort behavior: if you have your dirport set, you download
6434 descriptors aggressively like a directory mirror, whether or not
6436 - Get rid of the router_retry_connections notion. Now routers
6437 no longer try to rebuild long-term connections to directory
6438 authorities, and directory authorities no longer try to rebuild
6439 long-term connections to all servers. We still don't hang up
6440 connections in these two cases though -- we need to look at it
6441 more carefully to avoid flapping, and we likely need to wait til
6442 0.1.1.x is obsolete.
6443 - Drop compatibility with obsolete Tors that permit create cells
6444 to have the wrong circ_id_type.
6445 - Re-enable per-connection rate limiting. Get rid of the "OP
6446 bandwidth" concept. Lay groundwork for "bandwidth classes" --
6447 separate global buckets that apply depending on what sort of conn
6449 - Start publishing one minute or so after we find our ORPort
6450 to be reachable. This will help reduce the number of descriptors
6451 we have for ourselves floating around, since it's quite likely
6452 other things (e.g. DirPort) will change during that minute too.
6453 - Fork the v1 directory protocol into its own spec document,
6454 and mark dir-spec.txt as the currently correct (v2) spec.
6457 - When we find our DirPort to be reachable, publish a new descriptor
6458 so we'll tell the world (reported by pnx).
6459 - Publish a new descriptor after we hup/reload. This is important
6460 if our config has changed such that we'll want to start advertising
6461 our DirPort now, etc.
6462 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6463 - When we have a state file we cannot parse, tell the user and
6464 move it aside. Now we avoid situations where the user starts
6465 Tor in 1904, Tor writes a state file with that timestamp in it,
6466 the user fixes her clock, and Tor refuses to start.
6467 - Fix configure.in to not produce broken configure files with
6468 more recent versions of autoconf. Thanks to Clint for his auto*
6470 - "tor --verify-config" now exits with -1(255) or 0 depending on
6471 whether the config options are bad or good.
6472 - Resolve bug 321 when using dnsworkers: append a period to every
6473 address we resolve at the exit node, so that we do not accidentally
6474 pick up local addresses, and so that failing searches are retried
6475 in the resolver search domains. (This is already solved for
6476 eventdns.) (This breaks Blossom servers for now.)
6477 - If we are using an exit enclave and we can't connect, e.g. because
6478 its webserver is misconfigured to not listen on localhost, then
6479 back off and try connecting from somewhere else before we fail.
6482 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
6483 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
6484 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
6485 when the IP address is mapped through MapAddress to a hostname.
6486 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6487 useless IPv6 DNS resolves.
6488 - Patch suggested by Karsten Loesing: respond to SIGNAL command
6489 before we execute the signal, in case the signal shuts us down.
6490 - Clean up AllowInvalidNodes man page entry.
6491 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
6492 - Add more asserts to track down an assert error on a windows Tor
6493 server with connection_add being called with socket == -1.
6494 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
6495 - Fix misleading log messages: an entry guard that is "unlisted",
6496 as well as not known to be "down" (because we've never heard
6497 of it), is not therefore "up".
6498 - Remove code to special-case "-cvs" ending, since it has not
6499 actually mattered since 0.0.9.
6500 - Make our socks5 handling more robust to broken socks clients:
6501 throw out everything waiting on the buffer in between socks
6502 handshake phases, since they can't possibly (so the theory
6503 goes) have predicted what we plan to respond to them.
6506 Changes in version 0.1.1.23 - 2006-07-30
6508 - Fast Tor servers, especially exit nodes, were triggering asserts
6509 due to a bug in handling the list of pending DNS resolves. Some
6510 bugs still remain here; we're hunting them.
6511 - Entry guards could crash clients by sending unexpected input.
6512 - More fixes on reachability testing: if you find yourself reachable,
6513 then don't ever make any client requests (so you stop predicting
6514 circuits), then hup or have your clock jump, then later your IP
6515 changes, you won't think circuits are working, so you won't try to
6516 test reachability, so you won't publish.
6519 - Avoid a crash if the controller does a resetconf firewallports
6520 and then a setconf fascistfirewall=1.
6521 - Avoid an integer underflow when the dir authority decides whether
6522 a router is stable: we might wrongly label it stable, and compute
6523 a slightly wrong median stability, when a descriptor is published
6525 - Fix a place where we might trigger an assert if we can't build our
6526 own server descriptor yet.
6529 Changes in version 0.1.1.22 - 2006-07-05
6531 - Fix a big bug that was causing servers to not find themselves
6532 reachable if they changed IP addresses. Since only 0.1.1.22+
6533 servers can do reachability testing correctly, now we automatically
6534 make sure to test via one of these.
6535 - Fix to allow clients and mirrors to learn directory info from
6536 descriptor downloads that get cut off partway through.
6537 - Directory authorities had a bug in deciding if a newly published
6538 descriptor was novel enough to make everybody want a copy -- a few
6539 servers seem to be publishing new descriptors many times a minute.
6541 - Fix a rare bug that was causing some servers to complain about
6542 "closing wedged cpuworkers" and skip some circuit create requests.
6543 - Make the Exit flag in directory status documents actually work.
6546 Changes in version 0.1.1.21 - 2006-06-10
6547 o Crash and assert fixes from 0.1.1.20:
6548 - Fix a rare crash on Tor servers that have enabled hibernation.
6549 - Fix a seg fault on startup for Tor networks that use only one
6550 directory authority.
6551 - Fix an assert from a race condition that occurs on Tor servers
6552 while exiting, where various threads are trying to log that they're
6553 exiting, and delete the logs, at the same time.
6554 - Make our unit tests pass again on certain obscure platforms.
6557 - Add support for building SUSE RPM packages.
6558 - Speed up initial bootstrapping for clients: if we are making our
6559 first ever connection to any entry guard, then don't mark it down
6561 - When only one Tor server in the network is labelled as a guard,
6562 and we've already picked him, we would cycle endlessly picking him
6563 again, being unhappy about it, etc. Now we specifically exclude
6564 current guards when picking a new guard.
6565 - Servers send create cells more reliably after the TLS connection
6566 is established: we were sometimes forgetting to send half of them
6567 when we had more than one pending.
6568 - If we get a create cell that asks us to extend somewhere, but the
6569 Tor server there doesn't match the expected digest, we now send
6570 a destroy cell back, rather than silently doing nothing.
6571 - Make options->RedirectExit work again.
6572 - Make cookie authentication for the controller work again.
6573 - Stop being picky about unusual characters in the arguments to
6574 mapaddress. It's none of our business.
6575 - Add a new config option "TestVia" that lets you specify preferred
6576 middle hops to use for test circuits. Perhaps this will let me
6577 debug the reachability problems better.
6579 o Log / documentation fixes:
6580 - If we're a server and some peer has a broken TLS certificate, don't
6581 log about it unless ProtocolWarnings is set, i.e., we want to hear
6582 about protocol violations by others.
6583 - Fix spelling of VirtualAddrNetwork in man page.
6584 - Add a better explanation at the top of the autogenerated torrc file
6585 about what happened to our old torrc.
6588 Changes in version 0.1.1.20 - 2006-05-23
6590 - Downgrade a log severity where servers complain that they're
6592 - Avoid a compile warning on FreeBSD.
6593 - Remove string size limit on NEWDESC messages; solve bug 291.
6594 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
6595 more thoroughly when we're running on windows.
6598 Changes in version 0.1.1.19-rc - 2006-05-03
6600 - Regenerate our local descriptor if it's dirty and we try to use
6601 it locally (e.g. if it changes during reachability detection).
6602 - If we setconf our ORPort to 0, we continued to listen on the
6603 old ORPort and receive connections.
6604 - Avoid a second warning about machine/limits.h on Debian
6606 - Be willing to add our own routerinfo into the routerlist.
6607 Now authorities will include themselves in their directories
6608 and network-statuses.
6609 - Stop trying to upload rendezvous descriptors to every
6610 directory authority: only try the v1 authorities.
6611 - Servers no longer complain when they think they're not
6612 registered with the directory authorities. There were too many
6614 - Backport dist-rpm changes so rpms can be built without errors.
6617 - Implement an option, VirtualAddrMask, to set which addresses
6618 get handed out in response to mapaddress requests. This works
6619 around a bug in tsocks where 127.0.0.0/8 is never socksified.
6622 Changes in version 0.1.1.18-rc - 2006-04-10
6624 - Work harder to download live network-statuses from all the
6625 directory authorities we know about. Improve the threshold
6626 decision logic so we're more robust to edge cases.
6627 - When fetching rendezvous descriptors, we were willing to ask
6628 v2 authorities too, which would always return 404.
6631 - Stop listing down or invalid nodes in the v1 directory. This will
6632 reduce its bulk by about 1/3, and reduce load on directory
6634 - When deciding whether a router is Fast or Guard-worthy, consider
6635 his advertised BandwidthRate and not just the BandwidthCapacity.
6636 - No longer ship INSTALL and README files -- they are useless now.
6637 - Force rpmbuild to behave and honor target_cpu.
6638 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6639 - Start to include translated versions of the tor-doc-*.html
6640 files, along with the screenshots. Still needs more work.
6641 - Start sending back 512 and 451 errors if mapaddress fails,
6642 rather than not sending anything back at all.
6643 - When we fail to bind or listen on an incoming or outgoing
6644 socket, we should close it before failing. otherwise we just
6645 leak it. (thanks to weasel for finding.)
6646 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
6647 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
6648 - Make NoPublish (even though deprecated) work again.
6649 - Fix a minor security flaw where a versioning auth dirserver
6650 could list a recommended version many times in a row to make
6651 clients more convinced that it's recommended.
6652 - Fix crash bug if there are two unregistered servers running
6653 with the same nickname, one of them is down, and you ask for
6654 them by nickname in your EntryNodes or ExitNodes. Also, try
6655 to pick the one that's running rather than an arbitrary one.
6656 - Fix an infinite loop we could hit if we go offline for too long.
6657 - Complain when we hit WSAENOBUFS on recv() or write() too.
6658 Perhaps this will help us hunt the bug.
6659 - If you're not a versioning dirserver, don't put the string
6660 "client-versions \nserver-versions \n" in your network-status.
6661 - Lower the minimum required number of file descriptors to 1000,
6662 so we can have some overhead for Valgrind on Linux, where the
6663 default ulimit -n is 1024.
6666 - Add tor.dizum.com as the fifth authoritative directory server.
6667 - Add a new config option FetchUselessDescriptors, off by default,
6668 for when you plan to run "exitlist" on your client and you want
6669 to know about even the non-running descriptors.
6672 Changes in version 0.1.1.17-rc - 2006-03-28
6674 - Clients and servers since 0.1.1.10-alpha have been expiring
6675 connections whenever they are idle for 5 minutes and they *do*
6676 have circuits on them. Oops. With this new version, clients will
6677 discard their previous entry guard choices and avoid choosing
6678 entry guards running these flawed versions.
6679 - Fix memory leak when uncompressing concatenated zlib streams. This
6680 was causing substantial leaks over time on Tor servers.
6681 - The v1 directory was including servers as much as 48 hours old,
6682 because that's how the new routerlist->routers works. Now only
6683 include them if they're 20 hours old or less.
6686 - Resume building on irix64, netbsd 2.0, etc.
6687 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
6689 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
6690 and it is confusing some users.
6691 - Mirrors stop caching the v1 directory so often.
6692 - Make the max number of old descriptors that a cache will hold
6693 rise with the number of directory authorities, so we can scale.
6694 - Change our win32 uname() hack to be more forgiving about what
6695 win32 versions it thinks it's found.
6698 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
6700 - When the controller's *setconf commands fail, collect an error
6701 message in a string and hand it back to the controller.
6702 - Make the v2 dir's "Fast" flag based on relative capacity, just
6703 like "Stable" is based on median uptime. Name everything in the
6704 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
6705 - Log server fingerprint on startup, so new server operators don't
6706 have to go hunting around their filesystem for it.
6707 - Return a robots.txt on our dirport to discourage google indexing.
6708 - Let the controller ask for GETINFO dir/status/foo so it can ask
6709 directly rather than connecting to the dir port. Only works when
6710 dirport is set for now.
6712 o New config options rather than constants in the code:
6713 - SocksTimeout: How long do we let a socks connection wait
6714 unattached before we fail it?
6715 - CircuitBuildTimeout: Cull non-open circuits that were born
6716 at least this many seconds ago.
6717 - CircuitIdleTimeout: Cull open clean circuits that were born
6718 at least this many seconds ago.
6721 Changes in version 0.1.1.16-rc - 2006-03-18
6722 o Bugfixes on 0.1.1.15-rc:
6723 - Fix assert when the controller asks to attachstream a connect-wait
6724 or resolve-wait stream.
6725 - Now do address rewriting when the controller asks us to attach
6726 to a particular circuit too. This will let Blossom specify
6727 "moria2.exit" without having to learn what moria2's IP address is.
6728 - Make the "tor --verify-config" command-line work again, so people
6729 can automatically check if their torrc will parse.
6730 - Authoritative dirservers no longer require an open connection from
6731 a server to consider him "reachable". We need this change because
6732 when we add new auth dirservers, old servers won't know not to
6734 - Let Tor build on Sun CC again.
6735 - Fix an off-by-one buffer size in dirserv.c that magically never
6736 hit our three authorities but broke sjmurdoch's own tor network.
6737 - If we as a directory mirror don't know of any v1 directory
6738 authorities, then don't try to cache any v1 directories.
6739 - Stop warning about unknown servers in our family when they are
6740 given as hex digests.
6741 - Stop complaining as quickly to the server operator that he
6742 hasn't registered his nickname/key binding.
6743 - Various cleanups so we can add new V2 Auth Dirservers.
6744 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
6745 reflect the updated flags in our v2 dir protocol.
6746 - Resume allowing non-printable characters for exit streams (both
6747 for connecting and for resolving). Now we tolerate applications
6748 that don't follow the RFCs. But continue to block malformed names
6751 o Bugfixes on 0.1.0.x:
6752 - Fix assert bug in close_logs(): when we close and delete logs,
6753 remove them all from the global "logfiles" list.
6754 - Fix minor integer overflow in calculating when we expect to use up
6755 our bandwidth allocation before hibernating.
6756 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
6757 there are multiple SSLs installed with different versions.
6758 - When we try to be a server and Address is not explicitly set and
6759 our hostname resolves to a private IP address, try to use an
6760 interface address if it has a public address. Now Windows machines
6761 that think of themselves as localhost can work by default.
6764 - Let the controller ask for GETINFO dir/server/foo so it can ask
6765 directly rather than connecting to the dir port.
6766 - Let the controller tell us about certain router descriptors
6767 that it doesn't want Tor to use in circuits. Implement
6768 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
6769 - New config option SafeSocks to reject all application connections
6770 using unsafe socks protocols. Defaults to off.
6773 Changes in version 0.1.1.15-rc - 2006-03-11
6774 o Bugfixes and cleanups:
6775 - When we're printing strings from the network, don't try to print
6776 non-printable characters. This protects us against shell escape
6777 sequence exploits, and also against attacks to fool humans into
6778 misreading their logs.
6779 - Fix a bug where Tor would fail to establish any connections if you
6780 left it off for 24 hours and then started it: we were happy with
6781 the obsolete network statuses, but they all referred to router
6782 descriptors that were too old to fetch, so we ended up with no
6783 valid router descriptors.
6784 - Fix a seg fault in the controller's "getinfo orconn-status"
6785 command while listing status on incoming handshaking connections.
6786 Introduce a status name "NEW" for these connections.
6787 - If we get a linelist or linelist_s config option from the torrc
6788 (e.g. ExitPolicy) and it has no value, warn and skip rather than
6789 silently resetting it to its default.
6790 - Don't abandon entry guards until they've been down or gone for
6792 - Cleaner and quieter log messages.
6795 - New controller signal NEWNYM that makes new application requests
6797 - Add a new circuit purpose 'controller' to let the controller ask
6798 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
6799 controller command to let you specify the purpose if you're
6800 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
6801 command to let you change a circuit's purpose after it's been
6803 - Accept "private:*" in routerdesc exit policies; not generated yet
6804 because older Tors do not understand it.
6805 - Add BSD-style contributed startup script "rc.subr" from Peter
6809 Changes in version 0.1.1.14-alpha - 2006-02-20
6810 o Bugfixes on 0.1.1.x:
6811 - Don't die if we ask for a stdout or stderr log (even implicitly)
6812 and we're set to RunAsDaemon -- just warn.
6813 - We still had a few bugs in the OR connection rotation code that
6814 caused directory servers to slowly aggregate connections to other
6815 fast Tor servers. This time for sure!
6816 - Make log entries on Win32 include the name of the function again.
6817 - We were treating a pair of exit policies if they were equal even
6818 if one said accept and the other said reject -- causing us to
6819 not always publish a new descriptor since we thought nothing
6821 - Retry pending server downloads as well as pending networkstatus
6822 downloads when we unexpectedly get a socks request.
6823 - We were ignoring the IS_FAST flag in the directory status,
6824 meaning we were willing to pick trivial-bandwidth nodes for "fast"
6826 - If the controller's SAVECONF command fails (e.g. due to file
6827 permissions), let the controller know that it failed.
6830 - If we're trying to be a Tor server and running Windows 95/98/ME
6831 as a server, explain that we'll likely crash.
6832 - When we're a server, a client asks for an old-style directory,
6833 and our write bucket is empty, don't give it to him. This way
6834 small servers can continue to serve the directory *sometimes*,
6835 without getting overloaded.
6836 - Compress exit policies even more -- look for duplicate lines
6838 - Clients now honor the "guard" flag in the router status when
6839 picking entry guards, rather than looking at is_fast or is_stable.
6840 - Retain unrecognized lines in $DATADIR/state file, so that we can
6841 be forward-compatible.
6842 - Generate 18.0.0.0/8 address policy format in descs when we can;
6843 warn when the mask is not reducible to a bit-prefix.
6844 - Let the user set ControlListenAddress in the torrc. This can be
6845 dangerous, but there are some cases (like a secured LAN) where it
6847 - Split ReachableAddresses into ReachableDirAddresses and
6848 ReachableORAddresses, so we can restrict Dir conns to port 80
6849 and OR conns to port 443.
6850 - Now we can target arch and OS in rpm builds (contributed by
6851 Phobos). Also make the resulting dist-rpm filename match the
6853 - New config options to help controllers: FetchServerDescriptors
6854 and FetchHidServDescriptors for whether to fetch server
6855 info and hidserv info or let the controller do it, and
6856 PublishServerDescriptor and PublishHidServDescriptors.
6857 - Also let the controller set the __AllDirActionsPrivate config
6858 option if you want all directory fetches/publishes to happen via
6859 Tor (it assumes your controller bootstraps your circuits).
6862 Changes in version 0.1.0.17 - 2006-02-17
6863 o Crash bugfixes on 0.1.0.x:
6864 - When servers with a non-zero DirPort came out of hibernation,
6865 sometimes they would trigger an assert.
6867 o Other important bugfixes:
6868 - On platforms that don't have getrlimit (like Windows), we were
6869 artificially constraining ourselves to a max of 1024
6870 connections. Now just assume that we can handle as many as 15000
6871 connections. Hopefully this won't cause other problems.
6873 o Backported features:
6874 - When we're a server, a client asks for an old-style directory,
6875 and our write bucket is empty, don't give it to him. This way
6876 small servers can continue to serve the directory *sometimes*,
6877 without getting overloaded.
6878 - Whenever you get a 503 in response to a directory fetch, try
6879 once more. This will become important once servers start sending
6880 503's whenever they feel busy.
6881 - Fetch a new directory every 120 minutes, not every 40 minutes.
6882 Now that we have hundreds of thousands of users running the old
6883 directory algorithm, it's starting to hurt a lot.
6884 - Bump up the period for forcing a hidden service descriptor upload
6885 from 20 minutes to 1 hour.
6888 Changes in version 0.1.1.13-alpha - 2006-02-09
6889 o Crashes in 0.1.1.x:
6890 - When you tried to setconf ORPort via the controller, Tor would
6891 crash. So people using TorCP to become a server were sad.
6892 - Solve (I hope) the stack-smashing bug that we were seeing on fast
6893 servers. The problem appears to be something do with OpenSSL's
6894 random number generation, or how we call it, or something. Let me
6895 know if the crashes continue.
6896 - Turn crypto hardware acceleration off by default, until we find
6897 somebody smart who can test it for us. (It appears to produce
6898 seg faults in at least some cases.)
6899 - Fix a rare assert error when we've tried all intro points for
6900 a hidden service and we try fetching the service descriptor again:
6901 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
6904 - Fix a major load balance bug: we were round-robining in 16 KB
6905 chunks, and servers with bandwidthrate of 20 KB, while downloading
6906 a 600 KB directory, would starve their other connections. Now we
6907 try to be a bit more fair.
6908 - Dir authorities and mirrors were never expiring the newest
6909 descriptor for each server, causing memory and directory bloat.
6910 - Fix memory-bloating and connection-bloating bug on servers: We
6911 were never closing any connection that had ever had a circuit on
6912 it, because we were checking conn->n_circuits == 0, yet we had a
6913 bug that let it go negative.
6914 - Make Tor work using squid as your http proxy again -- squid
6915 returns an error if you ask for a URL that's too long, and it uses
6916 a really generic error message. Plus, many people are behind a
6917 transparent squid so they don't even realize it.
6918 - On platforms that don't have getrlimit (like Windows), we were
6919 artificially constraining ourselves to a max of 1024
6920 connections. Now just assume that we can handle as many as 15000
6921 connections. Hopefully this won't cause other problems.
6922 - Add a new config option ExitPolicyRejectPrivate which defaults to
6923 1. This means all exit policies will begin with rejecting private
6924 addresses, unless the server operator explicitly turns it off.
6927 - Clients no longer download descriptors for non-running
6929 - Before we add new directory authorities, we should make it
6930 clear that only v1 authorities should receive/publish hidden
6931 service descriptors.
6934 - As soon as we've fetched some more directory info, immediately
6935 try to download more server descriptors. This way we don't have
6936 a 10 second pause during initial bootstrapping.
6937 - Remove even more loud log messages that the server operator can't
6939 - When we're running an obsolete or un-recommended version, make
6940 the log message more clear about what the problem is and what
6941 versions *are* still recommended.
6942 - Provide a more useful warn message when our onion queue gets full:
6943 the CPU is too slow or the exit policy is too liberal.
6944 - Don't warn when we receive a 503 from a dirserver/cache -- this
6945 will pave the way for them being able to refuse if they're busy.
6946 - When we fail to bind a listener, try to provide a more useful
6947 log message: e.g., "Is Tor already running?"
6948 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
6949 Goldberg can prove things about our handshake protocol more
6951 - MaxConn has been obsolete for a while now. Document the ConnLimit
6952 config option, which is a *minimum* number of file descriptors
6953 that must be available else Tor refuses to start.
6954 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
6955 if you log to syslog and want something other than LOG_DAEMON.
6956 - Make dirservers generate a separate "guard" flag to mean,
6957 "would make a good entry guard". Make clients parse it and vote
6958 on it. Not used by clients yet.
6959 - Implement --with-libevent-dir option to ./configure. Also, improve
6960 search techniques to find libevent, and use those for openssl too.
6961 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
6962 - Only start testing reachability once we've established a
6963 circuit. This will make startup on dirservers less noisy.
6964 - Don't try to upload hidden service descriptors until we have
6965 established a circuit.
6966 - Fix the controller's "attachstream 0" command to treat conn like
6967 it just connected, doing address remapping, handling .exit and
6968 .onion idioms, and so on. Now we're more uniform in making sure
6969 that the controller hears about new and closing connections.
6972 Changes in version 0.1.1.12-alpha - 2006-01-11
6973 o Bugfixes on 0.1.1.x:
6974 - The fix to close duplicate server connections was closing all
6975 Tor client connections if they didn't establish a circuit
6976 quickly enough. Oops.
6977 - Fix minor memory issue (double-free) that happened on exit.
6979 o Bugfixes on 0.1.0.x:
6980 - Tor didn't warn when it failed to open a log file.
6983 Changes in version 0.1.1.11-alpha - 2006-01-10
6984 o Crashes in 0.1.1.x:
6985 - Include all the assert/crash fixes from 0.1.0.16.
6986 - If you start Tor and then quit very quickly, there were some
6987 races that tried to free things that weren't allocated yet.
6988 - Fix a rare memory stomp if you're running hidden services.
6989 - Fix segfault when specifying DirServer in config without nickname.
6990 - Fix a seg fault when you finish connecting to a server but at
6991 that moment you dump his server descriptor.
6992 - Extendcircuit and Attachstream controller commands would
6993 assert/crash if you don't give them enough arguments.
6994 - Fix an assert error when we're out of space in the connection_list
6995 and we try to post a hidden service descriptor (reported by weasel).
6996 - If you specify a relative torrc path and you set RunAsDaemon in
6997 your torrc, then it chdir()'s to the new directory. If you HUP,
6998 it tries to load the new torrc location, fails, and exits.
6999 The fix: no longer allow a relative path to torrc using -f.
7002 - Implement "entry guards": automatically choose a handful of entry
7003 nodes and stick with them for all circuits. Only pick new guards
7004 when the ones you have are unsuitable, and if the old guards
7005 become suitable again, switch back. This will increase security
7006 dramatically against certain end-point attacks. The EntryNodes
7007 config option now provides some hints about which entry guards you
7008 want to use most; and StrictEntryNodes means to only use those.
7009 - New directory logic: download by descriptor digest, not by
7010 fingerprint. Caches try to download all listed digests from
7011 authorities; clients try to download "best" digests from caches.
7012 This avoids partitioning and isolating attacks better.
7013 - Make the "stable" router flag in network-status be the median of
7014 the uptimes of running valid servers, and make clients pay
7015 attention to the network-status flags. Thus the cutoff adapts
7016 to the stability of the network as a whole, making IRC, IM, etc
7017 connections more reliable.
7020 - Tor servers with dynamic IP addresses were needing to wait 18
7021 hours before they could start doing reachability testing using
7022 the new IP address and ports. This is because they were using
7023 the internal descriptor to learn what to test, yet they were only
7024 rebuilding the descriptor once they decided they were reachable.
7025 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
7026 to download certain server descriptors, throw them away, and then
7027 fetch them again after 30 minutes. Now mirrors throw away these
7028 server descriptors so clients can't get them.
7029 - We were leaving duplicate connections to other ORs open for a week,
7030 rather than closing them once we detect a duplicate. This only
7031 really affected authdirservers, but it affected them a lot.
7032 - Spread the authdirservers' reachability testing over the entire
7033 testing interval, so we don't try to do 500 TLS's at once every
7037 - If the network is down, and we try to connect to a conn because
7038 we have a circuit in mind, and we timeout (30 seconds) because the
7039 network never answers, we were expiring the circuit, but we weren't
7040 obsoleting the connection or telling the entry_guards functions.
7041 - Some Tor servers process billions of cells per day. These statistics
7042 need to be uint64_t's.
7043 - Check for integer overflows in more places, when adding elements
7044 to smartlists. This could possibly prevent a buffer overflow
7045 on malicious huge inputs. I don't see any, but I haven't looked
7047 - ReachableAddresses kept growing new "reject *:*" lines on every
7049 - When you "setconf log" via the controller, it should remove all
7050 logs. We were automatically adding back in a "log notice stdout".
7051 - Newly bootstrapped Tor networks couldn't establish hidden service
7052 circuits until they had nodes with high uptime. Be more tolerant.
7053 - We were marking servers down when they could not answer every piece
7054 of the directory request we sent them. This was far too harsh.
7055 - Fix the torify (tsocks) config file to not use Tor for localhost
7057 - Directory authorities now go to the proper authority when asking for
7058 a networkstatus, even when they want a compressed one.
7059 - Fix a harmless bug that was causing Tor servers to log
7060 "Got an end because of misc error, but we're not an AP. Closing."
7061 - Authorities were treating their own descriptor changes as cosmetic,
7062 meaning the descriptor available in the network-status and the
7063 descriptor that clients downloaded were different.
7064 - The OS X installer was adding a symlink for tor_resolve but
7065 the binary was called tor-resolve (reported by Thomas Hardly).
7066 - Workaround a problem with some http proxies where they refuse GET
7067 requests that specify "Content-Length: 0" (reported by Adrian).
7068 - Fix wrong log message when you add a "HiddenServiceNodes" config
7069 line without any HiddenServiceDir line (reported by Chris Thomas).
7072 - Write the TorVersion into the state file so we have a prayer of
7073 keeping forward and backward compatibility.
7074 - Revive the FascistFirewall config option rather than eliminating it:
7075 now it's a synonym for ReachableAddresses *:80,*:443.
7076 - Clients choose directory servers from the network status lists,
7077 not from their internal list of router descriptors. Now they can
7078 go to caches directly rather than needing to go to authorities
7080 - Directory authorities ignore router descriptors that have only
7081 cosmetic differences: do this for 0.1.0.x servers now too.
7082 - Add a new flag to network-status indicating whether the server
7083 can answer v2 directory requests too.
7084 - Authdirs now stop whining so loudly about bad descriptors that
7085 they fetch from other dirservers. So when there's a log complaint,
7086 it's for sure from a freshly uploaded descriptor.
7087 - Reduce memory requirements in our structs by changing the order
7089 - There used to be two ways to specify your listening ports in a
7090 server descriptor: on the "router" line and with a separate "ports"
7091 line. Remove support for the "ports" line.
7092 - New config option "AuthDirRejectUnlisted" for auth dirservers as
7093 a panic button: if we get flooded with unusable servers we can
7094 revert to only listing servers in the approved-routers file.
7095 - Auth dir servers can now mark a fingerprint as "!reject" or
7096 "!invalid" in the approved-routers file (as its nickname), to
7097 refuse descriptors outright or include them but marked as invalid.
7098 - Servers store bandwidth history across restarts/crashes.
7099 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
7100 get a better idea of why their circuits failed. Not used yet.
7101 - Directory mirrors now cache up to 16 unrecognized network-status
7102 docs. Now we can add new authdirservers and they'll be cached too.
7103 - When picking a random directory, prefer non-authorities if any
7105 - New controller option "getinfo desc/all-recent" to fetch the
7106 latest server descriptor for every router that Tor knows about.
7109 Changes in version 0.1.0.16 - 2006-01-02
7110 o Crash bugfixes on 0.1.0.x:
7111 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
7112 corrupting the heap, losing FDs, or crashing when we need to resize
7113 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
7114 - It turns out sparc64 platforms crash on unaligned memory access
7115 too -- so detect and avoid this.
7116 - Handle truncated compressed data correctly (by detecting it and
7118 - Fix possible-but-unlikely free(NULL) in control.c.
7119 - When we were closing connections, there was a rare case that
7120 stomped on memory, triggering seg faults and asserts.
7121 - Avoid potential infinite recursion when building a descriptor. (We
7122 don't know that it ever happened, but better to fix it anyway.)
7123 - We were neglecting to unlink marked circuits from soon-to-close OR
7124 connections, which caused some rare scribbling on freed memory.
7125 - Fix a memory stomping race bug when closing the joining point of two
7126 rendezvous circuits.
7127 - Fix an assert in time parsing found by Steven Murdoch.
7129 o Other bugfixes on 0.1.0.x:
7130 - When we're doing reachability testing, provide more useful log
7131 messages so the operator knows what to expect.
7132 - Do not check whether DirPort is reachable when we are suppressing
7133 advertising it because of hibernation.
7134 - When building with -static or on Solaris, we sometimes needed -ldl.
7135 - When we're deciding whether a stream has enough circuits around
7136 that can handle it, count the freshly dirty ones and not the ones
7137 that are so dirty they won't be able to handle it.
7138 - When we're expiring old circuits, we had a logic error that caused
7139 us to close new rendezvous circuits rather than old ones.
7140 - Give a more helpful log message when you try to change ORPort via
7141 the controller: you should upgrade Tor if you want that to work.
7142 - We were failing to parse Tor versions that start with "Tor ".
7143 - Tolerate faulty streams better: when a stream fails for reason
7144 exitpolicy, stop assuming that the router is lying about his exit
7145 policy. When a stream fails for reason misc, allow it to retry just
7146 as if it was resolvefailed. When a stream has failed three times,
7147 reset its failure count so we can try again and get all three tries.
7150 Changes in version 0.1.1.10-alpha - 2005-12-11
7151 o Correctness bugfixes on 0.1.0.x:
7152 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
7153 corrupting the heap, losing FDs, or crashing when we need to resize
7154 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
7155 - Stop doing the complex voodoo overkill checking for insecure
7156 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
7157 - When we were closing connections, there was a rare case that
7158 stomped on memory, triggering seg faults and asserts.
7159 - We were neglecting to unlink marked circuits from soon-to-close OR
7160 connections, which caused some rare scribbling on freed memory.
7161 - When we're deciding whether a stream has enough circuits around
7162 that can handle it, count the freshly dirty ones and not the ones
7163 that are so dirty they won't be able to handle it.
7164 - Recover better from TCP connections to Tor servers that are
7165 broken but don't tell you (it happens!); and rotate TLS
7166 connections once a week.
7167 - When we're expiring old circuits, we had a logic error that caused
7168 us to close new rendezvous circuits rather than old ones.
7169 - Fix a scary-looking but apparently harmless bug where circuits
7170 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
7171 servers, and never switch to state CIRCUIT_STATE_OPEN.
7172 - When building with -static or on Solaris, we sometimes needed to
7174 - Give a useful message when people run Tor as the wrong user,
7175 rather than telling them to start chowning random directories.
7176 - We were failing to inform the controller about new .onion streams.
7178 o Security bugfixes on 0.1.0.x:
7179 - Refuse server descriptors if the fingerprint line doesn't match
7180 the included identity key. Tor doesn't care, but other apps (and
7181 humans) might actually be trusting the fingerprint line.
7182 - We used to kill the circuit when we receive a relay command we
7183 don't recognize. Now we just drop it.
7184 - Start obeying our firewall options more rigorously:
7185 . If we can't get to a dirserver directly, try going via Tor.
7186 . Don't ever try to connect (as a client) to a place our
7187 firewall options forbid.
7188 . If we specify a proxy and also firewall options, obey the
7189 firewall options even when we're using the proxy: some proxies
7190 can only proxy to certain destinations.
7191 - Fix a bug found by Lasse Overlier: when we were making internal
7192 circuits (intended to be cannibalized later for rendezvous and
7193 introduction circuits), we were picking them so that they had
7194 useful exit nodes. There was no need for this, and it actually
7195 aids some statistical attacks.
7196 - Start treating internal circuits and exit circuits separately.
7197 It's important to keep them separate because internal circuits
7198 have their last hops picked like middle hops, rather than like
7199 exit hops. So exiting on them will break the user's expectations.
7201 o Bugfixes on 0.1.1.x:
7202 - Take out the mis-feature where we tried to detect IP address
7203 flapping for people with DynDNS, and chose not to upload a new
7204 server descriptor sometimes.
7205 - Try to be compatible with OpenSSL 0.9.6 again.
7206 - Log fix: when the controller is logging about .onion addresses,
7207 sometimes it didn't include the ".onion" part of the address.
7208 - Don't try to modify options->DirServers internally -- if the
7209 user didn't specify any, just add the default ones directly to
7210 the trusted dirserver list. This fixes a bug where people running
7211 controllers would use SETCONF on some totally unrelated config
7212 option, and Tor would start yelling at them about changing their
7214 - Let the controller's redirectstream command specify a port, in
7215 case the controller wants to change that too.
7216 - When we requested a pile of server descriptors, we sometimes
7217 accidentally launched a duplicate request for the first one.
7218 - Bugfix for trackhostexits: write down the fingerprint of the
7219 chosen exit, not its nickname, because the chosen exit might not
7221 - When parsing foo.exit, if foo is unknown, and we are leaving
7222 circuits unattached, set the chosen_exit field and leave the
7223 address empty. This matters because controllers got confused
7225 - Directory authorities no longer try to download server
7226 descriptors that they know they will reject.
7228 o Features and updates:
7229 - Replace balanced trees with hash tables: this should make stuff
7230 significantly faster.
7231 - Resume using the AES counter-mode implementation that we ship,
7232 rather than OpenSSL's. Ours is significantly faster.
7233 - Many other CPU and memory improvements.
7234 - Add a new config option FastFirstHopPK (on by default) so clients
7235 do a trivial crypto handshake for their first hop, since TLS has
7236 already taken care of confidentiality and authentication.
7237 - Add a new config option TestSocks so people can see if their
7238 applications are using socks4, socks4a, socks5-with-ip, or
7239 socks5-with-hostname. This way they don't have to keep mucking
7240 with tcpdump and wondering if something got cached somewhere.
7241 - Warn when listening on a public address for socks. I suspect a
7242 lot of people are setting themselves up as open socks proxies,
7243 and they have no idea that jerks on the Internet are using them,
7244 since they simply proxy the traffic into the Tor network.
7245 - Add "private:*" as an alias in configuration for policies. Now
7246 you can simplify your exit policy rather than needing to list
7247 every single internal or nonroutable network space.
7248 - Add a new controller event type that allows controllers to get
7249 all server descriptors that were uploaded to a router in its role
7250 as authoritative dirserver.
7251 - Start shipping socks-extensions.txt, tor-doc-unix.html,
7252 tor-doc-server.html, and stylesheet.css in the tarball.
7253 - Stop shipping tor-doc.html in the tarball.
7256 Changes in version 0.1.1.9-alpha - 2005-11-15
7257 o Usability improvements:
7258 - Start calling it FooListenAddress rather than FooBindAddress,
7259 since few of our users know what it means to bind an address
7261 - Reduce clutter in server logs. We're going to try to make
7262 them actually usable now. New config option ProtocolWarnings that
7263 lets you hear about how _other Tors_ are breaking the protocol. Off
7265 - Divide log messages into logging domains. Once we put some sort
7266 of interface on this, it will let people looking at more verbose
7267 log levels specify the topics they want to hear more about.
7268 - Make directory servers return better http 404 error messages
7269 instead of a generic "Servers unavailable".
7270 - Check for even more Windows version flags when writing the platform
7271 string in server descriptors, and note any we don't recognize.
7272 - Clean up more of the OpenSSL memory when exiting, so we can detect
7273 memory leaks better.
7274 - Make directory authorities be non-versioning, non-naming by
7275 default. Now we can add new directory servers without requiring
7276 their operators to pay close attention.
7277 - When logging via syslog, include the pid whenever we provide
7278 a log entry. Suggested by Todd Fries.
7280 o Performance improvements:
7281 - Directory servers now silently throw away new descriptors that
7282 haven't changed much if the timestamps are similar. We do this to
7283 tolerate older Tor servers that upload a new descriptor every 15
7284 minutes. (It seemed like a good idea at the time.)
7285 - Inline bottleneck smartlist functions; use fast versions by default.
7286 - Add a "Map from digest to void*" abstraction digestmap_t so we
7287 can do less hex encoding/decoding. Use it in router_get_by_digest()
7288 to resolve a performance bottleneck.
7289 - Allow tor_gzip_uncompress to extract as much as possible from
7290 truncated compressed data. Try to extract as many
7291 descriptors as possible from truncated http responses (when
7292 DIR_PURPOSE_FETCH_ROUTERDESC).
7293 - Make circ->onionskin a pointer, not a static array. moria2 was using
7294 125000 circuit_t's after it had been up for a few weeks, which
7295 translates to 20+ megs of wasted space.
7296 - The private half of our EDH handshake keys are now chosen out
7297 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
7299 o Security improvements:
7300 - Start making directory caches retain old routerinfos, so soon
7301 clients can start asking by digest of descriptor rather than by
7302 fingerprint of server.
7303 - Add half our entropy from RAND_poll in OpenSSL. This knows how
7304 to use egd (if present), openbsd weirdness (if present), vms/os2
7305 weirdness (if we ever port there), and more in the future.
7307 o Bugfixes on 0.1.0.x:
7308 - Do round-robin writes of at most 16 kB per write. This might be
7309 more fair on loaded Tor servers, and it might resolve our Windows
7310 crash bug. It might also slow things down.
7311 - Our TLS handshakes were generating a single public/private
7312 keypair for the TLS context, rather than making a new one for
7313 each new connections. Oops. (But we were still rotating them
7314 periodically, so it's not so bad.)
7315 - When we were cannibalizing a circuit with a particular exit
7316 node in mind, we weren't checking to see if that exit node was
7317 already present earlier in the circuit. Oops.
7318 - When a Tor server's IP changes (e.g. from a dyndns address),
7319 upload a new descriptor so clients will learn too.
7320 - Really busy servers were keeping enough circuits open on stable
7321 connections that they were wrapping around the circuit_id
7322 space. (It's only two bytes.) This exposed a bug where we would
7323 feel free to reuse a circuit_id even if it still exists but has
7324 been marked for close. Try to fix this bug. Some bug remains.
7325 - If we would close a stream early (e.g. it asks for a .exit that
7326 we know would refuse it) but the LeaveStreamsUnattached config
7327 option is set by the controller, then don't close it.
7329 o Bugfixes on 0.1.1.8-alpha:
7330 - Fix a big pile of memory leaks, some of them serious.
7331 - Do not try to download a routerdesc if we would immediately reject
7333 - Resume inserting a newline between all router descriptors when
7334 generating (old style) signed directories, since our spec says
7336 - When providing content-type application/octet-stream for
7337 server descriptors using .z, we were leaving out the
7338 content-encoding header. Oops. (Everything tolerated this just
7339 fine, but that doesn't mean we need to be part of the problem.)
7340 - Fix a potential seg fault in getconf and getinfo using version 1
7341 of the controller protocol.
7342 - Avoid crash: do not check whether DirPort is reachable when we
7343 are suppressing it because of hibernation.
7344 - Make --hash-password not crash on exit.
7347 Changes in version 0.1.1.8-alpha - 2005-10-07
7348 o New features (major):
7349 - Clients don't download or use the directory anymore. Now they
7350 download and use network-statuses from the trusted dirservers,
7351 and fetch individual server descriptors as needed from mirrors.
7352 See dir-spec.txt for all the gory details.
7353 - Be more conservative about whether to advertise our DirPort.
7354 The main change is to not advertise if we're running at capacity
7355 and either a) we could hibernate or b) our capacity is low and
7356 we're using a default DirPort.
7357 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
7359 o New features (minor):
7360 - Try to be smart about when to retry network-status and
7361 server-descriptor fetches. Still needs some tuning.
7362 - Stop parsing, storing, or using running-routers output (but
7363 mirrors still cache and serve it).
7364 - Consider a threshold of versioning dirservers (dirservers who have
7365 an opinion about which Tor versions are still recommended) before
7366 deciding whether to warn the user that he's obsolete.
7367 - Dirservers can now reject/invalidate by key and IP, with the
7368 config options "AuthDirInvalid" and "AuthDirReject". This is
7369 useful since currently we automatically list servers as running
7370 and usable even if we know they're jerks.
7371 - Provide dire warnings to any users who set DirServer; move it out
7372 of torrc.sample and into torrc.complete.
7373 - Add MyFamily to torrc.sample in the server section.
7374 - Add nicknames to the DirServer line, so we can refer to them
7375 without requiring all our users to memorize their IP addresses.
7376 - When we get an EOF or a timeout on a directory connection, note
7377 how many bytes of serverdesc we are dropping. This will help
7378 us determine whether it is smart to parse incomplete serverdesc
7380 - Add a new function to "change pseudonyms" -- that is, to stop
7381 using any currently-dirty circuits for new streams, so we don't
7382 link new actions to old actions. Currently it's only called on
7383 HUP (or SIGNAL RELOAD).
7384 - On sighup, if UseHelperNodes changed to 1, use new circuits.
7385 - Start using RAND_bytes rather than RAND_pseudo_bytes from
7386 OpenSSL. Also, reseed our entropy every hour, not just at
7387 startup. And entropy in 512-bit chunks, not 160-bit chunks.
7389 o Fixes on 0.1.1.7-alpha:
7390 - Nobody ever implemented EVENT_ADDRMAP for control protocol
7391 version 0, so don't let version 0 controllers ask for it.
7392 - If you requested something with too many newlines via the
7393 v1 controller protocol, you could crash tor.
7394 - Fix a number of memory leaks, including some pretty serious ones.
7395 - Re-enable DirPort testing again, so Tor servers will be willing
7396 to advertise their DirPort if it's reachable.
7397 - On TLS handshake, only check the other router's nickname against
7398 its expected nickname if is_named is set.
7400 o Fixes forward-ported from 0.1.0.15:
7401 - Don't crash when we don't have any spare file descriptors and we
7402 try to spawn a dns or cpu worker.
7403 - Make the numbers in read-history and write-history into uint64s,
7404 so they don't overflow and publish negatives in the descriptor.
7407 - For the OS X package's modified privoxy config file, comment
7408 out the "logfile" line so we don't log everything passed
7410 - We were whining about using socks4 or socks5-with-local-lookup
7411 even when it's an IP in the "virtual" range we designed exactly
7413 - We were leaking some memory every time the client changes IPs.
7414 - Never call free() on tor_malloc()d memory. This will help us
7415 use dmalloc to detect memory leaks.
7416 - Check for named servers when looking them up by nickname;
7417 warn when we'recalling a non-named server by its nickname;
7418 don't warn twice about the same name.
7419 - Try to list MyFamily elements by key, not by nickname, and warn
7420 if we've not heard of the server.
7421 - Make windows platform detection (uname equivalent) smarter.
7422 - It turns out sparc64 doesn't like unaligned access either.
7425 Changes in version 0.1.0.15 - 2005-09-23
7426 o Bugfixes on 0.1.0.x:
7427 - Reject ports 465 and 587 (spam targets) in default exit policy.
7428 - Don't crash when we don't have any spare file descriptors and we
7429 try to spawn a dns or cpu worker.
7430 - Get rid of IgnoreVersion undocumented config option, and make us
7431 only warn, never exit, when we're running an obsolete version.
7432 - Don't try to print a null string when your server finds itself to
7433 be unreachable and the Address config option is empty.
7434 - Make the numbers in read-history and write-history into uint64s,
7435 so they don't overflow and publish negatives in the descriptor.
7436 - Fix a minor memory leak in smartlist_string_remove().
7437 - We were only allowing ourselves to upload a server descriptor at
7438 most every 20 minutes, even if it changed earlier than that.
7439 - Clean up log entries that pointed to old URLs.
7442 Changes in version 0.1.1.7-alpha - 2005-09-14
7443 o Fixes on 0.1.1.6-alpha:
7444 - Exit servers were crashing when people asked them to make a
7445 connection to an address not in their exit policy.
7446 - Looking up a non-existent stream for a v1 control connection would
7448 - Fix a seg fault if we ask a dirserver for a descriptor by
7449 fingerprint but he doesn't know about him.
7450 - SETCONF was appending items to linelists, not clearing them.
7451 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
7452 out and refuse the setconf if it would fail.
7453 - Downgrade the dirserver log messages when whining about
7457 - Add Peter Palfrader's check-tor script to tor/contrib/
7458 It lets you easily check whether a given server (referenced by
7459 nickname) is reachable by you.
7460 - Numerous changes to move towards client-side v2 directories. Not
7464 - If the user gave tor an odd number of command-line arguments,
7465 we were silently ignoring the last one. Now we complain and fail.
7466 [This wins the oldest-bug prize -- this bug has been present since
7467 November 2002, as released in Tor 0.0.0.]
7468 - Do not use unaligned memory access on alpha, mips, or mipsel.
7469 It *works*, but is very slow, so we treat them as if it doesn't.
7470 - Retry directory requests if we fail to get an answer we like
7471 from a given dirserver (we were retrying before, but only if
7472 we fail to connect).
7473 - When writing the RecommendedVersions line, sort them first.
7474 - When the client asked for a rendezvous port that the hidden
7475 service didn't want to provide, we were sending an IP address
7476 back along with the end cell. Fortunately, it was zero. But stop
7478 - Correct "your server is reachable" log entries to indicate that
7479 it was self-testing that told us so.
7482 Changes in version 0.1.1.6-alpha - 2005-09-09
7483 o Fixes on 0.1.1.5-alpha:
7484 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
7485 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
7486 - Fix bug with tor_memmem finding a match at the end of the string.
7487 - Make unit tests run without segfaulting.
7488 - Resolve some solaris x86 compile warnings.
7489 - Handle duplicate lines in approved-routers files without warning.
7490 - Fix bug where as soon as a server refused any requests due to his
7491 exit policy (e.g. when we ask for localhost and he tells us that's
7492 127.0.0.1 and he won't do it), we decided he wasn't obeying his
7493 exit policy using him for any exits.
7494 - Only do openssl hardware accelerator stuff if openssl version is
7497 o New controller features/fixes:
7498 - Add a "RESETCONF" command so you can set config options like
7499 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7500 a config option in the torrc with no value, then it clears it
7501 entirely (rather than setting it to its default).
7502 - Add a "GETINFO config-file" to tell us where torrc is.
7503 - Avoid sending blank lines when GETINFO replies should be empty.
7504 - Add a QUIT command for the controller (for using it manually).
7505 - Fix a bug in SAVECONF that was adding default dirservers and
7506 other redundant entries to the torrc file.
7508 o Start on the new directory design:
7509 - Generate, publish, cache, serve new network-status format.
7510 - Publish individual descriptors (by fingerprint, by "all", and by
7512 - Publish client and server recommended versions separately.
7513 - Allow tor_gzip_uncompress() to handle multiple concatenated
7514 compressed strings. Serve compressed groups of router
7515 descriptors. The compression logic here could be more
7517 - Distinguish v1 authorities (all currently trusted directories)
7518 from v2 authorities (all trusted directories).
7519 - Change DirServers config line to note which dirs are v1 authorities.
7520 - Add configuration option "V1AuthoritativeDirectory 1" which
7521 moria1, moria2, and tor26 should set.
7522 - Remove option when getting directory cache to see whether they
7523 support running-routers; they all do now. Replace it with one
7524 to see whether caches support v2 stuff.
7527 - Dirservers now do their own external reachability testing of each
7528 Tor server, and only list them as running if they've been found to
7529 be reachable. We also send back warnings to the server's logs if
7530 it uploads a descriptor that we already believe is unreachable.
7531 - Implement exit enclaves: if we know an IP address for the
7532 destination, and there's a running Tor server at that address
7533 which allows exit to the destination, then extend the circuit to
7534 that exit first. This provides end-to-end encryption and end-to-end
7535 authentication. Also, if the user wants a .exit address or enclave,
7536 use 4 hops rather than 3, and cannibalize a general circ for it
7538 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
7539 controller. Also, rotate dns and cpu workers if the controller
7540 changes options that will affect them; and initialize the dns
7541 worker cache tree whether or not we start out as a server.
7542 - Only upload a new server descriptor when options change, 18
7543 hours have passed, uptime is reset, or bandwidth changes a lot.
7544 - Check [X-]Forwarded-For headers in HTTP requests when generating
7545 log messages. This lets people run dirservers (and caches) behind
7546 Apache but still know which IP addresses are causing warnings.
7548 o Config option changes:
7549 - Replace (Fascist)Firewall* config options with a new
7550 ReachableAddresses option that understands address policies.
7551 For example, "ReachableAddresses *:80,*:443"
7552 - Get rid of IgnoreVersion undocumented config option, and make us
7553 only warn, never exit, when we're running an obsolete version.
7554 - Make MonthlyAccountingStart config option truly obsolete now.
7557 - Reject ports 465 and 587 in the default exit policy, since
7558 people have started using them for spam too.
7559 - It turns out we couldn't bootstrap a network since we added
7560 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7561 has never gone down. Add an AssumeReachable config option to let
7562 servers and dirservers bootstrap. When we're trying to build a
7563 high-uptime or high-bandwidth circuit but there aren't enough
7564 suitable servers, try being less picky rather than simply failing.
7565 - Our logic to decide if the OR we connected to was the right guy
7566 was brittle and maybe open to a mitm for unverified routers.
7567 - We weren't cannibalizing circuits correctly for
7568 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7569 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7570 build those from scratch. This should make hidden services faster.
7571 - Predict required circuits better, with an eye toward making hidden
7572 services faster on the service end.
7573 - Retry streams if the exit node sends back a 'misc' failure. This
7574 should result in fewer random failures. Also, after failing
7575 from resolve failed or misc, reset the num failures, so we give
7576 it a fair shake next time we try.
7577 - Clean up the rendezvous warn log msgs, and downgrade some to info.
7578 - Reduce severity on logs about dns worker spawning and culling.
7579 - When we're shutting down and we do something like try to post a
7580 server descriptor or rendezvous descriptor, don't complain that
7581 we seem to be unreachable. Of course we are, we're shutting down.
7582 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7583 We don't use them yet, but maybe one day our DNS resolver will be
7584 able to discover them.
7585 - Make ContactInfo mandatory for authoritative directory servers.
7586 - Require server descriptors to list IPv4 addresses -- hostnames
7587 are no longer allowed. This also fixes some potential security
7588 problems with people providing hostnames as their address and then
7589 preferentially resolving them to partition users.
7590 - Change log line for unreachability to explicitly suggest /etc/hosts
7591 as the culprit. Also make it clearer what IP address and ports we're
7592 testing for reachability.
7593 - Put quotes around user-supplied strings when logging so users are
7594 more likely to realize if they add bad characters (like quotes)
7596 - Let auth dir servers start without specifying an Address config
7598 - Make unit tests (and other invocations that aren't the real Tor)
7599 run without launching listeners, creating subdirectories, and so on.
7602 Changes in version 0.1.1.5-alpha - 2005-08-08
7603 o Bugfixes included in 0.1.0.14.
7605 o Bugfixes on 0.1.0.x:
7606 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7607 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7608 it would silently using ignore the 6668.
7611 Changes in version 0.1.0.14 - 2005-08-08
7612 o Bugfixes on 0.1.0.x:
7613 - Fix the other half of the bug with crypto handshakes
7615 - Fix an assert trigger if you send a 'signal term' via the
7616 controller when it's listening for 'event info' messages.
7619 Changes in version 0.1.1.4-alpha - 2005-08-04
7620 o Bugfixes included in 0.1.0.13.
7623 - Improve tor_gettimeofday() granularity on windows.
7624 - Make clients regenerate their keys when their IP address changes.
7625 - Implement some more GETINFO goodness: expose helper nodes, config
7626 options, getinfo keys.
7629 Changes in version 0.1.0.13 - 2005-08-04
7630 o Bugfixes on 0.1.0.x:
7631 - Fix a critical bug in the security of our crypto handshakes.
7632 - Fix a size_t underflow in smartlist_join_strings2() that made
7633 it do bad things when you hand it an empty smartlist.
7634 - Fix Windows installer to ship Tor license (thanks to Aphex for
7635 pointing out this oversight) and put a link to the doc directory
7637 - Explicitly set no-unaligned-access for sparc: it turns out the
7638 new gcc's let you compile broken code, but that doesn't make it
7642 Changes in version 0.1.1.3-alpha - 2005-07-23
7643 o Bugfixes on 0.1.1.2-alpha:
7644 - Fix a bug in handling the controller's "post descriptor"
7646 - Fix several bugs in handling the controller's "extend circuit"
7648 - Fix a bug in handling the controller's "stream status" event.
7649 - Fix an assert failure if we have a controller listening for
7650 circuit events and we go offline.
7651 - Re-allow hidden service descriptors to publish 0 intro points.
7652 - Fix a crash when generating your hidden service descriptor if
7653 you don't have enough intro points already.
7655 o New features on 0.1.1.2-alpha:
7656 - New controller function "getinfo accounting", to ask how
7657 many bytes we've used in this time period.
7658 - Experimental support for helper nodes: a lot of the risk from
7659 a small static adversary comes because users pick new random
7660 nodes every time they rebuild a circuit. Now users will try to
7661 stick to the same small set of entry nodes if they can. Not
7662 enabled by default yet.
7664 o Bugfixes on 0.1.0.12:
7665 - If you're an auth dir server, always publish your dirport,
7666 even if you haven't yet found yourself to be reachable.
7667 - Fix a size_t underflow in smartlist_join_strings2() that made
7668 it do bad things when you hand it an empty smartlist.
7671 Changes in version 0.1.0.12 - 2005-07-18
7672 o New directory servers:
7673 - tor26 has changed IP address.
7675 o Bugfixes on 0.1.0.x:
7676 - Fix a possible double-free in tor_gzip_uncompress().
7677 - When --disable-threads is set, do not search for or link against
7679 - Don't trigger an assert if an authoritative directory server
7680 claims its dirport is 0.
7681 - Fix bug with removing Tor as an NT service: some people were
7682 getting "The service did not return an error." Thanks to Matt
7686 Changes in version 0.1.1.2-alpha - 2005-07-15
7687 o New directory servers:
7688 - tor26 has changed IP address.
7690 o Bugfixes on 0.1.0.x, crashes/leaks:
7691 - Port the servers-not-obeying-their-exit-policies fix from
7693 - Fix an fd leak in start_daemon().
7694 - On Windows, you can't always reopen a port right after you've
7695 closed it. So change retry_listeners() to only close and re-open
7696 ports that have changed.
7697 - Fix a possible double-free in tor_gzip_uncompress().
7699 o Bugfixes on 0.1.0.x, usability:
7700 - When tor_socketpair() fails in Windows, give a reasonable
7701 Windows-style errno back.
7702 - Let people type "tor --install" as well as "tor -install" when
7704 want to make it an NT service.
7705 - NT service patch from Matt Edman to improve error messages.
7706 - When the controller asks for a config option with an abbreviated
7707 name, give the full name in our response.
7708 - Correct the man page entry on TrackHostExitsExpire.
7709 - Looks like we were never delivering deflated (i.e. compressed)
7710 running-routers lists, even when asked. Oops.
7711 - When --disable-threads is set, do not search for or link against
7714 o Bugfixes on 0.1.1.x:
7715 - Fix a seg fault with autodetecting which controller version is
7719 - New hidden service descriptor format: put a version in it, and
7720 let people specify introduction/rendezvous points that aren't
7721 in "the directory" (which is subjective anyway).
7722 - Allow the DEBUG controller event to work again. Mark certain log
7723 entries as "don't tell this to controllers", so we avoid cycles.
7726 Changes in version 0.1.0.11 - 2005-06-30
7727 o Bugfixes on 0.1.0.x:
7728 - Fix major security bug: servers were disregarding their
7729 exit policies if clients behaved unexpectedly.
7730 - Make OS X init script check for missing argument, so we don't
7731 confuse users who invoke it incorrectly.
7732 - Fix a seg fault in "tor --hash-password foo".
7733 - The MAPADDRESS control command was broken.
7736 Changes in version 0.1.1.1-alpha - 2005-06-29
7738 - Make OS X init script check for missing argument, so we don't
7739 confuse users who invoke it incorrectly.
7740 - Fix a seg fault in "tor --hash-password foo".
7741 - Fix a possible way to DoS dirservers.
7742 - When we complain that your exit policy implicitly allows local or
7743 private address spaces, name them explicitly so operators can
7745 - Make the log message less scary when all the dirservers are
7746 temporarily unreachable.
7747 - We were printing the number of idle dns workers incorrectly when
7751 - Revised controller protocol (version 1) that uses ascii rather
7752 than binary. Add supporting libraries in python and java so you
7753 can use the controller from your applications without caring how
7755 - Spiffy new support for crypto hardware accelerators. Can somebody
7759 Changes in version 0.0.9.10 - 2005-06-16
7760 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
7761 - Refuse relay cells that claim to have a length larger than the
7762 maximum allowed. This prevents a potential attack that could read
7763 arbitrary memory (e.g. keys) from an exit server's process
7767 Changes in version 0.1.0.10 - 2005-06-14
7768 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
7769 libevent before 1.1a.
7772 Changes in version 0.1.0.9-rc - 2005-06-09
7774 - Reset buf->highwater every time buf_shrink() is called, not just on
7775 a successful shrink. This was causing significant memory bloat.
7776 - Fix buffer overflow when checking hashed passwords.
7777 - Security fix: if seeding the RNG on Win32 fails, quit.
7778 - Allow seeding the RNG on Win32 even when you're not running as
7780 - Disable threading on Solaris too. Something is wonky with it,
7781 cpuworkers, and reentrant libs.
7782 - Reenable the part of the code that tries to flush as soon as an
7783 OR outbuf has a full TLS record available. Perhaps this will make
7784 OR outbufs not grow as huge except in rare cases, thus saving lots
7785 of CPU time plus memory.
7786 - Reject malformed .onion addresses rather then passing them on as
7787 normal web requests.
7788 - Adapt patch from Adam Langley: fix possible memory leak in
7789 tor_lookup_hostname().
7790 - Initialize libevent later in the startup process, so the logs are
7791 already established by the time we start logging libevent warns.
7792 - Use correct errno on win32 if libevent fails.
7793 - Check and warn about known-bad/slow libevent versions.
7794 - Pay more attention to the ClientOnly config option.
7795 - Have torctl.in/tor.sh.in check for location of su binary (needed
7797 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
7798 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
7799 HttpProxyAuthenticator
7800 - Stop warning about sigpipes in the logs. We're going to
7801 pretend that getting these occassionally is normal and fine.
7802 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
7804 installer screens; and don't put stuff into StartupItems unless
7805 the user asks you to.
7806 - Require servers that use the default dirservers to have public IP
7807 addresses. We have too many servers that are configured with private
7808 IPs and their admins never notice the log entries complaining that
7809 their descriptors are being rejected.
7810 - Add OSX uninstall instructions. An actual uninstall script will
7814 Changes in version 0.1.0.8-rc - 2005-05-23
7816 - It turns out that kqueue on OS X 10.3.9 was causing kernel
7817 panics. Disable kqueue on all OS X Tors.
7818 - Fix RPM: remove duplicate line accidentally added to the rpm
7820 - Disable threads on openbsd too, since its gethostaddr is not
7822 - Tolerate libevent 0.8 since it still works, even though it's
7824 - Enable building on Red Hat 9.0 again.
7825 - Allow the middle hop of the testing circuit to be running any
7826 version, now that most of them have the bugfix to let them connect
7827 to unknown servers. This will allow reachability testing to work
7828 even when 0.0.9.7-0.0.9.9 become obsolete.
7829 - Handle relay cells with rh.length too large. This prevents
7830 a potential attack that could read arbitrary memory (maybe even
7831 keys) from the exit server's process.
7832 - We screwed up the dirport reachability testing when we don't yet
7833 have a cached version of the directory. Hopefully now fixed.
7834 - Clean up router_load_single_router() (used by the controller),
7835 so it doesn't seg fault on error.
7836 - Fix a minor memory leak when somebody establishes an introduction
7837 point at your Tor server.
7838 - If a socks connection ends because read fails, don't warn that
7839 you're not sending a socks reply back.
7842 - Add HttpProxyAuthenticator config option too, that works like
7843 the HttpsProxyAuthenticator config option.
7844 - Encode hashed controller passwords in hex instead of base64,
7845 to make it easier to write controllers.
7848 Changes in version 0.1.0.7-rc - 2005-05-17
7850 - Fix a bug in the OS X package installer that prevented it from
7851 installing on Tiger.
7852 - Fix a script bug in the OS X package installer that made it
7853 complain during installation.
7854 - Find libevent even if it's hiding in /usr/local/ and your
7855 CFLAGS and LDFLAGS don't tell you to look there.
7856 - Be able to link with libevent as a shared library (the default
7857 after 1.0d), even if it's hiding in /usr/local/lib and even
7858 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7859 assuming you're running gcc. Otherwise fail and give a useful
7861 - Fix a bug in the RPM packager: set home directory for _tor to
7862 something more reasonable when first installing.
7863 - Free a minor amount of memory that is still reachable on exit.
7866 Changes in version 0.1.0.6-rc - 2005-05-14
7868 - Implement --disable-threads configure option. Disable threads on
7869 netbsd by default, because it appears to have no reentrant resolver
7871 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
7872 release (1.1) detects and disables kqueue if it's broken.
7873 - Append default exit policy before checking for implicit internal
7874 addresses. Now we don't log a bunch of complaints on startup
7875 when using the default exit policy.
7876 - Some people were putting "Address " in their torrc, and they had
7877 a buggy resolver that resolved " " to 0.0.0.0. Oops.
7878 - If DataDir is ~/.tor, and that expands to /.tor, then default to
7879 LOCALSTATEDIR/tor instead.
7880 - Fix fragmented-message bug in TorControl.py.
7881 - Resolve a minor bug which would prevent unreachable dirports
7882 from getting suppressed in the published descriptor.
7883 - When the controller gave us a new descriptor, we weren't resolving
7884 it immediately, so Tor would think its address was 0.0.0.0 until
7885 we fetched a new directory.
7886 - Fix an uppercase/lowercase case error in suppressing a bogus
7887 libevent warning on some Linuxes.
7890 - Begin scrubbing sensitive strings from logs by default. Turn off
7891 the config option SafeLogging if you need to do debugging.
7892 - Switch to a new buffer management algorithm, which tries to avoid
7893 reallocing and copying quite as much. In first tests it looks like
7894 it uses *more* memory on average, but less cpu.
7895 - First cut at support for "create-fast" cells. Clients can use
7896 these when extending to their first hop, since the TLS already
7897 provides forward secrecy and authentication. Not enabled on
7899 - When dirservers refuse a router descriptor, we now log its
7900 contactinfo, platform, and the poster's IP address.
7901 - Call tor_free_all instead of connections_free_all after forking, to
7902 save memory on systems that need to fork.
7903 - Whine at you if you're a server and you don't set your contactinfo.
7904 - Implement --verify-config command-line option to check if your torrc
7905 is valid without actually launching Tor.
7906 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
7907 rather than just rejecting it.
7910 Changes in version 0.1.0.5-rc - 2005-04-27
7912 - Stop trying to print a null pointer if an OR conn fails because
7913 we didn't like its cert.
7915 - Switch our internal buffers implementation to use a ring buffer,
7916 to hopefully improve performance for fast servers a lot.
7917 - Add HttpsProxyAuthenticator support (basic auth only), based
7918 on patch from Adam Langley.
7919 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7920 the fast servers that have been joining lately.
7921 - Give hidden service accesses extra time on the first attempt,
7922 since 60 seconds is often only barely enough. This might improve
7924 - Improve performance for dirservers: stop re-parsing the whole
7925 directory every time you regenerate it.
7926 - Add more debugging info to help us find the weird dns freebsd
7927 pthreads bug; cleaner debug messages to help track future issues.
7930 Changes in version 0.0.9.9 - 2005-04-23
7931 o Bugfixes on 0.0.9.x:
7932 - If unofficial Tor clients connect and send weird TLS certs, our
7933 Tor server triggers an assert. This release contains a minimal
7934 backport from the broader fix that we put into 0.1.0.4-rc.
7937 Changes in version 0.1.0.4-rc - 2005-04-23
7939 - If unofficial Tor clients connect and send weird TLS certs, our
7940 Tor server triggers an assert. Stop asserting, and start handling
7941 TLS errors better in other situations too.
7942 - When the controller asks us to tell it about all the debug-level
7943 logs, it turns out we were generating debug-level logs while
7944 telling it about them, which turns into a bad loop. Now keep
7945 track of whether you're sending a debug log to the controller,
7946 and don't log when you are.
7947 - Fix the "postdescriptor" feature of the controller interface: on
7948 non-complete success, only say "done" once.
7950 - Clients are now willing to load balance over up to 2mB, not 1mB,
7951 of advertised bandwidth capacity.
7952 - Add a NoPublish config option, so you can be a server (e.g. for
7953 testing running Tor servers in other Tor networks) without
7954 publishing your descriptor to the primary dirservers.
7957 Changes in version 0.1.0.3-rc - 2005-04-08
7958 o Improvements on 0.1.0.2-rc:
7959 - Client now retries when streams end early for 'hibernating' or
7960 'resource limit' reasons, rather than failing them.
7961 - More automated handling for dirserver operators:
7962 - Automatically approve nodes running 0.1.0.2-rc or later,
7963 now that the the reachability detection stuff is working.
7964 - Now we allow two unverified servers with the same nickname
7965 but different keys. But if a nickname is verified, only that
7966 nickname+key are allowed.
7967 - If you're an authdirserver connecting to an address:port,
7968 and it's not the OR you were expecting, forget about that
7969 descriptor. If he *was* the one you were expecting, then forget
7970 about all other descriptors for that address:port.
7971 - Allow servers to publish descriptors from 12 hours in the future.
7972 Corollary: only whine about clock skew from the dirserver if
7973 he's a trusted dirserver (since now even verified servers could
7974 have quite wrong clocks).
7975 - Adjust maximum skew and age for rendezvous descriptors: let skew
7976 be 48 hours rather than 90 minutes.
7977 - Efficiency improvements:
7978 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7979 it much faster to look up a circuit for each relay cell.
7980 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7981 since they're eating our cpu on exit nodes.
7982 - Stop wasting time doing a case insensitive comparison for every
7983 dns name every time we do any lookup. Canonicalize the names to
7984 lowercase and be done with it.
7985 - Start sending 'truncated' cells back rather than destroy cells,
7986 if the circuit closes in front of you. This means we won't have
7987 to abandon partially built circuits.
7988 - Only warn once per nickname from add_nickname_list_to_smartlist
7989 per failure, so an entrynode or exitnode choice that's down won't
7991 - Put a note in the torrc about abuse potential with the default
7993 - Revise control spec and implementation to allow all log messages to
7994 be sent to controller with their severities intact (suggested by
7995 Matt Edman). Update TorControl to handle new log event types.
7996 - Provide better explanation messages when controller's POSTDESCRIPTOR
7998 - Stop putting nodename in the Platform string in server descriptors.
7999 It doesn't actually help, and it is confusing/upsetting some people.
8001 o Bugfixes on 0.1.0.2-rc:
8002 - We were printing the host mask wrong in exit policies in server
8003 descriptors. This isn't a critical bug though, since we were still
8004 obeying the exit policy internally.
8005 - Fix Tor when compiled with libevent but without pthreads: move
8006 connection_unregister() from _connection_free() to
8008 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
8009 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
8010 when we look through the connection array, we'll find any of the
8011 cpu/dnsworkers. This is no good.
8013 o Bugfixes on 0.0.9.8:
8014 - Fix possible bug on threading platforms (e.g. win32) which was
8015 leaking a file descriptor whenever a cpuworker or dnsworker died.
8016 - When using preferred entry or exit nodes, ignore whether the
8017 circuit wants uptime or capacity. They asked for the nodes, they
8019 - chdir() to your datadirectory at the *end* of the daemonize process,
8020 not the beginning. This was a problem because the first time you
8021 run tor, if your datadir isn't there, and you have runasdaemon set
8022 to 1, it will try to chdir to it before it tries to create it. Oops.
8023 - Handle changed router status correctly when dirserver reloads
8024 fingerprint file. We used to be dropping all unverified descriptors
8025 right then. The bug was hidden because we would immediately
8026 fetch a directory from another dirserver, which would include the
8027 descriptors we just dropped.
8028 - When we're connecting to an OR and he's got a different nickname/key
8029 than we were expecting, only complain loudly if we're an OP or a
8030 dirserver. Complaining loudly to the OR admins just confuses them.
8031 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
8032 artificially capped at 500kB.
8035 Changes in version 0.0.9.8 - 2005-04-07
8036 o Bugfixes on 0.0.9.x:
8037 - We have a bug that I haven't found yet. Sometimes, very rarely,
8038 cpuworkers get stuck in the 'busy' state, even though the cpuworker
8039 thinks of itself as idle. This meant that no new circuits ever got
8040 established. Here's a workaround to kill any cpuworker that's been
8041 busy for more than 100 seconds.
8044 Changes in version 0.1.0.2-rc - 2005-04-01
8045 o Bugfixes on 0.1.0.1-rc:
8046 - Fixes on reachability detection:
8047 - Don't check for reachability while hibernating.
8048 - If ORPort is reachable but DirPort isn't, still publish the
8049 descriptor, but zero out DirPort until it's found reachable.
8050 - When building testing circs for ORPort testing, use only
8051 high-bandwidth nodes, so fewer circuits fail.
8052 - Complain about unreachable ORPort separately from unreachable
8053 DirPort, so the user knows what's going on.
8054 - Make sure we only conclude ORPort reachability if we didn't
8055 initiate the conn. Otherwise we could falsely conclude that
8056 we're reachable just because we connected to the guy earlier
8057 and he used that same pipe to extend to us.
8058 - Authdirservers shouldn't do ORPort reachability detection,
8059 since they're in clique mode, so it will be rare to find a
8060 server not already connected to them.
8061 - When building testing circuits, always pick middle hops running
8062 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
8063 bug. (This is a kludge; it will go away when 0.0.9.x becomes
8065 - When we decide we're reachable, actually publish our descriptor
8067 - Fix bug in redirectstream in the controller.
8068 - Fix the state descriptor strings so logs don't claim edge streams
8069 are in a different state than they actually are.
8070 - Use recent libevent features when possible (this only really affects
8071 win32 and osx right now, because the new libevent with these
8072 features hasn't been released yet). Add code to suppress spurious
8074 - Prevent possible segfault in connection_close_unattached_ap().
8075 - Fix newlines on torrc in win32.
8076 - Improve error msgs when tor-resolve fails.
8078 o Improvements on 0.0.9.x:
8079 - New experimental script tor/contrib/ExerciseServer.py (needs more
8080 work) that uses the controller interface to build circuits and
8081 fetch pages over them. This will help us bootstrap servers that
8082 have lots of capacity but haven't noticed it yet.
8083 - New experimental script tor/contrib/PathDemo.py (needs more work)
8084 that uses the controller interface to let you choose whole paths
8086 "<hostname>.<path,separated by dots>.<length of path>.path"
8087 - When we've connected to an OR and handshaked but didn't like
8088 the result, we were closing the conn without sending destroy
8089 cells back for pending circuits. Now send those destroys.
8092 Changes in version 0.0.9.7 - 2005-04-01
8093 o Bugfixes on 0.0.9.x:
8094 - Fix another race crash bug (thanks to Glenn Fink for reporting).
8095 - Compare identity to identity, not to nickname, when extending to
8096 a router not already in the directory. This was preventing us from
8097 extending to unknown routers. Oops.
8098 - Make sure to create OS X Tor user in <500 range, so we aren't
8099 creating actual system users.
8100 - Note where connection-that-hasn't-sent-end was marked, and fix
8101 a few really loud instances of this harmless bug (it's fixed more
8105 Changes in version 0.1.0.1-rc - 2005-03-28
8107 - Add reachability testing. Your Tor server will automatically try
8108 to see if its ORPort and DirPort are reachable from the outside,
8109 and it won't upload its descriptor until it decides they are.
8110 - Handle unavailable hidden services better. Handle slow or busy
8111 hidden services better.
8112 - Add support for CONNECTing through https proxies, with "HttpsProxy"
8114 - New exit policy: accept most low-numbered ports, rather than
8115 rejecting most low-numbered ports.
8116 - More Tor controller support (still experimental). See
8117 http://tor.eff.org/doc/control-spec.txt for all the new features,
8118 including signals to emulate unix signals from any platform;
8119 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
8120 closestream; closecircuit; etc.
8121 - Make nt services work and start on startup on win32 (based on
8122 patch by Matt Edman).
8123 - Add a new AddressMap config directive to rewrite incoming socks
8124 addresses. This lets you, for example, declare an implicit
8125 required exit node for certain sites.
8126 - Add a new TrackHostExits config directive to trigger addressmaps
8127 for certain incoming socks addresses -- for sites that break when
8128 your exit keeps changing (based on patch by Mike Perry).
8129 - Redo the client-side dns cache so it's just an addressmap too.
8130 - Notice when our IP changes, and reset stats/uptime/reachability.
8131 - When an application is using socks5, give him the whole variety of
8132 potential socks5 responses (connect refused, host unreachable, etc),
8133 rather than just "success" or "failure".
8134 - A more sane version numbering system. See
8135 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
8136 - New contributed script "exitlist": a simple python script to
8137 parse directories and find Tor nodes that exit to listed
8139 - New contributed script "privoxy-tor-toggle" to toggle whether
8140 Privoxy uses Tor. Seems to be configured for Debian by default.
8141 - Report HTTP reasons to client when getting a response from directory
8142 servers -- so you can actually know what went wrong.
8143 - New config option MaxAdvertisedBandwidth which lets you advertise
8144 a low bandwidthrate (to not attract as many circuits) while still
8145 allowing a higher bandwidthrate in reality.
8147 o Robustness/stability fixes:
8148 - Make Tor use Niels Provos's libevent instead of its current
8149 poll-but-sometimes-select mess. This will let us use faster async
8150 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
8152 - pthread support now too. This was forced because when we forked,
8153 we ended up wasting a lot of duplicate ram over time. Also switch
8154 to foo_r versions of some library calls to allow reentry and
8156 - Better handling for heterogeneous / unreliable nodes:
8157 - Annotate circuits w/ whether they aim to contain high uptime nodes
8158 and/or high capacity nodes. When building circuits, choose
8160 - This means that every single node in an intro rend circuit,
8161 not just the last one, will have a minimum uptime.
8162 - New config option LongLivedPorts to indicate application streams
8163 that will want high uptime circuits.
8164 - Servers reset uptime when a dir fetch entirely fails. This
8165 hopefully reflects stability of the server's network connectivity.
8166 - If somebody starts his tor server in Jan 2004 and then fixes his
8167 clock, don't make his published uptime be a year.
8168 - Reset published uptime when you wake up from hibernation.
8169 - Introduce a notion of 'internal' circs, which are chosen without
8170 regard to the exit policy of the last hop. Intro and rendezvous
8171 circs must be internal circs, to avoid leaking information. Resolve
8172 and connect streams can use internal circs if they want.
8173 - New circuit pooling algorithm: make sure to have enough circs around
8174 to satisfy any predicted ports, and also make sure to have 2 internal
8175 circs around if we've required internal circs lately (and with high
8176 uptime if we've seen that lately too).
8177 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
8178 which describes how often we retry making new circuits if current
8179 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
8180 how long we're willing to make use of an already-dirty circuit.
8181 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
8182 circ as necessary, if there are any completed ones lying around
8183 when we try to launch one.
8184 - Make hidden services try to establish a rendezvous for 30 seconds,
8185 rather than for n (where n=3) attempts to build a circuit.
8186 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
8187 "ShutdownWaitLength".
8188 - Try to be more zealous about calling connection_edge_end when
8189 things go bad with edge conns in connection.c.
8190 - Revise tor-spec to add more/better stream end reasons.
8191 - Revise all calls to connection_edge_end to avoid sending "misc",
8192 and to take errno into account where possible.
8195 - Fix a race condition that can trigger an assert, when we have a
8196 pending create cell and an OR connection fails right then.
8197 - Fix several double-mark-for-close bugs, e.g. where we were finding
8198 a conn for a cell even if that conn is already marked for close.
8199 - Make sequence of log messages when starting on win32 with no config
8200 file more reasonable.
8201 - When choosing an exit node for a new non-internal circ, don't take
8202 into account whether it'll be useful for any pending x.onion
8203 addresses -- it won't.
8204 - Turn addr_policy_compare from a tristate to a quadstate; this should
8205 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
8206 for google.com" problem.
8207 - Make "platform" string in descriptor more accurate for Win32 servers,
8208 so it's not just "unknown platform".
8209 - Fix an edge case in parsing config options (thanks weasel).
8210 If they say "--" on the commandline, it's not an option.
8211 - Reject odd-looking addresses at the client (e.g. addresses that
8212 contain a colon), rather than having the server drop them because
8214 - tor-resolve requests were ignoring .exit if there was a working circuit
8215 they could use instead.
8216 - REUSEADDR on normal platforms means you can rebind to the port
8217 right after somebody else has let it go. But REUSEADDR on win32
8218 means to let you bind to the port _even when somebody else
8219 already has it bound_! So, don't do that on Win32.
8220 - Change version parsing logic: a version is "obsolete" if it is not
8221 recommended and (1) there is a newer recommended version in the
8222 same series, or (2) there are no recommended versions in the same
8223 series, but there are some recommended versions in a newer series.
8224 A version is "new" if it is newer than any recommended version in
8226 - Stop most cases of hanging up on a socks connection without sending
8230 - Require BandwidthRate to be at least 20kB/s for servers.
8231 - When a dirserver causes you to give a warn, mention which dirserver
8233 - New config option DirAllowPrivateAddresses for authdirservers.
8234 Now by default they refuse router descriptors that have non-IP or
8235 private-IP addresses.
8236 - Stop publishing socksport in the directory, since it's not
8237 actually meant to be public. For compatibility, publish a 0 there
8239 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
8240 smart" value, that is low for servers and high for clients.
8241 - If our clock jumps forward by 100 seconds or more, assume something
8242 has gone wrong with our network and abandon all not-yet-used circs.
8243 - Warn when exit policy implicitly allows local addresses.
8244 - If we get an incredibly skewed timestamp from a dirserver mirror
8245 that isn't a verified OR, don't warn -- it's probably him that's
8247 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
8248 cookies to disk and doesn't log each web request to disk. (Thanks
8249 to Brett Carrington for pointing this out.)
8250 - When a client asks us for a dir mirror and we don't have one,
8251 launch an attempt to get a fresh one.
8252 - If we're hibernating and we get a SIGINT, exit immediately.
8253 - Add --with-dmalloc ./configure option, to track memory leaks.
8254 - And try to free all memory on closing, so we can detect what
8256 - Cache local dns resolves correctly even when they're .exit
8258 - Give a better warning when some other server advertises an
8259 ORPort that is actually an apache running ssl.
8260 - Add "opt hibernating 1" to server descriptor to make it clearer
8261 whether the server is hibernating.
8264 Changes in version 0.0.9.6 - 2005-03-24
8265 o Bugfixes on 0.0.9.x (crashes and asserts):
8266 - Add new end stream reasons to maintainance branch. Fix bug where
8267 reason (8) could trigger an assert. Prevent bug from recurring.
8268 - Apparently win32 stat wants paths to not end with a slash.
8269 - Fix assert triggers in assert_cpath_layer_ok(), where we were
8270 blowing away the circuit that conn->cpath_layer points to, then
8271 checking to see if the circ is well-formed. Backport check to make
8272 sure we dont use the cpath on a closed connection.
8273 - Prevent circuit_resume_edge_reading_helper() from trying to package
8274 inbufs for marked-for-close streams.
8275 - Don't crash on hup if your options->address has become unresolvable.
8276 - Some systems (like OS X) sometimes accept() a connection and tell
8277 you the remote host is 0.0.0.0:0. If this happens, due to some
8278 other mis-features, we get confused; so refuse the conn for now.
8280 o Bugfixes on 0.0.9.x (other):
8281 - Fix harmless but scary "Unrecognized content encoding" warn message.
8282 - Add new stream error reason: TORPROTOCOL reason means "you are not
8283 speaking a version of Tor I understand; say bye-bye to your stream."
8284 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
8285 into the future, now that we are more tolerant of skew. This
8286 resolves a bug where a Tor server would refuse to cache a directory
8287 because all the directories it gets are too far in the future;
8288 yet the Tor server never logs any complaints about clock skew.
8289 - Mac packaging magic: make man pages useable, and do not overwrite
8290 existing torrc files.
8291 - Make OS X log happily to /var/log/tor/tor.log
8294 Changes in version 0.0.9.5 - 2005-02-22
8295 o Bugfixes on 0.0.9.x:
8296 - Fix an assert race at exit nodes when resolve requests fail.
8297 - Stop picking unverified dir mirrors--it only leads to misery.
8298 - Patch from Matt Edman to make NT services work better. Service
8299 support is still not compiled into the executable by default.
8300 - Patch from Dmitri Bely so the Tor service runs better under
8301 the win32 SYSTEM account.
8302 - Make tor-resolve actually work (?) on Win32.
8303 - Fix a sign bug when getrlimit claims to have 4+ billion
8304 file descriptors available.
8305 - Stop refusing to start when bandwidthburst == bandwidthrate.
8306 - When create cells have been on the onion queue more than five
8307 seconds, just send back a destroy and take them off the list.
8310 Changes in version 0.0.9.4 - 2005-02-03
8311 o Bugfixes on 0.0.9:
8312 - Fix an assert bug that took down most of our servers: when
8313 a server claims to have 1 GB of bandwidthburst, don't
8315 - Don't crash as badly if we have spawned the max allowed number
8316 of dnsworkers, or we're out of file descriptors.
8317 - Block more file-sharing ports in the default exit policy.
8318 - MaxConn is now automatically set to the hard limit of max
8319 file descriptors we're allowed (ulimit -n), minus a few for
8321 - Give a clearer message when servers need to raise their
8322 ulimit -n when they start running out of file descriptors.
8323 - SGI Compatibility patches from Jan Schaumann.
8324 - Tolerate a corrupt cached directory better.
8325 - When a dirserver hasn't approved your server, list which one.
8326 - Go into soft hibernation after 95% of the bandwidth is used,
8327 not 99%. This is especially important for daily hibernators who
8328 have a small accounting max. Hopefully it will result in fewer
8329 cut connections when the hard hibernation starts.
8330 - Load-balance better when using servers that claim more than
8331 800kB/s of capacity.
8332 - Make NT services work (experimental, only used if compiled in).
8335 Changes in version 0.0.9.3 - 2005-01-21
8336 o Bugfixes on 0.0.9:
8337 - Backport the cpu use fixes from main branch, so busy servers won't
8338 need as much processor time.
8339 - Work better when we go offline and then come back, or when we
8340 run Tor at boot before the network is up. We do this by
8341 optimistically trying to fetch a new directory whenever an
8342 application request comes in and we think we're offline -- the
8343 human is hopefully a good measure of when the network is back.
8344 - Backport some minimal hidserv bugfixes: keep rend circuits open as
8345 long as you keep using them; actually publish hidserv descriptors
8346 shortly after they change, rather than waiting 20-40 minutes.
8347 - Enable Mac startup script by default.
8348 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
8349 - When you update AllowUnverifiedNodes or FirewallPorts via the
8350 controller's setconf feature, we were always appending, never
8352 - When you update HiddenServiceDir via setconf, it was screwing up
8353 the order of reading the lines, making it fail.
8354 - Do not rewrite a cached directory back to the cache; otherwise we
8355 will think it is recent and not fetch a newer one on startup.
8356 - Workaround for webservers that lie about Content-Encoding: Tor
8357 now tries to autodetect compressed directories and compression
8358 itself. This lets us Proxypass dir fetches through apache.
8361 Changes in version 0.0.9.2 - 2005-01-04
8362 o Bugfixes on 0.0.9 (crashes and asserts):
8363 - Fix an assert on startup when the disk is full and you're logging
8365 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
8366 style address, then we'd crash.
8367 - Fix an assert trigger when the running-routers string we get from
8368 a dirserver is broken.
8369 - Make worker threads start and run on win32. Now win32 servers
8371 - Bandaid (not actually fix, but now it doesn't crash) an assert
8372 where the dns worker dies mysteriously and the main Tor process
8373 doesn't remember anything about the address it was resolving.
8375 o Bugfixes on 0.0.9 (Win32):
8376 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
8377 name out of the warning/assert messages.
8378 - Fix a superficial "unhandled error on read" bug on win32.
8379 - The win32 installer no longer requires a click-through for our
8380 license, since our Free Software license grants rights but does not
8382 - Win32: When connecting to a dirserver fails, try another one
8383 immediately. (This was already working for non-win32 Tors.)
8384 - Stop trying to parse $HOME on win32 when hunting for default
8386 - Make tor-resolve.c work on win32 by calling network_init().
8388 o Bugfixes on 0.0.9 (other):
8389 - Make 0.0.9.x build on Solaris again.
8390 - Due to a fencepost error, we were blowing away the \n when reporting
8391 confvalue items in the controller. So asking for multiple config
8392 values at once couldn't work.
8393 - When listing circuits that are pending on an opening OR connection,
8394 if we're an OR we were listing circuits that *end* at us as
8395 being pending on every listener, dns/cpu worker, etc. Stop that.
8396 - Dirservers were failing to create 'running-routers' or 'directory'
8397 strings if we had more than some threshold of routers. Fix them so
8398 they can handle any number of routers.
8399 - Fix a superficial "Duplicate mark for close" bug.
8400 - Stop checking for clock skew for OR connections, even for servers.
8401 - Fix a fencepost error that was chopping off the last letter of any
8402 nickname that is the maximum allowed nickname length.
8403 - Update URLs in log messages so they point to the new website.
8404 - Fix a potential problem in mangling server private keys while
8405 writing to disk (not triggered yet, as far as we know).
8406 - Include the licenses for other free software we include in Tor,
8407 now that we're shipping binary distributions more regularly.
8410 Changes in version 0.0.9.1 - 2004-12-15
8411 o Bugfixes on 0.0.9:
8412 - Make hibernation actually work.
8413 - Make HashedControlPassword config option work.
8414 - When we're reporting event circuit status to a controller,
8415 don't use the stream status code.
8418 Changes in version 0.0.9 - 2004-12-12
8420 - Clean up manpage and torrc.sample file.
8421 - Clean up severities and text of log warnings.
8423 - Make servers trigger an assert when they enter hibernation.
8426 Changes in version 0.0.9rc7 - 2004-12-08
8427 o Bugfixes on 0.0.9rc:
8428 - Fix a stack-trashing crash when an exit node begins hibernating.
8429 - Avoid looking at unallocated memory while considering which
8430 ports we need to build circuits to cover.
8431 - Stop a sigpipe: when an 'end' cell races with eof from the app,
8432 we shouldn't hold-open-until-flush if the eof arrived first.
8433 - Fix a bug with init_cookie_authentication() in the controller.
8434 - When recommending new-format log lines, if the upper bound is
8435 LOG_ERR, leave it implicit.
8437 o Bugfixes on 0.0.8.1:
8438 - Fix a whole slew of memory leaks.
8439 - Fix isspace() and friends so they still make Solaris happy
8440 but also so they don't trigger asserts on win32.
8441 - Fix parse_iso_time on platforms without strptime (eg win32).
8442 - win32: tolerate extra "readable" events better.
8443 - win32: when being multithreaded, leave parent fdarray open.
8444 - Make unit tests work on win32.
8447 Changes in version 0.0.9rc6 - 2004-12-06
8448 o Bugfixes on 0.0.9pre:
8449 - Clean up some more integer underflow opportunities (not exploitable
8451 - While hibernating, hup should not regrow our listeners.
8452 - Send an end to the streams we close when we hibernate, rather
8453 than just chopping them off.
8454 - React to eof immediately on non-open edge connections.
8456 o Bugfixes on 0.0.8.1:
8457 - Calculate timeout for waiting for a connected cell from the time
8458 we sent the begin cell, not from the time the stream started. If
8459 it took a long time to establish the circuit, we would time out
8460 right after sending the begin cell.
8461 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8462 of * as always matching, so we were picking reject *:* nodes as
8463 exit nodes too. Oops.
8466 - New circuit building strategy: keep a list of ports that we've
8467 used in the past 6 hours, and always try to have 2 circuits open
8468 or on the way that will handle each such port. Seed us with port
8469 80 so web users won't complain that Tor is "slow to start up".
8470 - Make kill -USR1 dump more useful stats about circuits.
8471 - When warning about retrying or giving up, print the address, so
8472 the user knows which one it's talking about.
8473 - If you haven't used a clean circuit in an hour, throw it away,
8474 just to be on the safe side. (This means after 6 hours a totally
8475 unused Tor client will have no circuits open.)
8478 Changes in version 0.0.9rc5 - 2004-12-01
8479 o Bugfixes on 0.0.8.1:
8480 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8481 - Let resolve conns retry/expire also, rather than sticking around
8483 - If we are using select, make sure we stay within FD_SETSIZE.
8485 o Bugfixes on 0.0.9pre:
8486 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
8487 but doesn't seem to be currently; thanks to Ilja van Sprundel for
8489 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
8490 instead. Impose minima and maxima for all *Period options; impose
8491 even tighter maxima for fetching if we are a caching dirserver.
8492 Clip rather than rejecting.
8493 - Fetch cached running-routers from servers that serve it (that is,
8494 authdirservers and servers running 0.0.9rc5-cvs or later.)
8497 - Accept *:706 (silc) in default exit policy.
8498 - Implement new versioning format for post 0.1.
8499 - Support "foo.nickname.exit" addresses, to let Alice request the
8500 address "foo" as viewed by exit node "nickname". Based on a patch
8502 - Make tor --version --version dump the cvs Id of every file.
8505 Changes in version 0.0.9rc4 - 2004-11-28
8506 o Bugfixes on 0.0.8.1:
8507 - Make windows sockets actually non-blocking (oops), and handle
8508 win32 socket errors better.
8510 o Bugfixes on 0.0.9rc1:
8511 - Actually catch the -USR2 signal.
8514 Changes in version 0.0.9rc3 - 2004-11-25
8515 o Bugfixes on 0.0.8.1:
8516 - Flush the log file descriptor after we print "Tor opening log file",
8517 so we don't see those messages days later.
8519 o Bugfixes on 0.0.9rc1:
8520 - Make tor-resolve work again.
8521 - Avoid infinite loop in tor-resolve if tor hangs up on it.
8522 - Fix an assert trigger for clients/servers handling resolves.
8525 Changes in version 0.0.9rc2 - 2004-11-24
8526 o Bugfixes on 0.0.9rc1:
8527 - I broke socks5 support while fixing the eof bug.
8528 - Allow unitless bandwidths and intervals; they default to bytes
8530 - New servers don't start out hibernating; they are active until
8531 they run out of bytes, so they have a better estimate of how
8532 long it takes, and so their operators can know they're working.
8535 Changes in version 0.0.9rc1 - 2004-11-23
8536 o Bugfixes on 0.0.8.1:
8537 - Finally fix a bug that's been plaguing us for a year:
8538 With high load, circuit package window was reaching 0. Whenever
8539 we got a circuit-level sendme, we were reading a lot on each
8540 socket, but only writing out a bit. So we would eventually reach
8541 eof. This would be noticed and acted on even when there were still
8542 bytes sitting in the inbuf.
8543 - When poll() is interrupted, we shouldn't believe the revents values.
8545 o Bugfixes on 0.0.9pre6:
8546 - Fix hibernate bug that caused pre6 to be broken.
8547 - Don't keep rephist info for routers that haven't had activity for
8548 24 hours. (This matters now that clients have keys, since we track
8550 - Never call close_temp_logs while validating log options.
8551 - Fix backslash-escaping on tor.sh.in and torctl.in.
8554 - Implement weekly/monthly/daily accounting: now you specify your
8555 hibernation properties by
8556 AccountingMax N bytes|KB|MB|GB|TB
8557 AccountingStart day|week|month [day] HH:MM
8558 Defaults to "month 1 0:00".
8559 - Let bandwidth and interval config options be specified as 5 bytes,
8560 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8561 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8562 get back to normal.)
8563 - If your requested entry or exit node has advertised bandwidth 0,
8565 - Be more greedy about filling up relay cells -- we try reading again
8566 once we've processed the stuff we read, in case enough has arrived
8567 to fill the last cell completely.
8568 - Apply NT service patch from Osamu Fujino. Still needs more work.
8571 Changes in version 0.0.9pre6 - 2004-11-15
8572 o Bugfixes on 0.0.8.1:
8573 - Fix assert failure on malformed socks4a requests.
8574 - Use identity comparison, not nickname comparison, to choose which
8575 half of circuit-ID-space each side gets to use. This is needed
8576 because sometimes we think of a router as a nickname, and sometimes
8577 as a hex ID, and we can't predict what the other side will do.
8578 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8579 write() call will fail and we handle it there.
8580 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8581 and smartlist_len, which are two major profiling offenders.
8583 o Bugfixes on 0.0.9pre5:
8584 - Fix a bug in read_all that was corrupting config files on windows.
8585 - When we're raising the max number of open file descriptors to
8586 'unlimited', don't log that we just raised it to '-1'.
8587 - Include event code with events, as required by control-spec.txt.
8588 - Don't give a fingerprint when clients do --list-fingerprint:
8589 it's misleading, because it will never be the same again.
8590 - Stop using strlcpy in tor_strndup, since it was slowing us
8592 - Remove warn on startup about missing cached-directory file.
8593 - Make kill -USR1 work again.
8594 - Hibernate if we start tor during the "wait for wakeup-time" phase
8595 of an accounting interval. Log our hibernation plans better.
8596 - Authoritative dirservers now also cache their directory, so they
8597 have it on start-up.
8600 - Fetch running-routers; cache running-routers; compress
8601 running-routers; serve compressed running-routers.z
8602 - Add NSI installer script contributed by J Doe.
8603 - Commit VC6 and VC7 workspace/project files.
8604 - Commit a tor.spec for making RPM files, with help from jbash.
8605 - Add contrib/torctl.in contributed by Glenn Fink.
8606 - Implement the control-spec's SAVECONF command, to write your
8607 configuration to torrc.
8608 - Get cookie authentication for the controller closer to working.
8609 - Include control-spec.txt in the tarball.
8610 - When set_conf changes our server descriptor, upload a new copy.
8611 But don't upload it too often if there are frequent changes.
8612 - Document authentication config in man page, and document signals
8614 - Clean up confusing parts of man page and torrc.sample.
8615 - Make expand_filename handle ~ and ~username.
8616 - Use autoconf to enable largefile support where necessary. Use
8617 ftello where available, since ftell can fail at 2GB.
8618 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8619 log more informatively.
8620 - Give a slightly more useful output for "tor -h".
8621 - Refuse application socks connections to port 0.
8622 - Check clock skew for verified servers, but allow unverified
8623 servers and clients to have any clock skew.
8624 - Break DirFetchPostPeriod into:
8625 - DirFetchPeriod for fetching full directory,
8626 - StatusFetchPeriod for fetching running-routers,
8627 - DirPostPeriod for posting server descriptor,
8628 - RendPostPeriod for posting hidden service descriptors.
8629 - Make sure the hidden service descriptors are at a random offset
8630 from each other, to hinder linkability.
8633 Changes in version 0.0.9pre5 - 2004-11-09
8634 o Bugfixes on 0.0.9pre4:
8635 - Fix a seg fault in unit tests (doesn't affect main program).
8636 - Fix an assert bug where a hidden service provider would fail if
8637 the first hop of his rendezvous circuit was down.
8638 - Hidden service operators now correctly handle version 1 style
8639 INTRODUCE1 cells (nobody generates them still, so not a critical
8641 - If do_hup fails, actually notice.
8642 - Handle more errnos from accept() without closing the listener.
8643 Some OpenBSD machines were closing their listeners because
8644 they ran out of file descriptors.
8645 - Send resolve cells to exit routers that are running a new
8646 enough version of the resolve code to work right.
8647 - Better handling of winsock includes on non-MSV win32 compilers.
8648 - Some people had wrapped their tor client/server in a script
8649 that would restart it whenever it died. This did not play well
8650 with our "shut down if your version is obsolete" code. Now people
8651 don't fetch a new directory if their local cached version is
8653 - Make our autogen.sh work on ksh as well as bash.
8656 - Hibernation: New config option "AccountingMaxKB" lets you
8657 set how many KBytes per month you want to allow your server to
8658 consume. Rather than spreading those bytes out evenly over the
8659 month, we instead hibernate for some of the month and pop up
8660 at a deterministic time, work until the bytes are consumed, then
8661 hibernate again. Config option "MonthlyAccountingStart" lets you
8662 specify which day of the month your billing cycle starts on.
8663 - Control interface: a separate program can now talk to your
8664 client/server over a socket, and get/set config options, receive
8665 notifications of circuits and streams starting/finishing/dying,
8666 bandwidth used, etc. The next step is to get some GUIs working.
8667 Let us know if you want to help out. See doc/control-spec.txt .
8668 - Ship a contrib/tor-control.py as an example script to interact
8669 with the control port.
8670 - "tor --hash-password zzyxz" will output a salted password for
8671 use in authenticating to the control interface.
8672 - New log format in config:
8673 "Log minsev[-maxsev] stdout|stderr|syslog" or
8674 "Log minsev[-maxsev] file /var/foo"
8677 - DirPolicy config option, to let people reject incoming addresses
8678 from their dirserver.
8679 - "tor --list-fingerprint" will list your identity key fingerprint
8681 - Add "pass" target for RedirectExit, to make it easier to break
8682 out of a sequence of RedirectExit rules.
8683 - Clients now generate a TLS cert too, in preparation for having
8684 them act more like real nodes.
8685 - Ship src/win32/ in the tarball, so people can use it to build.
8686 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8688 - New "router-status" line in directory, to better bind each verified
8689 nickname to its identity key.
8690 - Deprecate unofficial config option abbreviations, and abbreviations
8691 not on the command line.
8692 - Add a pure-C tor-resolve implementation.
8693 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8694 1024) file descriptors.
8696 o Code security improvements, inspired by Ilja:
8697 - Replace sprintf with snprintf. (I think they were all safe, but
8699 - Replace strcpy/strncpy with strlcpy in more places.
8700 - Avoid strcat; use snprintf or strlcat instead.
8701 - snprintf wrapper with consistent (though not C99) overflow behavior.
8704 Changes in version 0.0.9pre4 - 2004-10-17
8705 o Bugfixes on 0.0.9pre3:
8706 - If the server doesn't specify an exit policy, use the real default
8707 exit policy, not reject *:*.
8708 - Ignore fascistfirewall when uploading/downloading hidden service
8709 descriptors, since we go through Tor for those; and when using
8710 an HttpProxy, since we assume it can reach them all.
8711 - When looking for an authoritative dirserver, use only the ones
8712 configured at boot. Don't bother looking in the directory.
8713 - The rest of the fix for get_default_conf_file() on older win32.
8714 - Make 'Routerfile' config option obsolete.
8717 - New 'MyFamily nick1,...' config option for a server to
8718 specify other servers that shouldn't be used in the same circuit
8719 with it. Only believed if nick1 also specifies us.
8720 - New 'NodeFamily nick1,nick2,...' config option for a client to
8721 specify nodes that it doesn't want to use in the same circuit.
8722 - New 'Redirectexit pattern address:port' config option for a
8723 server to redirect exit connections, e.g. to a local squid.
8726 Changes in version 0.0.9pre3 - 2004-10-13
8727 o Bugfixes on 0.0.8.1:
8728 - Better torrc example lines for dirbindaddress and orbindaddress.
8729 - Improved bounds checking on parsed ints (e.g. config options and
8730 the ones we find in directories.)
8731 - Better handling of size_t vs int, so we're more robust on 64
8733 - Fix the rest of the bug where a newly started OR would appear
8734 as unverified even after we've added his fingerprint and hupped
8736 - Fix a bug from 0.0.7: when read() failed on a stream, we would
8737 close it without sending back an end. So 'connection refused'
8738 would simply be ignored and the user would get no response.
8740 o Bugfixes on 0.0.9pre2:
8741 - Serving the cached-on-disk directory to people is bad. We now
8742 provide no directory until we've fetched a fresh one.
8743 - Workaround for bug on windows where cached-directories get crlf
8745 - Make get_default_conf_file() work on older windows too.
8746 - If we write a *:* exit policy line in the descriptor, don't write
8747 any more exit policy lines.
8750 - Use only 0.0.9pre1 and later servers for resolve cells.
8751 - Make the dirservers file obsolete.
8752 - Include a dir-signing-key token in directories to tell the
8753 parsing entity which key is being used to sign.
8754 - Remove the built-in bulky default dirservers string.
8755 - New config option "Dirserver %s:%d [fingerprint]", which can be
8756 repeated as many times as needed. If no dirservers specified,
8757 default to moria1,moria2,tor26.
8758 - Make moria2 advertise a dirport of 80, so people behind firewalls
8759 will be able to get a directory.
8760 - Http proxy support
8761 - Dirservers translate requests for http://%s:%d/x to /x
8762 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8763 be routed through this host.
8764 - Clients ask for /tor/x rather than /x for new enough dirservers.
8765 This way we can one day coexist peacefully with apache.
8766 - Clients specify a "Host: %s%d" http header, to be compatible
8767 with more proxies, and so running squid on an exit node can work.
8770 Changes in version 0.0.8.1 - 2004-10-13
8772 - Fix a seg fault that can be triggered remotely for Tor
8773 clients/servers with an open dirport.
8774 - Fix a rare assert trigger, where routerinfos for entries in
8775 our cpath would expire while we're building the path.
8776 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8777 - Fix a rare seg fault for people running hidden services on
8778 intermittent connections.
8779 - Fix a bug in parsing opt keywords with objects.
8780 - Fix a stale pointer assert bug when a stream detaches and
8782 - Fix a string format vulnerability (probably not exploitable)
8783 in reporting stats locally.
8784 - Fix an assert trigger: sometimes launching circuits can fail
8785 immediately, e.g. because too many circuits have failed recently.
8786 - Fix a compile warning on 64 bit platforms.
8789 Changes in version 0.0.9pre2 - 2004-10-03
8791 - Make fetching a cached directory work for 64-bit platforms too.
8792 - Make zlib.h a required header, not an optional header.
8795 Changes in version 0.0.9pre1 - 2004-10-01
8797 - Stop using separate defaults for no-config-file and
8798 empty-config-file. Now you have to explicitly turn off SocksPort,
8799 if you don't want it open.
8800 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8801 - Improve man page to mention more of the 0.0.8 features.
8802 - Fix a rare seg fault for people running hidden services on
8803 intermittent connections.
8804 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8806 - Fix more dns related bugs: send back resolve_failed and end cells
8807 more reliably when the resolve fails, rather than closing the
8808 circuit and then trying to send the cell. Also attach dummy resolve
8809 connections to a circuit *before* calling dns_resolve(), to fix
8810 a bug where cached answers would never be sent in RESOLVED cells.
8811 - When we run out of disk space, or other log writing error, don't
8812 crash. Just stop logging to that log and continue.
8813 - We were starting to daemonize before we opened our logs, so if
8814 there were any problems opening logs, we would complain to stderr,
8815 which wouldn't work, and then mysteriously exit.
8816 - Fix a rare bug where sometimes a verified OR would connect to us
8817 before he'd uploaded his descriptor, which would cause us to
8818 assign conn->nickname as though he's unverified. Now we look through
8819 the fingerprint list to see if he's there.
8820 - Fix a rare assert trigger, where routerinfos for entries in
8821 our cpath would expire while we're building the path.
8824 - Clients can ask dirservers for /dir.z to get a compressed version
8825 of the directory. Only works for servers running 0.0.9, of course.
8826 - Make clients cache directories and use them to seed their router
8827 lists at startup. This means clients have a datadir again.
8828 - Configuration infrastructure support for warning on obsolete
8830 - Respond to content-encoding headers by trying to uncompress as
8832 - Reply with a deflated directory when a client asks for "dir.z".
8833 We could use allow-encodings instead, but allow-encodings isn't
8834 specified in HTTP 1.0.
8835 - Raise the max dns workers from 50 to 100.
8836 - Discourage people from setting their dirfetchpostperiod more often
8837 than once per minute.
8838 - Protect dirservers from overzealous descriptor uploading -- wait
8839 10 seconds after directory gets dirty, before regenerating.
8842 Changes in version 0.0.8 - 2004-08-25
8843 o Port it to SunOS 5.9 / Athena
8846 Changes in version 0.0.8rc2 - 2004-08-20
8847 o Make it compile on cygwin again.
8848 o When picking unverified routers, skip those with low uptime and/or
8849 low bandwidth, depending on what properties you care about.
8852 Changes in version 0.0.8rc1 - 2004-08-18
8853 o Changes from 0.0.7.3:
8855 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8856 don't put it into the client dns cache.
8857 - If a begin failed due to exit policy, but we believe the IP address
8858 should have been allowed, switch that router to exitpolicy reject *:*
8859 until we get our next directory.
8861 - Clients choose nodes proportional to advertised bandwidth.
8862 - Avoid using nodes with low uptime as introduction points.
8863 - Handle servers with dynamic IP addresses: don't replace
8864 options->Address with the resolved one at startup, and
8865 detect our address right before we make a routerinfo each time.
8866 - 'FascistFirewall' option to pick dirservers and ORs on specific
8867 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8868 which ports are open. (Defaults to 80,443)
8869 - Be more aggressive about trying to make circuits when the network
8870 has changed (e.g. when you unsuspend your laptop).
8871 - Check for time skew on http headers; report date in response to
8873 - If the entrynode config line has only one node, don't pick it as
8875 - Add strict{entry|exit}nodes config options. If set to 1, then
8876 we refuse to build circuits that don't include the specified entry
8878 - OutboundBindAddress config option, to bind to a specific
8879 IP address for outgoing connect()s.
8880 - End truncated log entries (e.g. directories) with "[truncated]".
8882 o Patches to 0.0.8preX:
8884 - Patches to compile and run on win32 again (maybe)?
8885 - Fix crash when looking for ~/.torrc with no $HOME set.
8886 - Fix a race bug in the unit tests.
8887 - Handle verified/unverified name collisions better when new
8888 routerinfo's arrive in a directory.
8889 - Sometimes routers were getting entered into the stats before
8890 we'd assigned their identity_digest. Oops.
8891 - Only pick and establish intro points after we've gotten a
8894 - AllowUnverifiedNodes config option to let circuits choose no-name
8895 routers in entry,middle,exit,introduction,rendezvous positions.
8896 Allow middle and rendezvous positions by default.
8897 - Add a man page for tor-resolve.
8900 Changes in version 0.0.7.3 - 2004-08-12
8901 o Stop dnsworkers from triggering an assert failure when you
8902 ask them to resolve the host "".
8905 Changes in version 0.0.8pre3 - 2004-08-09
8906 o Changes from 0.0.7.2:
8907 - Allow multiple ORs with same nickname in routerlist -- now when
8908 people give us one identity key for a nickname, then later
8909 another, we don't constantly complain until the first expires.
8910 - Remember used bandwidth (both in and out), and publish 15-minute
8911 snapshots for the past day into our descriptor.
8912 - You can now fetch $DIRURL/running-routers to get just the
8913 running-routers line, not the whole descriptor list. (But
8914 clients don't use this yet.)
8915 - When people mistakenly use Tor as an http proxy, point them
8916 at the tor-doc.html rather than the INSTALL.
8917 - Remove our mostly unused -- and broken -- hex_encode()
8918 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8919 for pointing out this bug.)
8920 - Rotate onion keys every 12 hours, not every 2 hours, so we have
8921 fewer problems with people using the wrong key.
8922 - Change the default exit policy to reject the default edonkey,
8923 kazaa, gnutella ports.
8924 - Add replace_file() to util.[ch] to handle win32's rename().
8926 o Changes from 0.0.8preX:
8927 - Fix two bugs in saving onion keys to disk when rotating, so
8928 hopefully we'll get fewer people using old onion keys.
8929 - Fix an assert error that was making SocksPolicy not work.
8930 - Be willing to expire routers that have an open dirport -- it's
8931 just the authoritative dirservers we want to not forget.
8932 - Reject tor-resolve requests for .onion addresses early, so we
8933 don't build a whole rendezvous circuit and then fail.
8934 - When you're warning a server that he's unverified, don't cry
8936 - Fix a race condition: don't try to extend onto a connection
8937 that's still handshaking.
8938 - For servers in clique mode, require the conn to be open before
8939 you'll choose it for your path.
8940 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
8941 end relay cell, etc.
8942 - Measure bandwidth capacity over the last 24 hours, not just 12
8943 - Bugfix: authoritative dirservers were making and signing a new
8944 directory for each client, rather than reusing the cached one.
8947 Changes in version 0.0.8pre2 - 2004-08-04
8948 o Changes from 0.0.7.2:
8950 - Check directory signature _before_ you decide whether you're
8951 you're running an obsolete version and should exit.
8952 - Check directory signature _before_ you parse the running-routers
8953 list to decide who's running or verified.
8954 - Bugfixes and features:
8955 - Check return value of fclose while writing to disk, so we don't
8956 end up with broken files when servers run out of disk space.
8957 - Log a warning if the user uses an unsafe socks variant, so people
8958 are more likely to learn about privoxy or socat.
8959 - Dirservers now include RFC1123-style dates in the HTTP headers,
8960 which one day we will use to better detect clock skew.
8962 o Changes from 0.0.8pre1:
8963 - Make it compile without warnings again on win32.
8964 - Log a warning if you're running an unverified server, to let you
8965 know you might want to get it verified.
8966 - Only pick a default nickname if you plan to be a server.
8969 Changes in version 0.0.8pre1 - 2004-07-23
8971 - Made our unit tests compile again on OpenBSD 3.5, and tor
8972 itself compile again on OpenBSD on a sparc64.
8973 - We were neglecting milliseconds when logging on win32, so
8974 everything appeared to happen at the beginning of each second.
8977 - 'Extend' relay cell payloads now include the digest of the
8978 intended next hop's identity key. Now we can verify that we're
8979 extending to the right router, and also extend to routers we
8980 hadn't heard of before.
8983 - Tor nodes can now act as relays (with an advertised ORPort)
8984 without being manually verified by the dirserver operators.
8985 - Uploaded descriptors of unverified routers are now accepted
8986 by the dirservers, and included in the directory.
8987 - Verified routers are listed by nickname in the running-routers
8988 list; unverified routers are listed as "$<fingerprint>".
8989 - We now use hash-of-identity-key in most places rather than
8990 nickname or addr:port, for improved security/flexibility.
8991 - To avoid Sybil attacks, paths still use only verified servers.
8992 But now we have a chance to play around with hybrid approaches.
8993 - Nodes track bandwidth usage to estimate capacity (not used yet).
8994 - ClientOnly option for nodes that never want to become servers.
8995 - Directory caching.
8996 - "AuthoritativeDir 1" option for the official dirservers.
8997 - Now other nodes (clients and servers) will cache the latest
8998 directory they've pulled down.
8999 - They can enable their DirPort to serve it to others.
9000 - Clients will pull down a directory from any node with an open
9001 DirPort, and check the signature/timestamp correctly.
9002 - Authoritative dirservers now fetch directories from other
9003 authdirservers, to stay better synced.
9004 - Running-routers list tells who's down also, along with noting
9005 if they're verified (listed by nickname) or unverified (listed
9007 - Allow dirservers to serve running-router list separately.
9008 This isn't used yet.
9009 - ORs connect-on-demand to other ORs
9010 - If you get an extend cell to an OR you're not connected to,
9011 connect, handshake, and forward the create cell.
9012 - The authoritative dirservers stay connected to everybody,
9013 and everybody stays connected to 0.0.7 servers, but otherwise
9014 clients/servers expire unused connections after 5 minutes.
9015 - When servers get a sigint, they delay 30 seconds (refusing new
9016 connections) then exit. A second sigint causes immediate exit.
9017 - File and name management:
9018 - Look for .torrc if no CONFDIR "torrc" is found.
9019 - If no datadir is defined, then choose, make, and secure ~/.tor
9021 - If torrc not found, exitpolicy reject *:*.
9022 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
9023 - If no nickname is defined, derive default from hostname.
9024 - Rename secret key files, e.g. identity.key -> secret_id_key,
9025 to discourage people from mailing their identity key to tor-ops.
9026 - Refuse to build a circuit before the directory has arrived --
9027 it won't work anyway, since you won't know the right onion keys
9029 - Try other dirservers immediately if the one you try is down. This
9030 should tolerate down dirservers better now.
9031 - Parse tor version numbers so we can do an is-newer-than check
9032 rather than an is-in-the-list check.
9033 - New socks command 'resolve', to let us shim gethostbyname()
9035 - A 'tor_resolve' script to access the socks resolve functionality.
9036 - A new socks-extensions.txt doc file to describe our
9037 interpretation and extensions to the socks protocols.
9038 - Add a ContactInfo option, which gets published in descriptor.
9039 - Publish OR uptime in descriptor (and thus in directory) too.
9040 - Write tor version at the top of each log file
9041 - New docs in the tarball:
9043 - Document that you should proxy your SSL traffic too.
9046 Changes in version 0.0.7.2 - 2004-07-07
9047 o A better fix for the 0.0.0.0 problem, that will hopefully
9048 eliminate the remaining related assertion failures.
9051 Changes in version 0.0.7.1 - 2004-07-04
9052 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
9053 since internally we use 0.0.0.0 to signify "not yet resolved".
9056 Changes in version 0.0.7 - 2004-06-07
9057 o Updated the man page to reflect the new features.
9060 Changes in version 0.0.7rc2 - 2004-06-06
9061 o Changes from 0.0.7rc1:
9062 - Make it build on Win32 again.
9063 o Changes from 0.0.6.2:
9064 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
9068 Changes in version 0.0.7rc1 - 2004-06-02
9070 - On sighup, we were adding another log without removing the first
9071 one. So log messages would get duplicated n times for n sighups.
9072 - Several cases of using a connection after we'd freed it. The
9073 problem was that connections that are pending resolve are in both
9074 the pending_resolve tree, and also the circuit's resolving_streams
9075 list. When you want to remove one, you must remove it from both.
9076 - Fix a double-mark-for-close where an end cell arrived for a
9077 resolving stream, and then the resolve failed.
9078 - Check directory signatures based on name of signer, not on whom
9079 we got the directory from. This will let us cache directories more
9082 - Crank up some of our constants to handle more users.
9085 Changes in version 0.0.7pre1 - 2004-06-02
9086 o Fixes for crashes and other obnoxious bugs:
9087 - Fix an epipe bug: sometimes when directory connections failed
9088 to connect, we would give them a chance to flush before closing
9090 - When we detached from a circuit because of resolvefailed, we
9091 would immediately try the same circuit twice more, and then
9092 give up on the resolve thinking we'd tried three different
9094 - Limit the number of intro circuits we'll attempt to build for a
9095 hidden service per 15-minute period.
9096 - Check recommended-software string *early*, before actually parsing
9097 the directory. Thus we can detect an obsolete version and exit,
9098 even if the new directory format doesn't parse.
9099 o Fixes for security bugs:
9100 - Remember which nodes are dirservers when you startup, and if a
9101 random OR enables his dirport, don't automatically assume he's
9102 a trusted dirserver.
9104 - Directory connections were asking the wrong poll socket to
9105 start writing, and not asking themselves to start writing.
9106 - When we detached from a circuit because we sent a begin but
9107 didn't get a connected, we would use it again the first time;
9108 but after that we would correctly switch to a different one.
9109 - Stop warning when the first onion decrypt attempt fails; they
9110 will sometimes legitimately fail now that we rotate keys.
9111 - Override unaligned-access-ok check when $host_cpu is ia64 or
9112 arm. Apparently they allow it but the kernel whines.
9113 - Dirservers try to reconnect periodically too, in case connections
9115 - Fix some memory leaks in directory servers.
9116 - Allow backslash in Win32 filenames.
9117 - Made Tor build complain-free on FreeBSD, hopefully without
9118 breaking other BSD builds. We'll see.
9120 - Doxygen markup on all functions and global variables.
9121 - Make directory functions update routerlist, not replace it. So
9122 now directory disagreements are not so critical a problem.
9123 - Remove the upper limit on number of descriptors in a dirserver's
9124 directory (not that we were anywhere close).
9125 - Allow multiple logfiles at different severity ranges.
9126 - Allow *BindAddress to specify ":port" rather than setting *Port
9127 separately. Allow multiple instances of each BindAddress config
9128 option, so you can bind to multiple interfaces if you want.
9129 - Allow multiple exit policy lines, which are processed in order.
9130 Now we don't need that huge line with all the commas in it.
9131 - Enable accept/reject policies on SOCKS connections, so you can bind
9132 to 0.0.0.0 but still control who can use your OP.
9135 Changes in version 0.0.6.2 - 2004-05-16
9136 o Our integrity-checking digest was checking only the most recent cell,
9137 not the previous cells like we'd thought.
9138 Thanks to Stefan Mark for finding the flaw!
9141 Changes in version 0.0.6.1 - 2004-05-06
9142 o Fix two bugs in our AES counter-mode implementation (this affected
9143 onion-level stream encryption, but not TLS-level). It turns
9144 out we were doing something much more akin to a 16-character
9145 polyalphabetic cipher. Oops.
9146 Thanks to Stefan Mark for finding the flaw!
9147 o Retire moria3 as a directory server, and add tor26 as a directory
9151 Changes in version 0.0.6 - 2004-05-02
9155 Changes in version 0.0.6rc4 - 2004-05-01
9156 o Update the built-in dirservers list to use the new directory format
9157 o Fix a rare seg fault: if a node offering a hidden service attempts
9158 to build a circuit to Alice's rendezvous point and fails before it
9159 reaches the last hop, it retries with a different circuit, but
9161 o Handle windows socket errors correctly.
9164 Changes in version 0.0.6rc3 - 2004-04-28
9165 o Don't expire non-general excess circuits (if we had enough
9166 circuits open, we were expiring rendezvous circuits -- even
9167 when they had a stream attached. oops.)
9168 o Fetch randomness from /dev/urandom better (not via fopen/fread)
9169 o Better debugging for tls errors
9170 o Some versions of openssl have an SSL_pending function that erroneously
9171 returns bytes when there is a non-application record pending.
9172 o Set Content-Type on the directory and hidserv descriptor.
9173 o Remove IVs from cipher code, since AES-ctr has none.
9174 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
9175 o We were using an array of length zero in a few places.
9176 o win32's gethostbyname can't resolve an IP to an IP.
9177 o win32's close can't close a socket.
9180 Changes in version 0.0.6rc2 - 2004-04-26
9181 o Fix a bug where we were closing tls connections intermittently.
9182 It turns out openssl keeps its errors around -- so if an error
9183 happens, and you don't ask about it, and then another openssl
9184 operation happens and succeeds, and you ask if there was an error,
9185 it tells you about the first error. Fun fun.
9186 o Fix a bug that's been lurking since 27 may 03 (!)
9187 When passing back a destroy cell, we would use the wrong circ id.
9188 'Mostly harmless', but still worth fixing.
9189 o Since we don't support truncateds much, don't bother sending them;
9190 just close the circ.
9191 o check for <machine/limits.h> so we build on NetBSD again (I hope).
9192 o don't crash if a conn that sent a begin has suddenly lost its circuit
9193 (this was quite rare).
9196 Changes in version 0.0.6rc1 - 2004-04-25
9197 o We now rotate link (tls context) keys and onion keys.
9198 o CREATE cells now include oaep padding, so you can tell
9199 if you decrypted them correctly.
9200 o Add bandwidthburst to server descriptor.
9201 o Directories now say which dirserver signed them.
9202 o Use a tor_assert macro that logs failed assertions too.
9205 Changes in version 0.0.6pre5 - 2004-04-18
9206 o changes from 0.0.6pre4:
9207 - make tor build on broken freebsd 5.2 installs
9208 - fix a failed assert when you try an intro point, get a nack, and try
9209 a second one and it works.
9210 - when alice uses a port that the hidden service doesn't accept,
9211 it now sends back an end cell (denied by exit policy). otherwise
9212 alice would just have to wait to time out.
9213 - fix another rare bug: when we had tried all the intro
9214 points for a hidden service, we fetched the descriptor
9215 again, but we left our introcirc thinking it had already
9216 sent an intro, so it kept waiting for a response...
9217 - bugfix: when you sleep your hidden-service laptop, as soon
9218 as it wakes up it tries to upload a service descriptor, but
9219 socketpair fails for some reason (localhost not up yet?).
9220 now we simply give up on that upload, and we'll try again later.
9221 i'd still like to find the bug though.
9222 - if an intro circ waiting for an ack dies before getting one, then
9224 - we were reusing stale service descriptors and refetching usable
9228 Changes in version 0.0.6pre4 - 2004-04-14
9229 o changes from 0.0.6pre3:
9230 - when bob fails to connect to the rendezvous point, and his
9231 circ didn't fail because of the rendezvous point itself, then
9232 he retries a couple of times
9233 - we expire introduction and rendezvous circs more thoroughly
9234 (sometimes they were hanging around forever)
9235 - we expire unattached rendezvous streams that have been around
9236 too long (they were sticking around forever).
9237 - fix a measly fencepost error that was crashing everybody with
9241 Changes in version 0.0.6pre3 - 2004-04-14
9242 o changes from 0.0.6pre2:
9243 - make hup work again
9244 - fix some memory leaks for dirservers
9245 - allow more skew in rendezvous descriptor timestamps, to help
9246 handle people like blanu who don't know what time it is
9247 - normal circs are 3 hops, but some rend/intro circs are 4, if
9248 the initiator doesn't get to choose the last hop
9249 - send acks for introductions, so alice can know whether to try
9251 - bob publishes intro points more correctly
9252 o changes from 0.0.5:
9253 - fix an assert trigger that's been plaguing us since the days
9254 of 0.0.2prexx (thanks weasel!)
9255 - retry stream correctly when we fail to connect because of
9256 exit-policy-reject (should try another) or can't-resolve-address
9257 (also should try another, because dns on random internet servers
9259 - when we hup a dirserver and we've *removed* a server from the
9260 approved-routers list, now we remove that server from the
9261 in-memory directories too
9264 Changes in version 0.0.6pre2 - 2004-04-08
9265 o We fixed our base32 implementation. Now it works on all architectures.
9268 Changes in version 0.0.6pre1 - 2004-04-08
9270 - Hidden services and rendezvous points are implemented. Go to
9271 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
9272 hidden services. (This only works via a socks4a proxy such as
9273 Privoxy, and currently it's quite slow.)
9276 Changes in version 0.0.5 - 2004-03-30
9280 Changes in version 0.0.5rc3 - 2004-03-29
9281 o Install torrc as torrc.sample -- we no longer clobber your
9283 o Re-enable recommendedversion checking (we broke it in rc2, oops)
9284 o Add in a 'notice' log level for things the operator should hear
9285 but that aren't warnings
9288 Changes in version 0.0.5rc2 - 2004-03-29
9289 o Hold socks connection open until reply is flushed (if possible)
9290 o Make exit nodes resolve IPs to IPs immediately, rather than asking
9291 the dns farm to do it.
9292 o Fix c99 aliasing warnings in rephist.c
9293 o Don't include server descriptors that are older than 24 hours in the
9295 o Give socks 'reject' replies their whole 15s to attempt to flush,
9296 rather than seeing the 60s timeout and assuming the flush had failed.
9297 o Clean automake droppings from the cvs repository
9300 Changes in version 0.0.5rc1 - 2004-03-28
9301 o Fix mangled-state bug in directory fetching (was causing sigpipes).
9302 o Only build circuits after we've fetched the directory: clients were
9303 using only the directory servers before they'd fetched a directory.
9304 This also means longer startup time; so it goes.
9305 o Fix an assert trigger where an OP would fail to handshake, and we'd
9306 expect it to have a nickname.
9307 o Work around a tsocks bug: do a socks reject when AP connection dies
9308 early, else tsocks goes into an infinite loop.
9311 Changes in version 0.0.4 - 2004-03-26
9312 o When connecting to a dirserver or OR and the network is down,
9316 Changes in version 0.0.3 - 2004-03-26
9317 o Warn and fail if server chose a nickname with illegal characters
9318 o Port to Solaris and Sparc:
9319 - include missing header fcntl.h
9320 - have autoconf find -lsocket -lnsl automatically
9321 - deal with hardware word alignment
9322 - make uname() work (solaris has a different return convention)
9323 - switch from using signal() to sigaction()
9324 o Preliminary work on reputation system:
9325 - Keep statistics on success/fail of connect attempts; they're published
9326 by kill -USR1 currently.
9327 - Add a RunTesting option to try to learn link state by creating test
9328 circuits, even when SocksPort is off.
9329 - Remove unused open circuits when there are too many.
9332 Changes in version 0.0.2 - 2004-03-19
9333 - Include strlcpy and strlcat for safer string ops
9334 - define INADDR_NONE so we compile (but still not run) on solaris
9337 Changes in version 0.0.2pre27 - 2004-03-14
9339 - Allow internal tor networks (we were rejecting internal IPs,
9340 now we allow them if they're set explicitly).
9341 - And fix a few endian issues.
9344 Changes in version 0.0.2pre26 - 2004-03-14
9346 - If a stream times out after 15s without a connected cell, don't
9347 try that circuit again: try a new one.
9348 - Retry streams at most 4 times. Then give up.
9349 - When a dirserver gets a descriptor from an unknown router, it
9350 logs its fingerprint (so the dirserver operator can choose to
9351 accept it even without mail from the server operator).
9352 - Inform unapproved servers when we reject their descriptors.
9353 - Make tor build on Windows again. It works as a client, who knows
9355 - Clearer instructions in the torrc for how to set up a server.
9356 - Be more efficient about reading fd's when our global token bucket
9357 (used for rate limiting) becomes empty.
9359 - Stop asserting that computers always go forward in time. It's
9361 - When we sent a cell (e.g. destroy) and then marked an OR connection
9362 expired, we might close it before finishing a flush if the other
9363 side isn't reading right then.
9364 - Don't allow dirservers to start if they haven't defined
9366 - We were caching transient dns failures. Oops.
9367 - Prevent servers from publishing an internal IP as their address.
9368 - Address a strcat vulnerability in circuit.c
9371 Changes in version 0.0.2pre25 - 2004-03-04
9373 - Put the OR's IP in its router descriptor, not its fqdn. That way
9374 we'll stop being stalled by gethostbyname for nodes with flaky dns,
9377 - If the user typed in an address that didn't resolve, the server
9381 Changes in version 0.0.2pre24 - 2004-03-03
9383 - Fix an assertion failure in dns.c, where we were trying to dequeue
9384 a pending dns resolve even if it wasn't pending
9385 - Fix a spurious socks5 warning about still trying to write after the
9386 connection is finished.
9387 - Hold certain marked_for_close connections open until they're finished
9388 flushing, rather than losing bytes by closing them too early.
9389 - Correctly report the reason for ending a stream
9390 - Remove some duplicate calls to connection_mark_for_close
9391 - Put switch_id and start_daemon earlier in the boot sequence, so it
9392 will actually try to chdir() to options.DataDirectory
9393 - Make 'make test' exit(1) if a test fails; fix some unit tests
9394 - Make tor fail when you use a config option it doesn't know about,
9395 rather than warn and continue.
9396 - Make --version work
9397 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
9400 Changes in version 0.0.2pre23 - 2004-02-29
9402 - Print a statement when the first circ is finished, so the user
9404 - If a relay cell is unrecognized at the end of the circuit,
9405 send back a destroy. (So attacks to mutate cells are more
9407 - New config option 'excludenodes' to avoid certain nodes for circuits.
9408 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
9409 so you can collect coredumps there.
9411 - Fix a bug in tls flushing where sometimes data got wedged and
9412 didn't flush until more data got sent. Hopefully this bug was
9413 a big factor in the random delays we were seeing.
9414 - Make 'connected' cells include the resolved IP, so the client
9415 dns cache actually gets populated.
9416 - Disallow changing from ORPort=0 to ORPort>0 on hup.
9417 - When we time-out on a stream and detach from the circuit, send an
9418 end cell down it first.
9419 - Only warn about an unknown router (in exitnodes, entrynodes,
9420 excludenodes) after we've fetched a directory.
9423 Changes in version 0.0.2pre22 - 2004-02-26
9425 - Servers publish less revealing uname information in descriptors.
9426 - More memory tracking and assertions, to crash more usefully when
9428 - If the default torrc isn't there, just use some default defaults.
9429 Plus provide an internal dirservers file if they don't have one.
9430 - When the user tries to use Tor as an http proxy, give them an http
9431 501 failure explaining that we're a socks proxy.
9432 - Dump a new router.desc on hup, to help confused people who change
9433 their exit policies and then wonder why router.desc doesn't reflect
9435 - Clean up the generic tor.sh init script that we ship with.
9437 - If the exit stream is pending on the resolve, and a destroy arrives,
9438 then the stream wasn't getting removed from the pending list. I
9439 think this was the one causing recent server crashes.
9440 - Use a more robust poll on OSX 10.3, since their poll is flaky.
9441 - When it couldn't resolve any dirservers, it was useless from then on.
9442 Now it reloads the RouterFile (or default dirservers) if it has no
9444 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
9445 many users don't even *have* a /usr/local/sbin/.
9448 Changes in version 0.0.2pre21 - 2004-02-18
9450 - There's a ChangeLog file that actually reflects the changelog.
9451 - There's a 'torify' wrapper script, with an accompanying
9452 tor-tsocks.conf, that simplifies the process of using tsocks for
9453 tor. It even has a man page.
9454 - The tor binary gets installed to sbin rather than bin now.
9455 - Retry streams where the connected cell hasn't arrived in 15 seconds
9456 - Clean up exit policy handling -- get the default out of the torrc,
9457 so we can update it without forcing each server operator to fix
9459 - Allow imaps and pop3s in default exit policy
9461 - Prevent picking middleman nodes as the last node in the circuit
9464 Changes in version 0.0.2pre20 - 2004-01-30
9466 - We now have a deb package, and it's in debian unstable. Go to
9468 - I've split the TotalBandwidth option into BandwidthRate (how many
9469 bytes per second you want to allow, long-term) and
9470 BandwidthBurst (how many bytes you will allow at once before the cap
9471 kicks in). This better token bucket approach lets you, say, set
9472 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
9473 performance while not exceeding your monthly bandwidth quota.
9474 - Push out a tls record's worth of data once you've got it, rather
9475 than waiting until you've read everything waiting to be read. This
9476 may improve performance by pipelining better. We'll see.
9477 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
9478 from failed circuits (if they haven't been connected yet) and attach
9480 - Expire old streams that haven't managed to connect. Some day we'll
9481 have them reattach to new circuits instead.
9484 - Fix several memory leaks that were causing servers to become bloated
9486 - Fix a few very rare assert triggers. A few more remain.
9487 - Setuid to User _before_ complaining about running as root.
9490 Changes in version 0.0.2pre19 - 2004-01-07
9492 - Fix deadlock condition in dns farm. We were telling a child to die by
9493 closing the parent's file descriptor to him. But newer children were
9494 inheriting the open file descriptor from the parent, and since they
9495 weren't closing it, the socket never closed, so the child never read
9496 eof, so he never knew to exit. Similarly, dns workers were holding
9497 open other sockets, leading to all sorts of chaos.
9498 - New cleaner daemon() code for forking and backgrounding.
9499 - If you log to a file, it now prints an entry at the top of the
9500 logfile so you know it's working.
9501 - The onionskin challenge length was 30 bytes longer than necessary.
9502 - Started to patch up the spec so it's not quite so out of date.
9505 Changes in version 0.0.2pre18 - 2004-01-02
9507 - Fix endian issues with the 'integrity' field in the relay header.
9508 - Fix a potential bug where connections in state
9509 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9512 Changes in version 0.0.2pre17 - 2003-12-30
9514 - Made --debuglogfile (or any second log file, actually) work.
9515 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9516 adversary could force us into an infinite loop.
9519 - Each onionskin handshake now includes a hash of the computed key,
9520 to prove the server's identity and help perfect forward secrecy.
9521 - Changed cell size from 256 to 512 bytes (working toward compatibility
9523 - Changed cell length to 2 bytes, and moved it to the relay header.
9524 - Implemented end-to-end integrity checking for the payloads of
9526 - Separated streamid from 'recognized' (otherwise circuits will get
9527 messed up when we try to have streams exit from the middle). We
9528 use the integrity-checking to confirm that a cell is addressed to
9530 - Randomize the initial circid and streamid values, so an adversary who
9531 breaks into a node can't learn how many circuits or streams have
9535 Changes in version 0.0.2pre16 - 2003-12-14
9537 - Fixed a bug that made HUP trigger an assert
9538 - Fixed a bug where a circuit that immediately failed wasn't being
9539 counted as a failed circuit in counting retries.
9542 - Now we close the circuit when we get a truncated cell: otherwise we're
9543 open to an anonymity attack where a bad node in the path truncates
9544 the circuit and then we open streams at him.
9545 - Add port ranges to exit policies
9546 - Add a conservative default exit policy
9547 - Warn if you're running tor as root
9548 - on HUP, retry OR connections and close/rebind listeners
9549 - options.EntryNodes: try these nodes first when picking the first node
9550 - options.ExitNodes: if your best choices happen to include any of
9551 your preferred exit nodes, you choose among just those preferred
9553 - options.ExcludedNodes: nodes that are never picked in path building
9556 Changes in version 0.0.2pre15 - 2003-12-03
9557 o Robustness and bugfixes:
9558 - Sometimes clients would cache incorrect DNS resolves, which would
9559 really screw things up.
9560 - An OP that goes offline would slowly leak all its sockets and stop
9562 - A wide variety of bugfixes in exit node selection, exit policy
9563 handling, and processing pending streams when a new circuit is
9565 - Pick nodes for a path only from those the directory says are up
9566 - Choose randomly from all running dirservers, not always the first one
9567 - Increase allowed http header size for directory fetch.
9568 - Stop writing to stderr (if we're daemonized it will be closed).
9569 - Enable -g always, so cores will be more useful to me.
9570 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9573 - Wrote a man page. It lists commonly used options.
9576 - Change default loglevel to warn.
9577 - Make PidFile default to null rather than littering in your CWD.
9578 - OnionRouter config option is now obsolete. Instead it just checks
9580 - Moved to a single unified torrc file for both clients and servers.
9583 Changes in version 0.0.2pre14 - 2003-11-29
9584 o Robustness and bugfixes:
9585 - Force the admin to make the DataDirectory himself
9586 - to get ownership/permissions right
9587 - so clients no longer make a DataDirectory and then never use it
9588 - fix bug where a client who was offline for 45 minutes would never
9589 pull down a directory again
9590 - fix (or at least hide really well) the dns assert bug that was
9591 causing server crashes
9592 - warnings and improved robustness wrt clockskew for certs
9593 - use the native daemon(3) to daemonize, when available
9594 - exit if bind() fails
9595 - exit if neither socksport nor orport is defined
9596 - include our own tor_timegm (Win32 doesn't have its own)
9597 - bugfix for win32 with lots of connections
9598 - fix minor bias in PRNG
9599 - make dirserver more robust to corrupt cached directory
9602 - Wrote the design document (woo)
9604 o Circuit building and exit policies:
9605 - Circuits no longer try to use nodes that the directory has told them
9607 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9608 bitcounts (18.0.0.0/8).
9609 - Make AP connections standby for a circuit if no suitable circuit
9610 exists, rather than failing
9611 - Circuits choose exit node based on addr/port, exit policies, and
9612 which AP connections are standing by
9613 - Bump min pathlen from 2 to 3
9614 - Relay end cells have a payload to describe why the stream ended.
9615 - If the stream failed because of exit policy, try again with a new
9617 - Clients have a dns cache to remember resolved addresses.
9618 - Notice more quickly when we have no working circuits
9621 - APPort is now called SocksPort
9622 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9624 - RecommendedVersions is now a config variable rather than
9625 hardcoded (for dirservers)
9626 - Reloads config on HUP
9627 - Usage info on -h or --help
9628 - If you set User and Group config vars, it'll setu/gid to them.
9631 Changes in version 0.0.2pre13 - 2003-10-19
9632 o General stability:
9633 - SSL_write no longer fails when it returns WANTWRITE and the number
9634 of bytes in the buf has changed by the next SSL_write call.
9635 - Fix segfault fetching directory when network is down
9636 - Fix a variety of minor memory leaks
9637 - Dirservers reload the fingerprints file on HUP, so I don't have
9638 to take down the network when I approve a new router
9639 - Default server config file has explicit Address line to specify fqdn
9642 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9643 - Make listener connections not ever alloc bufs
9645 o Autoconf improvements:
9646 - don't clobber an external CFLAGS in ./configure
9647 - Make install now works
9648 - create var/lib/tor on make install
9649 - autocreate a tor.sh initscript to help distribs
9650 - autocreate the torrc and sample-server-torrc with correct paths
9652 o Log files and Daemonizing now work:
9653 - If --DebugLogFile is specified, log to it at -l debug
9654 - If --LogFile is specified, use it instead of commandline
9655 - If --RunAsDaemon is set, tor forks and backgrounds on startup