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