1 Changes in version 0.2.3.5-alpha - 2011-09-28
2 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
3 bridge relays; fixes an assertion error that many users started hitting
4 today; and adds the ability to refill token buckets more often than
5 once per second, allowing significant performance improvements.
8 - Bridge relays now do their directory fetches inside Tor TLS
9 connections, like all the other clients do, rather than connecting
10 directly to the DirPort like public relays do. Removes another
11 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
12 - Bridges relays now build circuits for themselves in a more similar
13 way to how clients build them. Removes another avenue for
14 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
15 when bridges were introduced.
18 - Fix an "Assertion md->held_by_node == 1 failed" error that could
19 occur when the same microdescriptor was referenced by two node_t
20 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
22 o Major features (networking):
23 - Add a new TokenBucketRefillInterval option to refill token buckets
24 more frequently than once per second. This should improve network
25 performance, alleviate queueing problems, and make traffic less
26 bursty. Implements proposal 183; closes ticket 3630. Design by
27 Florian Tschorsch and Björn Scheuermann; implementation by
31 - Change an integer overflow check in the OpenBSD_Malloc code so
32 that GCC is less likely to eliminate it as impossible. Patch
33 from Mansour Moufid. Fixes bug 4059.
35 o Minor bugfixes (usability):
36 - Downgrade log messages about circuit timeout calibration from
37 "notice" to "info": they don't require or suggest any human
38 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
39 bugfix on 0.2.2.14-alpha.
41 o Minor features (diagnostics):
42 - When the system call to create a listener socket fails, log the
43 error message explaining why. This may help diagnose bug 4027.
46 Changes in version 0.2.3.4-alpha - 2011-09-13
47 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
48 tweak to Tor's TLS handshake that makes relays and bridges that run
49 this new version reachable from Iran again. It also fixes a few new
50 bugs in 0.2.3.x, and teaches relays to recognize when they're not
51 listed in the network consensus and republish.
53 o Major bugfixes (also part of 0.2.2.33):
54 - Avoid an assertion failure when reloading a configuration with
55 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
56 3923; bugfix on 0.2.2.25-alpha.
58 o Minor features (security, also part of 0.2.2.33):
59 - Check for replays of the public-key encrypted portion of an
60 INTRODUCE1 cell, in addition to the current check for replays of
61 the g^x value. This prevents a possible class of active attacks
62 by an attacker who controls both an introduction point and a
63 rendezvous point, and who uses the malleability of AES-CTR to
64 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
65 that these attacks is infeasible (requiring the attacker to send
66 on the order of zettabytes of altered cells in a short interval),
67 but we'd rather block them off in case there are any classes of
68 this attack that we missed. Reported by Willem Pinckaers.
70 o Minor features (also part of 0.2.2.33):
71 - Adjust the expiration time on our SSL session certificates to
72 better match SSL certs seen in the wild. Resolves ticket 4014.
73 - Change the default required uptime for a relay to be accepted as
74 a HSDir (hidden service directory) from 24 hours to 25 hours.
75 Improves on 0.2.0.10-alpha; resolves ticket 2649.
76 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
77 authorities to abstain from voting on assignment of the HSDir
78 consensus flag. Related to bug 2649.
79 - Update to the September 6 2011 Maxmind GeoLite Country database.
81 o Minor bugfixes (also part of 0.2.2.33):
82 - Demote the 'replay detected' log message emitted when a hidden
83 service receives the same Diffie-Hellman public key in two different
84 INTRODUCE2 cells to info level. A normal Tor client can cause that
85 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
86 fixes part of bug 2442.
87 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
88 level. There is nothing that a hidden service's operator can do
89 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
91 - Clarify a log message specifying the characters permitted in
92 HiddenServiceAuthorizeClient client names. Previously, the log
93 message said that "[A-Za-z0-9+-_]" were permitted; that could have
94 given the impression that every ASCII character between "+" and "_"
95 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
97 o Build fixes (also part of 0.2.2.33):
98 - Clean up some code issues that prevented Tor from building on older
99 BSDs. Fixes bug 3894; reported by "grarpamp".
100 - Search for a platform-specific version of "ar" when cross-compiling.
101 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
104 - Fix a bug where the SocksPort option (for example) would get
105 ignored and replaced by the default if a SocksListenAddress
106 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
110 - Relays now try regenerating and uploading their descriptor more
111 frequently if they are not listed in the consensus, or if the
112 version of their descriptor listed in the consensus is too
113 old. This fix should prevent situations where a server declines
114 to re-publish itself because it has done so too recently, even
115 though the authorities decided not to list its recent-enough
116 descriptor. Fix for bug 3327.
119 - Relays now include a reason for regenerating their descriptors
120 in an HTTP header when uploading to the authorities. This will
121 make it easier to debug descriptor-upload issues in the future.
122 - When starting as root and then changing our UID via the User
123 control option, and we have a ControlSocket configured, make sure
124 that the ControlSocket is owned by the same account that Tor will
125 run under. Implements ticket 3421; fix by Jérémy Bobbio.
128 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
129 utility function used in the control-port code). This shouldn't
130 ever happen unless Tor is completely out of memory, but if it did
131 happen and Tor somehow recovered from it, Tor could have sent a log
132 message to a control port in the middle of a reply to a controller
133 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
134 - Make 'FetchUselessDescriptors' cause all descriptor types and
135 all consensus types (including microdescriptors) to get fetched.
136 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
139 - Make a new "entry connection" struct as an internal subtype of "edge
140 connection", to simplify the code and make exit connections smaller.
143 Changes in version 0.2.2.33 - 2011-09-13
144 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
145 TLS handshake that makes relays and bridges that run this new version
146 reachable from Iran again.
149 - Avoid an assertion failure when reloading a configuration with
150 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
151 3923; bugfix on 0.2.2.25-alpha.
153 o Minor features (security):
154 - Check for replays of the public-key encrypted portion of an
155 INTRODUCE1 cell, in addition to the current check for replays of
156 the g^x value. This prevents a possible class of active attacks
157 by an attacker who controls both an introduction point and a
158 rendezvous point, and who uses the malleability of AES-CTR to
159 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
160 that these attacks are infeasible (requiring the attacker to send
161 on the order of zettabytes of altered cells in a short interval),
162 but we'd rather block them off in case there are any classes of
163 this attack that we missed. Reported by Willem Pinckaers.
166 - Adjust the expiration time on our SSL session certificates to
167 better match SSL certs seen in the wild. Resolves ticket 4014.
168 - Change the default required uptime for a relay to be accepted as
169 a HSDir (hidden service directory) from 24 hours to 25 hours.
170 Improves on 0.2.0.10-alpha; resolves ticket 2649.
171 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
172 authorities to abstain from voting on assignment of the HSDir
173 consensus flag. Related to bug 2649.
174 - Update to the September 6 2011 Maxmind GeoLite Country database.
176 o Minor bugfixes (documentation and log messages):
177 - Correct the man page to explain that HashedControlPassword and
178 CookieAuthentication can both be set, in which case either method
179 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
180 when we decided to allow these config options to both be set. Issue
182 - Demote the 'replay detected' log message emitted when a hidden
183 service receives the same Diffie-Hellman public key in two different
184 INTRODUCE2 cells to info level. A normal Tor client can cause that
185 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
186 fixes part of bug 2442.
187 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
188 level. There is nothing that a hidden service's operator can do
189 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
191 - Clarify a log message specifying the characters permitted in
192 HiddenServiceAuthorizeClient client names. Previously, the log
193 message said that "[A-Za-z0-9+-_]" were permitted; that could have
194 given the impression that every ASCII character between "+" and "_"
195 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
198 - Provide a substitute implementation of lround() for MSVC, which
199 apparently lacks it. Patch from Gisle Vanem.
200 - Clean up some code issues that prevented Tor from building on older
201 BSDs. Fixes bug 3894; reported by "grarpamp".
202 - Search for a platform-specific version of "ar" when cross-compiling.
203 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
206 Changes in version 0.2.3.3-alpha - 2011-09-01
207 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
208 security, and provides client-side support for the microdescriptor
209 and optimistic data features introduced earlier in the 0.2.3.x
210 series. It also includes numerous critical bugfixes in the (optional)
211 bufferevent-based networking backend.
213 o Major features (stream isolation):
214 - You can now configure Tor so that streams from different
215 applications are isolated on different circuits, to prevent an
216 attacker who sees your streams as they leave an exit node from
217 linking your sessions to one another. To do this, choose some way
218 to distinguish the applications: have them connect to different
219 SocksPorts, or have one of them use SOCKS4 while the other uses
220 SOCKS5, or have them pass different authentication strings to the
221 SOCKS proxy. Then, use the new SocksPort syntax to configure the
222 degree of isolation you need. This implements Proposal 171.
223 - There's a new syntax for specifying multiple client ports (such as
224 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
225 multiple *Port entries with full addr:port syntax on each.
226 The old *ListenAddress format is still supported, but you can't
227 mix it with the new *Port syntax.
229 o Major features (other):
230 - Enable microdescriptor fetching by default for clients. This allows
231 clients to download a much smaller amount of directory information.
232 To disable it (and go back to the old-style consensus and
233 descriptors), set "UseMicrodescriptors 0" in your torrc file.
234 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
235 "PortForwarding" config option), now supports Windows.
236 - When using an exit relay running 0.2.3.x, clients can now
237 "optimistically" send data before the exit relay reports that
238 the stream has opened. This saves a round trip when starting
239 connections where the client speaks first (such as web browsing).
240 This behavior is controlled by a consensus parameter (currently
241 disabled). To turn it on or off manually, use the "OptimisticData"
242 torrc option. Implements proposal 181; code by Ian Goldberg.
244 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
245 - When using IOCP on Windows, we need to enable Libevent windows
247 - The IOCP backend now works even when the user has not specified
248 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
249 Fixes part of bug 3752.
250 - Correctly record the bytes we've read and written when using
251 bufferevents, so that we can include them in our bandwidth history
252 and advertised bandwidth. Fixes bug 3803.
253 - Apply rate-limiting only at the bottom of a chain of filtering
254 bufferevents. This prevents us from filling up internal read
255 buffers and violating rate-limits when filtering bufferevents
256 are enabled. Fixes part of bug 3804.
257 - Add high-watermarks to the output buffers for filtered
258 bufferevents. This prevents us from filling up internal write
259 buffers and wasting CPU cycles when filtering bufferevents are
260 enabled. Fixes part of bug 3804.
261 - Correctly notice when data has been written from a bufferevent
262 without flushing it completely. Fixes bug 3805.
263 - Fix a bug where server-side tunneled bufferevent-based directory
264 streams would get closed prematurely. Fixes bug 3814.
265 - Fix a use-after-free error with per-connection rate-limiting
266 buckets. Fixes bug 3888.
268 o Major bugfixes (also part of 0.2.2.31-rc):
269 - If we're configured to write our ControlPorts to disk, only write
270 them after switching UID and creating the data directory. This way,
271 we don't fail when starting up with a nonexistent DataDirectory
272 and a ControlPortWriteToFile setting based on that directory. Fixes
273 bug 3747; bugfix on Tor 0.2.2.26-beta.
276 - Added a new CONF_CHANGED event so that controllers can be notified
277 of any configuration changes made by other controllers, or by the
278 user. Implements ticket 1692.
279 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
280 leak when using bufferevents, and lets Libevent worry about how to
281 best copy data out of a buffer.
282 - Replace files in stats/ rather than appending to them. Now that we
283 include statistics in extra-info descriptors, it makes no sense to
284 keep old statistics forever. Implements ticket 2930.
286 o Minor features (build compatibility):
287 - Limited, experimental support for building with nmake and MSVC.
288 - Provide a substitute implementation of lround() for MSVC, which
289 apparently lacks it. Patch from Gisle Vanem.
291 o Minor features (also part of 0.2.2.31-rc):
292 - Update to the August 2 2011 Maxmind GeoLite Country database.
294 o Minor bugfixes (on 0.2.3.x-alpha):
295 - Fix a spurious warning when parsing SOCKS requests with
296 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
297 - Get rid of a harmless warning that could happen on relays running
298 with bufferevents. The warning was caused by someone doing an http
299 request to a relay's orport. Also don't warn for a few related
300 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
302 o Minor bugfixes (on 2.2.x and earlier):
303 - Correct the man page to explain that HashedControlPassword and
304 CookieAuthentication can both be set, in which case either method
305 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
306 when we decided to allow these config options to both be set. Issue
308 - The "--quiet" and "--hush" options now apply not only to Tor's
309 behavior before logs are configured, but also to Tor's behavior in
310 the absense of configured logs. Fixes bug 3550; bugfix on
313 o Minor bugfixes (also part of 0.2.2.31-rc):
314 - Write several files in text mode, on OSes that distinguish text
315 mode from binary mode (namely, Windows). These files are:
316 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
317 that collect those statistics; 'client_keys' and 'hostname' for
318 hidden services that use authentication; and (in the tor-gencert
319 utility) newly generated identity and signing keys. Previously,
320 we wouldn't specify text mode or binary mode, leading to an
321 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
322 the DirRecordUsageByCountry option which would have triggered
323 the assertion failure was added), although this assertion failure
324 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
325 - Selectively disable deprecation warnings on OS X because Lion
326 started deprecating the shipped copy of openssl. Fixes bug 3643.
327 - Remove an extra pair of quotation marks around the error
328 message in control-port STATUS_GENERAL BUG events. Bugfix on
329 0.1.2.6-alpha; fixes bug 3732.
330 - When unable to format an address as a string, report its value
331 as "???" rather than reusing the last formatted address. Bugfix
334 o Code simplifications and refactoring:
335 - Rewrite the listener-selection logic so that parsing which ports
336 we want to listen on is now separate from binding to the ports
340 - Building Tor with bufferevent support now requires Libevent
341 2.0.13-stable or later. Previous versions of Libevent had bugs in
342 SSL-related bufferevents and related issues that would make Tor
343 work badly with bufferevents. Requiring 2.0.13-stable also allows
344 Tor with bufferevents to take advantage of Libevent APIs
345 introduced after 2.0.8-rc.
348 Changes in version 0.2.2.32 - 2011-08-27
349 The Tor 0.2.2 release series is dedicated to the memory of Andreas
350 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
351 a founder of the PETS community, a leader in our field, a mentor,
352 and a friend. He left us with these words: "I had the possibility
353 to contribute to this world that is not as it should be. I hope I
354 could help in some areas to make the world a better place, and that
355 I could also encourage other people to be engaged in improving the
356 world. Please, stay engaged. This world needs you, your love, your
357 initiative -- now I cannot be part of that anymore."
359 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
360 ready. More than two years in the making, this release features improved
361 client performance and hidden service reliability, better compatibility
362 for Android, correct behavior for bridges that listen on more than
363 one address, more extensible and flexible directory object handling,
364 better reporting of network statistics, improved code security, and
365 many many other features and bugfixes.
368 Changes in version 0.2.2.31-rc - 2011-08-17
369 Tor 0.2.2.31-rc is the second and hopefully final release candidate
370 for the Tor 0.2.2.x series.
373 - Remove an extra pair of quotation marks around the error
374 message in control-port STATUS_GENERAL BUG events. Bugfix on
375 0.1.2.6-alpha; fixes bug 3732.
376 - If we're configured to write our ControlPorts to disk, only write
377 them after switching UID and creating the data directory. This way,
378 we don't fail when starting up with a nonexistent DataDirectory
379 and a ControlPortWriteToFile setting based on that directory. Fixes
380 bug 3747; bugfix on Tor 0.2.2.26-beta.
383 - Update to the August 2 2011 Maxmind GeoLite Country database.
386 - Allow GETINFO fingerprint to return a fingerprint even when
387 we have not yet built a router descriptor. Fixes bug 3577;
388 bugfix on 0.2.0.1-alpha.
389 - Write several files in text mode, on OSes that distinguish text
390 mode from binary mode (namely, Windows). These files are:
391 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
392 that collect those statistics; 'client_keys' and 'hostname' for
393 hidden services that use authentication; and (in the tor-gencert
394 utility) newly generated identity and signing keys. Previously,
395 we wouldn't specify text mode or binary mode, leading to an
396 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
397 the DirRecordUsageByCountry option which would have triggered
398 the assertion failure was added), although this assertion failure
399 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
400 - Selectively disable deprecation warnings on OS X because Lion
401 started deprecating the shipped copy of openssl. Fixes bug 3643.
402 - When unable to format an address as a string, report its value
403 as "???" rather than reusing the last formatted address. Bugfix
407 Changes in version 0.2.3.2-alpha - 2011-07-18
408 Tor 0.2.3.2-alpha introduces two new experimental features:
409 microdescriptors and pluggable transports. It also continues cleaning
410 up a variety of recently introduced features.
413 - Clients can now use microdescriptors instead of regular descriptors
414 to build circuits. Microdescriptors are authority-generated
415 summaries of regular descriptors' contents, designed to change
416 very rarely (see proposal 158 for details). This feature is
417 designed to save bandwidth, especially for clients on slow internet
418 connections. It's off by default for now, since nearly no caches
419 support it, but it will be on-by-default for clients in a future
420 version. You can use the UseMicrodescriptors option to turn it on.
421 - Tor clients using bridges can now be configured to use a separate
422 'transport' proxy for each bridge. This approach helps to resist
423 censorship by allowing bridges to use protocol obfuscation
424 plugins. It implements part of proposal 180. Implements ticket 2841.
425 - While we're trying to bootstrap, record how many TLS connections
426 fail in each state, and report which states saw the most failures
427 in response to any bootstrap failures. This feature may speed up
428 diagnosis of censorship events. Implements ticket 3116.
430 o Major bugfixes (on 0.2.3.1-alpha):
431 - When configuring a large set of nodes in EntryNodes (as with
432 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
433 random subset to be guards, and choose them in random
434 order. Fixes bug 2798.
435 - Tor could crash when remembering a consensus in a non-used consensus
436 flavor without having a current consensus set. Fixes bug 3361.
437 - Comparing an unknown address to a microdescriptor's shortened exit
438 policy would always give a "rejected" result. Fixes bug 3599.
439 - Using microdescriptors as a client no longer prevents Tor from
440 uploading and downloading hidden service descriptors. Fixes
444 - Allow nameservers with IPv6 address. Resolves bug 2574.
445 - Accept attempts to include a password authenticator in the
446 handshake, as supported by SOCKS5. This handles SOCKS clients that
447 don't know how to omit a password when authenticating. Resolves
449 - When configuring a large set of nodes in EntryNodes, and there are
450 enough of them listed as Guard so that we don't need to consider
451 the non-guard entries, prefer the ones listed with the Guard flag.
452 - Check for and recover from inconsistency in the microdescriptor
453 cache. This will make it harder for us to accidentally free a
454 microdescriptor without removing it from the appropriate data
455 structures. Fixes issue 3135; issue noted by "wanoskarnet".
456 - Log SSL state transitions at log level DEBUG, log domain
457 HANDSHAKE. This can be useful for debugging censorship events.
458 Implements ticket 3264.
459 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
460 implements ticket 3439.
462 o Minor bugfixes (on 0.2.3.1-alpha):
463 - Do not free all general-purpose regular descriptors just
464 because microdescriptor use is enabled. Fixes bug 3113.
465 - Correctly link libevent_openssl when --enable-static-libevent
466 is passed to configure. Fixes bug 3118.
467 - Bridges should not complain during their heartbeat log messages that
468 they are unlisted in the consensus: that's more or less the point
469 of being a bridge. Fixes bug 3183.
470 - Report a SIGNAL event to controllers when acting on a delayed
471 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
472 event to the controller if we acted on a SIGNAL NEWNYM command
473 immediately, and otherwise not report a SIGNAL event for the
474 command at all. Fixes bug 3349.
475 - Fix a crash when handling the SIGNAL controller command or
476 reporting ERR-level status events with bufferevents enabled. Found
477 by Robert Ransom. Fixes bug 3367.
478 - Always ship the tor-fw-helper manpage in our release tarballs.
479 Fixes bug 3389. Reported by Stephen Walker.
480 - Fix a class of double-mark-for-close bugs when bufferevents
481 are enabled. Fixes bug 3403.
482 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
483 - Add SIGNAL to the list returned by the 'GETINFO events/names'
484 control-port command. Fixes part of bug 3465.
485 - Prevent using negative indices during unit test runs when read_all()
486 fails. Spotted by coverity.
487 - Fix a rare memory leak when checking the nodelist without it being
488 present. Found by coverity.
489 - Only try to download a microdescriptor-flavored consensus from
490 a directory cache that provides them.
492 o Minor bugfixes (on 0.2.2.x and earlier):
493 - Assert that hidden-service-related operations are not performed
494 using single-hop circuits. Previously, Tor would assert that
495 client-side streams are not attached to single-hop circuits,
496 but not that other sensitive operations on the client and service
497 side are not performed using single-hop circuits. Fixes bug 3332;
499 - Don't publish a new relay descriptor when we reload our onion key,
500 unless the onion key has actually changed. Fixes bug 3263 and
501 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
502 - Allow GETINFO fingerprint to return a fingerprint even when
503 we have not yet built a router descriptor. Fixes bug 3577;
504 bugfix on 0.2.0.1-alpha.
505 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
506 on 0.2.2.4-alpha; fixes bug 3427.
508 o Code simplification and refactoring:
509 - Use tor_sscanf() in place of scanf() in more places through the
510 code. This makes us a little more locale-independent, and
511 should help shut up code-analysis tools that can't tell
512 a safe sscanf string from a dangerous one.
513 - Use tt_assert(), not tor_assert(), for checking for test failures.
514 This makes the unit tests more able to go on in the event that
516 - Split connection_about_to_close() into separate functions for each
520 - On Windows, we now define the _WIN32_WINNT macros only if they
521 are not already defined. This lets the person building Tor decide,
522 if they want, to require a later version of Windows.
525 Changes in version 0.2.2.30-rc - 2011-07-07
526 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
527 series. It fixes a few smaller bugs, but generally appears stable.
528 Please test it and let us know whether it is!
531 - Send a SUCCEEDED stream event to the controller when a reverse
532 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
533 discovered by katmagic.
534 - Always NUL-terminate the sun_path field of a sockaddr_un before
535 passing it to the kernel. (Not a security issue: kernels are
536 smart enough to reject bad sockaddr_uns.) Found by Coverity;
537 CID #428. Bugfix on Tor 0.2.0.3-alpha.
538 - Don't stack-allocate the list of supplementary GIDs when we're
539 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
540 could take up to 256K, which is way too much stack. Found by
541 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
542 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
543 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
544 fixes part of bug 3465.
545 - Fix a memory leak when receiving a descriptor for a hidden
546 service we didn't ask for. Found by Coverity; CID #30. Bugfix
550 - Update to the July 1 2011 Maxmind GeoLite Country database.
553 Changes in version 0.2.2.29-beta - 2011-06-20
554 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
555 have bridge lines in their torrc but don't want to use them; gets
556 us closer to having the control socket feature working on Debian;
557 and fixes a variety of smaller bugs.
560 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
561 When we changed the default behavior to "use bridges if any
562 are listed in the torrc", we surprised users who had bridges
563 in their torrc files but who didn't actually want to use them.
564 Partial resolution for bug 3354.
567 - Don't attach new streams to old rendezvous circuits after SIGNAL
568 NEWNYM. Previously, we would keep using an existing rendezvous
569 circuit if it remained open (i.e. if it were kept open by a
570 long-lived stream, or if a new stream were attached to it before
571 Tor could notice that it was old and no longer in use). Bugfix on
572 0.1.1.15-rc; fixes bug 3375.
575 - Fix a bug when using ControlSocketsGroupWritable with User. The
576 directory's group would be checked against the current group, not
577 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
578 bugfix on 0.2.2.26-beta.
579 - Make connection_printf_to_buf()'s behaviour sane. Its callers
580 expect it to emit a CRLF iff the format string ends with CRLF;
581 it actually emitted a CRLF iff (a) the format string ended with
582 CRLF or (b) the resulting string was over 1023 characters long or
583 (c) the format string did not end with CRLF *and* the resulting
584 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
585 fixes part of bug 3407.
586 - Make send_control_event_impl()'s behaviour sane. Its callers
587 expect it to always emit a CRLF at the end of the string; it
588 might have emitted extra control characters as well. Bugfix on
589 0.1.1.9-alpha; fixes another part of bug 3407.
590 - Make crypto_rand_int() check the value of its input correctly.
591 Previously, it accepted values up to UINT_MAX, but could return a
592 negative number if given a value above INT_MAX+1. Found by George
593 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
594 - Avoid a segfault when reading a malformed circuit build state
595 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
597 - When asked about a DNS record type we don't support via a
598 client DNSPort, reply with NOTIMPL rather than an empty
599 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
600 - Fix a rare memory leak during stats writing. Found by coverity.
603 - Update to the June 1 2011 Maxmind GeoLite Country database.
605 o Code simplifications and refactoring:
606 - Remove some dead code as indicated by coverity.
607 - Remove a few dead assignments during router parsing. Found by
609 - Add some forgotten return value checks during unit tests. Found
611 - Don't use 1-bit wide signed bit fields. Found by coverity.
614 Changes in version 0.2.2.28-beta - 2011-06-04
615 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
616 fixed a big bug in whether relays stay in the consensus consistently,
617 we moved closer to handling bridges and hidden services correctly,
618 and we started the process of better handling the dreaded "my Vidalia
619 died, and now my Tor demands a password when I try to reconnect to it"
623 - Don't decide to make a new descriptor when receiving a HUP signal.
624 This bug has caused a lot of 0.2.2.x relays to disappear from the
625 consensus periodically. Fixes the most common case of triggering
626 bug 1810; bugfix on 0.2.2.7-alpha.
627 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
628 - Don't try to build descriptors if "ORPort auto" is set and we
629 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
631 - Resolve a crash that occurred when setting BridgeRelay to 1 with
632 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
633 - Apply circuit timeouts to opened hidden-service-related circuits
634 based on the correct start time. Previously, we would apply the
635 circuit build timeout based on time since the circuit's creation;
636 it was supposed to be applied based on time since the circuit
637 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
638 - Use the same circuit timeout for client-side introduction
639 circuits as for other four-hop circuits, rather than the timeout
640 for single-hop directory-fetch circuits; the shorter timeout may
641 have been appropriate with the static circuit build timeout in
642 0.2.1.x and earlier, but caused many hidden service access attempts
643 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
644 on 0.2.2.2-alpha; fixes another part of bug 1297.
645 - In ticket 2511 we fixed a case where you could use an unconfigured
646 bridge if you had configured it as a bridge the last time you ran
647 Tor. Now fix another edge case: if you had configured it as a bridge
648 but then switched to a different bridge via the controller, you
649 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
653 - Add an __OwningControllerProcess configuration option and a
654 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
655 that when it exits, Tor will shut down. Implements feature 3049.
656 - If "UseBridges 1" is set and no bridges are configured, Tor will
657 now refuse to build any circuits until some bridges are set.
658 If "UseBridges auto" is set, Tor will use bridges if they are
659 configured and we are not running as a server, but otherwise will
660 make circuits as usual. The new default is "auto". Patch by anonym,
661 so the Tails LiveCD can stop automatically revealing you as a Tor
665 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
666 - Remove a trailing asterisk from "exit-policy/default" in the
667 output of the control port command "GETINFO info/names". Bugfix
669 - Use a wide type to hold sockets when built for 64-bit Windows builds.
671 - Warn when the user configures two HiddenServiceDir lines that point
672 to the same directory. Bugfix on 0.0.6 (the version introducing
673 HiddenServiceDir); fixes bug 3289.
674 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
675 part of bug 2748; bugfix on 0.2.0.10-alpha.
676 - Log malformed requests for rendezvous descriptors as protocol
677 warnings, not warnings. Also, use a more informative log message
678 in case someone sees it at log level warning without prior
679 info-level messages. Fixes the other part of bug 2748; bugfix
681 - Clear the table recording the time of the last request for each
682 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
683 Previously, we would clear our HS descriptor cache on SIGNAL
684 NEWNYM, but if we had previously retrieved a descriptor (or tried
685 to) from every directory responsible for it, we would refuse to
686 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
688 - Fix a log message that said "bits" while displaying a value in
689 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
691 - When checking for 1024-bit keys, check for 1024 bits, not 128
692 bytes. This allows Tor to correctly discard keys of length 1017
693 through 1023. Bugfix on 0.0.9pre5.
696 - Relays now log the reason for publishing a new relay descriptor,
697 so we have a better chance of hunting down instances of bug 1810.
698 Resolves ticket 3252.
699 - Revise most log messages that refer to nodes by nickname to
700 instead use the "$key=nickname at address" format. This should be
701 more useful, especially since nicknames are less and less likely
702 to be unique. Resolves ticket 3045.
703 - Log (at info level) when purging pieces of hidden-service-client
704 state because of SIGNAL NEWNYM.
707 - Remove undocumented option "-F" from tor-resolve: it hasn't done
708 anything since 0.2.1.16-rc.
711 Changes in version 0.2.2.27-beta - 2011-05-18
712 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
713 release, and also adds a few more general bugfixes.
716 - Fix a crash bug when changing bridges in a running Tor process.
717 Fixes bug 3213; bugfix on 0.2.2.26-beta.
718 - When the controller configures a new bridge, don't wait 10 to 60
719 seconds before trying to fetch its descriptor. Bugfix on
720 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
723 - Require that onion keys have exponent 65537 in microdescriptors too.
724 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
725 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
726 Changed the limit to 512 characters by removing base64 newlines.
727 Fixes bug 2752. Fix by Michael Yakubovich.
728 - When a client starts or stops using bridges, never use a circuit
729 that was built before the configuration change. This behavior could
730 put at risk a user who uses bridges to ensure that her traffic
731 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
735 Changes in version 0.2.2.26-beta - 2011-05-17
736 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
737 also introduces a new "socksport auto" approach that should make it
738 easier to run multiple Tors on the same system, and does a lot of
739 cleanup to get us closer to a release candidate.
741 o Security/privacy fixes:
742 - Replace all potentially sensitive memory comparison operations
743 with versions whose runtime does not depend on the data being
744 compared. This will help resist a class of attacks where an
745 adversary can use variations in timing information to learn
746 sensitive data. Fix for one case of bug 3122. (Safe memcmp
747 implementation by Robert Ransom based partially on code by DJB.)
748 - When receiving a hidden service descriptor, check that it is for
749 the hidden service we wanted. Previously, Tor would store any
750 hidden service descriptors that a directory gave it, whether it
751 wanted them or not. This wouldn't have let an attacker impersonate
752 a hidden service, but it did let directories pre-seed a client
753 with descriptors that it didn't want. Bugfix on 0.0.6.
754 - On SIGHUP, do not clear out all TrackHostExits mappings, client
755 DNS cache entries, and virtual address mappings: that's what
756 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
759 - The options SocksPort, ControlPort, and so on now all accept a
760 value "auto" that opens a socket on an OS-selected port. A
761 new ControlPortWriteToFile option tells Tor to write its
762 actual control port or ports to a chosen file. If the option
763 ControlPortFileGroupReadable is set, the file is created as
764 group-readable. Now users can run two Tor clients on the same
765 system without needing to manually mess with parameters. Resolves
767 - Set SO_REUSEADDR on all sockets, not just listeners. This should
768 help busy exit nodes avoid running out of useable ports just
769 because all the ports have been used in the near past. Resolves
773 - New "GETINFO net/listeners/(type)" controller command to return
774 a list of addresses and ports that are bound for listeners for a
775 given connection type. This is useful when the user has configured
776 "SocksPort auto" and the controller needs to know which port got
777 chosen. Resolves another part of ticket 3076.
778 - Add a new ControlSocketsGroupWritable configuration option: when
779 it is turned on, ControlSockets are group-writeable by the default
780 group of the current user. Patch by Jérémy Bobbio; implements
782 - Tor now refuses to create a ControlSocket in a directory that is
783 world-readable (or group-readable if ControlSocketsGroupWritable
784 is 0). This is necessary because some operating systems do not
785 enforce permissions on an AF_UNIX sockets. Permissions on the
786 directory holding the socket, however, seems to work everywhere.
787 - Rate-limit a warning about failures to download v2 networkstatus
788 documents. Resolves part of bug 1352.
789 - Backport code from 0.2.3.x that allows directory authorities to
790 clean their microdescriptor caches. Needed to resolve bug 2230.
791 - When an HTTPS proxy reports "403 Forbidden", we now explain
792 what it means rather than calling it an unexpected status code.
793 Closes bug 2503. Patch from Michael Yakubovich.
794 - Update to the May 1 2011 Maxmind GeoLite Country database.
797 - Authorities now clean their microdesc cache periodically and when
798 reading from disk initially, not only when adding new descriptors.
799 This prevents a bug where we could lose microdescriptors. Bugfix
800 on 0.2.2.6-alpha. Fixes bug 2230.
801 - Do not crash when our configuration file becomes unreadable, for
802 example due to a permissions change, between when we start up
803 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
805 - Avoid a bug that would keep us from replacing a microdescriptor
806 cache on Windows. (We would try to replace the file while still
807 holding it open. That's fine on Unix, but Windows doesn't let us
808 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
809 - Add missing explanations for the authority-related torrc options
810 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
811 man page. Resolves issue 2379.
812 - As an authority, do not upload our own vote or signature set to
813 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
814 it would get flagged as a duplicate. Resolves bug 3026.
815 - Accept hidden service descriptors if we think we might be a hidden
816 service directory, regardless of what our consensus says. This
817 helps robustness, since clients and hidden services can sometimes
818 have a more up-to-date view of the network consensus than we do,
819 and if they think that the directory authorities list us a HSDir,
820 we might actually be one. Related to bug 2732; bugfix on
822 - When a controller changes TrackHostExits, remove mappings for
823 hosts that should no longer have their exits tracked. Bugfix on
825 - When a controller changes VirtualAddrNetwork, remove any mappings
826 for hosts that were automapped to the old network. Bugfix on
828 - When a controller changes one of the AutomapHosts* options, remove
829 any mappings for hosts that should no longer be automapped. Bugfix
831 - Do not reset the bridge descriptor download status every time we
832 re-parse our configuration or get a configuration change. Fixes
833 bug 3019; bugfix on 0.2.0.3-alpha.
835 o Minor bugfixes (code cleanup):
836 - When loading the microdesc journal, remember its current size.
837 In 0.2.2, this helps prevent the microdesc journal from growing
838 without limit on authorities (who are the only ones to use it in
839 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
840 Fix posted by "cypherpunks."
841 - The microdesc journal is supposed to get rebuilt only if it is
842 at least _half_ the length of the store, not _twice_ the length
843 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
844 - Fix a potential null-pointer dereference while computing a
845 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
847 - Avoid a possible null-pointer dereference when rebuilding the mdesc
848 cache without actually having any descriptors to cache. Bugfix on
849 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
850 - If we fail to compute the identity digest of a v3 legacy keypair,
851 warn, and don't use a buffer-full of junk instead. Bugfix on
852 0.2.1.1-alpha; fixes bug 3106.
853 - Resolve an untriggerable issue in smartlist_string_num_isin(),
854 where if the function had ever in the future been used to check
855 for the presence of a too-large number, it would have given an
856 incorrect result. (Fortunately, we only used it for 16-bit
857 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
858 - Require that introduction point keys and onion handshake keys
859 have a public exponent of 65537. Starts to fix bug 3207; bugfix
863 - Caches no longer download and serve v2 networkstatus documents
864 unless FetchV2Networkstatus flag is set: these documents haven't
865 haven't been used by clients or relays since 0.2.0.x. Resolves
869 Changes in version 0.2.3.1-alpha - 2011-05-05
870 Tor 0.2.3.1-alpha adds some new experimental features, including support
871 for an improved network IO backend, IOCP networking on Windows,
872 microdescriptor caching, "fast-start" support for streams, and automatic
873 home router configuration. There are also numerous internal improvements
874 to try to make the code easier for developers to work with.
876 This is the first alpha release in a new series, so expect there to be
877 bugs. Users who would rather test out a more stable branch should
878 stay with 0.2.2.x for now.
881 - Tor can now optionally build with the "bufferevents" buffered IO
882 backend provided by Libevent 2. To use this feature, make sure you
883 have the latest possible version of Libevent, and pass the
884 --enable-bufferevents flag to configure when building Tor from
885 source. This feature will make our networking code more flexible,
886 let us stack layers on each other, and let us use more efficient
887 zero-copy transports where available.
888 - As an experimental feature, Tor can use IOCP for networking on Windows.
889 Once this code is tuned and optimized, it promises much better
890 performance than the select-based backend we've used in the past. To
891 try this feature, you must build Tor with Libevent 2, configure Tor
892 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
893 your torrc. There are known bugs here: only try this if you can help
894 debug it as it breaks.
895 - The EntryNodes option can now include country codes like {de} or IP
896 addresses or network masks. Previously we had disallowed these options
897 because we didn't have an efficient way to keep the list up to
898 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
899 - Exit nodes now accept and queue data on not-yet-connected streams.
900 Previously, the client wasn't allowed to send data until the stream was
901 connected, which slowed down all connections. This change will enable
902 clients to perform a "fast-start" on streams and send data without
903 having to wait for a confirmation that the stream has opened. (Patch
904 from Ian Goldberg; implements the server side of Proposal 174.)
905 - Tor now has initial support for automatic port mapping on the many
906 home routers that support NAT-PMP or UPnP. (Not yet supported on
907 Windows). To build the support code, you'll need to have libnatpnp
908 library and/or the libminiupnpc library, and you'll need to enable the
909 feature specifically by passing "--enable-upnp" and/or
910 "--enable-natpnp" to configure. To turn it on, use the new
911 PortForwarding option.
912 - Caches now download, cache, and serve multiple "flavors" of the
913 consensus, including a flavor that describes microdescriptors.
914 - Caches now download, cache, and serve microdescriptors -- small
915 summaries of router descriptors that are authenticated by all of the
916 directory authorities. Once enough caches are running this code,
917 clients will be able to save significant amounts of directory bandwidth
918 by downloading microdescriptors instead of router descriptors.
921 - Make logging resolution configurable with a new LogTimeGranularity
922 option, and change the default from 1 millisecond to 1 second.
923 Implements enhancement 1668.
924 - We log which torrc file we're using on startup. Implements ticket
926 - Ordinarily, Tor does not count traffic from private addresses (like
927 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
928 There is now a new option, CountPrivateBandwidth, to disable this
929 behavior. Patch from Daniel Cagara.
930 - New --enable-static-tor configure option for building Tor as
931 statically as possible. Idea, general hackery and thoughts from
932 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
934 - If you set the NumCPUs option to 0, Tor will now try to detect how
935 many CPUs you have. This is the new default behavior.
936 - Turn on directory request statistics by default and include them in
937 extra-info descriptors. Don't break if we have no GeoIP database.
938 - Relays that set "ConnDirectionStatistics 1" write statistics on the
939 bidirectional use of connections to disk every 24 hours.
940 - Add a GeoIP file digest to the extra-info descriptor. Implements
942 - The NodeFamily option -- which let you declare that you want to
943 consider nodes to be part of a family whether they list themselves
944 that way or not -- now allows IP address ranges and country codes.
945 - Add a new 'Heartbeat' log message type to periodically log a message
946 describing Tor's status at level Notice. This feature is meant for
947 operators who log at notice, and want to make sure that their Tor
948 server is still working. Implementation by George Kadianakis.
950 o Minor bugfixes (on 0.2.2.25-alpha):
951 - When loading the microdesc journal, remember its current size.
952 In 0.2.2, this helps prevent the microdesc journal from growing
953 without limit on authorities (who are the only ones to use it in
954 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
955 Fix posted by "cypherpunks."
956 - The microdesc journal is supposed to get rebuilt only if it is
957 at least _half_ the length of the store, not _twice_ the length
958 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
959 - If as an authority we fail to compute the identity digest of a v3
960 legacy keypair, warn, and don't use a buffer-full of junk instead.
961 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
962 - Authorities now clean their microdesc cache periodically and when
963 reading from disk initially, not only when adding new descriptors.
964 This prevents a bug where we could lose microdescriptors. Bugfix
967 o Minor features (controller):
968 - Add a new SIGNAL event to the controller interface so that
969 controllers can be notified when Tor handles a signal. Resolves
970 issue 1955. Patch by John Brooks.
971 - Add a new GETINFO option to get total bytes read and written. Patch
972 from pipe, revised by atagar. Resolves ticket 2345.
973 - Implement some GETINFO controller fields to provide information about
974 the Tor process's pid, euid, username, and resource limits.
977 - Our build system requires automake 1.6 or later to create the
978 Makefile.in files. Previously, you could have used 1.4.
979 This only affects developers and people building Tor from git;
980 people who build Tor from the source distribution without changing
981 the Makefile.am files should be fine.
982 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
983 so on. This is more robust against some of the failure modes
984 associated with running the autotools pieces on their own.
986 o Minor packaging issues:
987 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
988 already created. Patch from Andreas Stieger. Fixes bug 2573.
990 o Code simplifications and refactoring:
991 - A major revision to our internal node-selecting and listing logic.
992 Tor already had at least two major ways to look at the question of
993 "which Tor servers do we know about": a list of router descriptors,
994 and a list of entries in the current consensus. With
995 microdescriptors, we're adding a third. Having so many systems
996 without an abstraction layer over them was hurting the codebase.
997 Now, we have a new "node_t" abstraction that presents a consistent
998 interface to a client's view of a Tor node, and holds (nearly) all
999 of the mutable state formerly in routerinfo_t and routerstatus_t.
1000 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
1001 no longer link against Libevent: they never used it, but
1002 our library structure used to force them to link it.
1005 - Remove some old code to work around even older versions of Tor that
1006 used forked processes to handle DNS requests. Such versions of Tor
1007 are no longer in use as servers.
1009 o Documentation fixes:
1010 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
1011 - Add missing documentation for the authority-related torrc options
1012 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
1016 Changes in version 0.2.2.25-alpha - 2011-04-29
1017 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
1018 robust, routers no longer overreport their bandwidth, Win7 should crash
1019 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
1020 now prevents hidden service-related activity from being linkable. It
1021 provides more information to Vidalia so you can see if your bridge is
1022 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
1023 StrictNodes configuration options to make them more reliable, more
1024 understandable, and more regularly applied. If you use those options,
1025 please see the revised documentation for them in the manual page.
1028 - Relays were publishing grossly inflated bandwidth values because
1029 they were writing their state files wrong--now they write the
1030 correct value. Also, resume reading bandwidth history from the
1031 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
1032 - Improve hidden service robustness: When we find that we have
1033 extended a hidden service's introduction circuit to a relay not
1034 listed as an introduction point in the HS descriptor we currently
1035 have, retry with an introduction point from the current
1036 descriptor. Previously we would just give up. Fixes bugs 1024 and
1037 1930; bugfix on 0.2.0.10-alpha.
1038 - Clients now stop trying to use an exit node associated with a given
1039 destination by TrackHostExits if they fail to reach that exit node.
1040 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
1041 - Fix crash bug on platforms where gmtime and localtime can return
1042 NULL. Windows 7 users were running into this one. Fixes part of bug
1043 2077. Bugfix on all versions of Tor. Found by boboper.
1045 o Security and stability fixes:
1046 - Don't double-free a parsable, but invalid, microdescriptor, even if
1047 it is followed in the blob we're parsing by an unparsable
1048 microdescriptor. Fixes an issue reported in a comment on bug 2954.
1049 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
1050 - If the Nickname configuration option isn't given, Tor would pick a
1051 nickname based on the local hostname as the nickname for a relay.
1052 Because nicknames are not very important in today's Tor and the
1053 "Unnamed" nickname has been implemented, this is now problematic
1054 behavior: It leaks information about the hostname without being
1055 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
1056 introduced the Unnamed nickname. Reported by tagnaq.
1057 - Fix an uncommon assertion failure when running with DNSPort under
1058 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1059 - Avoid linkability based on cached hidden service descriptors: forget
1060 all hidden service descriptors cached as a client when processing a
1061 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1064 - Export GeoIP information on bridge usage to controllers even if we
1065 have not yet been running for 24 hours. Now Vidalia bridge operators
1066 can get more accurate and immediate feedback about their
1067 contributions to the network.
1069 o Major features and bugfixes (node selection):
1070 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
1071 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
1072 options. Previously, we had been ambiguous in describing what
1073 counted as an "exit" node, and what operations exactly "StrictNodes
1074 0" would permit. This created confusion when people saw nodes built
1075 through unexpected circuits, and made it hard to tell real bugs from
1076 surprises. Now the intended behavior is:
1077 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
1078 a node that delivers user traffic outside the Tor network.
1079 . "Entry", in the context of EntryNodes, means a node used as the
1080 first hop of a multihop circuit. It doesn't include direct
1081 connections to directory servers.
1082 . "ExcludeNodes" applies to all nodes.
1083 . "StrictNodes" changes the behavior of ExcludeNodes only. When
1084 StrictNodes is set, Tor should avoid all nodes listed in
1085 ExcludeNodes, even when it will make user requests fail. When
1086 StrictNodes is *not* set, then Tor should follow ExcludeNodes
1087 whenever it can, except when it must use an excluded node to
1088 perform self-tests, connect to a hidden service, provide a
1089 hidden service, fulfill a .exit request, upload directory
1090 information, or fetch directory information.
1091 Collectively, the changes to implement the behavior fix bug 1090.
1092 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
1093 a node is listed in both, it's treated as excluded.
1094 - ExcludeNodes now applies to directory nodes -- as a preference if
1095 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
1096 Don't exclude all the directory authorities and set StrictNodes to 1
1097 unless you really want your Tor to break.
1098 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
1099 - ExcludeExitNodes now overrides .exit requests.
1100 - We don't use bridges listed in ExcludeNodes.
1101 - When StrictNodes is 1:
1102 . We now apply ExcludeNodes to hidden service introduction points
1103 and to rendezvous points selected by hidden service users. This
1104 can make your hidden service less reliable: use it with caution!
1105 . If we have used ExcludeNodes on ourself, do not try relay
1106 reachability self-tests.
1107 . If we have excluded all the directory authorities, we will not
1108 even try to upload our descriptor if we're a relay.
1109 . Do not honor .exit requests to an excluded node.
1110 - Remove a misfeature that caused us to ignore the Fast/Stable flags
1111 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
1112 - When the set of permitted nodes changes, we now remove any mappings
1113 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
1115 - We never cannibalize a circuit that had excluded nodes on it, even
1116 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
1117 - Revert a change where we would be laxer about attaching streams to
1118 circuits than when building the circuits. This was meant to prevent
1119 a set of bugs where streams were never attachable, but our improved
1120 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
1121 - Keep track of how many times we launch a new circuit to handle a
1122 given stream. Too many launches could indicate an inconsistency
1123 between our "launch a circuit to handle this stream" logic and our
1124 "attach this stream to one of the available circuits" logic.
1125 - Improve log messages related to excluded nodes.
1128 - Fix a spurious warning when moving from a short month to a long
1129 month on relays with month-based BandwidthAccounting. Bugfix on
1130 0.2.2.17-alpha; fixes bug 3020.
1131 - When a client finds that an origin circuit has run out of 16-bit
1132 stream IDs, we now mark it as unusable for new streams. Previously,
1133 we would try to close the entire circuit. Bugfix on 0.0.6.
1134 - Add a forgotten cast that caused a compile warning on OS X 10.6.
1135 Bugfix on 0.2.2.24-alpha.
1136 - Be more careful about reporting the correct error from a failed
1137 connect() system call. Under some circumstances, it was possible to
1138 look at an incorrect value for errno when sending the end reason.
1139 Bugfix on 0.1.0.1-rc.
1140 - Correctly handle an "impossible" overflow cases in connection byte
1141 counting, where we write or read more than 4GB on an edge connection
1142 in a single second. Bugfix on 0.1.2.8-beta.
1143 - Correct the warning displayed when a rendezvous descriptor exceeds
1144 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1146 - Clients and hidden services now use HSDir-flagged relays for hidden
1147 service descriptor downloads and uploads even if the relays have no
1148 DirPort set and the client has disabled TunnelDirConns. This will
1149 eventually allow us to give the HSDir flag to relays with no
1150 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
1151 - Downgrade "no current certificates known for authority" message from
1152 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
1153 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
1154 2917. Bugfix on 0.1.1.1-alpha.
1155 - Only limit the lengths of single HS descriptors, even when multiple
1156 HS descriptors are published to an HSDir relay in a single POST
1157 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
1158 - Write the current time into the LastWritten line in our state file,
1159 rather than the time from the previous write attempt. Also, stop
1160 trying to use a time of -1 in our log statements. Fixes bug 3039;
1161 bugfix on 0.2.2.14-alpha.
1162 - Be more consistent in our treatment of file system paths. "~" should
1163 get expanded to the user's home directory in the Log config option.
1164 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
1165 feature for the -f and --DataDirectory options.
1168 - Make sure every relay writes a state file at least every 12 hours.
1169 Previously, a relay could go for weeks without writing its state
1170 file, and on a crash could lose its bandwidth history, capacity
1171 estimates, client country statistics, and so on. Addresses bug 3012.
1172 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
1173 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
1174 clients are already deprecated because of security bugs.
1175 - Don't allow v0 hidden service authorities to act as clients.
1176 Required by fix for bug 3000.
1177 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
1178 by fix for bug 3000.
1179 - Ensure that no empty [dirreq-](read|write)-history lines are added
1180 to an extrainfo document. Implements ticket 2497.
1182 o Code simplification and refactoring:
1183 - Remove workaround code to handle directory responses from servers
1184 that had bug 539 (they would send HTTP status 503 responses _and_
1185 send a body too). Since only server versions before
1186 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
1187 keep the workaround in place.
1188 - Remove the old 'fuzzy time' logic. It was supposed to be used for
1189 handling calculations where we have a known amount of clock skew and
1190 an allowed amount of unknown skew. But we only used it in three
1191 places, and we never adjusted the known/unknown skew values. This is
1192 still something we might want to do someday, but if we do, we'll
1193 want to do it differently.
1194 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1195 None of the cases where we did this before were wrong, but by making
1196 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1197 - Use GetTempDir to find the proper temporary directory location on
1198 Windows when generating temporary files for the unit tests. Patch by
1202 Changes in version 0.2.2.24-alpha - 2011-04-08
1203 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
1204 prevented Tor clients from effectively using "multihomed" bridges,
1205 that is, bridges that listen on multiple ports or IP addresses so users
1206 can continue to use some of their addresses even if others get blocked.
1209 - Fix a bug where bridge users who configure the non-canonical
1210 address of a bridge automatically switch to its canonical
1211 address. If a bridge listens at more than one address, it should be
1212 able to advertise those addresses independently and any non-blocked
1213 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
1215 - If you configured Tor to use bridge A, and then quit and
1216 configured Tor to use bridge B instead, it would happily continue
1217 to use bridge A if it's still reachable. While this behavior is
1218 a feature if your goal is connectivity, in some scenarios it's a
1219 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
1220 - Directory authorities now use data collected from their own
1221 uptime observations when choosing whether to assign the HSDir flag
1222 to relays, instead of trusting the uptime value the relay reports in
1223 its descriptor. This change helps prevent an attack where a small
1224 set of nodes with frequently-changing identity keys can blackhole
1225 a hidden service. (Only authorities need upgrade; others will be
1226 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
1229 - When we restart our relay, we might get a successful connection
1230 from the outside before we've started our reachability tests,
1231 triggering a warning: "ORPort found reachable, but I have no
1232 routerinfo yet. Failing to inform controller of success." This
1233 bug was harmless unless Tor is running under a controller
1234 like Vidalia, in which case the controller would never get a
1235 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1237 - Make directory authorities more accurate at recording when
1238 relays that have failed several reachability tests became
1239 unreachable, so we can provide more accuracy at assigning Stable,
1240 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
1241 - Fix an issue that prevented static linking of libevent on
1242 some platforms (notably Linux). Fixes bug 2698; bugfix on
1243 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
1244 the --with-static-libevent configure option).
1245 - We now ask the other side of a stream (the client or the exit)
1246 for more data on that stream when the amount of queued data on
1247 that stream dips low enough. Previously, we wouldn't ask the
1248 other side for more data until either it sent us more data (which
1249 it wasn't supposed to do if it had exhausted its window!) or we
1250 had completely flushed all our queued data. This flow control fix
1251 should improve throughput. Fixes bug 2756; bugfix on the earliest
1252 released versions of Tor (svn commit r152).
1253 - Avoid a double-mark-for-free warning when failing to attach a
1254 transparent proxy connection. (We thought we had fixed this in
1255 0.2.2.23-alpha, but it turns out our fix was checking the wrong
1256 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
1257 bug) and 0.2.2.23-alpha (the incorrect fix).
1258 - When warning about missing zlib development packages during compile,
1259 give the correct package names. Bugfix on 0.2.0.1-alpha.
1262 - Directory authorities now log the source of a rejected POSTed v3
1264 - Make compilation with clang possible when using
1265 --enable-gcc-warnings by removing two warning options that clang
1266 hasn't implemented yet and by fixing a few warnings. Implements
1268 - When expiring circuits, use microsecond timers rather than
1269 one-second timers. This can avoid an unpleasant situation where a
1270 circuit is launched near the end of one second and expired right
1271 near the beginning of the next, and prevent fluctuations in circuit
1273 - Use computed circuit-build timeouts to decide when to launch
1274 parallel introduction circuits for hidden services. (Previously,
1275 we would retry after 15 seconds.)
1276 - Update to the April 1 2011 Maxmind GeoLite Country database.
1279 - Create the /var/run/tor directory on startup on OpenSUSE if it is
1280 not already created. Patch from Andreas Stieger. Fixes bug 2573.
1282 o Documentation changes:
1283 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
1284 - Resolve all doxygen warnings except those for missing documentation.
1286 - Add doxygen documentation for more functions, fields, and types.
1289 Changes in version 0.2.2.23-alpha - 2011-03-08
1290 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
1291 they restart they don't lose their bandwidth capacity estimate. This
1292 release also fixes a diverse set of user-facing bugs, ranging from
1293 relays overrunning their rate limiting to clients falsely warning about
1294 clock skew to bridge descriptor leaks by our bridge directory authority.
1297 - Stop sending a CLOCK_SKEW controller status event whenever
1298 we fetch directory information from a relay that has a wrong clock.
1299 Instead, only inform the controller when it's a trusted authority
1300 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
1301 the rest of bug 1074.
1302 - Fix an assert in parsing router descriptors containing IPv6
1303 addresses. This one took down the directory authorities when
1304 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1305 - Make the bridge directory authority refuse to answer directory
1306 requests for "all" descriptors. It used to include bridge
1307 descriptors in its answer, which was a major information leak.
1308 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1309 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
1310 Tor would ignore their RelayBandwidthBurst setting,
1311 potentially using more bandwidth than expected. Bugfix on
1312 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
1313 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
1314 hidserv" in her torrc. The 'hidserv' argument never controlled
1315 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
1318 - Relays now save observed peak bandwidth throughput rates to their
1319 state file (along with total usage, which was already saved)
1320 so that they can determine their correct estimated bandwidth on
1321 restart. Resolves bug 1863, where Tor relays would reset their
1322 estimated bandwidth to 0 after restarting.
1323 - Directory authorities now take changes in router IP address and
1324 ORPort into account when determining router stability. Previously,
1325 if a router changed its IP or ORPort, the authorities would not
1326 treat it as having any downtime for the purposes of stability
1327 calculation, whereas clients would experience downtime since the
1328 change could take a while to propagate to them. Resolves issue 1035.
1329 - Enable Address Space Layout Randomization (ASLR) and Data Execution
1330 Prevention (DEP) by default on Windows to make it harder for
1331 attackers to exploit vulnerabilities. Patch from John Brooks.
1333 o Minor bugfixes (on 0.2.1.x and earlier):
1334 - Fix a rare crash bug that could occur when a client was configured
1335 with a large number of bridges. Fixes bug 2629; bugfix on
1336 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1337 - Avoid a double mark-for-free warning when failing to attach a
1338 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
1340 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
1341 found by "cypherpunks". This bug was introduced before the first
1342 Tor release, in svn commit r110.
1343 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
1344 don't mention them in the manpage. Fixes bug 2450; issue
1345 spotted by keb and G-Lo.
1346 - Fix a bug in bandwidth history state parsing that could have been
1347 triggered if a future version of Tor ever changed the timing
1348 granularity at which bandwidth history is measured. Bugfix on
1350 - When a relay decides that its DNS is too broken for it to serve
1351 as an exit server, it advertised itself as a non-exit, but
1352 continued to act as an exit. This could create accidental
1353 partitioning opportunities for users. Instead, if a relay is
1354 going to advertise reject *:* as its exit policy, it should
1355 really act with exit policy "reject *:*". Fixes bug 2366.
1356 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
1357 - In the special case where you configure a public exit relay as your
1358 bridge, Tor would be willing to use that exit relay as the last
1359 hop in your circuit as well. Now we fail that circuit instead.
1360 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
1361 - Fix a bug with our locking implementation on Windows that couldn't
1362 correctly detect when a file was already locked. Fixes bug 2504,
1363 bugfix on 0.2.1.6-alpha.
1364 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
1365 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
1367 - Set target port in get_interface_address6() correctly. Bugfix
1368 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
1369 - Directory authorities are now more robust to hops back in time
1370 when calculating router stability. Previously, if a run of uptime
1371 or downtime appeared to be negative, the calculation could give
1372 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
1374 - Fix an assert that got triggered when using the TestingTorNetwork
1375 configuration option and then issuing a GETINFO config-text control
1376 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
1378 o Minor bugfixes (on 0.2.2.x):
1379 - Clients should not weight BadExit nodes as Exits in their node
1380 selection. Similarly, directory authorities should not count BadExit
1381 bandwidth as Exit bandwidth when computing bandwidth-weights.
1382 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
1383 - Correctly clear our dir_read/dir_write history when there is an
1384 error parsing any bw history value from the state file. Bugfix on
1386 - Resolve a bug in verifying signatures of directory objects
1387 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
1388 Fixes bug 2409. Found by "piebeer".
1389 - Bridge authorities no longer crash on SIGHUP when they try to
1390 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
1394 - Log less aggressively about circuit timeout changes, and improve
1395 some other circuit timeout messages. Resolves bug 2004.
1396 - Log a little more clearly about the times at which we're no longer
1397 accepting new connections. Resolves bug 2181.
1398 - Reject attempts at the client side to open connections to private
1399 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
1400 a randomly chosen exit node. Attempts to do so are always
1401 ill-defined, generally prevented by exit policies, and usually
1402 in error. This will also help to detect loops in transparent
1403 proxy configurations. You can disable this feature by setting
1404 "ClientRejectInternalAddresses 0" in your torrc.
1405 - Always treat failure to allocate an RSA key as an unrecoverable
1407 - Update to the March 1 2011 Maxmind GeoLite Country database.
1409 o Minor features (log subsystem):
1410 - Add documentation for configuring logging at different severities in
1411 different log domains. We've had this feature since 0.2.1.1-alpha,
1412 but for some reason it never made it into the manpage. Fixes
1414 - Make it simpler to specify "All log domains except for A and B".
1415 Previously you needed to say "[*,~A,~B]". Now you can just say
1417 - Add a "LogMessageDomains 1" option to include the domains of log
1418 messages along with the messages. Without this, there's no way
1419 to use log domains without reading the source or doing a lot
1422 o Packaging changes:
1423 - Stop shipping the Tor specs files and development proposal documents
1424 in the tarball. They are now in a separate git repository at
1425 git://git.torproject.org/torspec.git
1428 Changes in version 0.2.1.30 - 2011-02-23
1429 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
1430 change is a slight tweak to Tor's TLS handshake that makes relays
1431 and bridges that run this new version reachable from Iran again.
1432 We don't expect this tweak will win the arms race long-term, but it
1433 buys us time until we roll out a better solution.
1436 - Stop sending a CLOCK_SKEW controller status event whenever
1437 we fetch directory information from a relay that has a wrong clock.
1438 Instead, only inform the controller when it's a trusted authority
1439 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
1440 the rest of bug 1074.
1441 - Fix a bounds-checking error that could allow an attacker to
1442 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
1444 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
1445 Tor would ignore their RelayBandwidthBurst setting,
1446 potentially using more bandwidth than expected. Bugfix on
1447 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
1448 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
1449 hidserv" in her torrc. The 'hidserv' argument never controlled
1450 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
1453 - Adjust our TLS Diffie-Hellman parameters to match those used by
1455 - Update to the February 1 2011 Maxmind GeoLite Country database.
1458 - Check for and reject overly long directory certificates and
1459 directory tokens before they have a chance to hit any assertions.
1460 Bugfix on 0.2.1.28. Found by "doorss".
1461 - Bring the logic that gathers routerinfos and assesses the
1462 acceptability of circuits into line. This prevents a Tor OP from
1463 getting locked in a cycle of choosing its local OR as an exit for a
1464 path (due to a .exit request) and then rejecting the circuit because
1465 its OR is not listed yet. It also prevents Tor clients from using an
1466 OR running in the same instance as an exit (due to a .exit request)
1467 if the OR does not meet the same requirements expected of an OR
1468 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1470 o Packaging changes:
1471 - Stop shipping the Tor specs files and development proposal documents
1472 in the tarball. They are now in a separate git repository at
1473 git://git.torproject.org/torspec.git
1474 - Do not include Git version tags as though they are SVN tags when
1475 generating a tarball from inside a repository that has switched
1476 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1479 Changes in version 0.2.2.22-alpha - 2011-01-25
1480 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
1481 main other change is a slight tweak to Tor's TLS handshake that makes
1482 relays and bridges that run this new version reachable from Iran again.
1483 We don't expect this tweak will win the arms race long-term, but it
1484 will buy us a bit more time until we roll out a better solution.
1487 - Fix a bounds-checking error that could allow an attacker to
1488 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
1490 - Don't assert when changing from bridge to relay or vice versa
1491 via the controller. The assert happened because we didn't properly
1492 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
1493 bug 2433. Reported by bastik.
1496 - Adjust our TLS Diffie-Hellman parameters to match those used by
1498 - Provide a log message stating which geoip file we're parsing
1499 instead of just stating that we're parsing the geoip file.
1500 Implements ticket 2432.
1503 - Check for and reject overly long directory certificates and
1504 directory tokens before they have a chance to hit any assertions.
1505 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
1508 Changes in version 0.2.2.21-alpha - 2011-01-15
1509 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
1510 continues our recent code security audit work. The main fix resolves
1511 a remote heap overflow vulnerability that can allow remote code
1512 execution (CVE-2011-0427). Other fixes address a variety of assert
1513 and crash bugs, most of which we think are hard to exploit remotely.
1515 o Major bugfixes (security), also included in 0.2.1.29:
1516 - Fix a heap overflow bug where an adversary could cause heap
1517 corruption. This bug probably allows remote code execution
1518 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1520 - Prevent a denial-of-service attack by disallowing any
1521 zlib-compressed data whose compression factor is implausibly
1522 high. Fixes part of bug 2324; reported by "doorss".
1523 - Zero out a few more keys in memory before freeing them. Fixes
1524 bug 2384 and part of bug 2385. These key instances found by
1525 "cypherpunks", based on Andrew Case's report about being able
1526 to find sensitive data in Tor's memory space if you have enough
1527 permissions. Bugfix on 0.0.2pre9.
1529 o Major bugfixes (crashes), also included in 0.2.1.29:
1530 - Prevent calls to Libevent from inside Libevent log handlers.
1531 This had potential to cause a nasty set of crashes, especially
1532 if running Libevent with debug logging enabled, and running
1533 Tor with a controller watching for low-severity log messages.
1534 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1535 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1536 underflow errors there too. Fixes the other part of bug 2324.
1537 - Fix a bug where we would assert if we ever had a
1538 cached-descriptors.new file (or another file read directly into
1539 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1540 on 0.2.1.25. Found by doorss.
1541 - Fix some potential asserts and parsing issues with grossly
1542 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1545 o Minor bugfixes (other), also included in 0.2.1.29:
1546 - Fix a bug with handling misformed replies to reverse DNS lookup
1547 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1548 bug reported by doorss.
1549 - Fix compilation on mingw when a pthreads compatibility library
1550 has been installed. (We don't want to use it, so we shouldn't
1551 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1552 - Fix a bug where we would declare that we had run out of virtual
1553 addresses when the address space was only half-exhausted. Bugfix
1555 - Correctly handle the case where AutomapHostsOnResolve is set but
1556 no virtual addresses are available. Fixes bug 2328; bugfix on
1557 0.1.2.1-alpha. Bug found by doorss.
1558 - Correctly handle wrapping around when we run out of virtual
1559 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
1561 o Minor features, also included in 0.2.1.29:
1562 - Update to the January 1 2011 Maxmind GeoLite Country database.
1563 - Introduce output size checks on all of our decryption functions.
1565 o Build changes, also included in 0.2.1.29:
1566 - Tor does not build packages correctly with Automake 1.6 and earlier;
1567 added a check to Makefile.am to make sure that we're building with
1568 Automake 1.7 or later.
1569 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1570 because we built it with a too-old version of automake. Thus that
1571 release broke ./configure --enable-openbsd-malloc, which is popular
1572 among really fast exit relays on Linux.
1574 o Major bugfixes, new in 0.2.2.21-alpha:
1575 - Prevent crash/heap corruption when the cbtnummodes consensus
1576 parameter is set to 0 or large values. Fixes bug 2317; bugfix
1579 o Major features, new in 0.2.2.21-alpha:
1580 - Introduce minimum/maximum values that clients will believe
1581 from the consensus. Now we'll have a better chance to avoid crashes
1582 or worse when a consensus param has a weird value.
1584 o Minor features, new in 0.2.2.21-alpha:
1585 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
1586 used on bridges, and it makes bridge scanning somewhat easier.
1587 - If writing the state file to disk fails, wait up to an hour before
1588 retrying again, rather than trying again each second. Fixes bug
1589 2346; bugfix on Tor 0.1.1.3-alpha.
1590 - Make Libevent log messages get delivered to controllers later,
1591 and not from inside the Libevent log handler. This prevents unsafe
1592 reentrant Libevent calls while still letting the log messages
1594 - Detect platforms that brokenly use a signed size_t, and refuse to
1595 build there. Found and analyzed by doorss and rransom.
1596 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
1599 o Minor bugfixes, new in 0.2.2.21-alpha:
1600 - Handle SOCKS messages longer than 128 bytes long correctly, rather
1601 than waiting forever for them to finish. Fixes bug 2330; bugfix
1602 on 0.2.0.16-alpha. Found by doorss.
1603 - Add assertions to check for overflow in arguments to
1604 base32_encode() and base32_decode(); fix a signed-unsigned
1605 comparison there too. These bugs are not actually reachable in Tor,
1606 but it's good to prevent future errors too. Found by doorss.
1607 - Correctly detect failures to create DNS requests when using Libevent
1608 versions before v2. (Before Libevent 2, we used our own evdns
1609 implementation. Its return values for Libevent's evdns_resolve_*()
1610 functions are not consistent with those from Libevent.) Fixes bug
1611 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
1613 o Documentation, new in 0.2.2.21-alpha:
1614 - Document the default socks host and port (127.0.0.1:9050) for
1618 Changes in version 0.2.1.29 - 2011-01-15
1619 Tor 0.2.1.29 continues our recent code security audit work. The main
1620 fix resolves a remote heap overflow vulnerability that can allow remote
1621 code execution. Other fixes address a variety of assert and crash bugs,
1622 most of which we think are hard to exploit remotely.
1624 o Major bugfixes (security):
1625 - Fix a heap overflow bug where an adversary could cause heap
1626 corruption. This bug probably allows remote code execution
1627 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1629 - Prevent a denial-of-service attack by disallowing any
1630 zlib-compressed data whose compression factor is implausibly
1631 high. Fixes part of bug 2324; reported by "doorss".
1632 - Zero out a few more keys in memory before freeing them. Fixes
1633 bug 2384 and part of bug 2385. These key instances found by
1634 "cypherpunks", based on Andrew Case's report about being able
1635 to find sensitive data in Tor's memory space if you have enough
1636 permissions. Bugfix on 0.0.2pre9.
1638 o Major bugfixes (crashes):
1639 - Prevent calls to Libevent from inside Libevent log handlers.
1640 This had potential to cause a nasty set of crashes, especially
1641 if running Libevent with debug logging enabled, and running
1642 Tor with a controller watching for low-severity log messages.
1643 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1644 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1645 underflow errors there too. Fixes the other part of bug 2324.
1646 - Fix a bug where we would assert if we ever had a
1647 cached-descriptors.new file (or another file read directly into
1648 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1649 on 0.2.1.25. Found by doorss.
1650 - Fix some potential asserts and parsing issues with grossly
1651 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1654 o Minor bugfixes (other):
1655 - Fix a bug with handling misformed replies to reverse DNS lookup
1656 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1657 bug reported by doorss.
1658 - Fix compilation on mingw when a pthreads compatibility library
1659 has been installed. (We don't want to use it, so we shouldn't
1660 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1661 - Fix a bug where we would declare that we had run out of virtual
1662 addresses when the address space was only half-exhausted. Bugfix
1664 - Correctly handle the case where AutomapHostsOnResolve is set but
1665 no virtual addresses are available. Fixes bug 2328; bugfix on
1666 0.1.2.1-alpha. Bug found by doorss.
1667 - Correctly handle wrapping around to when we run out of virtual
1668 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
1669 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1670 because we built it with a too-old version of automake. Thus that
1671 release broke ./configure --enable-openbsd-malloc, which is popular
1672 among really fast exit relays on Linux.
1675 - Update to the January 1 2011 Maxmind GeoLite Country database.
1676 - Introduce output size checks on all of our decryption functions.
1679 - Tor does not build packages correctly with Automake 1.6 and earlier;
1680 added a check to Makefile.am to make sure that we're building with
1681 Automake 1.7 or later.
1684 Changes in version 0.2.2.20-alpha - 2010-12-17
1685 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
1686 exploitable bugs. We also fix a variety of other significant bugs,
1687 change the IP address for one of our directory authorities, and update
1688 the minimum version that Tor relays must run to join the network.
1691 - Fix a remotely exploitable bug that could be used to crash instances
1692 of Tor remotely by overflowing on the heap. Remote-code execution
1693 hasn't been confirmed, but can't be ruled out. Everyone should
1694 upgrade. Bugfix on the 0.1.1 series and later.
1695 - Fix a bug that could break accounting on 64-bit systems with large
1696 time_t values, making them hibernate for impossibly long intervals.
1697 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
1698 - Fix a logic error in directory_fetches_from_authorities() that
1699 would cause all _non_-exits refusing single-hop-like circuits
1700 to fetch from authorities, when we wanted to have _exits_ fetch
1701 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
1703 - Fix a stream fairness bug that would cause newer streams on a given
1704 circuit to get preference when reading bytes from the origin or
1705 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
1706 introduced before the first Tor release, in svn revision r152.
1708 o Directory authority changes:
1709 - Change IP address and ports for gabelmoo (v3 directory authority).
1712 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
1713 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
1714 - Fix an off-by-one error in calculating some controller command
1715 argument lengths. Fortunately, this mistake is harmless since
1716 the controller code does redundant NUL termination too. Found by
1717 boboper. Bugfix on 0.1.1.1-alpha.
1718 - Do not dereference NULL if a bridge fails to build its
1719 extra-info descriptor. Found by an anonymous commenter on
1720 Trac. Bugfix on 0.2.2.19-alpha.
1723 - Update to the December 1 2010 Maxmind GeoLite Country database.
1724 - Directory authorities now reject relays running any versions of
1725 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
1726 known bugs that keep RELAY_EARLY cells from working on rendezvous
1727 circuits. Followup to fix for bug 2081.
1728 - Directory authorities now reject relays running any version of Tor
1729 older than 0.2.0.26-rc. That version is the earliest that fetches
1730 current directory information correctly. Fixes bug 2156.
1731 - Report only the top 10 ports in exit-port stats in order not to
1732 exceed the maximum extra-info descriptor length of 50 KB. Implements
1736 Changes in version 0.2.1.28 - 2010-12-17
1737 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
1738 exploitable bugs. We also took this opportunity to change the IP address
1739 for one of our directory authorities, and to update the geoip database
1743 - Fix a remotely exploitable bug that could be used to crash instances
1744 of Tor remotely by overflowing on the heap. Remote-code execution
1745 hasn't been confirmed, but can't be ruled out. Everyone should
1746 upgrade. Bugfix on the 0.1.1 series and later.
1748 o Directory authority changes:
1749 - Change IP address and ports for gabelmoo (v3 directory authority).
1752 - Update to the December 1 2010 Maxmind GeoLite Country database.
1755 Changes in version 0.2.1.27 - 2010-11-23
1756 Yet another OpenSSL security patch broke its compatibility with Tor:
1757 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
1758 also took this opportunity to fix several crash bugs, integrate a new
1759 directory authority, and update the bundled GeoIP database.
1762 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1763 No longer set the tlsext_host_name extension on server SSL objects;
1764 but continue to set it on client SSL objects. Our goal in setting
1765 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1766 bugfix on 0.2.1.1-alpha.
1767 - Do not log messages to the controller while shrinking buffer
1768 freelists. Doing so would sometimes make the controller connection
1769 try to allocate a buffer chunk, which would mess up the internals
1770 of the freelist and cause an assertion failure. Fixes bug 1125;
1771 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1772 - Learn our external IP address when we're a relay or bridge, even if
1773 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1774 where we introduced bridge relays that don't need to publish to
1775 be useful. Fixes bug 2050.
1776 - Do even more to reject (and not just ignore) annotations on
1777 router descriptors received anywhere but from the cache. Previously
1778 we would ignore such annotations at first, but cache them to disk
1779 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1780 - When you're using bridges and your network goes away and your
1781 bridges get marked as down, recover when you attempt a new socks
1782 connection (if the network is back), rather than waiting up to an
1783 hour to try fetching new descriptors for your bridges. Bugfix on
1784 0.2.0.3-alpha; fixes bug 1981.
1787 - Move to the November 2010 Maxmind GeoLite country db (rather
1788 than the June 2009 ip-to-country GeoIP db) for our statistics that
1789 count how many users relays are seeing from each country. Now we'll
1790 have more accurate data, especially for many African countries.
1792 o New directory authorities:
1793 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
1797 - Fix an assertion failure that could occur in directory caches or
1798 bridge users when using a very short voting interval on a testing
1799 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
1801 - Enforce multiplicity rules when parsing annotations. Bugfix on
1802 0.2.0.8-alpha. Found by piebeer.
1803 - Allow handshaking OR connections to take a full KeepalivePeriod
1804 seconds to handshake. Previously, we would close them after
1805 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1806 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1808 - When building with --enable-gcc-warnings on OpenBSD, disable
1809 warnings in system headers. This makes --enable-gcc-warnings
1810 pass on OpenBSD 4.8.
1813 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
1814 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
1815 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
1816 Servers can start sending this code when enough clients recognize
1817 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
1818 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
1819 Patch from mingw-san.
1822 - Remove the old debian/ directory from the main Tor distribution.
1823 The official Tor-for-debian git repository lives at the URL
1824 https://git.torproject.org/debian/tor.git
1825 - Stop shipping the old doc/website/ directory in the tarball. We
1826 changed the website format in late 2010, and what we shipped in
1827 0.2.1.26 really wasn't that useful anyway.
1830 Changes in version 0.2.2.19-alpha - 2010-11-22
1831 Yet another OpenSSL security patch broke its compatibility with Tor:
1832 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
1835 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1836 No longer set the tlsext_host_name extension on server SSL objects;
1837 but continue to set it on client SSL objects. Our goal in setting
1838 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1839 bugfix on 0.2.1.1-alpha.
1842 - Try harder not to exceed the maximum length of 50 KB when writing
1843 statistics to extra-info descriptors. This bug was triggered by very
1844 fast relays reporting exit-port, entry, and dirreq statistics.
1845 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
1846 - Publish a router descriptor even if generating an extra-info
1847 descriptor fails. Previously we would not publish a router
1848 descriptor without an extra-info descriptor; this can cause fast
1849 exit relays collecting exit-port statistics to drop from the
1850 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
1853 Changes in version 0.2.2.18-alpha - 2010-11-16
1854 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
1855 us lately, makes unpublished bridge relays able to detect their IP
1856 address, and fixes a wide variety of other bugs to get us much closer
1857 to a stable release.
1860 - Do even more to reject (and not just ignore) annotations on
1861 router descriptors received anywhere but from the cache. Previously
1862 we would ignore such annotations at first, but cache them to disk
1863 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1864 - Do not log messages to the controller while shrinking buffer
1865 freelists. Doing so would sometimes make the controller connection
1866 try to allocate a buffer chunk, which would mess up the internals
1867 of the freelist and cause an assertion failure. Fixes bug 1125;
1868 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1869 - Learn our external IP address when we're a relay or bridge, even if
1870 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1871 where we introduced bridge relays that don't need to publish to
1872 be useful. Fixes bug 2050.
1873 - Maintain separate TLS contexts and certificates for incoming and
1874 outgoing connections in bridge relays. Previously we would use the
1875 same TLS contexts and certs for incoming and outgoing connections.
1876 Bugfix on 0.2.0.3-alpha; addresses bug 988.
1877 - Maintain separate identity keys for incoming and outgoing TLS
1878 contexts in bridge relays. Previously we would use the same
1879 identity keys for incoming and outgoing TLS contexts. Bugfix on
1880 0.2.0.3-alpha; addresses the other half of bug 988.
1881 - Avoid an assertion failure when we as an authority receive a
1882 duplicate upload of a router descriptor that we already have,
1883 but which we previously considered an obsolete descriptor.
1884 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
1885 - Avoid a crash bug triggered by looking at a dangling pointer while
1886 setting the network status consensus. Found by Robert Ransom.
1887 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
1888 - Fix a logic error where servers that _didn't_ act as exits would
1889 try to keep their server lists more aggressively up to date than
1890 exits, when it was supposed to be the other way around. Bugfix
1893 o Minor bugfixes (on Tor 0.2.1.x and earlier):
1894 - When we're trying to guess whether we know our IP address as
1895 a relay, we would log various ways that we failed to guess
1896 our address, but never log that we ended up guessing it
1897 successfully. Now add a log line to help confused and anxious
1898 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
1899 - Bring the logic that gathers routerinfos and assesses the
1900 acceptability of circuits into line. This prevents a Tor OP from
1901 getting locked in a cycle of choosing its local OR as an exit for a
1902 path (due to a .exit request) and then rejecting the circuit because
1903 its OR is not listed yet. It also prevents Tor clients from using an
1904 OR running in the same instance as an exit (due to a .exit request)
1905 if the OR does not meet the same requirements expected of an OR
1906 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1907 - Correctly describe errors that occur when generating a TLS object.
1908 Previously we would attribute them to a failure while generating a
1909 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
1911 - Enforce multiplicity rules when parsing annotations. Bugfix on
1912 0.2.0.8-alpha. Found by piebeer.
1913 - Fix warnings that newer versions of autoconf produced during
1914 ./autogen.sh. These warnings appear to be harmless in our case,
1915 but they were extremely verbose. Fixes bug 2020.
1917 o Minor bugfixes (on Tor 0.2.2.x):
1918 - Enable protection of small arrays whenever we build with gcc
1919 hardening features, not only when also building with warnings
1920 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
1923 - Make hidden services work better in private Tor networks by not
1924 requiring any uptime to join the hidden service descriptor
1925 DHT. Implements ticket 2088.
1926 - Rate-limit the "your application is giving Tor only an IP address"
1927 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
1928 - When AllowSingleHopExits is set, print a warning to explain to the
1929 relay operator why most clients are avoiding her relay.
1930 - Update to the November 1 2010 Maxmind GeoLite Country database.
1932 o Code simplifications and refactoring:
1933 - When we fixed bug 1038 we had to put in a restriction not to send
1934 RELAY_EARLY cells on rend circuits. This was necessary as long
1935 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
1936 active. Now remove this obsolete check. Resolves bug 2081.
1937 - Some options used different conventions for uppercasing of acronyms
1938 when comparing manpage and source. Fix those in favor of the
1939 manpage, as it makes sense to capitalize acronyms.
1940 - Remove the torrc.complete file. It hasn't been kept up to date
1941 and users will have better luck checking out the manpage.
1942 - Remove the obsolete "NoPublish" option; it has been flagged
1943 as obsolete and has produced a warning since 0.1.1.18-rc.
1944 - Remove everything related to building the expert bundle for OS X.
1945 It has confused many users, doesn't work right on OS X 10.6,
1946 and is hard to get rid of once installed. Resolves bug 1274.
1949 Changes in version 0.2.2.17-alpha - 2010-09-30
1950 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
1951 to use one-hop circuits (which can put the exit relays at higher risk,
1952 plus unbalance the network); fixes a big bug in bandwidth accounting
1953 for relays that want to limit their monthly bandwidth use; fixes a
1954 big pile of bugs in how clients tolerate temporary network failure;
1955 and makes our adaptive circuit build timeout feature (which improves
1956 client performance if your network is fast while not breaking things
1957 if your network is slow) better handle bad networks.
1960 - Exit relays now try harder to block exit attempts from unknown
1961 relays, to make it harder for people to use them as one-hop proxies
1962 a la tortunnel. Controlled by the refuseunknownexits consensus
1963 parameter (currently enabled), or you can override it on your
1964 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
1966 o Major bugfixes (0.2.1.x and earlier):
1967 - Fix a bug in bandwidth accounting that could make us use twice
1968 the intended bandwidth when our interval start changes due to
1969 daylight saving time. Now we tolerate skew in stored vs computed
1970 interval starts: if the start of the period changes by no more than
1971 50% of the period's duration, we remember bytes that we transferred
1972 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
1973 - Always search the Windows system directory for system DLLs, and
1974 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
1975 - When you're using bridges and your network goes away and your
1976 bridges get marked as down, recover when you attempt a new socks
1977 connection (if the network is back), rather than waiting up to an
1978 hour to try fetching new descriptors for your bridges. Bugfix on
1979 0.2.0.3-alpha; fixes bug 1981.
1981 o Major bugfixes (on 0.2.2.x):
1982 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
1984 - Fix a segfault that could happen when operating a bridge relay with
1985 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
1986 - The consensus bandwidth-weights (used by clients to choose fast
1987 relays) entered an unexpected edge case in September where
1988 Exits were much scarcer than Guards, resulting in bad weight
1989 recommendations. Now we compute them using new constraints that
1990 should succeed in all cases. Also alter directory authorities to
1991 not include the bandwidth-weights line if they fail to produce
1992 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
1993 - When weighting bridges during path selection, we used to trust
1994 the bandwidths they provided in their descriptor, only capping them
1995 at 10MB/s. This turned out to be problematic for two reasons:
1996 Bridges could claim to handle a lot more traffic then they
1997 actually would, thus making more clients pick them and have a
1998 pretty effective DoS attack. The other issue is that new bridges
1999 that might not have a good estimate for their bw capacity yet
2000 would not get used at all unless no other bridges are available
2001 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
2003 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
2004 - Ignore cannibalized circuits when recording circuit build times.
2005 This should provide for a minor performance improvement for hidden
2006 service users using 0.2.2.14-alpha, and should remove two spurious
2007 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
2008 - Simplify the logic that causes us to decide if the network is
2009 unavailable for purposes of recording circuit build times. If we
2010 receive no cells whatsoever for the entire duration of a circuit's
2011 full measured lifetime, the network is probably down. Also ignore
2012 one-hop directory fetching circuit timeouts when calculating our
2013 circuit build times. These changes should hopefully reduce the
2014 cases where we see ridiculous circuit build timeouts for people
2015 with spotty wireless connections. Fixes part of bug 1772; bugfix
2017 - Prevent the circuit build timeout from becoming larger than
2018 the maximum build time we have ever seen. Also, prevent the time
2019 period for measurement circuits from becoming larger than twice that
2020 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
2023 - When we run out of directory information such that we can't build
2024 circuits, but then get enough that we can build circuits, log when
2025 we actually construct a circuit, so the user has a better chance of
2026 knowing what's going on. Fixes bug 1362.
2027 - Be more generous with how much bandwidth we'd use up (with
2028 accounting enabled) before entering "soft hibernation". Previously,
2029 we'd refuse new connections and circuits once we'd used up 95% of
2030 our allotment. Now, we use up 95% of our allotment, AND make sure
2031 that we have no more than 500MB (or 3 hours of expected traffic,
2032 whichever is lower) remaining before we enter soft hibernation.
2033 - If we've configured EntryNodes and our network goes away and/or all
2034 our entrynodes get marked down, optimistically retry them all when
2035 a new socks application request appears. Fixes bug 1882.
2036 - Add some more defensive programming for architectures that can't
2037 handle unaligned integer accesses. We don't know of any actual bugs
2038 right now, but that's the best time to fix them. Fixes bug 1943.
2039 - Support line continuations in the torrc config file. If a line
2040 ends with a single backslash character, the newline is ignored, and
2041 the configuration value is treated as continuing on the next line.
2044 o Minor bugfixes (on 0.2.1.x and earlier):
2045 - For bandwidth accounting, calculate our expected bandwidth rate
2046 based on the time during which we were active and not in
2047 soft-hibernation during the last interval. Previously, we were
2048 also considering the time spent in soft-hibernation. If this
2049 was a long time, we would wind up underestimating our bandwidth
2050 by a lot, and skewing our wakeup time towards the start of the
2051 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
2053 o Minor bugfixes (on 0.2.2.x):
2054 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
2055 which were disabled by the circuit build timeout changes in
2056 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
2057 - Make sure we don't warn about missing bandwidth weights when
2058 choosing bridges or other relays not in the consensus. Bugfix on
2059 0.2.2.10-alpha; fixes bug 1805.
2060 - In our logs, do not double-report signatures from unrecognized
2061 authorities both as "from unknown authority" and "not
2062 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
2065 Changes in version 0.2.2.16-alpha - 2010-09-17
2066 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
2067 evident at exit relays), and also continues to resolve all the little
2068 bugs that have been filling up trac lately.
2070 o Major bugfixes (stream-level fairness):
2071 - When receiving a circuit-level SENDME for a blocked circuit, try
2072 to package cells fairly from all the streams that had previously
2073 been blocked on that circuit. Previously, we had started with the
2074 oldest stream, and allowed each stream to potentially exhaust
2075 the circuit's package window. This gave older streams on any
2076 given circuit priority over newer ones. Fixes bug 1937. Detected
2077 originally by Camilo Viecco. This bug was introduced before the
2078 first Tor release, in svn commit r152: it is the new winner of
2079 the longest-lived bug prize.
2080 - When the exit relay got a circuit-level sendme cell, it started
2081 reading on the exit streams, even if had 500 cells queued in the
2082 circuit queue already, so the circuit queue just grew and grew in
2083 some cases. We fix this by not re-enabling reading on receipt of a
2084 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
2085 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
2087 - Newly created streams were allowed to read cells onto circuits,
2088 even if the circuit's cell queue was blocked and waiting to drain.
2089 This created potential unfairness, as older streams would be
2090 blocked, but newer streams would gladly fill the queue completely.
2091 We add code to detect this situation and prevent any stream from
2092 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
2096 - Update to the September 1 2010 Maxmind GeoLite Country database.
2097 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
2098 not. This would lead to a cookie that is still not group readable.
2099 Closes bug 1843. Suggested by katmagic.
2100 - When logging a rate-limited warning, we now mention how many messages
2101 got suppressed since the last warning.
2102 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
2103 do individual connection-level rate limiting of clients. The torrc
2104 config options with the same names trump the consensus params, if
2105 both are present. Replaces the old "bwconnrate" and "bwconnburst"
2106 consensus params which were broken from 0.2.2.7-alpha through
2107 0.2.2.14-alpha. Closes bug 1947.
2108 - When a router changes IP address or port, authorities now launch
2109 a new reachability test for it. Implements ticket 1899.
2110 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
2111 2 no signature, 4 required" messages about consensus signatures
2112 easier to read, and make sure they get logged at the same severity
2113 as the messages explaining which keys are which. Fixes bug 1290.
2114 - Don't warn when we have a consensus that we can't verify because
2115 of missing certificates, unless those certificates are ones
2116 that we have been trying and failing to download. Fixes bug 1145.
2117 - If you configure your bridge with a known identity fingerprint,
2118 and the bridge authority is unreachable (as it is in at least
2119 one country now), fall back to directly requesting the descriptor
2120 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
2122 - When building with --enable-gcc-warnings on OpenBSD, disable
2123 warnings in system headers. This makes --enable-gcc-warnings
2124 pass on OpenBSD 4.8.
2126 o Minor bugfixes (on 0.2.1.x and earlier):
2127 - Authorities will now attempt to download consensuses if their
2128 own efforts to make a live consensus have failed. This change
2129 means authorities that restart will fetch a valid consensus, and
2130 it means authorities that didn't agree with the current consensus
2131 will still fetch and serve it if it has enough signatures. Bugfix
2132 on 0.2.0.9-alpha; fixes bug 1300.
2133 - Ensure DNS requests launched by "RESOLVE" commands from the
2134 controller respect the __LeaveStreamsUnattached setconf options. The
2135 same goes for requests launched via DNSPort or transparent
2136 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
2137 - Allow handshaking OR connections to take a full KeepalivePeriod
2138 seconds to handshake. Previously, we would close them after
2139 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
2140 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
2142 - Rate-limit "Failed to hand off onionskin" warnings.
2143 - Never relay a cell for a circuit we have already destroyed.
2144 Between marking a circuit as closeable and finally closing it,
2145 it may have been possible for a few queued cells to get relayed,
2146 even though they would have been immediately dropped by the next
2147 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
2148 - Never queue a cell for a circuit that's already been marked
2150 - Never vote for a server as "Running" if we have a descriptor for
2151 it claiming to be hibernating, and that descriptor was published
2152 more recently than our last contact with the server. Bugfix on
2153 0.2.0.3-alpha; fixes bug 911.
2154 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
2157 o Minor bugfixes (on 0.2.2.x):
2158 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
2159 down if a directory fetch fails and you've configured either
2160 bridges or EntryNodes. The intent was to mark the relay as down
2161 _unless_ you're using bridges or EntryNodes, since if you are
2162 then you could quickly run out of entry points.
2163 - Fix the Windows directory-listing code. A bug introduced in
2164 0.2.2.14-alpha could make Windows directory servers forget to load
2165 some of their cached v2 networkstatus files.
2166 - Really allow clients to use relays as bridges. Fixes bug 1776;
2167 bugfix on 0.2.2.15-alpha.
2168 - Demote a warn to info that happens when the CellStatistics option
2169 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
2170 Reported by Moritz Bartl.
2171 - On Windows, build correctly either with or without Unicode support.
2172 This is necessary so that Tor can support fringe platforms like
2173 Windows 98 (which has no Unicode), or Windows CE (which has no
2174 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
2177 - Add a unit test for cross-platform directory-listing code.
2180 Changes in version 0.2.2.15-alpha - 2010-08-18
2181 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
2182 fixes a variety of other bugs that were preventing performance
2183 experiments from moving forward, fixes several bothersome memory leaks,
2184 and generally closes a lot of smaller bugs that have been filling up
2188 - Stop assigning the HSDir flag to relays that disable their
2189 DirPort (and thus will refuse to answer directory requests). This
2190 fix should dramatically improve the reachability of hidden services:
2191 hidden services and hidden service clients pick six HSDir relays
2192 to store and retrieve the hidden service descriptor, and currently
2193 about half of the HSDir relays will refuse to work. Bugfix on
2194 0.2.0.10-alpha; fixes part of bug 1693.
2195 - The PerConnBWRate and Burst config options, along with the
2196 bwconnrate and bwconnburst consensus params, initialized each conn's
2197 token bucket values only when the connection is established. Now we
2198 update them if the config options change, and update them every time
2199 we get a new consensus. Otherwise we can encounter an ugly edge
2200 case where we initialize an OR conn to client-level bandwidth,
2201 but then later the relay joins the consensus and we leave it
2202 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
2203 - Fix a regression that caused Tor to rebind its ports if it receives
2204 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
2207 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
2208 should give us approximately 40-50% more Guard-flagged nodes,
2209 improving the anonymity the Tor network can provide and also
2210 decreasing the dropoff in throughput that relays experience when
2211 they first get the Guard flag.
2212 - Allow enabling or disabling the *Statistics config options while
2216 - Update to the August 1 2010 Maxmind GeoLite Country database.
2217 - Have the controller interface give a more useful message than
2218 "Internal Error" in response to failed GETINFO requests.
2219 - Warn when the same option is provided more than once in a torrc
2220 file, on the command line, or in a single SETCONF statement, and
2221 the option is one that only accepts a single line. Closes bug 1384.
2222 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
2223 Patch from mingw-san.
2224 - Add support for the country code "{??}" in torrc options like
2225 ExcludeNodes, to indicate all routers of unknown country. Closes
2227 - Relays report the number of bytes spent on answering directory
2228 requests in extra-info descriptors similar to {read,write}-history.
2229 Implements enhancement 1790.
2231 o Minor bugfixes (on 0.2.1.x and earlier):
2232 - Complain if PublishServerDescriptor is given multiple arguments that
2233 include 0 or 1. This configuration will be rejected in the future.
2234 Bugfix on 0.2.0.1-alpha; closes bug 1107.
2235 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
2236 Bugfix on 0.2.0.13-alpha; closes bug 928.
2237 - Change "Application request when we're believed to be offline."
2238 notice to "Application request when we haven't used client
2239 functionality lately.", to clarify that it's not an error. Bugfix
2240 on 0.0.9.3; fixes bug 1222.
2241 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
2242 would return "551 Internal error" rather than "552 Unrecognized key
2243 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
2244 - Users can't configure a regular relay to be their bridge. It didn't
2245 work because when Tor fetched the bridge descriptor, it found
2246 that it already had it, and didn't realize that the purpose of the
2247 descriptor had changed. Now we replace routers with a purpose other
2248 than bridge with bridge descriptors when fetching them. Bugfix on
2249 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
2250 refetch the descriptor with router purpose 'general', disabling
2252 - Fix a rare bug in rend_fn unit tests: we would fail a test when
2253 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
2254 on 0.2.0.10-alpha; fixes bug 1808.
2255 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
2256 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
2257 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
2258 Servers can start sending this code when enough clients recognize
2259 it. Also update the spec to reflect this new reason. Bugfix on
2260 0.1.0.1-rc; fixes part of bug 1793.
2261 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
2262 when we switch from being a public relay to a bridge. Otherwise
2263 there will still be clients that see the relay in their consensus,
2264 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
2266 - Instead of giving an assertion failure on an internal mismatch
2267 on estimated freelist size, just log a BUG warning and try later.
2268 Mitigates but does not fix bug 1125.
2269 - Fix an assertion failure that could occur in caches or bridge users
2270 when using a very short voting interval on a testing network.
2271 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
2273 o Minor bugfixes (on 0.2.2.x):
2274 - Alter directory authorities to always consider Exit-flagged nodes
2275 as potential Guard nodes in their votes. The actual decision to
2276 use Exits as Guards is done in the consensus bandwidth weights.
2277 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
2278 - When the controller is reporting the purpose of circuits that
2279 didn't finish building before the circuit build timeout, it was
2280 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
2281 - Our libevent version parsing code couldn't handle versions like
2282 1.4.14b-stable and incorrectly warned the user about using an
2283 old and broken version of libevent. Treat 1.4.14b-stable like
2284 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
2286 - Don't use substitution references like $(VAR:MOD) when
2287 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
2288 '$(:x)' to 'x' rather than the empty string. This bites us in
2289 doc/ when configured with --disable-asciidoc. Bugfix on
2290 0.2.2.9-alpha; fixes bug 1773.
2291 - Remove a spurious hidden service server-side log notice about
2292 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
2294 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
2296 - Correctly report written bytes on linked connections. Found while
2297 implementing 1790. Bugfix on 0.2.2.4-alpha.
2298 - Fix three memory leaks: one in circuit_build_times_parse_state(),
2299 one in dirvote_add_signatures_to_pending_consensus(), and one every
2300 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
2301 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
2303 o Code simplifications and refactoring:
2304 - Take a first step towards making or.h smaller by splitting out
2305 function definitions for all source files in src/or/. Leave
2306 structures and defines in or.h for now.
2307 - Remove a bunch of unused function declarations as well as a block of
2308 #if 0'd code from the unit tests. Closes bug 1824.
2309 - New unit tests for exit-port history statistics; refactored exit
2310 statistics code to be more easily tested.
2311 - Remove the old debian/ directory from the main Tor distribution.
2312 The official Tor-for-debian git repository lives at the URL
2313 https://git.torproject.org/debian/tor.git
2316 Changes in version 0.2.2.14-alpha - 2010-07-12
2317 Tor 0.2.2.14-alpha greatly improves client-side handling of
2318 circuit build timeouts, which are used to estimate speed and improve
2319 performance. We also move to a much better GeoIP database, port Tor to
2320 Windows CE, introduce new compile flags that improve code security,
2321 add an eighth v3 directory authority, and address a lot of more
2325 - Tor directory authorities no longer crash when started with a
2326 cached-microdesc-consensus file in their data directory. Bugfix
2327 on 0.2.2.6-alpha; fixes bug 1532.
2328 - Treat an unset $HOME like an empty $HOME rather than triggering an
2329 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
2330 - Ignore negative and large circuit build timeout values that can
2331 happen during a suspend or hibernate. These values caused various
2332 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
2333 - Alter calculation of Pareto distribution parameter 'Xm' for
2334 Circuit Build Timeout learning to use the weighted average of the
2335 top N=3 modes (because we have three entry guards). Considering
2336 multiple modes should improve the timeout calculation in some cases,
2337 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
2339 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
2340 right censored distribution model. This approach improves over the
2341 synthetic timeout generation approach that was producing insanely
2342 high timeout values. Now we calculate build timeouts using truncated
2343 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
2344 - Do not close circuits that are under construction when they reach
2345 the circuit build timeout. Instead, leave them building (but do not
2346 use them) for up until the time corresponding to the 95th percentile
2347 on the Pareto CDF or 60 seconds, whichever is greater. This is done
2348 to provide better data for the new Pareto model. This percentile
2349 can be controlled by the consensus.
2352 - Move to the June 2010 Maxmind GeoLite country db (rather than the
2353 June 2009 ip-to-country GeoIP db) for our statistics that count
2354 how many users relays are seeing from each country. Now we have
2355 more accurate data for many African countries.
2356 - Port Tor to build and run correctly on Windows CE systems, using
2357 the wcecompat library. Contributed by Valerio Lupi.
2358 - New "--enable-gcc-hardening" ./configure flag (off by default)
2359 to turn on gcc compile time hardening options. It ensures
2360 that signed ints have defined behavior (-fwrapv), enables
2361 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
2362 with canaries (-fstack-protector-all), turns on ASLR protection if
2363 supported by the kernel (-fPIE, -pie), and adds additional security
2364 related warnings. Verified to work on Mac OS X and Debian Lenny.
2365 - New "--enable-linker-hardening" ./configure flag (off by default)
2366 to turn on ELF specific hardening features (relro, now). This does
2367 not work with Mac OS X or any other non-ELF binary format.
2369 o New directory authorities:
2370 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
2374 - New config option "WarnUnsafeSocks 0" disables the warning that
2375 occurs whenever Tor receives a socks handshake using a version of
2376 the socks protocol that can only provide an IP address (rather
2377 than a hostname). Setups that do DNS locally over Tor are fine,
2378 and we shouldn't spam the logs in that case.
2379 - Convert the HACKING file to asciidoc, and add a few new sections
2380 to it, explaining how we use Git, how we make changelogs, and
2381 what should go in a patch.
2382 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
2383 event, to give information on the current rate of circuit timeouts
2384 over our stored history.
2385 - Add ability to disable circuit build time learning via consensus
2386 parameter and via a LearnCircuitBuildTimeout config option. Also
2387 automatically disable circuit build time calculation if we are
2388 either a AuthoritativeDirectory, or if we fail to write our state
2389 file. Fixes bug 1296.
2390 - More gracefully handle corrupt state files, removing asserts
2391 in favor of saving a backup and resetting state.
2392 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
2396 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2398 - When a2x fails, mention that the user could disable manpages instead
2399 of trying to fix their asciidoc installation.
2400 - Where available, use Libevent 2.0's periodic timers so that our
2401 once-per-second cleanup code gets called even more closely to
2402 once per second than it would otherwise. Fixes bug 943.
2403 - If you run a bridge that listens on multiple IP addresses, and
2404 some user configures a bridge address that uses a different IP
2405 address than your bridge writes in its router descriptor, and the
2406 user doesn't specify an identity key, their Tor would discard the
2407 descriptor because "it isn't one of our configured bridges", and
2408 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
2409 Bugfix on 0.2.0.3-alpha.
2410 - If OpenSSL fails to make a duplicate of a private or public key, log
2411 an error message and try to exit cleanly. May help with debugging
2412 if bug 1209 ever remanifests.
2413 - Save a couple bytes in memory allocation every time we escape
2414 certain characters in a string. Patch from Florian Zumbiehl.
2415 - Make it explicit that we don't cannibalize one-hop circuits. This
2416 happens in the wild, but doesn't turn out to be a problem because
2417 we fortunately don't use those circuits. Many thanks to outofwords
2418 for the initial analysis and to swissknife who confirmed that
2419 two-hop circuits are actually created.
2420 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
2421 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
2422 - Eliminate a case where a circuit build time warning was displayed
2423 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
2426 Changes in version 0.2.1.26 - 2010-05-02
2427 Tor 0.2.1.26 addresses the recent connection and memory overload
2428 problems we've been seeing on relays, especially relays with their
2429 DirPort open. If your relay has been crashing, or you turned it off
2430 because it used too many resources, give this release a try.
2432 This release also fixes yet another instance of broken OpenSSL libraries
2433 that was causing some relays to drop out of the consensus.
2436 - Teach relays to defend themselves from connection overload. Relays
2437 now close idle circuits early if it looks like they were intended
2438 for directory fetches. Relays are also more aggressive about closing
2439 TLS connections that have no circuits on them. Such circuits are
2440 unlikely to be re-used, and tens of thousands of them were piling
2441 up at the fast relays, causing the relays to run out of sockets
2442 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
2443 their directory fetches over TLS).
2444 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
2445 that claim to be earlier than 0.9.8m, but which have in reality
2446 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
2447 behavior. Possible fix for some cases of bug 1346.
2448 - Directory mirrors were fetching relay descriptors only from v2
2449 directory authorities, rather than v3 authorities like they should.
2450 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
2451 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
2454 - Finally get rid of the deprecated and now harmful notion of "clique
2455 mode", where directory authorities maintain TLS connections to
2459 - In the util/threads test, no longer free the test_mutex before all
2460 worker threads have finished. Bugfix on 0.2.1.6-alpha.
2461 - The master thread could starve the worker threads quite badly on
2462 certain systems, causing them to run only partially in the allowed
2463 window. This resulted in test failures. Now the master thread sleeps
2464 occasionally for a few microseconds while the two worker-threads
2465 compete for the mutex. Bugfix on 0.2.0.1-alpha.
2468 Changes in version 0.2.2.13-alpha - 2010-04-24
2469 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
2470 problems we've been seeing on relays, especially relays with their
2471 DirPort open. If your relay has been crashing, or you turned it off
2472 because it used too many resources, give this release a try.
2475 - Teach relays to defend themselves from connection overload. Relays
2476 now close idle circuits early if it looks like they were intended
2477 for directory fetches. Relays are also more aggressive about closing
2478 TLS connections that have no circuits on them. Such circuits are
2479 unlikely to be re-used, and tens of thousands of them were piling
2480 up at the fast relays, causing the relays to run out of sockets
2481 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
2482 their directory fetches over TLS).
2485 - Finally get rid of the deprecated and now harmful notion of "clique
2486 mode", where directory authorities maintain TLS connections to
2488 - Directory authorities now do an immediate reachability check as soon
2489 as they hear about a new relay. This change should slightly reduce
2490 the time between setting up a relay and getting listed as running
2491 in the consensus. It should also improve the time between setting
2492 up a bridge and seeing use by bridge users.
2493 - Directory authorities no longer launch a TLS connection to every
2494 relay as they startup. Now that we have 2k+ descriptors cached,
2495 the resulting network hiccup is becoming a burden. Besides,
2496 authorities already avoid voting about Running for the first half
2497 hour of their uptime.
2500 Changes in version 0.2.2.12-alpha - 2010-04-20
2501 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
2502 handle and vote on descriptors. It was causing relays to drop out of
2506 - Many relays have been falling out of the consensus lately because
2507 not enough authorities know about their descriptor for them to get
2508 a majority of votes. When we deprecated the v2 directory protocol,
2509 we got rid of the only way that v3 authorities can hear from each
2510 other about other descriptors. Now authorities examine every v3
2511 vote for new descriptors, and fetch them from that authority. Bugfix
2513 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
2514 and a warning in or.h related to bandwidth_weight_rule_t that
2515 prevented clean compile on OS X. Fixes bug 1363; bugfix on
2517 - Fix a segfault on relays when DirReqStatistics is enabled
2518 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
2522 - Demote a confusing TLS warning that relay operators might get when
2523 someone tries to talk to their OrPort. It is neither the operator's
2524 fault nor can they do anything about it. Fixes bug 1364; bugfix
2528 Changes in version 0.2.2.11-alpha - 2010-04-15
2529 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
2530 libraries that was causing some relays to drop out of the consensus.
2533 - Directory mirrors were fetching relay descriptors only from v2
2534 directory authorities, rather than v3 authorities like they should.
2535 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
2536 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
2537 - Fix a parsing error that made every possible value of
2538 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
2539 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
2540 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
2541 about the option without breaking older ones.
2542 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
2543 that claim to be earlier than 0.9.8m, but which have in reality
2544 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
2545 behavior. Possible fix for some cases of bug 1346.
2548 - Experiment with a more aggressive approach to preventing clients
2549 from making one-hop exit streams. Exit relays who want to try it
2550 out can set "RefuseUnknownExits 1" in their torrc, and then look
2551 for "Attempt by %s to open a stream" log messages. Let us know
2553 - Add support for statically linking zlib by specifying
2554 --enable-static-zlib, to go with our support for statically linking
2555 openssl and libevent. Resolves bug 1358.
2558 - Fix a segfault that happens whenever a Tor client that is using
2559 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
2561 - When we cleaned up the contrib/tor-exit-notice.html file, we left
2562 out the first line. Fixes bug 1295.
2563 - When building the manpage from a tarball, we required asciidoc, but
2564 the asciidoc -> roff/html conversion was already done for the
2565 tarball. Make 'make' complain only when we need asciidoc (either
2566 because we're compiling directly from git, or because we altered
2567 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
2568 - When none of the directory authorities vote on any params, Tor
2569 segfaulted when trying to make the consensus from the votes. We
2570 didn't trigger the bug in practice, because authorities do include
2571 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
2574 - In the util/threads test, no longer free the test_mutex before all
2575 worker threads have finished. Bugfix on 0.2.1.6-alpha.
2576 - The master thread could starve the worker threads quite badly on
2577 certain systems, causing them to run only partially in the allowed
2578 window. This resulted in test failures. Now the master thread sleeps
2579 occasionally for a few microseconds while the two worker-threads
2580 compete for the mutex. Bugfix on 0.2.0.1-alpha.
2583 Changes in version 0.2.2.10-alpha - 2010-03-07
2584 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
2585 could prevent relays from guessing their IP address correctly. It also
2586 starts the groundwork for another client-side performance boost, since
2587 currently we're not making efficient use of relays that have both the
2588 Guard flag and the Exit flag.
2591 - Fix a regression from our patch for bug 1244 that caused relays
2592 to guess their IP address incorrectly if they didn't set Address
2593 in their torrc and/or their address fails to resolve. Bugfix on
2594 0.2.2.9-alpha; fixes bug 1269.
2596 o Major features (performance):
2597 - Directory authorities now compute consensus weightings that instruct
2598 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
2599 and no flag. Clients that use these weightings will distribute
2600 network load more evenly across these different relay types. The
2601 weightings are in the consensus so we can change them globally in
2602 the future. Extra thanks to "outofwords" for finding some nasty
2603 security bugs in the first implementation of this feature.
2605 o Minor features (performance):
2606 - Always perform router selections using weighted relay bandwidth,
2607 even if we don't need a high capacity circuit at the time. Non-fast
2608 circuits now only differ from fast ones in that they can use relays
2609 not marked with the Fast flag. This "feature" could turn out to
2610 be a horrible bug; we should investigate more before it goes into
2614 - Allow disabling building of the manpages. Skipping the manpage
2615 speeds up the build considerably.
2617 o Minor bugfixes (on 0.2.2.x):
2618 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
2619 Bugfix on 0.2.2.9-alpha.
2620 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
2621 config option. Bugfix on 0.2.2.7-alpha.
2622 - Ship the asciidoc-helper file in the tarball, so that people can
2623 build from source if they want to, and touching the .1.txt files
2624 doesn't break the build. Bugfix on 0.2.2.9-alpha.
2626 o Minor bugfixes (on 0.2.1.x or earlier):
2627 - Fix a dereference-then-NULL-check sequence when publishing
2628 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
2630 - Fix another dereference-then-NULL-check sequence. Bugfix on
2631 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
2632 - Make sure we treat potentially not NUL-terminated strings correctly.
2633 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
2635 o Code simplifications and refactoring:
2636 - Fix some urls in the exit notice file and make it XHTML1.1 strict
2637 compliant. Based on a patch from Christian Kujau.
2638 - Don't use sed in asciidoc-helper anymore.
2639 - Make the build process fail if asciidoc cannot be found and
2640 building with asciidoc isn't disabled.
2643 Changes in version 0.2.2.9-alpha - 2010-02-22
2644 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
2645 location of a directory authority, and cleans up a bunch of small bugs.
2647 o Directory authority changes:
2648 - Change IP address for dannenberg (v3 directory authority), and
2649 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
2650 service directory authority) from the list.
2653 - Make Tor work again on the latest OS X: when deciding whether to
2654 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2655 version at run-time, not compile time. We need to do this because
2656 Apple doesn't update its dev-tools headers when it updates its
2657 libraries in a security patch.
2658 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2659 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2660 a memory leak when requesting a hidden service descriptor we've
2661 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2663 - Authorities could be tricked into giving out the Exit flag to relays
2664 that didn't allow exiting to any ports. This bug could screw
2665 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
2666 1238. Bug discovered by Martin Kowalczyk.
2667 - When freeing a session key, zero it out completely. We only zeroed
2668 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
2669 patched by ekir. Fixes bug 1254.
2672 - Fix static compilation by listing the openssl libraries in the right
2673 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
2674 - Resume handling .exit hostnames in a special way: originally we
2675 stripped the .exit part and used the requested exit relay. In
2676 0.2.2.1-alpha we stopped treating them in any special way, meaning
2677 if you use a .exit address then Tor will pass it on to the exit
2678 relay. Now we reject the .exit stream outright, since that behavior
2679 might be more expected by the user. Found and diagnosed by Scott
2680 Bennett and Downie on or-talk.
2681 - Don't spam the controller with events when we have no file
2682 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
2683 for log messages was already solved from bug 748.)
2684 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
2686 - Make the DNSPort option work with libevent 2.x. Don't alter the
2687 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
2688 - Emit a GUARD DROPPED controller event for a case we missed.
2689 - Make more fields in the controller protocol case-insensitive, since
2690 control-spec.txt said they were.
2691 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2692 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2693 - Fix a spec conformance issue: the network-status-version token
2694 must be the first token in a v3 consensus or vote. Discovered by
2695 parakeep. Bugfix on 0.2.0.3-alpha.
2697 o Code simplifications and refactoring:
2698 - Generate our manpage and HTML documentation using Asciidoc. This
2699 change should make it easier to maintain the documentation, and
2701 - Remove the --enable-iphone option. According to reports from Marco
2702 Bonetti, Tor builds fine without any special tweaking on recent
2703 iPhone SDK versions.
2704 - Removed some unnecessary files from the source distribution. The
2705 AUTHORS file has now been merged into the people page on the
2706 website. The roadmaps and design doc can now be found in the
2707 projects directory in svn.
2708 - Enabled various circuit build timeout constants to be controlled
2709 by consensus parameters. Also set better defaults for these
2710 parameters based on experimentation on broadband and simulated
2714 - The 'EXTENDCIRCUIT' control port command can now be used with
2715 a circ id of 0 and no path. This feature will cause Tor to build
2716 a new 'fast' general purpose circuit using its own path selection
2718 - Added a BUILDTIMEOUT_SET controller event to describe changes
2719 to the circuit build timeout.
2720 - Future-proof the controller protocol a bit by ignoring keyword
2721 arguments we do not recognize.
2722 - Expand homedirs passed to tor-checkkey. This should silence a
2723 coverity complaint about passing a user-supplied string into
2724 open() without checking it.
2727 Changes in version 0.2.1.25 - 2010-03-16
2728 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
2729 prevent relays from guessing their IP address correctly. It also fixes
2730 several minor potential security bugs.
2733 - Fix a regression from our patch for bug 1244 that caused relays
2734 to guess their IP address incorrectly if they didn't set Address
2735 in their torrc and/or their address fails to resolve. Bugfix on
2736 0.2.1.23; fixes bug 1269.
2737 - When freeing a session key, zero it out completely. We only zeroed
2738 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
2739 patched by ekir. Fixes bug 1254.
2742 - Fix a dereference-then-NULL-check sequence when publishing
2743 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
2745 - Fix another dereference-then-NULL-check sequence. Bugfix on
2746 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
2747 - Make sure we treat potentially not NUL-terminated strings correctly.
2748 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
2752 Changes in version 0.2.1.24 - 2010-02-21
2753 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
2757 - Work correctly out-of-the-box with even more vendor-patched versions
2758 of OpenSSL. In particular, make it so Debian and OS X don't need
2759 customized patches to run/build.
2762 Changes in version 0.2.1.23 - 2010-02-13
2763 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
2764 again on the latest OS X, and updates the location of a directory
2767 o Major bugfixes (performance):
2768 - We were selecting our guards uniformly at random, and then weighting
2769 which of our guards we'd use uniformly at random. This imbalance
2770 meant that Tor clients were severely limited on throughput (and
2771 probably latency too) by the first hop in their circuit. Now we
2772 select guards weighted by currently advertised bandwidth. We also
2773 automatically discard guards picked using the old algorithm. Fixes
2774 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2777 - Make Tor work again on the latest OS X: when deciding whether to
2778 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2779 version at run-time, not compile time. We need to do this because
2780 Apple doesn't update its dev-tools headers when it updates its
2781 libraries in a security patch.
2782 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2783 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2784 a memory leak when requesting a hidden service descriptor we've
2785 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2788 o Directory authority changes:
2789 - Change IP address for dannenberg (v3 directory authority), and
2790 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
2791 service directory authority) from the list.
2794 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2795 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2798 - Avoid a mad rush at the beginning of each month when each client
2799 rotates half of its guards. Instead we spread the rotation out
2800 throughout the month, but we still avoid leaving a precise timestamp
2801 in the state file about when we first picked the guard. Improves
2802 over the behavior introduced in 0.1.2.17.
2805 Changes in version 0.2.2.8-alpha - 2010-01-26
2806 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
2807 causing bridge relays to disappear. If you're running a bridge,
2811 - Fix a memory corruption bug on bridges that occured during the
2812 inclusion of stats data in extra-info descriptors. Also fix the
2813 interface for geoip_get_bridge_stats* to prevent similar bugs in
2814 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
2815 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
2818 - Ignore OutboundBindAddress when connecting to localhost.
2819 Connections to localhost need to come _from_ localhost, or else
2820 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
2824 Changes in version 0.2.2.7-alpha - 2010-01-19
2825 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
2826 as laying the groundwork for further relay-side performance fixes. It
2827 also starts cleaning up client behavior with respect to the EntryNodes,
2828 ExitNodes, and StrictNodes config options.
2830 This release also rotates two directory authority keys, due to a
2831 security breach of some of the Torproject servers.
2833 o Directory authority changes:
2834 - Rotate keys (both v3 identity and relay identity) for moria1
2837 o Major features (performance):
2838 - We were selecting our guards uniformly at random, and then weighting
2839 which of our guards we'd use uniformly at random. This imbalance
2840 meant that Tor clients were severely limited on throughput (and
2841 probably latency too) by the first hop in their circuit. Now we
2842 select guards weighted by currently advertised bandwidth. We also
2843 automatically discard guards picked using the old algorithm. Fixes
2844 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2845 - When choosing which cells to relay first, relays can now favor
2846 circuits that have been quiet recently, to provide lower latency
2847 for low-volume circuits. By default, relays enable or disable this
2848 feature based on a setting in the consensus. You can override
2849 this default by using the new "CircuitPriorityHalflife" config
2850 option. Design and code by Ian Goldberg, Can Tang, and Chris
2852 - Add separate per-conn write limiting to go with the per-conn read
2853 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
2854 but never per-conn write limits.
2855 - New consensus params "bwconnrate" and "bwconnburst" to let us
2856 rate-limit client connections as they enter the network. It's
2857 controlled in the consensus so we can turn it on and off for
2858 experiments. It's starting out off. Based on proposal 163.
2860 o Major features (relay selection options):
2861 - Switch to a StrictNodes config option, rather than the previous
2862 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
2863 "StrictExcludeNodes" option.
2864 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
2865 change during a config reload, mark and discard all our origin
2866 circuits. This fix should address edge cases where we change the
2867 config options and but then choose a circuit that we created before
2869 - If EntryNodes or ExitNodes are set, be more willing to use an
2870 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
2872 - Make EntryNodes config option much more aggressive even when
2873 StrictNodes is not set. Before it would prepend your requested
2874 entrynodes to your list of guard nodes, but feel free to use others
2875 after that. Now it chooses only from your EntryNodes if any of
2876 those are available, and only falls back to others if a) they're
2877 all down and b) StrictNodes is not set.
2878 - Now we refresh your entry guards from EntryNodes at each consensus
2879 fetch -- rather than just at startup and then they slowly rot as
2880 the network changes.
2883 - Stop bridge directory authorities from answering dbg-stability.txt
2884 directory queries, which would let people fetch a list of all
2885 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2888 - Log a notice when we get a new control connection. Now it's easier
2889 for security-conscious users to recognize when a local application
2890 is knocking on their controller door. Suggested by bug 1196.
2891 - New config option "CircuitStreamTimeout" to override our internal
2892 timeout schedule for how many seconds until we detach a stream from
2893 a circuit and try a new circuit. If your network is particularly
2894 slow, you might want to set this to a number like 60.
2895 - New controller command "getinfo config-text". It returns the
2896 contents that Tor would write if you send it a SAVECONF command,
2897 so the controller can write the file to disk itself.
2898 - New options for SafeLogging to allow scrubbing only log messages
2899 generated while acting as a relay.
2900 - Ship the bridges spec file in the tarball too.
2901 - Avoid a mad rush at the beginning of each month when each client
2902 rotates half of its guards. Instead we spread the rotation out
2903 throughout the month, but we still avoid leaving a precise timestamp
2904 in the state file about when we first picked the guard. Improves
2905 over the behavior introduced in 0.1.2.17.
2907 o Minor bugfixes (compiling):
2908 - Fix compilation on OS X 10.3, which has a stub mlockall() but
2909 hides it. Bugfix on 0.2.2.6-alpha.
2910 - Fix compilation on Solaris by removing support for the
2911 DisableAllSwap config option. Solaris doesn't have an rlimit for
2912 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
2915 o Minor bugfixes (crashes):
2916 - Do not segfault when writing buffer stats when we haven't observed
2917 a single circuit to report about. Found by Fabian Lanze. Bugfix on
2919 - If we're in the pathological case where there's no exit bandwidth
2920 but there is non-exit bandwidth, or no guard bandwidth but there
2921 is non-guard bandwidth, don't crash during path selection. Bugfix
2923 - Fix an impossible-to-actually-trigger buffer overflow in relay
2924 descriptor generation. Bugfix on 0.1.0.15.
2926 o Minor bugfixes (privacy):
2927 - Fix an instance where a Tor directory mirror might accidentally
2928 log the IP address of a misbehaving Tor client. Bugfix on
2930 - Don't list Windows capabilities in relay descriptors. We never made
2931 use of them, and maybe it's a bad idea to publish them. Bugfix
2934 o Minor bugfixes (other):
2935 - Resolve an edge case in path weighting that could make us misweight
2936 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
2937 - Fix statistics on client numbers by country as seen by bridges that
2938 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
2939 intervals instead of variable 12-to-48-hour intervals.
2940 - After we free an internal connection structure, overwrite it
2941 with a different memory value than we use for overwriting a freed
2942 internal circuit structure. Should help with debugging. Suggested
2944 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
2948 - Remove the HSAuthorityRecordStats option that version 0 hidden
2949 service authorities could have used to track statistics of overall
2950 hidden service usage.
2953 Changes in version 0.2.1.22 - 2010-01-19
2954 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
2955 authorities -- it would tell you its whole history of bridge descriptors
2956 if you make the right directory request. This stable update also
2957 rotates two of the seven v3 directory authority keys and locations.
2959 o Directory authority changes:
2960 - Rotate keys (both v3 identity and relay identity) for moria1
2964 - Stop bridge directory authorities from answering dbg-stability.txt
2965 directory queries, which would let people fetch a list of all
2966 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2969 Changes in version 0.2.1.21 - 2009-12-21
2970 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
2971 library. If you use Tor on Linux / Unix and you're getting SSL
2972 renegotiation errors, upgrading should help. We also recommend an
2973 upgrade if you're an exit relay.
2976 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2977 handshake from working unless we explicitly tell OpenSSL that we
2978 are using SSL renegotiation safely. We are, of course, but OpenSSL
2979 0.9.8l won't work unless we say we are.
2980 - Avoid crashing if the client is trying to upload many bytes and the
2981 circuit gets torn down at the same time, or if the flip side
2982 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
2985 - Do not refuse to learn about authority certs and v2 networkstatus
2986 documents that are older than the latest consensus. This bug might
2987 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2988 Spotted and fixed by xmux.
2989 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
2990 trigger platform-specific option misparsing case found by Coverity
2992 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
2993 trigger assert. Fixes bug 1173.
2996 Changes in version 0.2.2.6-alpha - 2009-11-19
2997 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
2998 support for the new lower-footprint "microdescriptor" directory design,
2999 future-proofing our consensus format against new hash functions or
3000 other changes, and an Android port. It also makes Tor compatible with
3001 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
3004 - Directory authorities can now create, vote on, and serve multiple
3005 parallel formats of directory data as part of their voting process.
3006 Partially implements Proposal 162: "Publish the consensus in
3008 - Directory authorities can now agree on and publish small summaries
3009 of router information that clients can use in place of regular
3010 server descriptors. This transition will eventually allow clients
3011 to use far less bandwidth for downloading information about the
3012 network. Begins the implementation of Proposal 158: "Clients
3013 download consensus + microdescriptors".
3014 - The directory voting system is now extensible to use multiple hash
3015 algorithms for signatures and resource selection. Newer formats
3016 are signed with SHA256, with a possibility for moving to a better
3017 hash algorithm in the future.
3018 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
3019 current and future memory pages via mlockall(). On supported
3020 platforms (modern Linux and probably BSD but not Windows or OS X),
3021 this should effectively disable any and all attempts to page out
3022 memory. This option requires that you start your Tor as root --
3023 if you use DisableAllSwap, please consider using the User option
3024 to properly reduce the privileges of your Tor.
3025 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
3026 to help Tor build correctly for Android phones.
3029 - Work around a security feature in OpenSSL 0.9.8l that prevents our
3030 handshake from working unless we explicitly tell OpenSSL that we
3031 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
3032 won't work unless we say we are.
3035 - Fix a crash bug when trying to initialize the evdns module in
3036 Libevent 2. Bugfix on 0.2.1.16-rc.
3037 - Stop logging at severity 'warn' when some other Tor client tries
3038 to establish a circuit with us using weak DH keys. It's a protocol
3039 violation, but that doesn't mean ordinary users need to hear about
3040 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
3041 - Do not refuse to learn about authority certs and v2 networkstatus
3042 documents that are older than the latest consensus. This bug might
3043 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
3044 Spotted and fixed by xmux.
3045 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
3046 - If all authorities restart at once right before a consensus vote,
3047 nobody will vote about "Running", and clients will get a consensus
3048 with no usable relays. Instead, authorities refuse to build a
3049 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
3050 - If your relay can't keep up with the number of incoming create
3051 cells, it would log one warning per failure into your logs. Limit
3052 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
3053 - Bridges now use "reject *:*" as their default exit policy. Bugfix
3054 on 0.2.0.3-alpha; fixes bug 1113.
3055 - Fix a memory leak on directory authorities during voting that was
3056 introduced in 0.2.2.1-alpha. Found via valgrind.
3059 Changes in version 0.2.1.20 - 2009-10-15
3060 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
3061 services at once, prepares for more performance improvements, and
3062 fixes a bunch of smaller bugs.
3064 The Windows and OS X bundles also include a more recent Vidalia,
3065 and switch from Privoxy to Polipo.
3067 The OS X installers are now drag and drop. It's best to un-install
3068 Tor/Vidalia and then install this new bundle, rather than upgrade. If
3069 you want to upgrade, you'll need to update the paths for Tor and Polipo
3070 in the Vidalia Settings window.
3073 - Send circuit or stream sendme cells when our window has decreased
3074 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
3075 by Karsten when testing the "reduce circuit window" performance
3076 patch. Bugfix on the 54th commit on Tor -- from July 2002,
3077 before the release of Tor 0.0.0. This is the new winner of the
3079 - Fix a remotely triggerable memory leak when a consensus document
3080 contains more than one signature from the same voter. Bugfix on
3082 - Avoid segfault in rare cases when finishing an introduction circuit
3083 as a client and finding out that we don't have an introduction key
3084 for it. Fixes bug 1073. Reported by Aaron Swartz.
3087 - Tor now reads the "circwindow" parameter out of the consensus,
3088 and uses that value for its circuit package window rather than the
3089 default of 1000 cells. Begins the implementation of proposal 168.
3091 o New directory authorities:
3092 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
3094 - Move moria1 and tonga to alternate IP addresses.
3097 - Fix a signed/unsigned compile warning in 0.2.1.19.
3098 - Fix possible segmentation fault on directory authorities. Bugfix on
3100 - Fix an extremely rare infinite recursion bug that could occur if
3101 we tried to log a message after shutting down the log subsystem.
3102 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
3103 - Fix an obscure bug where hidden services on 64-bit big-endian
3104 systems might mis-read the timestamp in v3 introduce cells, and
3105 refuse to connect back to the client. Discovered by "rotor".
3106 Bugfix on 0.2.1.6-alpha.
3107 - We were triggering a CLOCK_SKEW controller status event whenever
3108 we connect via the v2 connection protocol to any relay that has
3109 a wrong clock. Instead, we should only inform the controller when
3110 it's a trusted authority that claims our clock is wrong. Bugfix
3111 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
3112 - We were telling the controller about CHECKING_REACHABILITY and
3113 REACHABILITY_FAILED status events whenever we launch a testing
3114 circuit or notice that one has failed. Instead, only tell the
3115 controller when we want to inform the user of overall success or
3116 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
3118 - Don't warn when we're using a circuit that ends with a node
3119 excluded in ExcludeExitNodes, but the circuit is not used to access
3120 the outside world. This should help fix bug 1090. Bugfix on
3122 - Work around a small memory leak in some versions of OpenSSL that
3123 stopped the memory used by the hostname TLS extension from being
3127 - Add a "getinfo status/accepted-server-descriptor" controller
3128 command, which is the recommended way for controllers to learn
3129 whether our server descriptor has been successfully received by at
3130 least on directory authority. Un-recommend good-server-descriptor
3131 getinfo and status events until we have a better design for them.
3134 Changes in version 0.2.2.5-alpha - 2009-10-11
3135 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
3138 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
3140 o Directory authorities:
3141 - Temporarily (just for this release) move dizum to an alternate
3145 Changes in version 0.2.2.4-alpha - 2009-10-10
3146 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
3147 introduces a new unit test framework, shifts directry authority
3148 addresses around to reduce the impact from recent blocking events,
3149 and fixes a few smaller bugs.
3152 - Fix several more asserts in the circuit_build_times code, for
3153 example one that causes Tor to fail to start once we have
3154 accumulated 5000 build times in the state file. Bugfixes on
3155 0.2.2.2-alpha; fixes bug 1108.
3157 o New directory authorities:
3158 - Move moria1 and Tonga to alternate IP addresses.
3161 - Log SSL state transitions at debug level during handshake, and
3162 include SSL states in error messages. This may help debug future
3163 SSL handshake issues.
3164 - Add a new "Handshake" log domain for activities that happen
3165 during the TLS handshake.
3166 - Revert to the "June 3 2009" ip-to-country file. The September one
3167 seems to have removed most US IP addresses.
3168 - Directory authorities now reject Tor relays with versions less than
3169 0.1.2.14. This step cuts out four relays from the current network,
3170 none of which are very big.
3173 - Fix a couple of smaller issues with gathering statistics. Bugfixes
3175 - Fix two memory leaks in the error case of
3176 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
3177 - Don't count one-hop circuits when we're estimating how long it
3178 takes circuits to build on average. Otherwise we'll set our circuit
3179 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
3180 - Directory authorities no longer change their opinion of, or vote on,
3181 whether a router is Running, unless they have themselves been
3182 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
3185 o Code simplifications and refactoring:
3186 - Revise our unit tests to use the "tinytest" framework, so we
3187 can run tests in their own processes, have smarter setup/teardown
3188 code, and so on. The unit test code has moved to its own
3189 subdirectory, and has been split into multiple modules.
3192 Changes in version 0.2.2.3-alpha - 2009-09-23
3193 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
3196 - Fix an overzealous assert in our new circuit build timeout code.
3197 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
3200 - If the networkstatus consensus tells us that we should use a
3201 negative circuit package window, ignore it. Otherwise we'll
3202 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
3205 Changes in version 0.2.2.2-alpha - 2009-09-21
3206 Tor 0.2.2.2-alpha introduces our latest performance improvement for
3207 clients: Tor tracks the average time it takes to build a circuit, and
3208 avoids using circuits that take too long to build. For fast connections,
3209 this feature can cut your expected latency in half. For slow or flaky
3210 connections, it could ruin your Tor experience. Let us know if it does!
3213 - Tor now tracks how long it takes to build client-side circuits
3214 over time, and adapts its timeout to local network performance.
3215 Since a circuit that takes a long time to build will also provide
3216 bad performance, we get significant latency improvements by
3217 discarding the slowest 20% of circuits. Specifically, Tor creates
3218 circuits more aggressively than usual until it has enough data
3219 points for a good timeout estimate. Implements proposal 151.
3220 We are especially looking for reports (good and bad) from users with
3221 both EDGE and broadband connections that can move from broadband
3222 to EDGE and find out if the build-time data in the .tor/state gets
3223 reset without loss of Tor usability. You should also see a notice
3224 log message telling you that Tor has reset its timeout.
3225 - Directory authorities can now vote on arbitary integer values as
3226 part of the consensus process. This is designed to help set
3227 network-wide parameters. Implements proposal 167.
3228 - Tor now reads the "circwindow" parameter out of the consensus,
3229 and uses that value for its circuit package window rather than the
3230 default of 1000 cells. Begins the implementation of proposal 168.
3233 - Fix a remotely triggerable memory leak when a consensus document
3234 contains more than one signature from the same voter. Bugfix on
3238 - Fix an extremely rare infinite recursion bug that could occur if
3239 we tried to log a message after shutting down the log subsystem.
3240 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
3241 - Fix parsing for memory or time units given without a space between
3242 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
3243 - A networkstatus vote must contain exactly one signature. Spec
3244 conformance issue. Bugfix on 0.2.0.3-alpha.
3245 - Fix an obscure bug where hidden services on 64-bit big-endian
3246 systems might mis-read the timestamp in v3 introduce cells, and
3247 refuse to connect back to the client. Discovered by "rotor".
3248 Bugfix on 0.2.1.6-alpha.
3249 - We were triggering a CLOCK_SKEW controller status event whenever
3250 we connect via the v2 connection protocol to any relay that has
3251 a wrong clock. Instead, we should only inform the controller when
3252 it's a trusted authority that claims our clock is wrong. Bugfix
3253 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
3254 - We were telling the controller about CHECKING_REACHABILITY and
3255 REACHABILITY_FAILED status events whenever we launch a testing
3256 circuit or notice that one has failed. Instead, only tell the
3257 controller when we want to inform the user of overall success or
3258 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
3260 - Don't warn when we're using a circuit that ends with a node
3261 excluded in ExcludeExitNodes, but the circuit is not used to access
3262 the outside world. This should help fix bug 1090, but more problems
3263 remain. Bugfix on 0.2.1.6-alpha.
3264 - Work around a small memory leak in some versions of OpenSSL that
3265 stopped the memory used by the hostname TLS extension from being
3267 - Make our 'torify' script more portable; if we have only one of
3268 'torsocks' or 'tsocks' installed, don't complain to the user;
3269 and explain our warning about tsocks better.
3272 - Add a "getinfo status/accepted-server-descriptor" controller
3273 command, which is the recommended way for controllers to learn
3274 whether our server descriptor has been successfully received by at
3275 least on directory authority. Un-recommend good-server-descriptor
3276 getinfo and status events until we have a better design for them.
3277 - Update to the "September 4 2009" ip-to-country file.
3280 Changes in version 0.2.2.1-alpha - 2009-08-26
3281 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
3282 Tor clients to bootstrap on networks where only port 80 is reachable,
3283 makes it more straightforward to support hardware crypto accelerators,
3284 and starts the groundwork for gathering stats safely at relays.
3287 - Start the process of disabling ".exit" address notation, since it
3288 can be used for a variety of esoteric application-level attacks
3289 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
3292 o New directory authorities:
3293 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
3297 - New AccelName and AccelDir options add support for dynamic OpenSSL
3298 hardware crypto acceleration engines.
3299 - Tor now supports tunneling all of its outgoing connections over
3300 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
3301 configuration options. Code by Christopher Davis.
3304 - Send circuit or stream sendme cells when our window has decreased
3305 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
3306 by Karsten when testing the "reduce circuit window" performance
3307 patch. Bugfix on the 54th commit on Tor -- from July 2002,
3308 before the release of Tor 0.0.0. This is the new winner of the
3311 o New options for gathering stats safely:
3312 - Directory mirrors that set "DirReqStatistics 1" write statistics
3313 about directory requests to disk every 24 hours. As compared to the
3314 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
3315 1) stats are written to disk exactly every 24 hours; 2) estimated
3316 shares of v2 and v3 requests are determined as mean values, not at
3317 the end of a measurement period; 3) unresolved requests are listed
3318 with country code '??'; 4) directories also measure download times.
3319 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
3320 number of exit streams and transferred bytes per port to disk every
3322 - Relays that set "CellStatistics 1" write statistics on how long
3323 cells spend in their circuit queues to disk every 24 hours.
3324 - Entry nodes that set "EntryStatistics 1" write statistics on the
3325 rough number and origins of connecting clients to disk every 24
3327 - Relays that write any of the above statistics to disk and set
3328 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
3329 their extra-info documents.
3332 - New --digests command-line switch to output the digests of the
3333 source files Tor was built with.
3334 - The "torify" script now uses torsocks where available.
3335 - The memarea code now uses a sentinel value at the end of each area
3336 to make sure nothing writes beyond the end of an area. This might
3337 help debug some conceivable causes of bug 930.
3338 - Time and memory units in the configuration file can now be set to
3339 fractional units. For example, "2.5 GB" is now a valid value for
3341 - Certain Tor clients (such as those behind check.torproject.org) may
3342 want to fetch the consensus in an extra early manner. To enable this
3343 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
3344 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
3345 as only certain clients who must have this information sooner should
3347 - Instead of adding the svn revision to the Tor version string, report
3348 the git commit (when we're building from a git checkout).
3351 - If any of the v3 certs we download are unparseable, we should
3352 actually notice the failure so we don't retry indefinitely. Bugfix
3353 on 0.2.0.x; reported by "rotator".
3354 - If the cached cert file is unparseable, warn but don't exit.
3355 - Fix possible segmentation fault on directory authorities. Bugfix on
3357 - When Tor fails to parse a descriptor of any kind, dump it to disk.
3358 Might help diagnosing bug 1051.
3360 o Deprecated and removed features:
3361 - The controller no longer accepts the old obsolete "addr-mappings/"
3362 or "unregistered-servers-" GETINFO values.
3363 - Hidden services no longer publish version 0 descriptors, and clients
3364 do not request or use version 0 descriptors. However, the old hidden
3365 service authorities still accept and serve version 0 descriptors
3366 when contacted by older hidden services/clients.
3367 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
3368 always on; using them is necessary for correct forward-compatible
3370 - Remove support for .noconnect style addresses. Nobody was using
3371 them, and they provided another avenue for detecting Tor users
3372 via application-level web tricks.
3374 o Packaging changes:
3375 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
3376 installer bundles. See
3377 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
3378 for details of what's new in Vidalia 0.2.3.
3379 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
3380 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
3381 configuration file, rather than the old Privoxy.
3382 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
3383 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
3384 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
3385 better compatibility with OS X 10.6, aka Snow Leopard.
3386 - OS X Vidalia Bundle: The multi-package installer is now replaced
3387 by a simple drag and drop to the /Applications folder. This change
3388 occurred with the upgrade to Vidalia 0.2.3.
3391 Changes in version 0.2.1.19 - 2009-07-28
3392 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
3393 services on Tor 0.2.1.3-alpha through 0.2.1.18.
3396 - Make accessing hidden services on 0.2.1.x work right again.
3397 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
3398 part of patch provided by "optimist".
3401 - When a relay/bridge is writing out its identity key fingerprint to
3402 the "fingerprint" file and to its logs, write it without spaces. Now
3403 it will look like the fingerprints in our bridges documentation,
3404 and confuse fewer users.
3407 - Relays no longer publish a new server descriptor if they change
3408 their MaxAdvertisedBandwidth config option but it doesn't end up
3409 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
3410 fixes bug 1026. Patch from Sebastian.
3411 - Avoid leaking memory every time we get a create cell but we have
3412 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
3413 fixes bug 1034. Reported by BarkerJr.
3416 Changes in version 0.2.1.18 - 2009-07-24
3417 Tor 0.2.1.18 lays the foundations for performance improvements,
3418 adds status events to help users diagnose bootstrap problems, adds
3419 optional authentication/authorization for hidden services, fixes a
3420 variety of potential anonymity problems, and includes a huge pile of
3421 other features and bug fixes.
3424 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
3427 Changes in version 0.2.1.17-rc - 2009-07-07
3428 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
3429 candidate for the 0.2.1.x series. It lays the groundwork for further
3430 client performance improvements, and also fixes a big bug with directory
3431 authorities that were causing them to assign Guard and Stable flags
3434 The Windows bundles also finally include the geoip database that we
3435 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
3436 should actually install Torbutton rather than giving you a cryptic
3437 failure message (oops).
3440 - Clients now use the bandwidth values in the consensus, rather than
3441 the bandwidth values in each relay descriptor. This approach opens
3442 the door to more accurate bandwidth estimates once the directory
3443 authorities start doing active measurements. Implements more of
3447 - When Tor clients restart after 1-5 days, they discard all their
3448 cached descriptors as too old, but they still use the cached
3449 consensus document. This approach is good for robustness, but
3450 bad for performance: since they don't know any bandwidths, they
3451 end up choosing at random rather than weighting their choice by
3452 speed. Fixed by the above feature of putting bandwidths in the
3453 consensus. Bugfix on 0.2.0.x.
3454 - Directory authorities were neglecting to mark relays down in their
3455 internal histories if the relays fall off the routerlist without
3456 ever being found unreachable. So there were relays in the histories
3457 that haven't been seen for eight months, and are listed as being
3458 up for eight months. This wreaked havoc on the "median wfu"
3459 and "median mtbf" calculations, in turn making Guard and Stable
3460 flags very wrong, hurting network performance. Fixes bugs 696 and
3461 969. Bugfix on 0.2.0.6-alpha.
3464 - Serve the DirPortFrontPage page even when we have been approaching
3465 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
3466 - The control port would close the connection before flushing long
3467 replies, such as the network consensus, if a QUIT command was issued
3468 before the reply had completed. Now, the control port flushes all
3469 pending replies before closing the connection. Also fixed a spurious
3470 warning when a QUIT command is issued after a malformed or rejected
3471 AUTHENTICATE command, but before the connection was closed. Patch
3472 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
3473 - When we can't find an intro key for a v2 hidden service descriptor,
3474 fall back to the v0 hidden service descriptor and log a bug message.
3475 Workaround for bug 1024.
3476 - Fix a log message that did not respect the SafeLogging option.
3480 - If we're a relay and we change our IP address, be more verbose
3481 about the reason that made us change. Should help track down
3482 further bugs for relays on dynamic IP addresses.
3485 Changes in version 0.2.0.35 - 2009-06-24
3487 - Avoid crashing in the presence of certain malformed descriptors.
3488 Found by lark, and by automated fuzzing.
3489 - Fix an edge case where a malicious exit relay could convince a
3490 controller that the client's DNS question resolves to an internal IP
3491 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
3494 - Finally fix the bug where dynamic-IP relays disappear when their
3495 IP address changes: directory mirrors were mistakenly telling
3496 them their old address if they asked via begin_dir, so they
3497 never got an accurate answer about their new address, so they
3498 just vanished after a day. For belt-and-suspenders, relays that
3499 don't set Address in their config now avoid using begin_dir for
3500 all direct connections. Should fix bugs 827, 883, and 900.
3501 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
3502 that would occur on some exit nodes when DNS failures and timeouts
3503 occurred in certain patterns. Fix for bug 957.
3506 - When starting with a cache over a few days old, do not leak
3507 memory for the obsolete router descriptors in it. Bugfix on
3508 0.2.0.33; fixes bug 672.
3509 - Hidden service clients didn't use a cached service descriptor that
3510 was older than 15 minutes, but wouldn't fetch a new one either,
3511 because there was already one in the cache. Now, fetch a v2
3512 descriptor unless the same descriptor was added to the cache within
3513 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
3516 Changes in version 0.2.1.16-rc - 2009-06-20
3517 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
3518 a bunch of minor bugs.
3521 - Fix an edge case where a malicious exit relay could convince a
3522 controller that the client's DNS question resolves to an internal IP
3523 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
3525 o Major performance improvements (on 0.2.0.x):
3526 - Disable and refactor some debugging checks that forced a linear scan
3527 over the whole server-side DNS cache. These accounted for over 50%
3528 of CPU time on a relatively busy exit node's gprof profile. Found
3530 - Disable some debugging checks that appeared in exit node profile
3534 - Update to the "June 3 2009" ip-to-country file.
3535 - Do not have tor-resolve automatically refuse all .onion addresses;
3536 if AutomapHostsOnResolve is set in your torrc, this will work fine.
3538 o Minor bugfixes (on 0.2.0.x):
3539 - Log correct error messages for DNS-related network errors on
3541 - Fix a race condition that could cause crashes or memory corruption
3542 when running as a server with a controller listening for log
3544 - Avoid crashing when we have a policy specified in a DirPolicy or
3545 SocksPolicy or ReachableAddresses option with ports set on it,
3546 and we re-load the policy. May fix bug 996.
3547 - Hidden service clients didn't use a cached service descriptor that
3548 was older than 15 minutes, but wouldn't fetch a new one either,
3549 because there was already one in the cache. Now, fetch a v2
3550 descriptor unless the same descriptor was added to the cache within
3551 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
3553 o Minor bugfixes (on 0.2.1.x):
3554 - Don't warn users about low port and hibernation mix when they
3555 provide a *ListenAddress directive to fix that. Bugfix on
3557 - When switching back and forth between bridge mode, do not start
3558 gathering GeoIP data until two hours have passed.
3559 - Do not complain that the user has requested an excluded node as
3560 an exit when the node is not really an exit. This could happen
3561 because the circuit was for testing, or an introduction point.
3565 Changes in version 0.2.1.15-rc - 2009-05-25
3566 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
3567 series. It fixes a major bug on fast exit relays, as well as a variety
3570 o Major bugfixes (on 0.2.0.x):
3571 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
3572 that would occur on some exit nodes when DNS failures and timeouts
3573 occurred in certain patterns. Fix for bug 957.
3575 o Minor bugfixes (on 0.2.0.x):
3576 - Actually return -1 in the error case for read_bandwidth_usage().
3577 Harmless bug, since we currently don't care about the return value
3578 anywhere. Bugfix on 0.2.0.9-alpha.
3579 - Provide a more useful log message if bug 977 (related to buffer
3580 freelists) ever reappears, and do not crash right away.
3581 - Fix an assertion failure on 64-bit platforms when we allocated
3582 memory right up to the end of a memarea, then realigned the memory
3583 one step beyond the end. Fixes a possible cause of bug 930.
3584 - Protect the count of open sockets with a mutex, so we can't
3585 corrupt it when two threads are closing or opening sockets at once.
3586 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
3587 - Don't allow a bridge to publish its router descriptor to a
3588 non-bridge directory authority. Fixes part of bug 932.
3589 - When we change to or from being a bridge, reset our counts of
3590 client usage by country. Fixes bug 932.
3591 - Fix a bug that made stream bandwidth get misreported to the
3593 - Stop using malloc_usable_size() to use more area than we had
3594 actually allocated: it was safe, but made valgrind really unhappy.
3595 - Fix a memory leak when v3 directory authorities load their keys
3596 and cert from disk. Bugfix on 0.2.0.1-alpha.
3598 o Minor bugfixes (on 0.2.1.x):
3599 - Fix use of freed memory when deciding to mark a non-addable
3600 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
3603 Changes in version 0.2.1.14-rc - 2009-04-12
3604 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
3605 series. It begins fixing some major performance problems, and also
3606 finally addresses the bug that was causing relays on dynamic IP
3607 addresses to fall out of the directory.
3610 - Clients replace entry guards that were chosen more than a few months
3611 ago. This change should significantly improve client performance,
3612 especially once more people upgrade, since relays that have been
3613 a guard for a long time are currently overloaded.
3615 o Major bugfixes (on 0.2.0):
3616 - Finally fix the bug where dynamic-IP relays disappear when their
3617 IP address changes: directory mirrors were mistakenly telling
3618 them their old address if they asked via begin_dir, so they
3619 never got an accurate answer about their new address, so they
3620 just vanished after a day. For belt-and-suspenders, relays that
3621 don't set Address in their config now avoid using begin_dir for
3622 all direct connections. Should fix bugs 827, 883, and 900.
3623 - Relays were falling out of the networkstatus consensus for
3624 part of a day if they changed their local config but the
3625 authorities discarded their new descriptor as "not sufficiently
3626 different". Now directory authorities accept a descriptor as changed
3627 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
3629 - Avoid crashing in the presence of certain malformed descriptors.
3630 Found by lark, and by automated fuzzing.
3633 - When generating circuit events with verbose nicknames for
3634 controllers, try harder to look up nicknames for routers on a
3635 circuit. (Previously, we would look in the router descriptors we had
3636 for nicknames, but not in the consensus.) Partial fix for bug 941.
3637 - If the bridge config line doesn't specify a port, assume 443.
3638 This makes bridge lines a bit smaller and easier for users to
3640 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
3641 bytes (aka 20KB/s), to match our documentation. Also update
3642 directory authorities so they always assign the Fast flag to relays
3643 with 20KB/s of capacity. Now people running relays won't suddenly
3644 find themselves not seeing any use, if the network gets faster
3646 - Update to the "April 3 2009" ip-to-country file.
3649 - Avoid trying to print raw memory to the logs when we decide to
3650 give up on downloading a given relay descriptor. Bugfix on
3652 - In tor-resolve, when the Tor client to use is specified by
3653 <hostname>:<port>, actually use the specified port rather than
3654 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
3655 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
3656 - When starting with a cache over a few days old, do not leak
3657 memory for the obsolete router descriptors in it. Bugfix on
3659 - Avoid double-free on list of successfully uploaded hidden
3660 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
3661 - Change memarea_strndup() implementation to work even when
3662 duplicating a string at the end of a page. This bug was
3663 harmless for now, but could have meant crashes later. Fix by
3664 lark. Bugfix on 0.2.1.1-alpha.
3665 - Limit uploaded directory documents to be 16M rather than 500K.
3666 The directory authorities were refusing v3 consensus votes from
3667 other authorities, since the votes are now 504K. Fixes bug 959;
3668 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
3669 - Directory authorities should never send a 503 "busy" response to
3670 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
3674 Changes in version 0.2.1.13-alpha - 2009-03-09
3675 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
3676 cleanups. We're finally getting close to a release candidate.
3679 - Correctly update the list of which countries we exclude as
3680 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
3681 lark. Bugfix on 0.2.1.6-alpha.
3683 o Minor bugfixes (on 0.2.0.x and earlier):
3684 - Automatically detect MacOSX versions earlier than 10.4.0, and
3685 disable kqueue from inside Tor when running with these versions.
3686 We previously did this from the startup script, but that was no
3687 help to people who didn't use the startup script. Resolves bug 863.
3688 - When we had picked an exit node for a connection, but marked it as
3689 "optional", and it turned out we had no onion key for the exit,
3690 stop wanting that exit and try again. This situation may not
3691 be possible now, but will probably become feasible with proposal
3692 158. Spotted by rovv. Fixes another case of bug 752.
3693 - Clients no longer cache certificates for authorities they do not
3694 recognize. Bugfix on 0.2.0.9-alpha.
3695 - When we can't transmit a DNS request due to a network error, retry
3696 it after a while, and eventually transmit a failing response to
3697 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
3698 - If the controller claimed responsibility for a stream, but that
3699 stream never finished making its connection, it would live
3700 forever in circuit_wait state. Now we close it after SocksTimeout
3701 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
3702 - Drop begin cells to a hidden service if they come from the middle
3703 of a circuit. Patch from lark.
3704 - When we erroneously receive two EXTEND cells for the same circuit
3705 ID on the same connection, drop the second. Patch from lark.
3706 - Fix a crash that occurs on exit nodes when a nameserver request
3707 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
3708 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
3710 - Do not assume that a stack-allocated character array will be
3711 64-bit aligned on platforms that demand that uint64_t access is
3712 aligned. Possible fix for bug 604.
3713 - Parse dates and IPv4 addresses in a locale- and libc-independent
3714 manner, to avoid platform-dependent behavior on malformed input.
3715 - Build correctly when configured to build outside the main source
3716 path. Patch from Michael Gold.
3717 - We were already rejecting relay begin cells with destination port
3718 of 0. Now also reject extend cells with destination port or address
3719 of 0. Suggested by lark.
3721 o Minor bugfixes (on 0.2.1.x):
3722 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
3723 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
3724 - If we're an exit node, scrub the IP address to which we are exiting
3725 in the logs. Bugfix on 0.2.1.8-alpha.
3728 - On Linux, use the prctl call to re-enable core dumps when the user
3730 - New controller event NEWCONSENSUS that lists the networkstatus
3731 lines for every recommended relay. Now controllers like Torflow
3732 can keep up-to-date on which relays they should be using.
3733 - Update to the "February 26 2009" ip-to-country file.
3736 Changes in version 0.2.0.34 - 2009-02-08
3737 Tor 0.2.0.34 features several more security-related fixes. You should
3738 upgrade, especially if you run an exit relay (remote crash) or a
3739 directory authority (remote infinite loop), or you're on an older
3740 (pre-XP) or not-recently-patched Windows (remote exploit).
3742 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
3743 have many known flaws, and nobody should be using them. You should
3744 upgrade. If you're using a Linux or BSD and its packages are obsolete,
3745 stop using those packages and upgrade anyway.
3748 - Fix an infinite-loop bug on handling corrupt votes under certain
3749 circumstances. Bugfix on 0.2.0.8-alpha.
3750 - Fix a temporary DoS vulnerability that could be performed by
3751 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3752 - Avoid a potential crash on exit nodes when processing malformed
3753 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
3754 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
3755 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
3758 - Fix compilation on systems where time_t is a 64-bit integer.
3759 Patch from Matthias Drochner.
3760 - Don't consider expiring already-closed client connections. Fixes
3761 bug 893. Bugfix on 0.0.2pre20.
3764 Changes in version 0.2.1.12-alpha - 2009-02-08
3765 Tor 0.2.1.12-alpha features several more security-related fixes. You
3766 should upgrade, especially if you run an exit relay (remote crash) or
3767 a directory authority (remote infinite loop), or you're on an older
3768 (pre-XP) or not-recently-patched Windows (remote exploit). It also
3769 includes a big pile of minor bugfixes and cleanups.
3772 - Fix an infinite-loop bug on handling corrupt votes under certain
3773 circumstances. Bugfix on 0.2.0.8-alpha.
3774 - Fix a temporary DoS vulnerability that could be performed by
3775 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3776 - Avoid a potential crash on exit nodes when processing malformed
3777 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
3780 - Let controllers actually ask for the "clients_seen" event for
3781 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
3782 reported by Matt Edman.
3783 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
3785 - Fix a bug in address parsing that was preventing bridges or hidden
3786 service targets from being at IPv6 addresses.
3787 - Solve a bug that kept hardware crypto acceleration from getting
3788 enabled when accounting was turned on. Fixes bug 907. Bugfix on
3790 - Remove a bash-ism from configure.in to build properly on non-Linux
3791 platforms. Bugfix on 0.2.1.1-alpha.
3792 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
3793 headers. Bugfix on 0.2.0.10-alpha.
3794 - Don't consider expiring already-closed client connections. Fixes
3795 bug 893. Bugfix on 0.0.2pre20.
3796 - Fix another interesting corner-case of bug 891 spotted by rovv:
3797 Previously, if two hosts had different amounts of clock drift, and
3798 one of them created a new connection with just the wrong timing,
3799 the other might decide to deprecate the new connection erroneously.
3800 Bugfix on 0.1.1.13-alpha.
3801 - Resolve a very rare crash bug that could occur when the user forced
3802 a nameserver reconfiguration during the middle of a nameserver
3803 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
3804 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
3805 Bugfix on 0.2.1.7-alpha.
3806 - If we're using bridges and our network goes away, be more willing
3807 to forgive our bridges and try again when we get an application
3808 request. Bugfix on 0.2.0.x.
3811 - Support platforms where time_t is 64 bits long. (Congratulations,
3812 NetBSD!) Patch from Matthias Drochner.
3813 - Add a 'getinfo status/clients-seen' controller command, in case
3814 controllers want to hear clients_seen events but connect late.
3817 - Disable GCC's strict alias optimization by default, to avoid the
3818 likelihood of its introducing subtle bugs whenever our code violates
3819 the letter of C99's alias rules.
3822 Changes in version 0.2.0.33 - 2009-01-21
3823 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
3824 useful to users. It also finally fixes a bug where a relay or client
3825 that's been off for many days would take a long time to bootstrap.
3827 This update also fixes an important security-related bug reported by
3828 Ilja van Sprundel. You should upgrade. (We'll send out more details
3829 about the bug once people have had some time to upgrade.)
3832 - Fix a heap-corruption bug that may be remotely triggerable on
3833 some platforms. Reported by Ilja van Sprundel.
3836 - When a stream at an exit relay is in state "resolving" or
3837 "connecting" and it receives an "end" relay cell, the exit relay
3838 would silently ignore the end cell and not close the stream. If
3839 the client never closes the circuit, then the exit relay never
3840 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
3842 - When sending CREATED cells back for a given circuit, use a 64-bit
3843 connection ID to find the right connection, rather than an addr:port
3844 combination. Now that we can have multiple OR connections between
3845 the same ORs, it is no longer possible to use addr:port to uniquely
3846 identify a connection.
3847 - Bridge relays that had DirPort set to 0 would stop fetching
3848 descriptors shortly after startup, and then briefly resume
3849 after a new bandwidth test and/or after publishing a new bridge
3850 descriptor. Bridge users that try to bootstrap from them would
3851 get a recent networkstatus but would get descriptors from up to
3852 18 hours earlier, meaning most of the descriptors were obsolete
3853 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3854 - Prevent bridge relays from serving their 'extrainfo' document
3855 to anybody who asks, now that extrainfo docs include potentially
3856 sensitive aggregated client geoip summaries. Bugfix on
3858 - If the cached networkstatus consensus is more than five days old,
3859 discard it rather than trying to use it. In theory it could be
3860 useful because it lists alternate directory mirrors, but in practice
3861 it just means we spend many minutes trying directory mirrors that
3862 are long gone from the network. Also discard router descriptors as
3863 we load them if they are more than five days old, since the onion
3864 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
3867 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
3868 could make gcc generate non-functional binary search code. Bugfix
3870 - Build correctly on platforms without socklen_t.
3871 - Compile without warnings on solaris.
3872 - Avoid potential crash on internal error during signature collection.
3873 Fixes bug 864. Patch from rovv.
3874 - Correct handling of possible malformed authority signing key
3875 certificates with internal signature types. Fixes bug 880.
3876 Bugfix on 0.2.0.3-alpha.
3877 - Fix a hard-to-trigger resource leak when logging credential status.
3879 - When we can't initialize DNS because the network is down, do not
3880 automatically stop Tor from starting. Instead, we retry failed
3881 dns_init() every 10 minutes, and change the exit policy to reject
3882 *:* until one succeeds. Fixes bug 691.
3883 - Use 64 bits instead of 32 bits for connection identifiers used with
3884 the controller protocol, to greatly reduce risk of identifier reuse.
3885 - When we're choosing an exit node for a circuit, and we have
3886 no pending streams, choose a good general exit rather than one that
3887 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
3888 - Fix another case of assuming, when a specific exit is requested,
3889 that we know more than the user about what hosts it allows.
3890 Fixes one case of bug 752. Patch from rovv.
3891 - Clip the MaxCircuitDirtiness config option to a minimum of 10
3892 seconds. Warn the user if lower values are given in the
3893 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
3894 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
3895 user if lower values are given in the configuration. Bugfix on
3896 0.1.1.17-rc. Patch by Sebastian.
3897 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
3898 the cache because we already had a v0 descriptor with the same ID.
3899 Bugfix on 0.2.0.18-alpha.
3900 - Fix a race condition when freeing keys shared between main thread
3901 and CPU workers that could result in a memory leak. Bugfix on
3902 0.1.0.1-rc. Fixes bug 889.
3903 - Send a valid END cell back when a client tries to connect to a
3904 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
3905 840. Patch from rovv.
3906 - Check which hops rendezvous stream cells are associated with to
3907 prevent possible guess-the-streamid injection attacks from
3908 intermediate hops. Fixes another case of bug 446. Based on patch
3910 - If a broken client asks a non-exit router to connect somewhere,
3911 do not even do the DNS lookup before rejecting the connection.
3912 Fixes another case of bug 619. Patch from rovv.
3913 - When a relay gets a create cell it can't decrypt (e.g. because it's
3914 using the wrong onion key), we were dropping it and letting the
3915 client time out. Now actually answer with a destroy cell. Fixes
3916 bug 904. Bugfix on 0.0.2pre8.
3918 o Minor bugfixes (hidden services):
3919 - Do not throw away existing introduction points on SIGHUP. Bugfix on
3920 0.0.6pre1. Patch by Karsten. Fixes bug 874.
3923 - Report the case where all signatures in a detached set are rejected
3924 differently than the case where there is an error handling the
3926 - When we realize that another process has modified our cached
3927 descriptors, print out a more useful error message rather than
3928 triggering an assertion. Fixes bug 885. Patch from Karsten.
3929 - Implement the 0x20 hack to better resist DNS poisoning: set the
3930 case on outgoing DNS requests randomly, and reject responses that do
3931 not match the case correctly. This logic can be disabled with the
3932 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
3933 of servers that do not reliably preserve case in replies. See
3934 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
3936 - Check DNS replies for more matching fields to better resist DNS
3938 - Never use OpenSSL compression: it wastes RAM and CPU trying to
3939 compress cells, which are basically all encrypted, compressed, or
3943 Changes in version 0.2.1.11-alpha - 2009-01-20
3944 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
3945 week it will take a long time to bootstrap again" bug. It also fixes
3946 an important security-related bug reported by Ilja van Sprundel. You
3947 should upgrade. (We'll send out more details about the bug once people
3948 have had some time to upgrade.)
3951 - Fix a heap-corruption bug that may be remotely triggerable on
3952 some platforms. Reported by Ilja van Sprundel.
3955 - Discard router descriptors as we load them if they are more than
3956 five days old. Otherwise if Tor is off for a long time and then
3957 starts with cached descriptors, it will try to use the onion
3958 keys in those obsolete descriptors when building circuits. Bugfix
3959 on 0.2.0.x. Fixes bug 887.
3962 - Try to make sure that the version of Libevent we're running with
3963 is binary-compatible with the one we built with. May address bug
3965 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
3966 for bug 905. Bugfix on 0.2.1.7-alpha.
3967 - Add a new --enable-local-appdata configuration switch to change
3968 the default location of the datadir on win32 from APPDATA to
3969 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
3970 entirely. Patch from coderman.
3973 - Make outbound DNS packets respect the OutboundBindAddress setting.
3974 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
3975 - When our circuit fails at the first hop (e.g. we get a destroy
3976 cell back), avoid using that OR connection anymore, and also
3977 tell all the one-hop directory requests waiting for it that they
3978 should fail. Bugfix on 0.2.1.3-alpha.
3979 - In the torify(1) manpage, mention that tsocks will leak your
3983 Changes in version 0.2.1.10-alpha - 2009-01-06
3984 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
3985 would make the bridge relay not so useful if it had DirPort set to 0,
3986 and one that could let an attacker learn a little bit of information
3987 about the bridge's users), and a bug that would cause your Tor relay
3988 to ignore a circuit create request it can't decrypt (rather than reply
3989 with an error). It also fixes a wide variety of other bugs.
3992 - If the cached networkstatus consensus is more than five days old,
3993 discard it rather than trying to use it. In theory it could
3994 be useful because it lists alternate directory mirrors, but in
3995 practice it just means we spend many minutes trying directory
3996 mirrors that are long gone from the network. Helps bug 887 a bit;
3998 - Bridge relays that had DirPort set to 0 would stop fetching
3999 descriptors shortly after startup, and then briefly resume
4000 after a new bandwidth test and/or after publishing a new bridge
4001 descriptor. Bridge users that try to bootstrap from them would
4002 get a recent networkstatus but would get descriptors from up to
4003 18 hours earlier, meaning most of the descriptors were obsolete
4004 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
4005 - Prevent bridge relays from serving their 'extrainfo' document
4006 to anybody who asks, now that extrainfo docs include potentially
4007 sensitive aggregated client geoip summaries. Bugfix on
4011 - New controller event "clients_seen" to report a geoip-based summary
4012 of which countries we've seen clients from recently. Now controllers
4013 like Vidalia can show bridge operators that they're actually making
4015 - Build correctly against versions of OpenSSL 0.9.8 or later built
4016 without support for deprecated functions.
4017 - Update to the "December 19 2008" ip-to-country file.
4019 o Minor bugfixes (on 0.2.0.x):
4020 - Authorities now vote for the Stable flag for any router whose
4021 weighted MTBF is at least 5 days, regardless of the mean MTBF.
4022 - Do not remove routers as too old if we do not have any consensus
4023 document. Bugfix on 0.2.0.7-alpha.
4024 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
4025 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
4026 - When an exit relay resolves a stream address to a local IP address,
4027 do not just keep retrying that same exit relay over and
4028 over. Instead, just close the stream. Addresses bug 872. Bugfix
4029 on 0.2.0.32. Patch from rovv.
4030 - If a hidden service sends us an END cell, do not consider
4031 retrying the connection; just close it. Patch from rovv.
4032 - When we made bridge authorities stop serving bridge descriptors over
4033 unencrypted links, we also broke DirPort reachability testing for
4034 bridges. So bridges with a non-zero DirPort were printing spurious
4035 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
4036 - When a relay gets a create cell it can't decrypt (e.g. because it's
4037 using the wrong onion key), we were dropping it and letting the
4038 client time out. Now actually answer with a destroy cell. Fixes
4039 bug 904. Bugfix on 0.0.2pre8.
4040 - Squeeze 2-5% out of client performance (according to oprofile) by
4041 improving the implementation of some policy-manipulation functions.
4043 o Minor bugfixes (on 0.2.1.x):
4044 - Make get_interface_address() function work properly again; stop
4045 guessing the wrong parts of our address as our address.
4046 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
4047 send on that circuit. Otherwise we might violate the proposal-110
4048 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
4050 - When we're sending non-EXTEND cells to the first hop in a circuit,
4051 for example to use an encrypted directory connection, we don't need
4052 to use RELAY_EARLY cells: the first hop knows what kind of cell
4053 it is, and nobody else can even see the cell type. Conserving
4054 RELAY_EARLY cells makes it easier to cannibalize circuits like
4056 - Stop logging nameserver addresses in reverse order.
4057 - If we are retrying a directory download slowly over and over, do
4058 not automatically give up after the 254th failure. Bugfix on
4060 - Resume reporting accurate "stream end" reasons to the local control
4061 port. They were lost in the changes for Proposal 148. Bugfix on
4064 o Deprecated and removed features:
4065 - The old "tor --version --version" command, which would print out
4066 the subversion "Id" of most of the source files, is now removed. It
4067 turned out to be less useful than we'd expected, and harder to
4070 o Code simplifications and refactoring:
4071 - Change our header file guard macros to be less likely to conflict
4072 with system headers. Adam Langley noticed that we were conflicting
4073 with log.h on Android.
4074 - Tool-assisted documentation cleanup. Nearly every function or
4075 static variable in Tor should have its own documentation now.
4078 Changes in version 0.2.1.9-alpha - 2008-12-25
4079 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
4081 o New directory authorities:
4082 - gabelmoo (the authority run by Karsten Loesing) now has a new
4086 - Never use a connection with a mismatched address to extend a
4087 circuit, unless that connection is canonical. A canonical
4088 connection is one whose address is authenticated by the router's
4089 identity key, either in a NETINFO cell or in a router descriptor.
4090 - Avoid a possible memory corruption bug when receiving hidden service
4091 descriptors. Bugfix on 0.2.1.6-alpha.
4094 - Fix a logic error that would automatically reject all but the first
4095 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
4096 part of bug 813/868. Bug spotted by coderman.
4097 - When a stream at an exit relay is in state "resolving" or
4098 "connecting" and it receives an "end" relay cell, the exit relay
4099 would silently ignore the end cell and not close the stream. If
4100 the client never closes the circuit, then the exit relay never
4101 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
4103 - When we can't initialize DNS because the network is down, do not
4104 automatically stop Tor from starting. Instead, retry failed
4105 dns_init() every 10 minutes, and change the exit policy to reject
4106 *:* until one succeeds. Fixes bug 691.
4109 - Give a better error message when an overzealous init script says
4110 "sudo -u username tor --user username". Makes Bug 882 easier for
4112 - When a directory authority gives us a new guess for our IP address,
4113 log which authority we used. Hopefully this will help us debug
4114 the recent complaints about bad IP address guesses.
4115 - Detect svn revision properly when we're using git-svn.
4116 - Try not to open more than one descriptor-downloading connection
4117 to an authority at once. This should reduce load on directory
4118 authorities. Fixes bug 366.
4119 - Add cross-certification to newly generated certificates, so that
4120 a signing key is enough information to look up a certificate.
4121 Partial implementation of proposal 157.
4122 - Start serving certificates by <identity digest, signing key digest>
4123 pairs. Partial implementation of proposal 157.
4124 - Clients now never report any stream end reason except 'MISC'.
4125 Implements proposal 148.
4126 - On platforms with a maximum syslog string length, truncate syslog
4127 messages to that length ourselves, rather than relying on the
4128 system to do it for us.
4129 - Optimize out calls to time(NULL) that occur for every IO operation,
4130 or for every cell. On systems where time() is a slow syscall,
4131 this fix will be slightly helpful.
4132 - Exit servers can now answer resolve requests for ip6.arpa addresses.
4133 - When we download a descriptor that we then immediately (as
4134 a directory authority) reject, do not retry downloading it right
4135 away. Should save some bandwidth on authorities. Fix for bug
4136 888. Patch by Sebastian Hahn.
4137 - When a download gets us zero good descriptors, do not notify
4138 Tor that new directory information has arrived.
4139 - Avoid some nasty corner cases in the logic for marking connections
4140 as too old or obsolete or noncanonical for circuits. Partial
4143 o Minor features (controller):
4144 - New CONSENSUS_ARRIVED event to note when a new consensus has
4145 been fetched and validated.
4146 - When we realize that another process has modified our cached
4147 descriptors file, print out a more useful error message rather
4148 than triggering an assertion. Fixes bug 885. Patch from Karsten.
4149 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
4150 controllers to prevent SIGHUP from reloading the
4151 configuration. Fixes bug 856.
4154 - Resume using the correct "REASON=" stream when telling the
4155 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
4156 - When a canonical connection appears later in our internal list
4157 than a noncanonical one for a given OR ID, always use the
4158 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
4160 - Clip the MaxCircuitDirtiness config option to a minimum of 10
4161 seconds. Warn the user if lower values are given in the
4162 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
4163 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
4164 user if lower values are given in the configuration. Bugfix on
4165 0.1.1.17-rc. Patch by Sebastian.
4166 - Fix a race condition when freeing keys shared between main thread
4167 and CPU workers that could result in a memory leak. Bugfix on
4168 0.1.0.1-rc. Fixes bug 889.
4170 o Minor bugfixes (hidden services):
4171 - Do not throw away existing introduction points on SIGHUP (bugfix on
4172 0.0.6pre1); also, do not stall hidden services because we're
4173 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
4174 by John Brooks. Patch by Karsten. Fixes bug 874.
4175 - Fix a memory leak when we decline to add a v2 rendezvous
4176 descriptor to the cache because we already had a v0 descriptor
4177 with the same ID. Bugfix on 0.2.0.18-alpha.
4179 o Deprecated and removed features:
4180 - RedirectExits has been removed. It was deprecated since
4182 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
4183 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
4184 - Cell pools are now always enabled; --disable-cell-pools is ignored.
4186 o Code simplifications and refactoring:
4187 - Rename the confusing or_is_obsolete field to the more appropriate
4188 is_bad_for_new_circs, and move it to or_connection_t where it
4190 - Move edge-only flags from connection_t to edge_connection_t: not
4191 only is this better coding, but on machines of plausible alignment,
4192 it should save 4-8 bytes per connection_t. "Every little bit helps."
4193 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
4194 for consistency; keep old option working for backward compatibility.
4195 - Simplify the code for finding connections to use for a circuit.
4198 Changes in version 0.2.1.8-alpha - 2008-12-08
4199 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
4200 builds better on unusual platforms like Solaris and old OS X, and
4201 fixes a variety of other issues.
4204 - New DirPortFrontPage option that takes an html file and publishes
4205 it as "/" on the DirPort. Now relay operators can provide a
4206 disclaimer without needing to set up a separate webserver. There's
4207 a sample disclaimer in contrib/tor-exit-notice.html.
4210 - When the client is choosing entry guards, now it selects at most
4211 one guard from a given relay family. Otherwise we could end up with
4212 all of our entry points into the network run by the same operator.
4213 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
4216 - Fix a DOS opportunity during the voting signature collection process
4217 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
4218 - Fix a possible segfault when establishing an exit connection. Bugfix
4222 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
4224 - Made Tor a little less aggressive about deleting expired
4225 certificates. Partial fix for bug 854.
4226 - Stop doing unaligned memory access that generated bus errors on
4227 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
4228 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
4229 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
4230 - Make USR2 log-level switch take effect immediately. Bugfix on
4232 - If one win32 nameserver fails to get added, continue adding the
4233 rest, and don't automatically fail.
4234 - Use fcntl() for locking when flock() is not available. Should fix
4235 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
4236 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
4237 could make gcc generate non-functional binary search code. Bugfix
4239 - Build correctly on platforms without socklen_t.
4240 - Avoid potential crash on internal error during signature collection.
4241 Fixes bug 864. Patch from rovv.
4242 - Do not use C's stdio library for writing to log files. This will
4243 improve logging performance by a minute amount, and will stop
4244 leaking fds when our disk is full. Fixes bug 861.
4245 - Stop erroneous use of O_APPEND in cases where we did not in fact
4246 want to re-seek to the end of a file before every last write().
4247 - Correct handling of possible malformed authority signing key
4248 certificates with internal signature types. Fixes bug 880. Bugfix
4250 - Fix a hard-to-trigger resource leak when logging credential status.
4254 - Directory mirrors no longer fetch the v1 directory or
4255 running-routers files. They are obsolete, and nobody asks for them
4256 anymore. This is the first step to making v1 authorities obsolete.
4258 o Minor features (controller):
4259 - Return circuit purposes in response to GETINFO circuit-status. Fixes
4263 Changes in version 0.2.0.32 - 2008-11-20
4264 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
4265 packages (and maybe other packages) noticed by Theo de Raadt, fixes
4266 a smaller security flaw that might allow an attacker to access local
4267 services, further improves hidden service performance, and fixes a
4268 variety of other issues.
4271 - The "User" and "Group" config options did not clear the
4272 supplementary group entries for the Tor process. The "User" option
4273 is now more robust, and we now set the groups to the specified
4274 user's primary group. The "Group" option is now ignored. For more
4275 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
4276 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
4277 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
4278 - The "ClientDNSRejectInternalAddresses" config option wasn't being
4279 consistently obeyed: if an exit relay refuses a stream because its
4280 exit policy doesn't allow it, we would remember what IP address
4281 the relay said the destination address resolves to, even if it's
4282 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
4285 - Fix a DOS opportunity during the voting signature collection process
4286 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
4288 o Major bugfixes (hidden services):
4289 - When fetching v0 and v2 rendezvous service descriptors in parallel,
4290 we were failing the whole hidden service request when the v0
4291 descriptor fetch fails, even if the v2 fetch is still pending and
4292 might succeed. Similarly, if the last v2 fetch fails, we were
4293 failing the whole hidden service request even if a v0 fetch is
4294 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
4295 - When extending a circuit to a hidden service directory to upload a
4296 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
4297 requests failed, because the router descriptor has not been
4298 downloaded yet. In these cases, do not attempt to upload the
4299 rendezvous descriptor, but wait until the router descriptor is
4300 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
4301 descriptor from a hidden service directory for which the router
4302 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
4306 - Fix several infrequent memory leaks spotted by Coverity.
4307 - When testing for libevent functions, set the LDFLAGS variable
4308 correctly. Found by Riastradh.
4309 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
4310 bootstrapping with tunneled directory connections. Bugfix on
4311 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
4312 - When asked to connect to A.B.exit:80, if we don't know the IP for A
4313 and we know that server B rejects most-but-not all connections to
4314 port 80, we would previously reject the connection. Now, we assume
4315 the user knows what they were asking for. Fixes bug 752. Bugfix
4316 on 0.0.9rc5. Diagnosed by BarkerJr.
4317 - If we overrun our per-second write limits a little, count this as
4318 having used up our write allocation for the second, and choke
4319 outgoing directory writes. Previously, we had only counted this when
4320 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
4321 Bugfix on 0.2.0.x (??).
4322 - Remove the old v2 directory authority 'lefkada' from the default
4323 list. It has been gone for many months.
4324 - Stop doing unaligned memory access that generated bus errors on
4325 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
4326 - Make USR2 log-level switch take effect immediately. Bugfix on
4329 o Minor bugfixes (controller):
4330 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
4331 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
4334 Changes in version 0.2.1.7-alpha - 2008-11-08
4335 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
4336 packages (and maybe other packages) noticed by Theo de Raadt, fixes
4337 a smaller security flaw that might allow an attacker to access local
4338 services, adds better defense against DNS poisoning attacks on exit
4339 relays, further improves hidden service performance, and fixes a
4340 variety of other issues.
4343 - The "ClientDNSRejectInternalAddresses" config option wasn't being
4344 consistently obeyed: if an exit relay refuses a stream because its
4345 exit policy doesn't allow it, we would remember what IP address
4346 the relay said the destination address resolves to, even if it's
4347 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
4348 - The "User" and "Group" config options did not clear the
4349 supplementary group entries for the Tor process. The "User" option
4350 is now more robust, and we now set the groups to the specified
4351 user's primary group. The "Group" option is now ignored. For more
4352 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
4353 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
4354 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
4355 - Do not use or believe expired v3 authority certificates. Patch
4356 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
4359 - Now NodeFamily and MyFamily config options allow spaces in
4360 identity fingerprints, so it's easier to paste them in.
4361 Suggested by Lucky Green.
4362 - Implement the 0x20 hack to better resist DNS poisoning: set the
4363 case on outgoing DNS requests randomly, and reject responses that do
4364 not match the case correctly. This logic can be disabled with the
4365 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
4366 of servers that do not reliably preserve case in replies. See
4367 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
4369 - Preserve case in replies to DNSPort requests in order to support
4370 the 0x20 hack for resisting DNS poisoning attacks.
4372 o Hidden service performance improvements:
4373 - When the client launches an introduction circuit, retry with a
4374 new circuit after 30 seconds rather than 60 seconds.
4375 - Launch a second client-side introduction circuit in parallel
4376 after a delay of 15 seconds (based on work by Christian Wilms).
4377 - Hidden services start out building five intro circuits rather
4378 than three, and when the first three finish they publish a service
4379 descriptor using those. Now we publish our service descriptor much
4380 faster after restart.
4383 - Minor fix in the warning messages when you're having problems
4384 bootstrapping; also, be more forgiving of bootstrap problems when
4385 we're still making incremental progress on a given bootstrap phase.
4386 - When we're choosing an exit node for a circuit, and we have
4387 no pending streams, choose a good general exit rather than one that
4388 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
4389 - Send a valid END cell back when a client tries to connect to a
4390 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
4391 840. Patch from rovv.
4392 - If a broken client asks a non-exit router to connect somewhere,
4393 do not even do the DNS lookup before rejecting the connection.
4394 Fixes another case of bug 619. Patch from rovv.
4395 - Fix another case of assuming, when a specific exit is requested,
4396 that we know more than the user about what hosts it allows.
4397 Fixes another case of bug 752. Patch from rovv.
4398 - Check which hops rendezvous stream cells are associated with to
4399 prevent possible guess-the-streamid injection attacks from
4400 intermediate hops. Fixes another case of bug 446. Based on patch
4402 - Avoid using a negative right-shift when comparing 32-bit
4403 addresses. Possible fix for bug 845 and bug 811.
4404 - Make the assert_circuit_ok() function work correctly on circuits that
4405 have already been marked for close.
4406 - Fix read-off-the-end-of-string error in unit tests when decoding
4407 introduction points.
4408 - Fix uninitialized size field for memory area allocation: may improve
4409 memory performance during directory parsing.
4410 - Treat duplicate certificate fetches as failures, so that we do
4411 not try to re-fetch an expired certificate over and over and over.
4412 - Do not say we're fetching a certificate when we'll in fact skip it
4413 because of a pending download.
4416 Changes in version 0.2.1.6-alpha - 2008-09-30
4417 Tor 0.2.1.6-alpha further improves performance and robustness of
4418 hidden services, starts work on supporting per-country relay selection,
4419 and fixes a variety of smaller issues.
4422 - Implement proposal 121: make it possible to build hidden services
4423 that only certain clients are allowed to connect to. This is
4424 enforced at several points, so that unauthorized clients are unable
4425 to send INTRODUCE cells to the service, or even (depending on the
4426 type of authentication) to learn introduction points. This feature
4427 raises the bar for certain kinds of active attacks against hidden
4428 services. Code by Karsten Loesing.
4429 - Relays now store and serve v2 hidden service descriptors by default,
4430 i.e., the new default value for HidServDirectoryV2 is 1. This is
4431 the last step in proposal 114, which aims to make hidden service
4432 lookups more reliable.
4433 - Start work to allow node restrictions to include country codes. The
4434 syntax to exclude nodes in a country with country code XX is
4435 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
4436 refinement to decide what config options should take priority if
4437 you ask to both use a particular node and exclude it.
4438 - Allow ExitNodes list to include IP ranges and country codes, just
4439 like the Exclude*Nodes lists. Patch from Robert Hogan.
4442 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
4443 Tor to fail to start if you had it configured to use a bridge
4444 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
4445 - When extending a circuit to a hidden service directory to upload a
4446 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
4447 requests failed, because the router descriptor had not been
4448 downloaded yet. In these cases, we now wait until the router
4449 descriptor is downloaded, and then retry. Likewise, clients
4450 now skip over a hidden service directory if they don't yet have
4451 its router descriptor, rather than futilely requesting it and
4452 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
4454 - When fetching v0 and v2 rendezvous service descriptors in parallel,
4455 we were failing the whole hidden service request when the v0
4456 descriptor fetch fails, even if the v2 fetch is still pending and
4457 might succeed. Similarly, if the last v2 fetch fails, we were
4458 failing the whole hidden service request even if a v0 fetch is
4459 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
4460 - DNS replies need to have names matching their requests, but
4461 these names should be in the questions section, not necessarily
4462 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
4465 - Update to the "September 1 2008" ip-to-country file.
4466 - Allow ports 465 and 587 in the default exit policy again. We had
4467 rejected them in 0.1.0.15, because back in 2005 they were commonly
4468 misconfigured and ended up as spam targets. We hear they are better
4469 locked down these days.
4470 - Use a lockfile to make sure that two Tor processes are not
4471 simultaneously running with the same datadir.
4472 - Serve the latest v3 networkstatus consensus via the control
4473 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
4474 - Better logging about stability/reliability calculations on directory
4476 - Drop the requirement to have an open dir port for storing and
4477 serving v2 hidden service descriptors.
4478 - Directory authorities now serve a /tor/dbg-stability.txt URL to
4479 help debug WFU and MTBF calculations.
4480 - Implement most of Proposal 152: allow specialized servers to permit
4481 single-hop circuits, and clients to use those servers to build
4482 single-hop circuits when using a specialized controller. Patch
4483 from Josh Albrecht. Resolves feature request 768.
4484 - Add a -p option to tor-resolve for specifying the SOCKS port: some
4485 people find host:port too confusing.
4486 - Make TrackHostExit mappings expire a while after their last use, not
4487 after their creation. Patch from Robert Hogan.
4488 - Provide circuit purposes along with circuit events to the controller.
4491 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
4493 - Fixed some memory leaks -- some quite frequent, some almost
4494 impossible to trigger -- based on results from Coverity.
4495 - When testing for libevent functions, set the LDFLAGS variable
4496 correctly. Found by Riastradh.
4497 - Fix an assertion bug in parsing policy-related options; possible fix
4499 - Catch and report a few more bootstrapping failure cases when Tor
4500 fails to establish a TCP connection. Cleanup on 0.2.1.x.
4501 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
4502 bootstrapping with tunneled directory connections. Bugfix on
4503 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
4504 - When asked to connect to A.B.exit:80, if we don't know the IP for A
4505 and we know that server B rejects most-but-not all connections to
4506 port 80, we would previously reject the connection. Now, we assume
4507 the user knows what they were asking for. Fixes bug 752. Bugfix
4508 on 0.0.9rc5. Diagnosed by BarkerJr.
4509 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
4510 service directories if they have no advertised dir port. Bugfix
4512 - If we overrun our per-second write limits a little, count this as
4513 having used up our write allocation for the second, and choke
4514 outgoing directory writes. Previously, we had only counted this when
4515 we had met our limits precisely. Fixes bug 824. Patch by rovv.
4516 Bugfix on 0.2.0.x (??).
4517 - Avoid a "0 divided by 0" calculation when calculating router uptime
4518 at directory authorities. Bugfix on 0.2.0.8-alpha.
4519 - Make DNS resolved controller events into "CLOSED", not
4520 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
4522 - Fix a bug where an unreachable relay would establish enough
4523 reachability testing circuits to do a bandwidth test -- if
4524 we already have a connection to the middle hop of the testing
4525 circuit, then it could establish the last hop by using the existing
4526 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
4527 circuits no longer use entry guards in 0.2.1.3-alpha.
4528 - If we have correct permissions on $datadir, we complain to stdout
4529 and fail to start. But dangerous permissions on
4530 $datadir/cached-status/ would cause us to open a log and complain
4531 there. Now complain to stdout and fail to start in both cases. Fixes
4532 bug 820, reported by seeess.
4533 - Remove the old v2 directory authority 'lefkada' from the default
4534 list. It has been gone for many months.
4536 o Code simplifications and refactoring:
4537 - Revise the connection_new functions so that a more typesafe variant
4538 exists. This will work better with Coverity, and let us find any
4539 actual mistakes we're making here.
4540 - Refactor unit testing logic so that dmalloc can be used sensibly
4541 with unit tests to check for memory leaks.
4542 - Move all hidden-service related fields from connection and circuit
4543 structure to substructures: this way they won't eat so much memory.
4546 Changes in version 0.2.0.31 - 2008-09-03
4547 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
4548 a big bug we're seeing where in rare cases traffic from one Tor stream
4549 gets mixed into another stream, and fixes a variety of smaller issues.
4552 - Make sure that two circuits can never exist on the same connection
4553 with the same circuit ID, even if one is marked for close. This
4554 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
4555 - Relays now reject risky extend cells: if the extend cell includes
4556 a digest of all zeroes, or asks to extend back to the relay that
4557 sent the extend cell, tear down the circuit. Ideas suggested
4559 - If not enough of our entry guards are available so we add a new
4560 one, we might use the new one even if it overlapped with the
4561 current circuit's exit relay (or its family). Anonymity bugfix
4562 pointed out by rovv.
4565 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
4566 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
4567 - Correctly detect the presence of the linux/netfilter_ipv4.h header
4568 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
4569 - Pick size of default geoip filename string correctly on windows.
4570 Fixes bug 806. Bugfix on 0.2.0.30.
4571 - Make the autoconf script accept the obsolete --with-ssl-dir
4572 option as an alias for the actually-working --with-openssl-dir
4573 option. Fix the help documentation to recommend --with-openssl-dir.
4574 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
4575 - When using the TransPort option on OpenBSD, and using the User
4576 option to change UID and drop privileges, make sure to open
4577 /dev/pf before dropping privileges. Fixes bug 782. Patch from
4578 Christopher Davis. Bugfix on 0.1.2.1-alpha.
4579 - Try to attach connections immediately upon receiving a RENDEZVOUS2
4580 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
4581 on the client side when connecting to a hidden service. Bugfix
4582 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
4583 - When closing an application-side connection because its circuit is
4584 getting torn down, generate the stream event correctly. Bugfix on
4585 0.1.2.x. Anonymous patch.
4588 Changes in version 0.2.1.5-alpha - 2008-08-31
4589 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
4590 in a lot of the infrastructure for adding authorization to hidden
4591 services, lays the groundwork for having clients read their load
4592 balancing information out of the networkstatus consensus rather than
4593 the individual router descriptors, addresses two potential anonymity
4594 issues, and fixes a variety of smaller issues.
4597 - Convert many internal address representations to optionally hold
4599 - Generate and accept IPv6 addresses in many protocol elements.
4600 - Make resolver code handle nameservers located at ipv6 addresses.
4601 - Begin implementation of proposal 121 ("Client authorization for
4602 hidden services"): configure hidden services with client
4603 authorization, publish descriptors for them, and configure
4604 authorization data for hidden services at clients. The next
4605 step is to actually access hidden services that perform client
4607 - More progress toward proposal 141: Network status consensus
4608 documents and votes now contain bandwidth information for each
4609 router and a summary of that router's exit policy. Eventually this
4610 will be used by clients so that they do not have to download every
4611 known descriptor before building circuits.
4613 o Major bugfixes (on 0.2.0.x and before):
4614 - When sending CREATED cells back for a given circuit, use a 64-bit
4615 connection ID to find the right connection, rather than an addr:port
4616 combination. Now that we can have multiple OR connections between
4617 the same ORs, it is no longer possible to use addr:port to uniquely
4618 identify a connection.
4619 - Relays now reject risky extend cells: if the extend cell includes
4620 a digest of all zeroes, or asks to extend back to the relay that
4621 sent the extend cell, tear down the circuit. Ideas suggested
4623 - If not enough of our entry guards are available so we add a new
4624 one, we might use the new one even if it overlapped with the
4625 current circuit's exit relay (or its family). Anonymity bugfix
4626 pointed out by rovv.
4629 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
4630 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
4631 - When using the TransPort option on OpenBSD, and using the User
4632 option to change UID and drop privileges, make sure to open /dev/pf
4633 before dropping privileges. Fixes bug 782. Patch from Christopher
4634 Davis. Bugfix on 0.1.2.1-alpha.
4635 - Correctly detect the presence of the linux/netfilter_ipv4.h header
4636 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
4637 - Add a missing safe_str() call for a debug log message.
4638 - Use 64 bits instead of 32 bits for connection identifiers used with
4639 the controller protocol, to greatly reduce risk of identifier reuse.
4640 - Make the autoconf script accept the obsolete --with-ssl-dir
4641 option as an alias for the actually-working --with-openssl-dir
4642 option. Fix the help documentation to recommend --with-openssl-dir.
4643 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
4646 - Rate-limit too-many-sockets messages: when they happen, they happen
4647 a lot. Resolves bug 748.
4648 - Resist DNS poisoning a little better by making sure that names in
4649 answer sections match.
4650 - Print the SOCKS5 error message string as well as the error code
4651 when a tor-resolve request fails. Patch from Jacob.
4654 Changes in version 0.2.1.4-alpha - 2008-08-04
4655 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
4658 - The address part of exit policies was not correctly written
4659 to router descriptors. This generated router descriptors that failed
4660 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
4662 - Tor triggered a false assert when extending a circuit to a relay
4663 but we already have a connection open to that relay. Noticed by
4664 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
4667 - Fix a hidden service logging bug: in some edge cases, the router
4668 descriptor of a previously picked introduction point becomes
4669 obsolete and we need to give up on it rather than continually
4670 complaining that it has become obsolete. Observed by xiando. Bugfix
4674 - Take out the TestVia config option, since it was a workaround for
4675 a bug that was fixed in Tor 0.1.1.21.
4678 Changes in version 0.2.1.3-alpha - 2008-08-03
4679 Tor 0.2.1.3-alpha implements most of the pieces to prevent
4680 infinite-length circuit attacks (see proposal 110); fixes a bug that
4681 might cause exit relays to corrupt streams they send back; allows
4682 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
4683 ExcludeExitNodes config options; and fixes a big pile of bugs.
4685 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
4686 - Send a bootstrap problem "warn" event on the first problem if the
4687 reason is NO_ROUTE (that is, our network is down).
4690 - Implement most of proposal 110: The first K cells to be sent
4691 along a circuit are marked as special "early" cells; only K "early"
4692 cells will be allowed. Once this code is universal, we can block
4693 certain kinds of DOS attack by requiring that EXTEND commands must
4694 be sent using an "early" cell.
4697 - Try to attach connections immediately upon receiving a RENDEZVOUS2
4698 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
4699 on the client side when connecting to a hidden service. Bugfix
4700 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
4701 - Ensure that two circuits can never exist on the same connection
4702 with the same circuit ID, even if one is marked for close. This
4703 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
4706 - When relays do their initial bandwidth measurement, don't limit
4707 to just our entry guards for the test circuits. Otherwise we tend
4708 to have multiple test circuits going through a single entry guard,
4709 which makes our bandwidth test less accurate. Fixes part of bug 654;
4710 patch contributed by Josh Albrecht.
4711 - Add an ExcludeExitNodes option so users can list a set of nodes
4712 that should be be excluded from the exit node position, but
4713 allowed elsewhere. Implements proposal 151.
4714 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
4715 ExcludeNodes and ExcludeExitNodes lists.
4716 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
4717 be more efficient. Formerly it was quadratic in the number of
4718 servers; now it should be linear. Fixes bug 509.
4719 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
4720 and n_conn_id_digest fields into a separate structure that's
4721 only needed when the circuit has not yet attached to an n_conn.
4724 - Change the contrib/tor.logrotate script so it makes the new
4725 logs as "_tor:_tor" rather than the default, which is generally
4726 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
4727 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
4728 warnings (occasionally), but it can also cause the compiler to
4729 eliminate error-checking code. Suggested by Peter Gutmann.
4730 - When a hidden service is giving up on an introduction point candidate
4731 that was not included in the last published rendezvous descriptor,
4732 don't reschedule publication of the next descriptor. Fixes bug 763.
4734 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
4735 HiddenServiceExcludeNodes as obsolete: they never worked properly,
4736 and nobody claims to be using them. Fixes bug 754. Bugfix on
4737 0.1.0.1-rc. Patch from Christian Wilms.
4738 - Fix a small alignment and memory-wasting bug on buffer chunks.
4741 o Minor bugfixes (controller):
4742 - When closing an application-side connection because its circuit
4743 is getting torn down, generate the stream event correctly.
4744 Bugfix on 0.1.2.x. Anonymous patch.
4747 - Remove all backward-compatibility code to support relays running
4748 versions of Tor so old that they no longer work at all on the
4752 Changes in version 0.2.0.30 - 2008-07-15
4754 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
4755 warnings (occasionally), but it can also cause the compiler to
4756 eliminate error-checking code. Suggested by Peter Gutmann.
4759 Changes in version 0.2.0.29-rc - 2008-07-08
4760 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
4761 hidden-service performance bugs, and fixes a bunch of smaller bugs.
4764 - If you have more than one bridge but don't know their keys,
4765 you would only launch a request for the descriptor of the first one
4766 on your list. (Tor considered launching requests for the others, but
4767 found that it already had a connection on the way for $0000...0000
4768 so it didn't open another.) Bugfix on 0.2.0.x.
4769 - If you have more than one bridge but don't know their keys, and the
4770 connection to one of the bridges failed, you would cancel all
4771 pending bridge connections. (After all, they all have the same
4772 digest.) Bugfix on 0.2.0.x.
4773 - When a hidden service was trying to establish an introduction point,
4774 and Tor had built circuits preemptively for such purposes, we
4775 were ignoring all the preemptive circuits and launching a new one
4776 instead. Bugfix on 0.2.0.14-alpha.
4777 - When a hidden service was trying to establish an introduction point,
4778 and Tor *did* manage to reuse one of the preemptively built
4779 circuits, it didn't correctly remember which one it used,
4780 so it asked for another one soon after, until there were no
4781 more preemptive circuits, at which point it launched one from
4782 scratch. Bugfix on 0.0.9.x.
4783 - Make directory servers include the X-Your-Address-Is: http header in
4784 their responses even for begin_dir conns. Now clients who only
4785 ever use begin_dir connections still have a way to learn their IP
4786 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
4789 - Fix a macro/CPP interaction that was confusing some compilers:
4790 some GCCs don't like #if/#endif pairs inside macro arguments.
4792 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
4793 Fixes bug 704; fix from Steven Murdoch.
4794 - When opening /dev/null in finish_daemonize(), do not pass the
4795 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
4796 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
4797 - Correctly detect transparent proxy support on Linux hosts that
4798 require in.h to be included before netfilter_ipv4.h. Patch
4800 - Disallow session resumption attempts during the renegotiation
4801 stage of the v2 handshake protocol. Clients should never be trying
4802 session resumption at this point, but apparently some did, in
4803 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
4804 found by Geoff Goodell.
4807 Changes in version 0.2.1.2-alpha - 2008-06-20
4808 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
4809 make it easier to set up your own private Tor network; fixes several
4810 big bugs with using more than one bridge relay; fixes a big bug with
4811 offering hidden services quickly after Tor starts; and uses a better
4812 API for reporting potential bootstrapping problems to the controller.
4815 - New TestingTorNetwork config option to allow adjustment of
4816 previously constant values that, while reasonable, could slow
4817 bootstrapping. Implements proposal 135. Patch from Karsten.
4820 - If you have more than one bridge but don't know their digests,
4821 you would only learn a request for the descriptor of the first one
4822 on your list. (Tor considered launching requests for the others, but
4823 found that it already had a connection on the way for $0000...0000
4824 so it didn't open another.) Bugfix on 0.2.0.x.
4825 - If you have more than one bridge but don't know their digests,
4826 and the connection to one of the bridges failed, you would cancel
4827 all pending bridge connections. (After all, they all have the
4828 same digest.) Bugfix on 0.2.0.x.
4829 - When establishing a hidden service, introduction points that
4830 originate from cannibalized circuits are completely ignored and not
4831 included in rendezvous service descriptors. This might be another
4832 reason for delay in making a hidden service available. Bugfix
4833 from long ago (0.0.9.x?)
4836 - Allow OpenSSL to use dynamic locks if it wants.
4837 - When building a consensus, do not include routers that are down.
4838 This will cut down 30% to 40% on consensus size. Implements
4840 - In directory authorities' approved-routers files, allow
4841 fingerprints with or without space.
4842 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
4843 controller can query our current bootstrap state in case it attaches
4844 partway through and wants to catch up.
4845 - Send an initial "Starting" bootstrap status event, so we have a
4846 state to start out in.
4849 - Asking for a conditional consensus at .../consensus/<fingerprints>
4850 would crash a dirserver if it did not already have a
4851 consensus. Bugfix on 0.2.1.1-alpha.
4852 - Clean up some macro/CPP interactions: some GCC versions don't like
4853 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
4856 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
4857 - Directory authorities shouldn't complain about bootstrapping
4858 problems just because they do a lot of reachability testing and
4859 some of the connection attempts fail.
4860 - Start sending "count" and "recommendation" key/value pairs in
4861 bootstrap problem status events, so the controller can hear about
4862 problems even before Tor decides they're worth reporting for sure.
4863 - If you're using bridges, generate "bootstrap problem" warnings
4864 as soon as you run out of working bridges, rather than waiting
4865 for ten failures -- which will never happen if you have less than
4867 - If we close our OR connection because there's been a circuit
4868 pending on it for too long, we were telling our bootstrap status
4869 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
4872 Changes in version 0.2.1.1-alpha - 2008-06-13
4873 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
4874 were making the Tor process bloat especially on Linux; makes our TLS
4875 handshake blend in better; sends "bootstrap phase" status events to
4876 the controller, so it can keep the user informed of progress (and
4877 problems) fetching directory information and establishing circuits;
4878 and adds a variety of smaller features.
4881 - More work on making our TLS handshake blend in: modify the list
4882 of ciphers advertised by OpenSSL in client mode to even more
4883 closely resemble a common web browser. We cheat a little so that
4884 we can advertise ciphers that the locally installed OpenSSL doesn't
4886 - Start sending "bootstrap phase" status events to the controller,
4887 so it can keep the user informed of progress fetching directory
4888 information and establishing circuits. Also inform the controller
4889 if we think we're stuck at a particular bootstrap phase. Implements
4891 - Resume using OpenSSL's RAND_poll() for better (and more portable)
4892 cross-platform entropy collection again. We used to use it, then
4893 stopped using it because of a bug that could crash systems that
4894 called RAND_poll when they had a lot of fds open. It looks like the
4895 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
4896 at startup, and to call RAND_poll() when we reseed later only if
4897 we have a non-buggy OpenSSL version.
4900 - When we choose to abandon a new entry guard because we think our
4901 older ones might be better, close any circuits pending on that
4902 new entry guard connection. This fix should make us recover much
4903 faster when our network is down and then comes back. Bugfix on
4904 0.1.2.8-beta; found by lodger.
4906 o Memory fixes and improvements:
4907 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
4908 to avoid unused RAM in buffer chunks and memory pools.
4909 - Speed up parsing and cut down on memory fragmentation by using
4910 stack-style allocations for parsing directory objects. Previously,
4911 this accounted for over 40% of allocations from within Tor's code
4912 on a typical directory cache.
4913 - Use a Bloom filter rather than a digest-based set to track which
4914 descriptors we need to keep around when we're cleaning out old
4915 router descriptors. This speeds up the computation significantly,
4916 and may reduce fragmentation.
4917 - Reduce the default smartlist size from 32 to 16; it turns out that
4918 most smartlists hold around 8-12 elements tops.
4919 - Make dumpstats() log the fullness and size of openssl-internal
4921 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
4922 patch to their OpenSSL, turn it on to save memory on servers. This
4923 patch will (with any luck) get included in a mainline distribution
4925 - Never use OpenSSL compression: it wastes RAM and CPU trying to
4926 compress cells, which are basically all encrypted, compressed,
4930 - Stop reloading the router list from disk for no reason when we
4931 run out of reachable directory mirrors. Once upon a time reloading
4932 it would set the 'is_running' flag back to 1 for them. It hasn't
4933 done that for a long time.
4934 - In very rare situations new hidden service descriptors were
4935 published earlier than 30 seconds after the last change to the
4936 service. (We currently think that a hidden service descriptor
4937 that's been stable for 30 seconds is worth publishing.)
4940 - Allow separate log levels to be configured for different logging
4941 domains. For example, this allows one to log all notices, warnings,
4942 or errors, plus all memory management messages of level debug or
4943 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
4944 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
4945 and stop using a warning that had become unfixably verbose under
4947 - New --hush command-line option similar to --quiet. While --quiet
4948 disables all logging to the console on startup, --hush limits the
4949 output to messages of warning and error severity.
4950 - Servers support a new URL scheme for consensus downloads that
4951 allows the client to specify which authorities are trusted.
4952 The server then only sends the consensus if the client will trust
4953 it. Otherwise a 404 error is sent back. Clients use this
4954 new scheme when the server supports it (meaning it's running
4955 0.2.1.1-alpha or later). Implements proposal 134.
4956 - New configure/torrc options (--enable-geoip-stats,
4957 DirRecordUsageByCountry) to record how many IPs we've served
4958 directory info to in each country code, how many status documents
4959 total we've sent to each country code, and what share of the total
4960 directory requests we should expect to see.
4961 - Use the TLS1 hostname extension to more closely resemble browser
4963 - Lots of new unit tests.
4964 - Add a macro to implement the common pattern of iterating through
4965 two parallel lists in lockstep.
4968 Changes in version 0.2.0.28-rc - 2008-06-13
4969 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
4970 performance bug, and fixes a bunch of smaller bugs.
4973 - Fix a bug where, when we were choosing the 'end stream reason' to
4974 put in our relay end cell that we send to the exit relay, Tor
4975 clients on Windows were sometimes sending the wrong 'reason'. The
4976 anonymity problem is that exit relays may be able to guess whether
4977 the client is running Windows, thus helping partition the anonymity
4978 set. Down the road we should stop sending reasons to exit relays,
4979 or otherwise prevent future versions of this bug.
4982 - While setting up a hidden service, some valid introduction circuits
4983 were overlooked and abandoned. This might be the reason for
4984 the long delay in making a hidden service available. Bugfix on
4988 - Update to the "June 9 2008" ip-to-country file.
4989 - Run 'make test' as part of 'make dist', so we stop releasing so
4990 many development snapshots that fail their unit tests.
4993 - When we're checking if we have enough dir info for each relay
4994 to begin establishing circuits, make sure that we actually have
4995 the descriptor listed in the consensus, not just any descriptor.
4997 - Bridge relays no longer print "xx=0" in their extrainfo document
4998 for every single country code in the geoip db. Bugfix on
5000 - Only warn when we fail to load the geoip file if we were planning to
5001 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
5002 - If we change our MaxAdvertisedBandwidth and then reload torrc,
5003 Tor won't realize it should publish a new relay descriptor. Fixes
5004 bug 688, reported by mfr. Bugfix on 0.1.2.x.
5005 - When we haven't had any application requests lately, don't bother
5006 logging that we have expired a bunch of descriptors. Bugfix
5008 - Make relay cells written on a connection count as non-padding when
5009 tracking how long a connection has been in use. Bugfix on
5010 0.2.0.1-alpha. Spotted by lodger.
5011 - Fix unit tests in 0.2.0.27-rc.
5012 - Fix compile on Windows.
5015 Changes in version 0.2.0.27-rc - 2008-06-03
5016 Tor 0.2.0.27-rc adds a few features we left out of the earlier
5017 release candidates. In particular, we now include an IP-to-country
5018 GeoIP database, so controllers can easily look up what country a
5019 given relay is in, and so bridge relays can give us some sanitized
5020 summaries about which countries are making use of bridges. (See proposal
5021 126-geoip-fetching.txt for details.)
5024 - Include an IP-to-country GeoIP file in the tarball, so bridge
5025 relays can report sanitized summaries of the usage they're seeing.
5028 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
5029 Robert Hogan. Fixes the first part of bug 681.
5030 - Make bridge authorities never serve extrainfo docs.
5031 - Add support to detect Libevent versions in the 1.4.x series
5033 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
5034 - Include a new contrib/tor-exit-notice.html file that exit relay
5035 operators can put on their website to help reduce abuse queries.
5038 - When tunneling an encrypted directory connection, and its first
5039 circuit fails, do not leave it unattached and ask the controller
5040 to deal. Fixes the second part of bug 681.
5041 - Make bridge authorities correctly expire old extrainfo documents
5045 Changes in version 0.2.0.26-rc - 2008-05-13
5046 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
5047 in Debian's OpenSSL packages. All users running any 0.2.0.x version
5048 should upgrade, whether they're running Debian or not.
5050 o Major security fixes:
5051 - Use new V3 directory authority keys on the tor26, gabelmoo, and
5052 moria1 V3 directory authorities. The old keys were generated with
5053 a vulnerable version of Debian's OpenSSL package, and must be
5054 considered compromised. Other authorities' keys were not generated
5055 with an affected version of OpenSSL.
5058 - List authority signatures as "unrecognized" based on DirServer
5059 lines, not on cert cache. Bugfix on 0.2.0.x.
5062 - Add a new V3AuthUseLegacyKey option to make it easier for
5063 authorities to change their identity keys if they have to.
5066 Changes in version 0.2.0.25-rc - 2008-04-23
5067 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
5070 - Remember to initialize threading before initializing logging.
5071 Otherwise, many BSD-family implementations will crash hard on
5072 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
5075 - Authorities correctly free policies on bad servers on
5076 exit. Fixes bug 672. Bugfix on 0.2.0.x.
5079 Changes in version 0.2.0.24-rc - 2008-04-22
5080 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
5081 v3 directory authority, makes relays with dynamic IP addresses and no
5082 DirPort notice more quickly when their IP address changes, fixes a few
5083 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
5085 o New directory authorities:
5086 - Take lefkada out of the list of v3 directory authorities, since
5087 it has been down for months.
5088 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
5092 - Detect address changes more quickly on non-directory mirror
5093 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
5095 o Minor features (security):
5096 - Reject requests for reverse-dns lookup of names that are in
5097 a private address space. Patch from lodger.
5098 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
5101 o Minor bugfixes (crashes):
5102 - Avoid a rare assert that can trigger when Tor doesn't have much
5103 directory information yet and it tries to fetch a v2 hidden
5104 service descriptor. Fixes bug 651, reported by nwf.
5105 - Initialize log mutex before initializing dmalloc. Otherwise,
5106 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
5107 - Use recursive pthread mutexes in order to avoid deadlock when
5108 logging debug-level messages to a controller. Bug spotted by nwf,
5109 bugfix on 0.2.0.16-alpha.
5111 o Minor bugfixes (resource management):
5112 - Keep address policies from leaking memory: start their refcount
5113 at 1, not 2. Bugfix on 0.2.0.16-alpha.
5114 - Free authority certificates on exit, so they don't look like memory
5115 leaks. Bugfix on 0.2.0.19-alpha.
5116 - Free static hashtables for policy maps and for TLS connections on
5117 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
5118 - Avoid allocating extra space when computing consensuses on 64-bit
5119 platforms. Bug spotted by aakova.
5121 o Minor bugfixes (misc):
5122 - Do not read the configuration file when we've only been told to
5123 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
5124 based on patch from Sebastian Hahn.
5125 - Exit relays that are used as a client can now reach themselves
5126 using the .exit notation, rather than just launching an infinite
5127 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
5128 - When attempting to open a logfile fails, tell us why.
5129 - Fix a dumb bug that was preventing us from knowing that we should
5130 preemptively build circuits to handle expected directory requests.
5131 Fixes bug 660. Bugfix on 0.1.2.x.
5132 - Warn less verbosely about clock skew from netinfo cells from
5133 untrusted sources. Fixes bug 663.
5134 - Make controller stream events for DNS requests more consistent,
5135 by adding "new stream" events for DNS requests, and removing
5136 spurious "stream closed" events" for cached reverse resolves.
5137 Patch from mwenge. Fixes bug 646.
5138 - Correctly notify one-hop connections when a circuit build has
5139 failed. Possible fix for bug 669. Found by lodger.
5142 Changes in version 0.2.0.23-rc - 2008-03-24
5143 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
5144 makes bootstrapping faster if the first directory mirror you contact
5145 is down. The bundles also include the new Vidalia 0.1.2 release.
5148 - When a tunneled directory request is made to a directory server
5149 that's down, notice after 30 seconds rather than 120 seconds. Also,
5150 fail any begindir streams that are pending on it, so they can
5151 retry elsewhere. This was causing multi-minute delays on bootstrap.
5154 Changes in version 0.2.0.22-rc - 2008-03-18
5155 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
5156 enables encrypted directory connections by default for non-relays, fixes
5157 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
5158 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
5161 - Enable encrypted directory connections by default for non-relays,
5162 so censor tools that block Tor directory connections based on their
5163 plaintext patterns will no longer work. This means Tor works in
5164 certain censored countries by default again.
5167 - Make sure servers always request certificates from clients during
5168 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
5169 - Do not enter a CPU-eating loop when a connection is closed in
5170 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
5171 diagnosed by lodger; bugfix on 0.2.0.20-rc.
5172 - Fix assertion failure that could occur when a blocked circuit
5173 became unblocked, and it had pending client DNS requests. Bugfix
5174 on 0.2.0.1-alpha. Fixes bug 632.
5176 o Minor bugfixes (on 0.1.2.x):
5177 - Generate "STATUS_SERVER" events rather than misspelled
5178 "STATUS_SEVER" events. Caught by mwenge.
5179 - When counting the number of bytes written on a TLS connection,
5180 look at the BIO actually used for writing to the network, not
5181 at the BIO used (sometimes) to buffer data for the network.
5182 Looking at different BIOs could result in write counts on the
5183 order of ULONG_MAX. Fixes bug 614.
5184 - On Windows, correctly detect errors when listing the contents of
5185 a directory. Fix from lodger.
5187 o Minor bugfixes (on 0.2.0.x):
5188 - Downgrade "sslv3 alert handshake failure" message to INFO.
5189 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
5190 left BandwidthRate and BandwidthBurst at the default, we would be
5191 silently limited by those defaults. Now raise them to match the
5192 RelayBandwidth* values.
5193 - Fix the SVK version detection logic to work correctly on a branch.
5194 - Make --enable-openbsd-malloc work correctly on Linux with alpha
5195 CPUs. Fixes bug 625.
5196 - Logging functions now check that the passed severity is sane.
5197 - Use proper log levels in the testsuite call of
5198 get_interface_address6().
5199 - When using a nonstandard malloc, do not use the platform values for
5200 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
5201 - Make the openbsd malloc code use 8k pages on alpha CPUs and
5203 - Detect mismatched page sizes when using --enable-openbsd-malloc.
5204 - Avoid double-marked-for-close warning when certain kinds of invalid
5205 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
5206 for bug 617. Bugfix on 0.2.0.1-alpha.
5207 - Make sure that the "NULL-means-reject *:*" convention is followed by
5208 all the policy manipulation functions, avoiding some possible crash
5209 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
5210 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
5211 actually works, and doesn't warn about every single reverse lookup.
5212 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
5215 - Only log guard node status when guard node status has changed.
5216 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
5217 make "INFO" 75% less verbose.
5220 Changes in version 0.2.0.21-rc - 2008-03-02
5221 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
5222 makes Tor work well with Vidalia again, fixes a rare assert bug,
5223 and fixes a pair of more minor bugs. The bundles also include Vidalia
5224 0.1.0 and Torbutton 1.1.16.
5227 - The control port should declare that it requires password auth
5228 when HashedControlSessionPassword is set too. Patch from Matt Edman;
5229 bugfix on 0.2.0.20-rc. Fixes bug 615.
5230 - Downgrade assert in connection_buckets_decrement() to a log message.
5231 This may help us solve bug 614, and in any case will make its
5232 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
5233 - We were sometimes miscounting the number of bytes read from the
5234 network, causing our rate limiting to not be followed exactly.
5235 Bugfix on 0.2.0.16-alpha. Reported by lodger.
5238 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
5239 OpenSSL versions should have been working fine. Diagnosis and patch
5240 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
5241 Bugfix on 0.2.0.20-rc.
5244 Changes in version 0.2.0.20-rc - 2008-02-24
5245 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
5246 makes more progress towards normalizing Tor's TLS handshake, makes
5247 hidden services work better again, helps relays bootstrap if they don't
5248 know their IP address, adds optional support for linking in openbsd's
5249 allocator or tcmalloc, allows really fast relays to scale past 15000
5250 sockets, and fixes a bunch of minor bugs reported by Veracode.
5253 - Enable the revised TLS handshake based on the one designed by
5254 Steven Murdoch in proposal 124, as revised in proposal 130. It
5255 includes version negotiation for OR connections as described in
5256 proposal 105. The new handshake is meant to be harder for censors
5257 to fingerprint, and it adds the ability to detect certain kinds of
5258 man-in-the-middle traffic analysis attacks. The version negotiation
5259 feature will allow us to improve Tor's link protocol more safely
5261 - Choose which bridge to use proportional to its advertised bandwidth,
5262 rather than uniformly at random. This should speed up Tor for
5263 bridge users. Also do this for people who set StrictEntryNodes.
5264 - When a TrackHostExits-chosen exit fails too many times in a row,
5265 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
5268 - Resolved problems with (re-)fetching hidden service descriptors.
5269 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
5271 - If we only ever used Tor for hidden service lookups or posts, we
5272 would stop building circuits and start refusing connections after
5273 24 hours, since we falsely believed that Tor was dormant. Reported
5274 by nwf; bugfix on 0.1.2.x.
5275 - Servers that don't know their own IP address should go to the
5276 authorities for their first directory fetch, even if their DirPort
5277 is off or if they don't know they're reachable yet. This will help
5278 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
5279 - When counting the number of open sockets, count not only the number
5280 of sockets we have received from the socket() call, but also
5281 the number we've gotten from accept() and socketpair(). This bug
5282 made us fail to count all sockets that we were using for incoming
5283 connections. Bugfix on 0.2.0.x.
5284 - Fix code used to find strings within buffers, when those strings
5285 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
5286 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
5287 - Add a new __HashedControlSessionPassword option for controllers
5288 to use for one-off session password hashes that shouldn't get
5289 saved to disk by SAVECONF --- Vidalia users were accumulating a
5290 pile of HashedControlPassword lines in their torrc files, one for
5291 each time they had restarted Tor and then clicked Save. Make Tor
5292 automatically convert "HashedControlPassword" to this new option but
5293 only when it's given on the command line. Partial fix for bug 586.
5295 o Minor features (performance):
5296 - Tune parameters for cell pool allocation to minimize amount of
5298 - Add OpenBSD malloc code from phk as an optional malloc
5299 replacement on Linux: some glibc libraries do very poorly
5300 with Tor's memory allocation patterns. Pass
5301 --enable-openbsd-malloc to get the replacement malloc code.
5302 - Add a --with-tcmalloc option to the configure script to link
5303 against tcmalloc (if present). Does not yet search for
5304 non-system include paths.
5305 - Stop imposing an arbitrary maximum on the number of file descriptors
5306 used for busy servers. Bug reported by Olaf Selke; patch from
5309 o Minor features (other):
5310 - When SafeLogging is disabled, log addresses along with all TLS
5312 - When building with --enable-gcc-warnings, check for whether Apple's
5313 warning "-Wshorten-64-to-32" is available.
5314 - Add a --passphrase-fd argument to the tor-gencert command for
5317 o Minor bugfixes (memory leaks and code problems):
5318 - We were leaking a file descriptor if Tor started with a zero-length
5319 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
5320 - Detect size overflow in zlib code. Reported by Justin Ferguson and
5322 - We were comparing the raw BridgePassword entry with a base64'ed
5323 version of it, when handling a "/tor/networkstatus-bridges"
5324 directory request. Now compare correctly. Noticed by Veracode.
5325 - Recover from bad tracked-since value in MTBF-history file.
5327 - Alter the code that tries to recover from unhandled write
5328 errors, to not try to flush onto a socket that's given us
5329 unhandled errors. Bugfix on 0.1.2.x.
5330 - Make Unix controlsockets work correctly on OpenBSD. Patch from
5331 tup. Bugfix on 0.2.0.3-alpha.
5333 o Minor bugfixes (other):
5334 - If we have an extra-info document for our server, always make
5335 it available on the control port, even if we haven't gotten
5336 a copy of it from an authority yet. Patch from mwenge.
5337 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
5338 - Directory mirrors no longer include a guess at the client's IP
5339 address if the connection appears to be coming from the same /24
5340 network; it was producing too many wrong guesses.
5341 - Make the new hidden service code respect the SafeLogging setting.
5342 Bugfix on 0.2.0.x. Patch from Karsten.
5343 - When starting as an authority, do not overwrite all certificates
5344 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
5345 - If we're trying to flush the last bytes on a connection (for
5346 example, when answering a directory request), reset the
5347 time-to-give-up timeout every time we manage to write something
5348 on the socket. Bugfix on 0.1.2.x.
5349 - Change the behavior of "getinfo status/good-server-descriptor"
5350 so it doesn't return failure when any authority disappears.
5351 - Even though the man page said that "TrackHostExits ." should
5352 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
5353 - Report TLS "zero return" case as a "clean close" and "IO error"
5354 as a "close". Stop calling closes "unexpected closes": existing
5355 Tors don't use SSL_close(), so having a connection close without
5356 the TLS shutdown handshake is hardly unexpected.
5357 - Send NAMESERVER_STATUS messages for a single failed nameserver
5360 o Code simplifications and refactoring:
5361 - Remove the tor_strpartition function: its logic was confused,
5362 and it was only used for one thing that could be implemented far
5366 Changes in version 0.2.0.19-alpha - 2008-02-09
5367 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
5368 handshake, makes path selection for relays more secure and IP address
5369 guessing more robust, and generally fixes a lot of bugs in preparation
5370 for calling the 0.2.0 branch stable.
5373 - Do not include recognizeable strings in the commonname part of
5374 Tor's x509 certificates.
5377 - If we're a relay, avoid picking ourselves as an introduction point,
5378 a rendezvous point, or as the final hop for internal circuits. Bug
5379 reported by taranis and lodger. Bugfix on 0.1.2.x.
5380 - Patch from "Andrew S. Lists" to catch when we contact a directory
5381 mirror at IP address X and he says we look like we're coming from
5382 IP address X. Bugfix on 0.1.2.x.
5384 o Minor features (security):
5385 - Be more paranoid about overwriting sensitive memory on free(),
5386 as a defensive programming tactic to ensure forward secrecy.
5388 o Minor features (directory authority):
5389 - Actually validate the options passed to AuthDirReject,
5390 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
5391 - Reject router descriptors with out-of-range bandwidthcapacity or
5392 bandwidthburst values.
5394 o Minor features (controller):
5395 - Reject controller commands over 1MB in length. This keeps rogue
5396 processes from running us out of memory.
5398 o Minor features (misc):
5399 - Give more descriptive well-formedness errors for out-of-range
5400 hidden service descriptor/protocol versions.
5401 - Make memory debugging information describe more about history
5402 of cell allocation, so we can help reduce our memory use.
5404 o Deprecated features (controller):
5405 - The status/version/num-versioning and status/version/num-concurring
5406 GETINFO options are no longer useful in the v3 directory protocol:
5407 treat them as deprecated, and warn when they're used.
5410 - When our consensus networkstatus has been expired for a while, stop
5411 being willing to build circuits using it. Fixes bug 401. Bugfix
5413 - Directory caches now fetch certificates from all authorities
5414 listed in a networkstatus consensus, even when they do not
5415 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
5416 - When connecting to a bridge without specifying its key, insert
5417 the connection into the identity-to-connection map as soon as
5418 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
5419 - Detect versions of OS X where malloc_good_size() is present in the
5420 library but never actually declared. Resolves bug 587. Bugfix
5422 - Stop incorrectly truncating zlib responses to directory authority
5423 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
5424 - Stop recommending that every server operator send mail to tor-ops.
5425 Resolves bug 597. Bugfix on 0.1.2.x.
5426 - Don't trigger an assert if we start a directory authority with a
5427 private IP address (like 127.0.0.1).
5428 - Avoid possible failures when generating a directory with routers
5429 with over-long versions strings, or too many flags set. Bugfix
5431 - If an attempt to launch a DNS resolve request over the control
5432 port fails because we have overrun the limit on the number of
5433 connections, tell the controller that the request has failed.
5434 - Avoid using too little bandwidth when our clock skips a few
5435 seconds. Bugfix on 0.1.2.x.
5436 - Fix shell error when warning about missing packages in configure
5437 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
5438 - Do not become confused when receiving a spurious VERSIONS-like
5439 cell from a confused v1 client. Bugfix on 0.2.0.x.
5440 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
5441 introduction points for a hidden service have failed. Patch from
5442 Karsten Loesing. Bugfix on 0.2.0.x.
5444 o Code simplifications and refactoring:
5445 - Remove some needless generality from cpuworker code, for improved
5447 - Stop overloading the circuit_t.onionskin field for both "onionskin
5448 from a CREATE cell that we are waiting for a cpuworker to be
5449 assigned" and "onionskin from an EXTEND cell that we are going to
5450 send to an OR as soon as we are connected". Might help with bug 600.
5451 - Add an in-place version of aes_crypt() so that we can avoid doing a
5452 needless memcpy() call on each cell payload.
5455 Changes in version 0.2.0.18-alpha - 2008-01-25
5456 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
5457 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
5458 that can warn or reject connections to ports generally associated with
5459 vulnerable-plaintext protocols.
5461 o New directory authorities:
5462 - Set up dannenberg (run by CCC) as the sixth v3 directory
5466 - Fix a major memory leak when attempting to use the v2 TLS
5467 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
5468 - We accidentally enabled the under-development v2 TLS handshake
5469 code, which was causing log entries like "TLS error while
5470 renegotiating handshake". Disable it again. Resolves bug 590.
5471 - We were computing the wrong Content-Length: header for directory
5472 responses that need to be compressed on the fly, causing clients
5473 asking for those items to always fail. Bugfix on 0.2.0.x; partially
5477 - Avoid going directly to the directory authorities even if you're a
5478 relay, if you haven't found yourself reachable yet or if you've
5479 decided not to advertise your dirport yet. Addresses bug 556.
5480 - If we've gone 12 hours since our last bandwidth check, and we
5481 estimate we have less than 50KB bandwidth capacity but we could
5482 handle more, do another bandwidth test.
5483 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
5484 Tor can warn and/or refuse connections to ports commonly used with
5485 vulnerable-plaintext protocols. Currently we warn on ports 23,
5486 109, 110, and 143, but we don't reject any.
5489 - When we setconf ClientOnly to 1, close any current OR and Dir
5490 listeners. Reported by mwenge.
5491 - When we get a consensus that's been signed by more people than
5492 we expect, don't log about it; it's not a big deal. Reported
5496 - Don't answer "/tor/networkstatus-bridges" directory requests if
5497 the request isn't encrypted.
5498 - Make "ClientOnly 1" config option disable directory ports too.
5499 - Patches from Karsten Loesing to make v2 hidden services more
5500 robust: work even when there aren't enough HSDir relays available;
5501 retry when a v2 rend desc fetch fails; but don't retry if we
5502 already have a usable v0 rend desc.
5505 Changes in version 0.2.0.17-alpha - 2008-01-17
5506 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
5509 - Make the tor-gencert man page get included correctly in the tarball.
5512 Changes in version 0.2.0.16-alpha - 2008-01-17
5513 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
5514 Loesing, and generally cleans up a lot of features and minor bugs.
5516 o New directory authorities:
5517 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
5520 o Major performance improvements:
5521 - Switch our old ring buffer implementation for one more like that
5522 used by free Unix kernels. The wasted space in a buffer with 1mb
5523 of data will now be more like 8k than 1mb. The new implementation
5524 also avoids realloc();realloc(); patterns that can contribute to
5525 memory fragmentation.
5528 - Configuration files now accept C-style strings as values. This
5529 helps encode characters not allowed in the current configuration
5530 file format, such as newline or #. Addresses bug 557.
5531 - Although we fixed bug 539 (where servers would send HTTP status 503
5532 responses _and_ send a body too), there are still servers out
5533 there that haven't upgraded. Therefore, make clients parse such
5534 bodies when they receive them.
5535 - When we're not serving v2 directory information, there is no reason
5536 to actually keep any around. Remove the obsolete files and directory
5537 on startup if they are very old and we aren't going to serve them.
5539 o Minor performance improvements:
5540 - Reference-count and share copies of address policy entries; only 5%
5541 of them were actually distinct.
5542 - Never walk through the list of logs if we know that no log is
5543 interested in a given message.
5546 - When an authority has not signed a consensus, do not try to
5547 download a nonexistent "certificate with key 00000000". Bugfix
5548 on 0.2.0.x. Fixes bug 569.
5549 - Fix a rare assert error when we're closing one of our threads:
5550 use a mutex to protect the list of logs, so we never write to the
5551 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
5552 bug 575, which is kind of the revenge of bug 222.
5553 - Patch from Karsten Loesing to complain less at both the client
5554 and the relay when a relay used to have the HSDir flag but doesn't
5555 anymore, and we try to upload a hidden service descriptor.
5556 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
5558 - Do not try to download missing certificates until we have tried
5559 to check our fallback consensus. Fixes bug 583.
5560 - Make bridges round reported GeoIP stats info up to the nearest
5561 estimate, not down. Now we can distinguish between "0 people from
5562 this country" and "1 person from this country".
5563 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
5564 - Avoid possible segfault if key generation fails in
5565 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
5566 - Avoid segfault in the case where a badly behaved v2 versioning
5567 directory sends a signed networkstatus with missing client-versions.
5569 - Avoid segfaults on certain complex invocations of
5570 router_get_by_hexdigest(). Bugfix on 0.1.2.
5571 - Correct bad index on array access in parse_http_time(). Bugfix
5573 - Fix possible bug in vote generation when server versions are present
5574 but client versions are not.
5575 - Fix rare bug on REDIRECTSTREAM control command when called with no
5576 port set: it could erroneously report an error when none had
5578 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
5579 compressing large objects and find ourselves with more than 4k
5580 left over. Bugfix on 0.2.0.
5581 - Fix a small memory leak when setting up a hidden service.
5582 - Fix a few memory leaks that could in theory happen under bizarre
5584 - Fix an assert if we post a general-purpose descriptor via the
5585 control port but that descriptor isn't mentioned in our current
5586 network consensus. Bug reported by Jon McLachlan; bugfix on
5589 o Minor features (controller):
5590 - Get NS events working again. Patch from tup.
5591 - The GETCONF command now escapes and quotes configuration values
5592 that don't otherwise fit into the torrc file.
5593 - The SETCONF command now handles quoted values correctly.
5595 o Minor features (directory authorities):
5596 - New configuration options to override default maximum number of
5597 servers allowed on a single IP address. This is important for
5598 running a test network on a single host.
5599 - Actually implement the -s option to tor-gencert.
5600 - Add a manual page for tor-gencert.
5602 o Minor features (bridges):
5603 - Bridge authorities no longer serve bridge descriptors over
5604 unencrypted connections.
5606 o Minor features (other):
5607 - Add hidden services and DNSPorts to the list of things that make
5608 Tor accept that it has running ports. Change starting Tor with no
5609 ports from a fatal error to a warning; we might change it back if
5610 this turns out to confuse anybody. Fixes bug 579.
5613 Changes in version 0.1.2.19 - 2008-01-17
5614 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
5615 exit policy a little bit more conservative so it's safer to run an
5616 exit relay on a home system, and fixes a variety of smaller issues.
5619 - Exit policies now reject connections that are addressed to a
5620 relay's public (external) IP address too, unless
5621 ExitPolicyRejectPrivate is turned off. We do this because too
5622 many relays are running nearby to services that trust them based
5626 - When the clock jumps forward a lot, do not allow the bandwidth
5627 buckets to become negative. Fixes bug 544.
5628 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
5629 on every successful resolve. Reported by Mike Perry.
5630 - Purge old entries from the "rephist" database and the hidden
5631 service descriptor database even when DirPort is zero.
5632 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
5633 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
5634 crashing or mis-answering these requests.
5635 - When we decide to send a 503 response to a request for servers, do
5636 not then also send the server descriptors: this defeats the whole
5637 purpose. Fixes bug 539.
5640 - Changing the ExitPolicyRejectPrivate setting should cause us to
5641 rebuild our server descriptor.
5642 - Fix handling of hex nicknames when answering controller requests for
5643 networkstatus by name, or when deciding whether to warn about
5644 unknown routers in a config option. (Patch from mwenge.)
5645 - Fix a couple of hard-to-trigger autoconf problems that could result
5646 in really weird results on platforms whose sys/types.h files define
5647 nonstandard integer types.
5648 - Don't try to create the datadir when running --verify-config or
5649 --hash-password. Resolves bug 540.
5650 - If we were having problems getting a particular descriptor from the
5651 directory caches, and then we learned about a new descriptor for
5652 that router, we weren't resetting our failure count. Reported
5654 - Although we fixed bug 539 (where servers would send HTTP status 503
5655 responses _and_ send a body too), there are still servers out there
5656 that haven't upgraded. Therefore, make clients parse such bodies
5657 when they receive them.
5658 - Run correctly on systems where rlim_t is larger than unsigned long.
5659 This includes some 64-bit systems.
5660 - Run correctly on platforms (like some versions of OS X 10.5) where
5661 the real limit for number of open files is OPEN_FILES, not rlim_max
5662 from getrlimit(RLIMIT_NOFILES).
5663 - Avoid a spurious free on base64 failure.
5664 - Avoid segfaults on certain complex invocations of
5665 router_get_by_hexdigest().
5666 - Fix rare bug on REDIRECTSTREAM control command when called with no
5667 port set: it could erroneously report an error when none had
5671 Changes in version 0.2.0.15-alpha - 2007-12-25
5672 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
5673 features added in 0.2.0.13-alpha.
5676 - Fix several remotely triggerable asserts based on DirPort requests
5677 for a v2 or v3 networkstatus object before we were prepared. This
5678 was particularly bad for 0.2.0.13 and later bridge relays, who
5679 would never have a v2 networkstatus and would thus always crash
5680 when used. Bugfixes on 0.2.0.x.
5681 - Estimate the v3 networkstatus size more accurately, rather than
5682 estimating it at zero bytes and giving it artificially high priority
5683 compared to other directory requests. Bugfix on 0.2.0.x.
5686 - Fix configure.in logic for cross-compilation.
5687 - When we load a bridge descriptor from the cache, and it was
5688 previously unreachable, mark it as retriable so we won't just
5689 ignore it. Also, try fetching a new copy immediately. Bugfixes
5691 - The bridge GeoIP stats were counting other relays, for example
5692 self-reachability and authority-reachability tests.
5695 - Support compilation to target iPhone; patch from cjacker huang.
5696 To build for iPhone, pass the --enable-iphone option to configure.
5699 Changes in version 0.2.0.14-alpha - 2007-12-23
5701 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
5702 without a datadirectory from a previous Tor install. Reported
5704 - Fix a crash when we fetch a descriptor that turns out to be
5705 unexpected (it used to be in our networkstatus when we started
5706 fetching it, but it isn't in our current networkstatus), and we
5707 aren't using bridges. Bugfix on 0.2.0.x.
5708 - Fix a crash when accessing hidden services: it would work the first
5709 time you use a given introduction point for your service, but
5710 on subsequent requests we'd be using garbage memory. Fixed by
5711 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
5712 - Fix a crash when we load a bridge descriptor from disk but we don't
5713 currently have a Bridge line for it in our torrc. Bugfix on
5717 - If bridge authorities set BridgePassword, they will serve a
5718 snapshot of known bridge routerstatuses from their DirPort to
5719 anybody who knows that password. Unset by default.
5722 - Make the unit tests build again.
5723 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
5724 - Make PublishServerDescriptor default to 1, so the default doesn't
5725 have to change as we invent new directory protocol versions.
5726 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
5727 be included unless sys/time.h is already included. Fixes
5728 bug 553. Bugfix on 0.2.0.x.
5729 - If we receive a general-purpose descriptor and then receive an
5730 identical bridge-purpose descriptor soon after, don't discard
5731 the next one as a duplicate.
5734 - If BridgeRelay is set to 1, then the default for
5735 PublishServerDescriptor is now "bridge" rather than "v2,v3".
5736 - If the user sets RelayBandwidthRate but doesn't set
5737 RelayBandwidthBurst, then make them equal rather than erroring out.
5740 Changes in version 0.2.0.13-alpha - 2007-12-21
5741 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
5742 Goodell, fixes many more bugs, and adds a lot of infrastructure for
5745 o New directory authorities:
5746 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
5750 - Only update guard status (usable / not usable) once we have
5751 enough directory information. This was causing us to always pick
5752 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
5753 causing us to discard all our guards on startup if we hadn't been
5754 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
5755 - Purge old entries from the "rephist" database and the hidden
5756 service descriptor databases even when DirPort is zero. Bugfix
5758 - We were ignoring our RelayBandwidthRate for the first 30 seconds
5759 after opening a circuit -- even a relayed circuit. Bugfix on
5761 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
5762 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
5763 crashing or mis-answering these types of requests.
5764 - Relays were publishing their server descriptor to v1 and v2
5765 directory authorities, but they didn't try publishing to v3-only
5766 authorities. Fix this; and also stop publishing to v1 authorities.
5768 - When we were reading router descriptors from cache, we were ignoring
5769 the annotations -- so for example we were reading in bridge-purpose
5770 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
5771 - When we decided to send a 503 response to a request for servers, we
5772 were then also sending the server descriptors: this defeats the
5773 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
5776 - Bridge relays now behave like clients with respect to time
5777 intervals for downloading new consensus documents -- otherwise they
5778 stand out. Bridge users now wait until the end of the interval,
5779 so their bridge relay will be sure to have a new consensus document.
5780 - Three new config options (AlternateDirAuthority,
5781 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
5782 user selectively replace the default directory authorities by type,
5783 rather than the all-or-nothing replacement that DirServer offers.
5784 - Tor can now be configured to read a GeoIP file from disk in one
5785 of two formats. This can be used by controllers to map IP addresses
5786 to countries. Eventually, it may support exit-by-country.
5787 - When possible, bridge relays remember which countries users
5788 are coming from, and report aggregate information in their
5789 extra-info documents, so that the bridge authorities can learn
5790 where Tor is blocked.
5791 - Bridge directory authorities now do reachability testing on the
5792 bridges they know. They provide router status summaries to the
5793 controller via "getinfo ns/purpose/bridge", and also dump summaries
5794 to a file periodically.
5795 - Stop fetching directory info so aggressively if your DirPort is
5796 on but your ORPort is off; stop fetching v2 dir info entirely.
5797 You can override these choices with the new FetchDirInfoEarly
5801 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
5802 consensus documents when there are too many relays at a single
5803 IP address. Now clear it in v2 network status documents too, and
5804 also clear it in routerinfo_t when the relay is no longer listed
5805 in the relevant networkstatus document.
5806 - Don't crash if we get an unexpected value for the
5807 PublishServerDescriptor config option. Reported by Matt Edman;
5808 bugfix on 0.2.0.9-alpha.
5809 - Our new v2 hidden service descriptor format allows descriptors
5810 that have no introduction points. But Tor crashed when we tried
5811 to build a descriptor with no intro points (and it would have
5812 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
5814 - Fix building with dmalloc 5.5.2 with glibc.
5815 - Reject uploaded descriptors and extrainfo documents if they're
5816 huge. Otherwise we'll cache them all over the network and it'll
5817 clog everything up. Reported by Aljosha Judmayer.
5818 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
5819 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
5820 - When the DANGEROUS_VERSION controller status event told us we're
5821 running an obsolete version, it used the string "OLD" to describe
5822 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
5823 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
5824 - If we can't expand our list of entry guards (e.g. because we're
5825 using bridges or we have StrictEntryNodes set), don't mark relays
5826 down when they fail a directory request. Otherwise we're too quick
5827 to mark all our entry points down. Bugfix on 0.1.2.x.
5828 - Fix handling of hex nicknames when answering controller requests for
5829 networkstatus by name, or when deciding whether to warn about unknown
5830 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
5831 - Fix a couple of hard-to-trigger autoconf problems that could result
5832 in really weird results on platforms whose sys/types.h files define
5833 nonstandard integer types. Bugfix on 0.1.2.x.
5834 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
5835 - Don't crash on name lookup when we have no current consensus. Fixes
5836 bug 538; bugfix on 0.2.0.x.
5837 - Only Tors that want to mirror the v2 directory info should
5838 create the "cached-status" directory in their datadir. (All Tors
5839 used to create it.) Bugfix on 0.2.0.9-alpha.
5840 - Directory authorities should only automatically download Extra Info
5841 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
5844 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
5845 consumers. (We already do this on HUP.)
5846 - Authorities and caches fetch the v2 networkstatus documents
5847 less often, now that v3 is encouraged.
5848 - Add a new config option BridgeRelay that specifies you want to
5849 be a bridge relay. Right now the only difference is that it makes
5850 you answer begin_dir requests, and it makes you cache dir info,
5851 even if your DirPort isn't on.
5852 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
5853 ask about source, timestamp of arrival, purpose, etc. We need
5854 something like this to help Vidalia not do GeoIP lookups on bridge
5856 - Allow multiple HashedControlPassword config lines, to support
5857 multiple controller passwords.
5858 - Authorities now decide whether they're authoritative for a given
5859 router based on the router's purpose.
5860 - New config options AuthDirBadDir and AuthDirListBadDirs for
5861 authorities to mark certain relays as "bad directories" in the
5862 networkstatus documents. Also supports the "!baddir" directive in
5863 the approved-routers file.
5866 Changes in version 0.2.0.12-alpha - 2007-11-16
5867 This twelfth development snapshot fixes some more build problems as
5868 well as a few minor bugs.
5871 - Make it build on OpenBSD again. Patch from tup.
5872 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
5873 package-building for Red Hat, OS X, etc.
5875 o Minor bugfixes (on 0.1.2.x):
5876 - Changing the ExitPolicyRejectPrivate setting should cause us to
5877 rebuild our server descriptor.
5879 o Minor bugfixes (on 0.2.0.x):
5880 - When we're lacking a consensus, don't try to perform rendezvous
5881 operations. Reported by Karsten Loesing.
5882 - Fix a small memory leak whenever we decide against using a
5883 newly picked entry guard. Reported by Mike Perry.
5884 - When authorities detected more than two relays running on the same
5885 IP address, they were clearing all the status flags but forgetting
5886 to clear the "hsdir" flag. So clients were being told that a
5887 given relay was the right choice for a v2 hsdir lookup, yet they
5888 never had its descriptor because it was marked as 'not running'
5890 - If we're trying to fetch a bridge descriptor and there's no way
5891 the bridge authority could help us (for example, we don't know
5892 a digest, or there is no bridge authority), don't be so eager to
5893 fall back to asking the bridge authority.
5894 - If we're using bridges or have strictentrynodes set, and our
5895 chosen exit is in the same family as all our bridges/entry guards,
5896 then be flexible about families.
5899 - When we negotiate a v2 link-layer connection (not yet implemented),
5900 accept RELAY_EARLY cells and turn them into RELAY cells if we've
5901 negotiated a v1 connection for their next step. Initial code for
5905 Changes in version 0.2.0.11-alpha - 2007-11-12
5906 This eleventh development snapshot fixes some build problems with
5907 the previous snapshot. It also includes a more secure-by-default exit
5908 policy for relays, fixes an enormous memory leak for exit relays, and
5909 fixes another bug where servers were falling out of the directory list.
5912 - Exit policies now reject connections that are addressed to a
5913 relay's public (external) IP address too, unless
5914 ExitPolicyRejectPrivate is turned off. We do this because too
5915 many relays are running nearby to services that trust them based
5916 on network address. Bugfix on 0.1.2.x.
5919 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
5920 on every successful resolve. Reported by Mike Perry; bugfix
5922 - On authorities, never downgrade to old router descriptors simply
5923 because they're listed in the consensus. This created a catch-22
5924 where we wouldn't list a new descriptor because there was an
5925 old one in the consensus, and we couldn't get the new one in the
5926 consensus because we wouldn't list it. Possible fix for bug 548.
5927 Also, this might cause bug 543 to appear on authorities; if so,
5928 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
5930 o Packaging fixes on 0.2.0.10-alpha:
5931 - We were including instructions about what to do with the
5932 src/config/fallback-consensus file, but we weren't actually
5933 including it in the tarball. Disable all of that for now.
5936 - Allow people to say PreferTunnelledDirConns rather than
5937 PreferTunneledDirConns, for those alternate-spellers out there.
5940 - Don't reevaluate all the information from our consensus document
5941 just because we've downloaded a v2 networkstatus that we intend
5942 to cache. Fixes bug 545; bugfix on 0.2.0.x.
5945 Changes in version 0.2.0.10-alpha - 2007-11-10
5946 This tenth development snapshot adds a third v3 directory authority
5947 run by Mike Perry, adds most of Karsten Loesing's new hidden service
5948 descriptor format, fixes a bad crash bug and new bridge bugs introduced
5949 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
5950 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
5951 addresses many more minor issues.
5953 o New directory authorities:
5954 - Set up ides (run by Mike Perry) as the third v3 directory authority.
5957 - Allow tunnelled directory connections to ask for an encrypted
5958 "begin_dir" connection or an anonymized "uses a full Tor circuit"
5959 connection independently. Now we can make anonymized begin_dir
5960 connections for (e.g.) more secure hidden service posting and
5962 - More progress on proposal 114: code from Karsten Loesing to
5963 implement new hidden service descriptor format.
5964 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
5965 accommodate the growing number of servers that use the default
5966 and are reaching it.
5967 - Directory authorities use a new formula for selecting which nodes
5968 to advertise as Guards: they must be in the top 7/8 in terms of
5969 how long we have known about them, and above the median of those
5970 nodes in terms of weighted fractional uptime.
5971 - Make "not enough dir info yet" warnings describe *why* Tor feels
5972 it doesn't have enough directory info yet.
5975 - Stop servers from crashing if they set a Family option (or
5976 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
5978 - Make bridge users work again -- the move to v3 directories in
5979 0.2.0.9-alpha had introduced a number of bugs that made bridges
5980 no longer work for clients.
5981 - When the clock jumps forward a lot, do not allow the bandwidth
5982 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
5984 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
5985 - When the consensus lists a router descriptor that we previously were
5986 mirroring, but that we considered non-canonical, reload the
5987 descriptor as canonical. This fixes bug 543 where Tor servers
5988 would start complaining after a few days that they don't have
5989 enough directory information to build a circuit.
5990 - Consider replacing the current consensus when certificates arrive
5991 that make the pending consensus valid. Previously, we were only
5992 considering replacement when the new certs _didn't_ help.
5993 - Fix an assert error on startup if we didn't already have the
5994 consensus and certs cached in our datadirectory: we were caching
5995 the consensus in consensus_waiting_for_certs but then free'ing it
5997 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
5998 Request) if we need more v3 certs but we've already got pending
5999 requests for all of them.
6000 - Correctly back off from failing certificate downloads. Fixes
6002 - Authorities don't vote on the Running flag if they have been running
6003 for less than 30 minutes themselves. Fixes bug 547, where a newly
6004 started authority would vote that everyone was down.
6007 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
6008 it, it had no AES, and it hasn't seen any security patches since
6012 - Clients now hold circuitless TLS connections open for 1.5 times
6013 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
6014 rebuild a new circuit over them within that timeframe. Previously,
6015 they held them open only for KeepalivePeriod (5 minutes).
6016 - Use "If-Modified-Since" to avoid retrieving consensus
6017 networkstatuses that we already have.
6018 - When we have no consensus, check FallbackNetworkstatusFile (defaults
6019 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
6020 we start knowing some directory caches.
6021 - When we receive a consensus from the future, warn about skew.
6022 - Improve skew reporting: try to give the user a better log message
6023 about how skewed they are, and how much this matters.
6024 - When we have a certificate for an authority, believe that
6025 certificate's claims about the authority's IP address.
6026 - New --quiet command-line option to suppress the default console log.
6027 Good in combination with --hash-password.
6028 - Authorities send back an X-Descriptor-Not-New header in response to
6029 an accepted-but-discarded descriptor upload. Partially implements
6031 - Make the log message for "tls error. breaking." more useful.
6032 - Better log messages about certificate downloads, to attempt to
6033 track down the second incarnation of bug 546.
6035 o Minor features (bridges):
6036 - If bridge users set UpdateBridgesFromAuthority, but the digest
6037 they ask for is a 404 from the bridge authority, they now fall
6038 back to trying the bridge directly.
6039 - Bridges now use begin_dir to publish their server descriptor to
6040 the bridge authority, even when they haven't set TunnelDirConns.
6042 o Minor features (controller):
6043 - When reporting clock skew, and we know that the clock is _at least
6044 as skewed_ as some value, but we don't know the actual value,
6045 report the value as a "minimum skew."
6048 - Update linux-tor-prio.sh script to allow QoS based on the uid of
6049 the Tor process. Patch from Marco Bonetti with tweaks from Mike
6053 - Refuse to start if both ORPort and UseBridges are set. Bugfix
6054 on 0.2.0.x, suggested by Matt Edman.
6055 - Don't stop fetching descriptors when FetchUselessDescriptors is
6056 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
6057 reported by tup and ioerror.
6058 - Better log message on vote from unknown authority.
6059 - Don't log "Launching 0 request for 0 router" message.
6061 o Minor bugfixes (memory leaks):
6062 - Stop leaking memory every time we parse a v3 certificate. Bugfix
6064 - Stop leaking memory every time we load a v3 certificate. Bugfix
6065 on 0.2.0.1-alpha. Fixes bug 536.
6066 - Stop leaking a cached networkstatus on exit. Bugfix on
6068 - Stop leaking voter information every time we free a consensus.
6069 Bugfix on 0.2.0.3-alpha.
6070 - Stop leaking signed data every time we check a voter signature.
6071 Bugfix on 0.2.0.3-alpha.
6072 - Stop leaking a signature every time we fail to parse a consensus or
6073 a vote. Bugfix on 0.2.0.3-alpha.
6074 - Stop leaking v2_download_status_map on shutdown. Bugfix on
6076 - Stop leaking conn->nickname every time we make a connection to a
6077 Tor relay without knowing its expected identity digest (e.g. when
6078 using bridges). Bugfix on 0.2.0.3-alpha.
6080 - Minor bugfixes (portability):
6081 - Run correctly on platforms where rlim_t is larger than unsigned
6082 long, and/or where the real limit for number of open files is
6083 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
6084 particular, these may be needed for OS X 10.5.
6087 Changes in version 0.1.2.18 - 2007-10-28
6088 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
6089 hidden service introduction that were causing huge delays, and a big
6090 bug that was causing some servers to disappear from the network status
6091 lists for a few hours each day.
6093 o Major bugfixes (crashes):
6094 - If a connection is shut down abruptly because of something that
6095 happened inside connection_flushed_some(), do not call
6096 connection_finished_flushing(). Should fix bug 451:
6097 "connection_stop_writing: Assertion conn->write_event failed"
6098 Bugfix on 0.1.2.7-alpha.
6099 - Fix possible segfaults in functions called from
6100 rend_process_relay_cell().
6102 o Major bugfixes (hidden services):
6103 - Hidden services were choosing introduction points uniquely by
6104 hexdigest, but when constructing the hidden service descriptor
6105 they merely wrote the (potentially ambiguous) nickname.
6106 - Clients now use the v2 intro format for hidden service
6107 connections: they specify their chosen rendezvous point by identity
6108 digest rather than by (potentially ambiguous) nickname. These
6109 changes could speed up hidden service connections dramatically.
6111 o Major bugfixes (other):
6112 - Stop publishing a new server descriptor just because we get a
6113 HUP signal. This led (in a roundabout way) to some servers getting
6114 dropped from the networkstatus lists for a few hours each day.
6115 - When looking for a circuit to cannibalize, consider family as well
6116 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
6117 circuit cannibalization).
6118 - When a router wasn't listed in a new networkstatus, we were leaving
6119 the flags for that router alone -- meaning it remained Named,
6120 Running, etc -- even though absence from the networkstatus means
6121 that it shouldn't be considered to exist at all anymore. Now we
6122 clear all the flags for routers that fall out of the networkstatus
6123 consensus. Fixes bug 529.
6126 - Don't try to access (or alter) the state file when running
6127 --list-fingerprint or --verify-config or --hash-password. Resolves
6129 - When generating information telling us how to extend to a given
6130 router, do not try to include the nickname if it is
6131 absent. Resolves bug 467.
6132 - Fix a user-triggerable segfault in expand_filename(). (There isn't
6133 a way to trigger this remotely.)
6134 - When sending a status event to the controller telling it that an
6135 OR address is reachable, set the port correctly. (Previously we
6136 were reporting the dir port.)
6137 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
6138 command. Bugfix on 0.1.2.17.
6139 - When loading bandwidth history, do not believe any information in
6140 the future. Fixes bug 434.
6141 - When loading entry guard information, do not believe any information
6143 - When we have our clock set far in the future and generate an
6144 onion key, then re-set our clock to be correct, we should not stop
6145 the onion key from getting rotated.
6146 - On some platforms, accept() can return a broken address. Detect
6147 this more quietly, and deal accordingly. Fixes bug 483.
6148 - It's not actually an error to find a non-pending entry in the DNS
6149 cache when canceling a pending resolve. Don't log unless stuff
6150 is fishy. Resolves bug 463.
6151 - Don't reset trusted dir server list when we set a configuration
6152 option. Patch from Robert Hogan.
6153 - Don't try to create the datadir when running --verify-config or
6154 --hash-password. Resolves bug 540.
6157 Changes in version 0.2.0.9-alpha - 2007-10-24
6158 This ninth development snapshot switches clients to the new v3 directory
6159 system; allows servers to be listed in the network status even when they
6160 have the same nickname as a registered server; and fixes many other
6161 bugs including a big one that was causing some servers to disappear
6162 from the network status lists for a few hours each day.
6164 o Major features (directory system):
6165 - Clients now download v3 consensus networkstatus documents instead
6166 of v2 networkstatus documents. Clients and caches now base their
6167 opinions about routers on these consensus documents. Clients only
6168 download router descriptors listed in the consensus.
6169 - Authorities now list servers who have the same nickname as
6170 a different named server, but list them with a new flag,
6171 "Unnamed". Now we can list servers that happen to pick the same
6172 nickname as a server that registered two years ago and then
6173 disappeared. Partially implements proposal 122.
6174 - If the consensus lists a router as "Unnamed", the name is assigned
6175 to a different router: do not identify the router by that name.
6176 Partially implements proposal 122.
6177 - Authorities can now come to a consensus on which method to use to
6178 compute the consensus. This gives us forward compatibility.
6181 - Stop publishing a new server descriptor just because we HUP or
6182 when we find our DirPort to be reachable but won't actually publish
6183 it. New descriptors without any real changes are dropped by the
6184 authorities, and can screw up our "publish every 18 hours" schedule.
6186 - When a router wasn't listed in a new networkstatus, we were leaving
6187 the flags for that router alone -- meaning it remained Named,
6188 Running, etc -- even though absence from the networkstatus means
6189 that it shouldn't be considered to exist at all anymore. Now we
6190 clear all the flags for routers that fall out of the networkstatus
6191 consensus. Fixes bug 529; bugfix on 0.1.2.x.
6192 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
6193 extrainfo documents and then discard them immediately for not
6194 matching the latest router. Bugfix on 0.2.0.1-alpha.
6196 o Minor features (v3 directory protocol):
6197 - Allow tor-gencert to generate a new certificate without replacing
6199 - Allow certificates to include an address.
6200 - When we change our directory-cache settings, reschedule all voting
6201 and download operations.
6202 - Reattempt certificate downloads immediately on failure, as long as
6203 we haven't failed a threshold number of times yet.
6204 - Delay retrying consensus downloads while we're downloading
6205 certificates to verify the one we just got. Also, count getting a
6206 consensus that we already have (or one that isn't valid) as a failure,
6207 and count failing to get the certificates after 20 minutes as a
6209 - Build circuits and download descriptors even if our consensus is a
6210 little expired. (This feature will go away once authorities are
6213 o Minor features (router descriptor cache):
6214 - If we find a cached-routers file that's been sitting around for more
6215 than 28 days unmodified, then most likely it's a leftover from
6216 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
6218 - When we (as a cache) download a descriptor because it was listed
6219 in a consensus, remember when the consensus was supposed to expire,
6220 and don't expire the descriptor until then.
6222 o Minor features (performance):
6223 - Call routerlist_remove_old_routers() much less often. This should
6224 speed startup, especially on directory caches.
6225 - Don't try to launch new descriptor downloads quite so often when we
6226 already have enough directory information to build circuits.
6227 - Base64 decoding was actually showing up on our profile when parsing
6228 the initial descriptor file; switch to an in-process all-at-once
6229 implementation that's about 3.5x times faster than calling out to
6232 o Minor features (compilation):
6233 - Detect non-ASCII platforms (if any still exist) and refuse to
6234 build there: some of our code assumes that 'A' is 65 and so on.
6236 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
6237 - Make the "next period" votes into "current period" votes immediately
6238 after publishing the consensus; avoid a heisenbug that made them
6239 stick around indefinitely.
6240 - When we discard a vote as a duplicate, do not report this as
6242 - Treat missing v3 keys or certificates as an error when running as a
6243 v3 directory authority.
6244 - When we're configured to be a v3 authority, but we're only listed
6245 as a non-v3 authority in our DirServer line for ourself, correct
6247 - If an authority doesn't have a qualified hostname, just put
6248 its address in the vote. This fixes the problem where we referred to
6249 "moria on moria:9031."
6250 - Distinguish between detached signatures for the wrong period, and
6251 detached signatures for a divergent vote.
6252 - Fix a small memory leak when computing a consensus.
6253 - When there's no concensus, we were forming a vote every 30
6254 minutes, but writing the "valid-after" line in our vote based
6255 on our configured V3AuthVotingInterval: so unless the intervals
6256 matched up, we immediately rejected our own vote because it didn't
6257 start at the voting interval that caused us to construct a vote.
6259 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
6260 - Delete unverified-consensus when the real consensus is set.
6261 - Consider retrying a consensus networkstatus fetch immediately
6262 after one fails: don't wait 60 seconds to notice.
6263 - When fetching a consensus as a cache, wait until a newer consensus
6264 should exist before trying to replace the current one.
6265 - Use a more forgiving schedule for retrying failed consensus
6266 downloads than for other types.
6268 o Minor bugfixes (other directory issues):
6269 - Correct the implementation of "download votes by digest." Bugfix on
6271 - Authorities no longer send back "400 you're unreachable please fix
6272 it" errors to Tor servers that aren't online all the time. We're
6273 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
6275 o Minor bugfixes (controller):
6276 - Don't reset trusted dir server list when we set a configuration
6277 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
6278 - Respond to INT and TERM SIGNAL commands before we execute the
6279 signal, in case the signal shuts us down. We had a patch in
6280 0.1.2.1-alpha that tried to do this by queueing the response on
6281 the connection's buffer before shutting down, but that really
6282 isn't the same thing at all. Bug located by Matt Edman.
6284 o Minor bugfixes (misc):
6285 - Correctly check for bad options to the "PublishServerDescriptor"
6286 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
6287 - Stop leaking memory on failing case of base32_decode, and make
6288 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
6289 - Don't try to download extrainfo documents when we're trying to
6290 fetch enough directory info to build a circuit: having enough
6291 info should get priority. Bugfix on 0.2.0.x.
6292 - Don't complain that "your server has not managed to confirm that its
6293 ports are reachable" if we haven't been able to build any circuits
6294 yet. Bug found by spending four hours without a v3 consensus. Bugfix
6296 - Detect the reason for failing to mmap a descriptor file we just
6297 wrote, and give a more useful log message. Fixes bug 533. Bugfix
6300 o Code simplifications and refactoring:
6301 - Remove support for the old bw_accounting file: we've been storing
6302 bandwidth accounting information in the state file since
6303 0.1.2.5-alpha. This may result in bandwidth accounting errors
6304 if you try to upgrade from 0.1.1.x or earlier, or if you try to
6305 downgrade to 0.1.1.x or earlier.
6306 - New convenience code to locate a file within the DataDirectory.
6307 - Move non-authority functionality out of dirvote.c.
6308 - Refactor the arguments for router_pick_{directory_|trusteddir}server
6309 so that they all take the same named flags.
6312 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
6313 Unix users an easy way to script their Tor process (e.g. by
6314 adjusting bandwidth based on the time of the day).
6317 Changes in version 0.2.0.8-alpha - 2007-10-12
6318 This eighth development snapshot fixes a crash bug that's been bothering
6319 us since February 2007, lets bridge authorities store a list of bridge
6320 descriptors they've seen, gets v3 directory voting closer to working,
6321 starts caching v3 directory consensus documents on directory mirrors,
6322 and fixes a variety of smaller issues including some minor memory leaks.
6324 o Major features (router descriptor cache):
6325 - Store routers in a file called cached-descriptors instead of in
6326 cached-routers. Initialize cached-descriptors from cached-routers
6327 if the old format is around. The new format allows us to store
6328 annotations along with descriptors.
6329 - Use annotations to record the time we received each descriptor, its
6330 source, and its purpose.
6331 - Disable the SETROUTERPURPOSE controller command: it is now
6333 - Controllers should now specify cache=no or cache=yes when using
6334 the +POSTDESCRIPTOR command.
6335 - Bridge authorities now write bridge descriptors to disk, meaning
6336 we can export them to other programs and begin distributing them
6339 o Major features (directory authorities):
6340 - When a v3 authority is missing votes or signatures, it now tries
6342 - Directory authorities track weighted fractional uptime as well as
6343 weighted mean-time-between failures. WFU is suitable for deciding
6344 whether a node is "usually up", while MTBF is suitable for deciding
6345 whether a node is "likely to stay up." We need both, because
6346 "usually up" is a good requirement for guards, while "likely to
6347 stay up" is a good requirement for long-lived connections.
6349 o Major features (v3 directory system):
6350 - Caches now download v3 network status documents as needed,
6351 and download the descriptors listed in them.
6352 - All hosts now attempt to download and keep fresh v3 authority
6353 certificates, and re-attempt after failures.
6354 - More internal-consistency checks for vote parsing.
6356 o Major bugfixes (crashes):
6357 - If a connection is shut down abruptly because of something that
6358 happened inside connection_flushed_some(), do not call
6359 connection_finished_flushing(). Should fix bug 451. Bugfix on
6362 o Major bugfixes (performance):
6363 - Fix really bad O(n^2) performance when parsing a long list of
6364 routers: Instead of searching the entire list for an "extra-info "
6365 string which usually wasn't there, once for every routerinfo
6366 we read, just scan lines forward until we find one we like.
6368 - When we add data to a write buffer in response to the data on that
6369 write buffer getting low because of a flush, do not consider the
6370 newly added data as a candidate for immediate flushing, but rather
6371 make it wait until the next round of writing. Otherwise, we flush
6372 and refill recursively, and a single greedy TLS connection can
6373 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
6375 o Minor features (v3 authority system):
6376 - Add more ways for tools to download the votes that lead to the
6378 - Send a 503 when low on bandwidth and a vote, consensus, or
6379 certificate is requested.
6380 - If-modified-since is now implemented properly for all kinds of
6381 certificate requests.
6383 o Minor bugfixes (network statuses):
6384 - Tweak the implementation of proposal 109 slightly: allow at most
6385 two Tor servers on the same IP address, except if it's the location
6386 of a directory authority, in which case allow five. Bugfix on
6389 o Minor bugfixes (controller):
6390 - When sending a status event to the controller telling it that an
6391 OR address is reachable, set the port correctly. (Previously we
6392 were reporting the dir port.) Bugfix on 0.1.2.x.
6394 o Minor bugfixes (v3 directory system):
6395 - Fix logic to look up a cert by its signing key digest. Bugfix on
6397 - Only change the reply to a vote to "OK" if it's not already
6398 set. This gets rid of annoying "400 OK" log messages, which may
6399 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
6400 - When we get a valid consensus, recompute the voting schedule.
6401 - Base the valid-after time of a vote on the consensus voting
6402 schedule, not on our preferred schedule.
6403 - Make the return values and messages from signature uploads and
6404 downloads more sensible.
6405 - Fix a memory leak when serving votes and consensus documents, and
6406 another when serving certificates.
6408 o Minor bugfixes (performance):
6409 - Use a slightly simpler string hashing algorithm (copying Python's
6410 instead of Java's) and optimize our digest hashing algorithm to take
6411 advantage of 64-bit platforms and to remove some possibly-costly
6413 - Fix a minor memory leak whenever we parse guards from our state
6414 file. Bugfix on 0.2.0.7-alpha.
6415 - Fix a minor memory leak whenever we write out a file. Bugfix on
6417 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
6418 command. Bugfix on 0.2.0.5-alpha.
6420 o Minor bugfixes (portability):
6421 - On some platforms, accept() can return a broken address. Detect
6422 this more quietly, and deal accordingly. Fixes bug 483.
6423 - Stop calling tor_strlower() on uninitialized memory in some cases.
6424 Bugfix in 0.2.0.7-alpha.
6426 o Minor bugfixes (usability):
6427 - Treat some 403 responses from directory servers as INFO rather than
6428 WARN-severity events.
6429 - It's not actually an error to find a non-pending entry in the DNS
6430 cache when canceling a pending resolve. Don't log unless stuff is
6431 fishy. Resolves bug 463.
6433 o Minor bugfixes (anonymity):
6434 - Never report that we've used more bandwidth than we're willing to
6435 relay: it leaks how much non-relay traffic we're using. Resolves
6437 - When looking for a circuit to cannibalize, consider family as well
6438 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
6439 circuit cannibalization).
6441 o Code simplifications and refactoring:
6442 - Make a bunch of functions static. Remove some dead code.
6443 - Pull out about a third of the really big routerlist.c; put it in a
6444 new module, networkstatus.c.
6445 - Merge the extra fields in local_routerstatus_t back into
6446 routerstatus_t: we used to need one routerstatus_t for each
6447 authority's opinion, plus a local_routerstatus_t for the locally
6448 computed consensus opinion. To save space, we put the locally
6449 modified fields into local_routerstatus_t, and only the common
6450 stuff into routerstatus_t. But once v3 directories are in use,
6451 clients and caches will no longer need to hold authority opinions;
6452 thus, the rationale for keeping the types separate is now gone.
6453 - Make the code used to reschedule and reattempt downloads more
6455 - Turn all 'Are we a directory server/mirror?' logic into a call to
6457 - Remove the code to generate the oldest (v1) directory format.
6458 The code has been disabled since 0.2.0.5-alpha.
6461 Changes in version 0.2.0.7-alpha - 2007-09-21
6462 This seventh development snapshot makes bridges work again, makes bridge
6463 authorities work for the first time, fixes two huge performance flaws
6464 in hidden services, and fixes a variety of minor issues.
6466 o New directory authorities:
6467 - Set up moria1 and tor26 as the first v3 directory authorities. See
6468 doc/spec/dir-spec.txt for details on the new directory design.
6470 o Major bugfixes (crashes):
6471 - Fix possible segfaults in functions called from
6472 rend_process_relay_cell(). Bugfix on 0.1.2.x.
6474 o Major bugfixes (bridges):
6475 - Fix a bug that made servers send a "404 Not found" in response to
6476 attempts to fetch their server descriptor. This caused Tor servers
6477 to take many minutes to establish reachability for their DirPort,
6478 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
6479 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
6480 users configure that and specify a bridge with an identity
6481 fingerprint, now they will lookup the bridge descriptor at the
6482 default bridge authority via a one-hop tunnel, but once circuits
6483 are established they will switch to a three-hop tunnel for later
6484 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
6486 o Major bugfixes (hidden services):
6487 - Hidden services were choosing introduction points uniquely by
6488 hexdigest, but when constructing the hidden service descriptor
6489 they merely wrote the (potentially ambiguous) nickname.
6490 - Clients now use the v2 intro format for hidden service
6491 connections: they specify their chosen rendezvous point by identity
6492 digest rather than by (potentially ambiguous) nickname. Both
6493 are bugfixes on 0.1.2.x, and they could speed up hidden service
6494 connections dramatically. Thanks to Karsten Loesing.
6496 o Minor features (security):
6497 - As a client, do not believe any server that tells us that an
6498 address maps to an internal address space.
6499 - Make it possible to enable HashedControlPassword and
6500 CookieAuthentication at the same time.
6502 o Minor features (guard nodes):
6503 - Tag every guard node in our state file with the version that
6504 we believe added it, or with our own version if we add it. This way,
6505 if a user temporarily runs an old version of Tor and then switches
6506 back to a new one, she doesn't automatically lose her guards.
6508 o Minor features (speed):
6509 - When implementing AES counter mode, update only the portions of the
6510 counter buffer that need to change, and don't keep separate
6511 network-order and host-order counters when they are the same (i.e.,
6512 on big-endian hosts.)
6514 o Minor features (controller):
6515 - Accept LF instead of CRLF on controller, since some software has a
6516 hard time generating real Internet newlines.
6517 - Add GETINFO values for the server status events
6518 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
6522 - Routers no longer include bandwidth-history lines in their
6523 descriptors; this information is already available in extra-info
6524 documents, and including it in router descriptors took up 60%
6525 (!) of compressed router descriptor downloads. Completes
6526 implementation of proposal 104.
6527 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
6528 and TorControl.py, as they use the old v0 controller protocol,
6529 and are obsoleted by TorFlow anyway.
6530 - Drop support for v1 rendezvous descriptors, since we never used
6531 them anyway, and the code has probably rotted by now. Based on
6532 patch from Karsten Loesing.
6533 - On OSX, stop warning the user that kqueue support in libevent is
6534 "experimental", since it seems to have worked fine for ages.
6537 - When generating information telling us how to extend to a given
6538 router, do not try to include the nickname if it is absent. Fixes
6539 bug 467. Bugfix on 0.2.0.3-alpha.
6540 - Fix a user-triggerable (but not remotely-triggerable) segfault
6541 in expand_filename(). Bugfix on 0.1.2.x.
6542 - Fix a memory leak when freeing incomplete requests from DNSPort.
6543 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
6544 - Don't try to access (or alter) the state file when running
6545 --list-fingerprint or --verify-config or --hash-password. (Resolves
6546 bug 499.) Bugfix on 0.1.2.x.
6547 - Servers used to decline to publish their DirPort if their
6548 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
6549 were below a threshold. Now they only look at BandwidthRate and
6550 RelayBandwidthRate. Bugfix on 0.1.2.x.
6551 - Remove an optimization in the AES counter-mode code that assumed
6552 that the counter never exceeded 2^68. When the counter can be set
6553 arbitrarily as an IV (as it is by Karsten's new hidden services
6554 code), this assumption no longer holds. Bugfix on 0.1.2.x.
6555 - Resume listing "AUTHORITY" flag for authorities in network status.
6556 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
6558 o Code simplifications and refactoring:
6559 - Revamp file-writing logic so we don't need to have the entire
6560 contents of a file in memory at once before we write to disk. Tor,
6562 - Turn "descriptor store" into a full-fledged type.
6563 - Move all NT services code into a separate source file.
6564 - Unify all code that computes medians, percentile elements, etc.
6565 - Get rid of a needless malloc when parsing address policies.
6568 Changes in version 0.1.2.17 - 2007-08-30
6569 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
6570 X bundles. Vidalia 0.0.14 makes authentication required for the
6571 ControlPort in the default configuration, which addresses important
6572 security risks. Everybody who uses Vidalia (or another controller)
6575 In addition, this Tor update fixes major load balancing problems with
6576 path selection, which should speed things up a lot once many people
6579 o Major bugfixes (security):
6580 - We removed support for the old (v0) control protocol. It has been
6581 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
6582 become more of a headache than it's worth.
6584 o Major bugfixes (load balancing):
6585 - When choosing nodes for non-guard positions, weight guards
6586 proportionally less, since they already have enough load. Patch
6588 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6589 will allow fast Tor servers to get more attention.
6590 - When we're upgrading from an old Tor version, forget our current
6591 guards and pick new ones according to the new weightings. These
6592 three load balancing patches could raise effective network capacity
6593 by a factor of four. Thanks to Mike Perry for measurements.
6595 o Major bugfixes (stream expiration):
6596 - Expire not-yet-successful application streams in all cases if
6597 they've been around longer than SocksTimeout. Right now there are
6598 some cases where the stream will live forever, demanding a new
6599 circuit every 15 seconds. Fixes bug 454; reported by lodger.
6601 o Minor features (controller):
6602 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6603 is valid before any authentication has been received. It tells
6604 a controller what kind of authentication is expected, and what
6605 protocol is spoken. Implements proposal 119.
6607 o Minor bugfixes (performance):
6608 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
6609 greatly speeding up loading cached-routers from disk on startup.
6610 - Disable sentinel-based debugging for buffer code: we squashed all
6611 the bugs that this was supposed to detect a long time ago, and now
6612 its only effect is to change our buffer sizes from nice powers of
6613 two (which platform mallocs tend to like) to values slightly over
6614 powers of two (which make some platform mallocs sad).
6616 o Minor bugfixes (misc):
6617 - If exit bandwidth ever exceeds one third of total bandwidth, then
6618 use the correct formula to weight exit nodes when choosing paths.
6619 Based on patch from Mike Perry.
6620 - Choose perfectly fairly among routers when choosing by bandwidth and
6621 weighting by fraction of bandwidth provided by exits. Previously, we
6622 would choose with only approximate fairness, and correct ourselves
6623 if we ran off the end of the list.
6624 - If we require CookieAuthentication but we fail to write the
6625 cookie file, we would warn but not exit, and end up in a state
6626 where no controller could authenticate. Now we exit.
6627 - If we require CookieAuthentication, stop generating a new cookie
6628 every time we change any piece of our config.
6629 - Refuse to start with certain directory authority keys, and
6630 encourage people using them to stop.
6631 - Terminate multi-line control events properly. Original patch
6633 - Fix a minor memory leak when we fail to find enough suitable
6634 servers to choose a circuit.
6635 - Stop leaking part of the descriptor when we run into a particularly
6636 unparseable piece of it.
6639 Changes in version 0.2.0.6-alpha - 2007-08-26
6640 This sixth development snapshot features a new Vidalia version in the
6641 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
6642 the ControlPort in the default configuration, which addresses important
6645 In addition, this snapshot fixes major load balancing problems
6646 with path selection, which should speed things up a lot once many
6647 people have upgraded. The directory authorities also use a new
6648 mean-time-between-failure approach to tracking which servers are stable,
6649 rather than just looking at the most recent uptime.
6651 o New directory authorities:
6652 - Set up Tonga as the default bridge directory authority.
6655 - Directory authorities now track servers by weighted
6656 mean-times-between-failures. When we have 4 or more days of data,
6657 use measured MTBF rather than declared uptime to decide whether
6658 to call a router Stable. Implements proposal 108.
6660 o Major bugfixes (load balancing):
6661 - When choosing nodes for non-guard positions, weight guards
6662 proportionally less, since they already have enough load. Patch
6664 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6665 will allow fast Tor servers to get more attention.
6666 - When we're upgrading from an old Tor version, forget our current
6667 guards and pick new ones according to the new weightings. These
6668 three load balancing patches could raise effective network capacity
6669 by a factor of four. Thanks to Mike Perry for measurements.
6671 o Major bugfixes (descriptor parsing):
6672 - Handle unexpected whitespace better in malformed descriptors. Bug
6673 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
6676 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
6677 GETINFO for Torstat to use until it can switch to using extrainfos.
6678 - Optionally (if built with -DEXPORTMALLINFO) export the output
6679 of mallinfo via http, as tor/mallinfo.txt. Only accessible
6683 - Do not intermix bridge routers with controller-added
6684 routers. (Bugfix on 0.2.0.x)
6685 - Do not fail with an assert when accept() returns an unexpected
6686 address family. Addresses but does not wholly fix bug 483. (Bugfix
6688 - Let directory authorities startup even when they can't generate
6689 a descriptor immediately, e.g. because they don't know their
6691 - Stop putting the authentication cookie in a file called "0"
6692 in your working directory if you don't specify anything for the
6693 new CookieAuthFile option. Reported by Matt Edman.
6694 - Make it possible to read the PROTOCOLINFO response in a way that
6695 conforms to our control-spec. Reported by Matt Edman.
6696 - Fix a minor memory leak when we fail to find enough suitable
6697 servers to choose a circuit. Bugfix on 0.1.2.x.
6698 - Stop leaking part of the descriptor when we run into a particularly
6699 unparseable piece of it. Bugfix on 0.1.2.x.
6700 - Unmap the extrainfo cache file on exit.
6703 Changes in version 0.2.0.5-alpha - 2007-08-19
6704 This fifth development snapshot fixes compilation on Windows again;
6705 fixes an obnoxious client-side bug that slowed things down and put
6706 extra load on the network; gets us closer to using the v3 directory
6707 voting scheme; makes it easier for Tor controllers to use cookie-based
6708 authentication; and fixes a variety of other bugs.
6711 - Version 1 directories are no longer generated in full. Instead,
6712 authorities generate and serve "stub" v1 directories that list
6713 no servers. This will stop Tor versions 0.1.0.x and earlier from
6714 working, but (for security reasons) nobody should be running those
6717 o Major bugfixes (compilation, 0.2.0.x):
6718 - Try to fix Win32 compilation again: improve checking for IPv6 types.
6719 - Try to fix MSVC compilation: build correctly on platforms that do
6720 not define s6_addr16 or s6_addr32.
6721 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
6724 o Major bugfixes (stream expiration):
6725 - Expire not-yet-successful application streams in all cases if
6726 they've been around longer than SocksTimeout. Right now there are
6727 some cases where the stream will live forever, demanding a new
6728 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
6731 o Minor features (directory servers):
6732 - When somebody requests a list of statuses or servers, and we have
6733 none of those, return a 404 rather than an empty 200.
6735 o Minor features (directory voting):
6736 - Store v3 consensus status consensuses on disk, and reload them
6739 o Minor features (security):
6740 - Warn about unsafe ControlPort configurations.
6741 - Refuse to start with certain directory authority keys, and
6742 encourage people using them to stop.
6744 o Minor features (controller):
6745 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6746 is valid before any authentication has been received. It tells
6747 a controller what kind of authentication is expected, and what
6748 protocol is spoken. Implements proposal 119.
6749 - New config option CookieAuthFile to choose a new location for the
6750 cookie authentication file, and config option
6751 CookieAuthFileGroupReadable to make it group-readable.
6753 o Minor features (unit testing):
6754 - Add command-line arguments to unit-test executable so that we can
6755 invoke any chosen test from the command line rather than having
6756 to run the whole test suite at once; and so that we can turn on
6757 logging for the unit tests.
6759 o Minor bugfixes (on 0.1.2.x):
6760 - If we require CookieAuthentication but we fail to write the
6761 cookie file, we would warn but not exit, and end up in a state
6762 where no controller could authenticate. Now we exit.
6763 - If we require CookieAuthentication, stop generating a new cookie
6764 every time we change any piece of our config.
6765 - When loading bandwidth history, do not believe any information in
6766 the future. Fixes bug 434.
6767 - When loading entry guard information, do not believe any information
6769 - When we have our clock set far in the future and generate an
6770 onion key, then re-set our clock to be correct, we should not stop
6771 the onion key from getting rotated.
6772 - Clean up torrc sample config file.
6773 - Do not automatically run configure from autogen.sh. This
6774 non-standard behavior tended to annoy people who have built other
6777 o Minor bugfixes (on 0.2.0.x):
6778 - Fix a bug with AutomapHostsOnResolve that would always cause
6779 the second request to fail. Bug reported by Kate. Bugfix on
6781 - Fix a bug in ADDRMAP controller replies that would sometimes
6782 try to print a NULL. Patch from tup.
6783 - Read v3 directory authority keys from the right location.
6784 - Numerous bugfixes to directory voting code.
6787 Changes in version 0.1.2.16 - 2007-08-01
6788 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
6789 remote attacker in certain situations to rewrite the user's torrc
6790 configuration file. This can completely compromise anonymity of users
6791 in most configurations, including those running the Vidalia bundles,
6792 TorK, etc. Or worse.
6794 o Major security fixes:
6795 - Close immediately after missing authentication on control port;
6796 do not allow multiple authentication attempts.
6799 Changes in version 0.2.0.4-alpha - 2007-08-01
6800 This fourth development snapshot fixes a critical security vulnerability
6801 for most users, specifically those running Vidalia, TorK, etc. Everybody
6802 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
6804 o Major security fixes:
6805 - Close immediately after missing authentication on control port;
6806 do not allow multiple authentication attempts.
6808 o Major bugfixes (compilation):
6809 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
6812 o Minor features (performance):
6813 - Be even more aggressive about releasing RAM from small
6814 empty buffers. Thanks to our free-list code, this shouldn't be too
6815 performance-intensive.
6816 - Disable sentinel-based debugging for buffer code: we squashed all
6817 the bugs that this was supposed to detect a long time ago, and
6818 now its only effect is to change our buffer sizes from nice
6819 powers of two (which platform mallocs tend to like) to values
6820 slightly over powers of two (which make some platform mallocs sad).
6821 - Log malloc statistics from mallinfo() on platforms where it
6825 Changes in version 0.2.0.3-alpha - 2007-07-29
6826 This third development snapshot introduces new experimental
6827 blocking-resistance features and a preliminary version of the v3
6828 directory voting design, and includes many other smaller features
6832 - The first pieces of our "bridge" design for blocking-resistance
6833 are implemented. People can run bridge directory authorities;
6834 people can run bridges; and people can configure their Tor clients
6835 with a set of bridges to use as the first hop into the Tor network.
6836 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
6838 - Create listener connections before we setuid to the configured
6839 User and Group. Now non-Windows users can choose port values
6840 under 1024, start Tor as root, and have Tor bind those ports
6841 before it changes to another UID. (Windows users could already
6843 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
6844 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
6845 on "vserver" accounts. (Patch from coderman.)
6846 - Be even more aggressive about separating local traffic from relayed
6847 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
6849 o Major features (experimental):
6850 - First cut of code for "v3 dir voting": directory authorities will
6851 vote on a common network status document rather than each publishing
6852 their own opinion. This code needs more testing and more corner-case
6853 handling before it's ready for use.
6856 - Directory authorities now call routers Fast if their bandwidth is
6857 at least 100KB/s, and consider their bandwidth adequate to be a
6858 Guard if it is at least 250KB/s, no matter the medians. This fix
6859 complements proposal 107. [Bugfix on 0.1.2.x]
6860 - Directory authorities now never mark more than 3 servers per IP as
6861 Valid and Running. (Implements proposal 109, by Kevin Bauer and
6863 - Minor change to organizationName and commonName generation
6864 procedures in TLS certificates during Tor handshakes, to invalidate
6865 some earlier censorware approaches. This is not a long-term
6866 solution, but applying it will give us a bit of time to look into
6867 the epidemiology of countermeasures as they spread.
6869 o Major bugfixes (directory):
6870 - Rewrite directory tokenization code to never run off the end of
6871 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
6873 o Minor features (controller):
6874 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
6875 match requests to applications. (Patch from Robert Hogan.)
6876 - Report address and port correctly on connections to DNSPort. (Patch
6878 - Add a RESOLVE command to launch hostname lookups. (Original patch
6880 - Add GETINFO status/enough-dir-info to let controllers tell whether
6881 Tor has downloaded sufficient directory information. (Patch
6883 - You can now use the ControlSocket option to tell Tor to listen for
6884 controller connections on Unix domain sockets on systems that
6885 support them. (Patch from Peter Palfrader.)
6886 - STREAM NEW events are generated for DNSPort requests and for
6887 tunneled directory connections. (Patch from Robert Hogan.)
6888 - New "GETINFO address-mappings/*" command to get address mappings
6889 with expiry information. "addr-mappings/*" is now deprecated.
6892 o Minor features (misc):
6893 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
6895 - The tor-gencert tool for v3 directory authorities now creates all
6896 files as readable to the file creator only, and write-protects
6897 the authority identity key.
6898 - When dumping memory usage, list bytes used in buffer memory
6900 - When running with dmalloc, dump more stats on hup and on exit.
6901 - Directory authorities now fail quickly and (relatively) harmlessly
6902 if they generate a network status document that is somehow
6905 o Traffic load balancing improvements:
6906 - If exit bandwidth ever exceeds one third of total bandwidth, then
6907 use the correct formula to weight exit nodes when choosing paths.
6908 (Based on patch from Mike Perry.)
6909 - Choose perfectly fairly among routers when choosing by bandwidth and
6910 weighting by fraction of bandwidth provided by exits. Previously, we
6911 would choose with only approximate fairness, and correct ourselves
6912 if we ran off the end of the list. [Bugfix on 0.1.2.x]
6914 o Performance improvements:
6915 - Be more aggressive with freeing buffer RAM or putting it on the
6917 - Use Critical Sections rather than Mutexes for synchronizing threads
6918 on win32; Mutexes are heavier-weight, and designed for synchronizing
6921 o Deprecated and removed features:
6922 - RedirectExits is now deprecated.
6923 - Stop allowing address masks that do not correspond to bit prefixes.
6924 We have warned about these for a really long time; now it's time
6925 to reject them. (Patch from croup.)
6927 o Minor bugfixes (directory):
6928 - Fix another crash bug related to extra-info caching. (Bug found by
6929 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
6930 - Directories no longer return a "304 not modified" when they don't
6931 have the networkstatus the client asked for. Also fix a memory
6932 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
6933 - We had accidentally labelled 0.1.2.x directory servers as not
6934 suitable for begin_dir requests, and had labelled no directory
6935 servers as suitable for uploading extra-info documents. [Bugfix
6938 o Minor bugfixes (dns):
6939 - Fix a crash when DNSPort is set more than once. (Patch from Robert
6940 Hogan.) [Bugfix on 0.2.0.2-alpha]
6941 - Add DNSPort connections to the global connection list, so that we
6942 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
6944 - Fix a dangling reference that could lead to a crash when DNSPort is
6945 changed or closed (Patch from Robert Hogan.) [Bugfix on
6948 o Minor bugfixes (controller):
6949 - Provide DNS expiry times in GMT, not in local time. For backward
6950 compatibility, ADDRMAP events only provide GMT expiry in an extended
6951 field. "GETINFO address-mappings" always does the right thing.
6952 - Use CRLF line endings properly in NS events.
6953 - Terminate multi-line control events properly. (Original patch
6954 from tup.) [Bugfix on 0.1.2.x-alpha]
6955 - Do not include spaces in SOURCE_ADDR fields in STREAM
6956 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
6959 Changes in version 0.1.2.15 - 2007-07-17
6960 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
6961 problems, fixes compilation on BSD, and fixes a variety of other
6962 bugs. Everybody should upgrade.
6964 o Major bugfixes (compilation):
6965 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
6967 o Major bugfixes (crashes):
6968 - Try even harder not to dereference the first character after
6969 an mmap(). Reported by lodger.
6970 - Fix a crash bug in directory authorities when we re-number the
6971 routerlist while inserting a new router.
6972 - When the cached-routers file is an even multiple of the page size,
6973 don't run off the end and crash. (Fixes bug 455; based on idea
6975 - Fix eventdns.c behavior on Solaris: It is critical to include
6976 orconfig.h _before_ sys/types.h, so that we can get the expected
6977 definition of _FILE_OFFSET_BITS.
6979 o Major bugfixes (security):
6980 - Fix a possible buffer overrun when using BSD natd support. Bug
6982 - When sending destroy cells from a circuit's origin, don't include
6983 the reason for tearing down the circuit. The spec says we didn't,
6984 and now we actually don't. Reported by lodger.
6985 - Keep streamids from different exits on a circuit separate. This
6986 bug may have allowed other routers on a given circuit to inject
6987 cells into streams. Reported by lodger; fixes bug 446.
6988 - If there's a never-before-connected-to guard node in our list,
6989 never choose any guards past it. This way we don't expand our
6990 guard list unless we need to.
6992 o Minor bugfixes (guard nodes):
6993 - Weight guard selection by bandwidth, so that low-bandwidth nodes
6994 don't get overused as guards.
6996 o Minor bugfixes (directory):
6997 - Correctly count the number of authorities that recommend each
6998 version. Previously, we were under-counting by 1.
6999 - Fix a potential crash bug when we load many server descriptors at
7000 once and some of them make others of them obsolete. Fixes bug 458.
7002 o Minor bugfixes (hidden services):
7003 - Stop tearing down the whole circuit when the user asks for a
7004 connection to a port that the hidden service didn't configure.
7007 o Minor bugfixes (misc):
7008 - On Windows, we were preventing other processes from reading
7009 cached-routers while Tor was running. Reported by janbar.
7010 - Fix a possible (but very unlikely) bug in picking routers by
7011 bandwidth. Add a log message to confirm that it is in fact
7012 unlikely. Patch from lodger.
7013 - Backport a couple of memory leak fixes.
7014 - Backport miscellaneous cosmetic bugfixes.
7017 Changes in version 0.2.0.2-alpha - 2007-06-02
7018 o Major bugfixes on 0.2.0.1-alpha:
7019 - Fix an assertion failure related to servers without extra-info digests.
7020 Resolves bugs 441 and 442.
7022 o Minor features (directory):
7023 - Support "If-Modified-Since" when answering HTTP requests for
7024 directories, running-routers documents, and network-status documents.
7025 (There's no need to support it for router descriptors, since those
7026 are downloaded by descriptor digest.)
7028 o Minor build issues:
7029 - Clear up some MIPSPro compiler warnings.
7030 - When building from a tarball on a machine that happens to have SVK
7031 installed, report the micro-revision as whatever version existed
7032 in the tarball, not as "x".
7035 Changes in version 0.2.0.1-alpha - 2007-06-01
7036 This early development snapshot provides new features for people running
7037 Tor as both a client and a server (check out the new RelayBandwidth
7038 config options); lets Tor run as a DNS proxy; and generally moves us
7039 forward on a lot of fronts.
7041 o Major features, server usability:
7042 - New config options RelayBandwidthRate and RelayBandwidthBurst:
7043 a separate set of token buckets for relayed traffic. Right now
7044 relayed traffic is defined as answers to directory requests, and
7045 OR connections that don't have any local circuits on them.
7047 o Major features, client usability:
7048 - A client-side DNS proxy feature to replace the need for
7049 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
7050 for DNS requests on port 9999, use the Tor network to resolve them
7051 anonymously, and send the reply back like a regular DNS server.
7052 The code still only implements a subset of DNS.
7053 - Make PreferTunneledDirConns and TunnelDirConns work even when
7054 we have no cached directory info. This means Tor clients can now
7055 do all of their connections protected by TLS.
7057 o Major features, performance and efficiency:
7058 - Directory authorities accept and serve "extra info" documents for
7059 routers. These documents contain fields from router descriptors
7060 that aren't usually needed, and that use a lot of excess
7061 bandwidth. Once these fields are removed from router descriptors,
7062 the bandwidth savings should be about 60%. [Partially implements
7064 - Servers upload extra-info documents to any authority that accepts
7065 them. Authorities (and caches that have been configured to download
7066 extra-info documents) download them as needed. [Partially implements
7068 - Change the way that Tor buffers data that it is waiting to write.
7069 Instead of queueing data cells in an enormous ring buffer for each
7070 client->OR or OR->OR connection, we now queue cells on a separate
7071 queue for each circuit. This lets us use less slack memory, and
7072 will eventually let us be smarter about prioritizing different kinds
7074 - Use memory pools to allocate cells with better speed and memory
7075 efficiency, especially on platforms where malloc() is inefficient.
7076 - Stop reading on edge connections when their corresponding circuit
7077 buffers are full; start again as the circuits empty out.
7079 o Major features, other:
7080 - Add an HSAuthorityRecordStats option that hidden service authorities
7081 can use to track statistics of overall hidden service usage without
7082 logging information that would be very useful to an attacker.
7083 - Start work implementing multi-level keys for directory authorities:
7084 Add a standalone tool to generate key certificates. (Proposal 103.)
7087 - Directory authorities now call routers Stable if they have an
7088 uptime of at least 30 days, even if that's not the median uptime
7089 in the network. Implements proposal 107, suggested by Kevin Bauer
7092 o Minor fixes (resource management):
7093 - Count the number of open sockets separately from the number
7094 of active connection_t objects. This will let us avoid underusing
7095 our allocated connection limit.
7096 - We no longer use socket pairs to link an edge connection to an
7097 anonymous directory connection or a DirPort test connection.
7098 Instead, we track the link internally and transfer the data
7099 in-process. This saves two sockets per "linked" connection (at the
7100 client and at the server), and avoids the nasty Windows socketpair()
7102 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
7103 for every single inactive connection_t. Free items from the
7104 4k/16k-buffer free lists when they haven't been used for a while.
7106 o Minor features (build):
7107 - Make autoconf search for libevent, openssl, and zlib consistently.
7108 - Update deprecated macros in configure.in.
7109 - When warning about missing headers, tell the user to let us
7110 know if the compile succeeds anyway, so we can downgrade the
7112 - Include the current subversion revision as part of the version
7113 string: either fetch it directly if we're in an SVN checkout, do
7114 some magic to guess it if we're in an SVK checkout, or use
7115 the last-detected version if we're building from a .tar.gz.
7116 Use this version consistently in log messages.
7118 o Minor features (logging):
7119 - Always prepend "Bug: " to any log message about a bug.
7120 - Put a platform string (e.g. "Linux i686") in the startup log
7121 message, so when people paste just their logs, we know if it's
7122 OpenBSD or Windows or what.
7123 - When logging memory usage, break down memory used in buffers by
7126 o Minor features (directory system):
7127 - New config option V2AuthoritativeDirectory that all directory
7128 authorities should set. This will let future authorities choose
7129 not to serve V2 directory information.
7130 - Directory authorities allow multiple router descriptors and/or extra
7131 info documents to be uploaded in a single go. This will make
7132 implementing proposal 104 simpler.
7134 o Minor features (controller):
7135 - Add a new config option __DisablePredictedCircuits designed for
7136 use by the controller, when we don't want Tor to build any circuits
7138 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
7139 so we can exit from the middle of the circuit.
7140 - Implement "getinfo status/circuit-established".
7141 - Implement "getinfo status/version/..." so a controller can tell
7142 whether the current version is recommended, and whether any versions
7143 are good, and how many authorities agree. (Patch from shibz.)
7145 o Minor features (hidden services):
7146 - Allow multiple HiddenServicePort directives with the same virtual
7147 port; when they occur, the user is sent round-robin to one
7148 of the target ports chosen at random. Partially fixes bug 393 by
7149 adding limited ad-hoc round-robining.
7151 o Minor features (other):
7153 - Add a new AutomapHostsOnResolve option: when it is enabled, any
7154 resolve request for hosts matching a given pattern causes Tor to
7155 generate an internal virtual address mapping for that host. This
7156 allows DNSPort to work sensibly with hidden service users. By
7157 default, .exit and .onion addresses are remapped; the list of
7158 patterns can be reconfigured with AutomapHostsSuffixes.
7159 - Add an "-F" option to tor-resolve to force a resolve for a .onion
7160 address. Thanks to the AutomapHostsOnResolve option, this is no
7161 longer a completely silly thing to do.
7162 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
7163 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
7164 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
7165 minus 1 byte: the actual maximum declared bandwidth.
7168 - Removed support for the old binary "version 0" controller protocol.
7169 This has been deprecated since 0.1.1, and warnings have been issued
7170 since 0.1.2. When we encounter a v0 control message, we now send
7171 back an error and close the connection.
7172 - Remove the old "dns worker" server DNS code: it hasn't been default
7173 since 0.1.2.2-alpha, and all the servers seem to be using the new
7176 o Minor bugfixes (portability):
7177 - Even though Windows is equally happy with / and \ as path separators,
7178 try to use \ consistently on Windows and / consistently on Unix: it
7179 makes the log messages nicer.
7180 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
7181 - Read resolv.conf files correctly on platforms where read() returns
7182 partial results on small file reads.
7184 o Minor bugfixes (directory):
7185 - Correctly enforce that elements of directory objects do not appear
7186 more often than they are allowed to appear.
7187 - When we are reporting the DirServer line we just parsed, we were
7188 logging the second stanza of the key fingerprint, not the first.
7190 o Minor bugfixes (logging):
7191 - When we hit an EOF on a log (probably because we're shutting down),
7192 don't try to remove the log from the list: just mark it as
7193 unusable. (Bulletproofs against bug 222.)
7195 o Minor bugfixes (other):
7196 - In the exitlist script, only consider the most recently published
7197 server descriptor for each server. Also, when the user requests
7198 a list of servers that _reject_ connections to a given address,
7199 explicitly exclude the IPs that also have servers that accept
7200 connections to that address. (Resolves bug 405.)
7201 - Stop allowing hibernating servers to be "stable" or "fast".
7202 - On Windows, we were preventing other processes from reading
7203 cached-routers while Tor was running. (Reported by janbar)
7204 - Make the NodeFamilies config option work. (Reported by
7205 lodger -- it has never actually worked, even though we added it
7207 - Check return values from pthread_mutex functions.
7208 - Don't save non-general-purpose router descriptors to the disk cache,
7209 because we have no way of remembering what their purpose was when
7211 - Add even more asserts to hunt down bug 417.
7212 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
7213 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
7214 Add a log message to confirm that it is in fact unlikely.
7216 o Minor bugfixes (controller):
7217 - Make 'getinfo fingerprint' return a 551 error if we're not a
7218 server, so we match what the control spec claims we do. Reported
7220 - Fix a typo in an error message when extendcircuit fails that
7221 caused us to not follow the \r\n-based delimiter protocol. Reported
7224 o Code simplifications and refactoring:
7225 - Stop passing around circuit_t and crypt_path_t pointers that are
7226 implicit in other procedure arguments.
7227 - Drop the old code to choke directory connections when the
7228 corresponding OR connections got full: thanks to the cell queue
7229 feature, OR conns don't get full any more.
7230 - Make dns_resolve() handle attaching connections to circuits
7231 properly, so the caller doesn't have to.
7232 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
7233 - Keep the connection array as a dynamic smartlist_t, rather than as
7234 a fixed-sized array. This is important, as the number of connections
7235 is becoming increasingly decoupled from the number of sockets.
7238 Changes in version 0.1.2.14 - 2007-05-25
7239 Tor 0.1.2.14 changes the addresses of two directory authorities (this
7240 change especially affects those who serve or use hidden services),
7241 and fixes several other crash- and security-related bugs.
7243 o Directory authority changes:
7244 - Two directory authorities (moria1 and moria2) just moved to new
7245 IP addresses. This change will particularly affect those who serve
7246 or use hidden services.
7248 o Major bugfixes (crashes):
7249 - If a directory server runs out of space in the connection table
7250 as it's processing a begin_dir request, it will free the exit stream
7251 but leave it attached to the circuit, leading to unpredictable
7252 behavior. (Reported by seeess, fixes bug 425.)
7253 - Fix a bug in dirserv_remove_invalid() that would cause authorities
7254 to corrupt memory under some really unlikely scenarios.
7255 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
7256 - Avoid segfaults when reading from mmaped descriptor file. (Reported
7259 o Major bugfixes (security):
7260 - When choosing an entry guard for a circuit, avoid using guards
7261 that are in the same family as the chosen exit -- not just guards
7262 that are exactly the chosen exit. (Reported by lodger.)
7264 o Major bugfixes (resource management):
7265 - If a directory authority is down, skip it when deciding where to get
7266 networkstatus objects or descriptors. Otherwise we keep asking
7267 every 10 seconds forever. Fixes bug 384.
7268 - Count it as a failure if we fetch a valid network-status but we
7269 don't want to keep it. Otherwise we'll keep fetching it and keep
7270 not wanting to keep it. Fixes part of bug 422.
7271 - If all of our dirservers have given us bad or no networkstatuses
7272 lately, then stop hammering them once per minute even when we
7273 think they're failed. Fixes another part of bug 422.
7276 - Actually set the purpose correctly for descriptors inserted with
7278 - When we have k non-v2 authorities in our DirServer config,
7279 we ignored the last k authorities in the list when updating our
7281 - Correctly back-off from requesting router descriptors that we are
7282 having a hard time downloading.
7283 - Read resolv.conf files correctly on platforms where read() returns
7284 partial results on small file reads.
7285 - Don't rebuild the entire router store every time we get 32K of
7286 routers: rebuild it when the journal gets very large, or when
7287 the gaps in the store get very large.
7290 - When routers publish SVN revisions in their router descriptors,
7291 authorities now include those versions correctly in networkstatus
7293 - Warn when using a version of libevent before 1.3b to run a server on
7294 OSX or BSD: these versions interact badly with userspace threads.
7297 Changes in version 0.1.2.13 - 2007-04-24
7298 This release features some major anonymity fixes, such as safer path
7299 selection; better client performance; faster bootstrapping, better
7300 address detection, and better DNS support for servers; write limiting as
7301 well as read limiting to make servers easier to run; and a huge pile of
7302 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
7304 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
7305 of the Freenode IRC network, remembering his patience and vision for
7306 free speech on the Internet.
7309 - Fix a memory leak when we ask for "all" networkstatuses and we
7310 get one we don't recognize.
7311 - Add more asserts to hunt down bug 417.
7312 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
7315 Changes in version 0.1.2.12-rc - 2007-03-16
7317 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
7318 directory information requested inside Tor connections (i.e. via
7319 begin_dir cells). It only triggered when the same connection was
7320 serving other data at the same time. Reported by seeess.
7323 - When creating a circuit via the controller, send a 'launched'
7324 event when we're done, so we follow the spec better.
7327 Changes in version 0.1.2.11-rc - 2007-03-15
7328 o Minor bugfixes (controller), reported by daejees:
7329 - Correct the control spec to match how the code actually responds
7330 to 'getinfo addr-mappings/*'.
7331 - The control spec described a GUARDS event, but the code
7332 implemented a GUARD event. Standardize on GUARD, but let people
7336 Changes in version 0.1.2.10-rc - 2007-03-07
7337 o Major bugfixes (Windows):
7338 - Do not load the NT services library functions (which may not exist)
7339 just to detect if we're a service trying to shut down. Now we run
7340 on Win98 and friends again.
7342 o Minor bugfixes (other):
7343 - Clarify a couple of log messages.
7344 - Fix a misleading socks5 error number.
7347 Changes in version 0.1.2.9-rc - 2007-03-02
7348 o Major bugfixes (Windows):
7349 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
7350 of the usual GCC "%llu". This prevents a bug when saving 64-bit
7351 int configuration values: the high-order 32 bits would get
7352 truncated. In particular, we were being bitten by the default
7353 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
7354 and maybe also bug 397.)
7356 o Minor bugfixes (performance):
7357 - Use OpenSSL's AES implementation on platforms where it's faster.
7358 This could save us as much as 10% CPU usage.
7360 o Minor bugfixes (server):
7361 - Do not rotate onion key immediately after setting it for the first
7364 o Minor bugfixes (directory authorities):
7365 - Stop calling servers that have been hibernating for a long time
7366 "stable". Also, stop letting hibernating or obsolete servers affect
7367 uptime and bandwidth cutoffs.
7368 - Stop listing hibernating servers in the v1 directory.
7370 o Minor bugfixes (hidden services):
7371 - Upload hidden service descriptors slightly less often, to reduce
7372 load on authorities.
7374 o Minor bugfixes (other):
7375 - Fix an assert that could trigger if a controller quickly set then
7376 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
7377 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
7379 - Fix a potential race condition in the rpm installer. Found by
7381 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
7382 of 2 as indicating that the server is completely bad; it sometimes
7383 means that the server is just bad for the request in question. (may fix
7384 the last of bug 326.)
7385 - Disable encrypted directory connections when we don't have a server
7386 descriptor for the destination. We'll get this working again in
7390 Changes in version 0.1.2.8-beta - 2007-02-26
7391 o Major bugfixes (crashes):
7392 - Stop crashing when the controller asks us to resetconf more than
7393 one config option at once. (Vidalia 0.0.11 does this.)
7394 - Fix a crash that happened on Win98 when we're given command-line
7395 arguments: don't try to load NT service functions from advapi32.dll
7396 except when we need them. (Bug introduced in 0.1.2.7-alpha;
7398 - Fix a longstanding obscure crash bug that could occur when
7399 we run out of DNS worker processes. (Resolves bug 390.)
7401 o Major bugfixes (hidden services):
7402 - Correctly detect whether hidden service descriptor downloads are
7403 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
7405 o Major bugfixes (accounting):
7406 - When we start during an accounting interval before it's time to wake
7407 up, remember to wake up at the correct time. (May fix bug 342.)
7409 o Minor bugfixes (controller):
7410 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
7411 clear the corresponding on_circuit variable, and remember later
7412 that we don't need to send a redundant CLOSED event. (Resolves part
7414 - Report events where a resolve succeeded or where we got a socks
7415 protocol error correctly, rather than calling both of them
7417 - Change reported stream target addresses to IP consistently when
7418 we finally get the IP from an exit node.
7419 - Send log messages to the controller even if they happen to be very
7422 o Minor bugfixes (other):
7423 - Display correct results when reporting which versions are
7424 recommended, and how recommended they are. (Resolves bug 383.)
7425 - Improve our estimates for directory bandwidth to be less random:
7426 guess that an unrecognized directory will have the average bandwidth
7427 from all known directories, not that it will have the average
7428 bandwidth from those directories earlier than it on the list.
7429 - If we start a server with ClientOnly 1, then set ClientOnly to 0
7430 and hup, stop triggering an assert based on an empty onion_key.
7431 - On platforms with no working mmap() equivalent, don't warn the
7432 user when cached-routers doesn't exist.
7433 - Warn the user when mmap() [or its equivalent] fails for some reason
7434 other than file-not-found.
7435 - Don't warn the user when cached-routers.new doesn't exist: that's
7436 perfectly fine when starting up for the first time.
7437 - When EntryNodes are configured, rebuild the guard list to contain,
7438 in order: the EntryNodes that were guards before; the rest of the
7439 EntryNodes; the nodes that were guards before.
7440 - Mask out all signals in sub-threads; only the libevent signal
7441 handler should be processing them. This should prevent some crashes
7442 on some machines using pthreads. (Patch from coderman.)
7443 - Fix switched arguments on memset in the implementation of
7444 tor_munmap() for systems with no mmap() call.
7445 - When Tor receives a router descriptor that it asked for, but
7446 no longer wants (because it has received fresh networkstatuses
7447 in the meantime), do not warn the user. Cache the descriptor if
7448 we're a cache; drop it if we aren't.
7449 - Make earlier entry guards _really_ get retried when the network
7451 - On a malformed DNS reply, always give an error to the corresponding
7453 - Build with recent libevents on platforms that do not define the
7454 nonstandard types "u_int8_t" and friends.
7456 o Minor features (controller):
7457 - Warn the user when an application uses the obsolete binary v0
7458 control protocol. We're planning to remove support for it during
7459 the next development series, so it's good to give people some
7461 - Add STREAM_BW events to report per-entry-stream bandwidth
7462 use. (Patch from Robert Hogan.)
7463 - Rate-limit SIGNEWNYM signals in response to controllers that
7464 impolitely generate them for every single stream. (Patch from
7465 mwenge; closes bug 394.)
7466 - Make REMAP stream events have a SOURCE (cache or exit), and
7467 make them generated in every case where we get a successful
7468 connected or resolved cell.
7470 o Minor bugfixes (performance):
7471 - Call router_have_min_dir_info half as often. (This is showing up in
7472 some profiles, but not others.)
7473 - When using GCC, make log_debug never get called at all, and its
7474 arguments never get evaluated, when no debug logs are configured.
7475 (This is showing up in some profiles, but not others.)
7478 - Remove some never-implemented options. Mark PathlenCoinWeight as
7480 - Implement proposal 106: Stop requiring clients to have well-formed
7481 certificates; stop checking nicknames in certificates. (Clients
7482 have certificates so that they can look like Tor servers, but in
7483 the future we might want to allow them to look like regular TLS
7484 clients instead. Nicknames in certificates serve no purpose other
7485 than making our protocol easier to recognize on the wire.)
7486 - Revise messages on handshake failure again to be even more clear about
7487 which are incoming connections and which are outgoing.
7488 - Discard any v1 directory info that's over 1 month old (for
7489 directories) or over 1 week old (for running-routers lists).
7490 - Do not warn when individual nodes in the configuration's EntryNodes,
7491 ExitNodes, etc are down: warn only when all possible nodes
7492 are down. (Fixes bug 348.)
7493 - Always remove expired routers and networkstatus docs before checking
7494 whether we have enough information to build circuits. (Fixes
7496 - Put a lower-bound on MaxAdvertisedBandwidth.
7499 Changes in version 0.1.2.7-alpha - 2007-02-06
7500 o Major bugfixes (rate limiting):
7501 - Servers decline directory requests much more aggressively when
7502 they're low on bandwidth. Otherwise they end up queueing more and
7503 more directory responses, which can't be good for latency.
7504 - But never refuse directory requests from local addresses.
7505 - Fix a memory leak when sending a 503 response for a networkstatus
7507 - Be willing to read or write on local connections (e.g. controller
7508 connections) even when the global rate limiting buckets are empty.
7509 - If our system clock jumps back in time, don't publish a negative
7510 uptime in the descriptor. Also, don't let the global rate limiting
7511 buckets go absurdly negative.
7512 - Flush local controller connection buffers periodically as we're
7513 writing to them, so we avoid queueing 4+ megabytes of data before
7516 o Major bugfixes (NT services):
7517 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
7518 command-line flag so that admins can override the default by saying
7519 "tor --service install --user "SomeUser"". This will not affect
7520 existing installed services. Also, warn the user that the service
7521 will look for its configuration file in the service user's
7522 %appdata% directory. (We can't do the 'hardwire the user's appdata
7523 directory' trick any more, since we may not have read access to that
7526 o Major bugfixes (other):
7527 - Previously, we would cache up to 16 old networkstatus documents
7528 indefinitely, if they came from nontrusted authorities. Now we
7529 discard them if they are more than 10 days old.
7530 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
7532 - Detect and reject malformed DNS responses containing circular
7534 - If exits are rare enough that we're not marking exits as guards,
7535 ignore exit bandwidth when we're deciding the required bandwidth
7537 - When we're handling a directory connection tunneled over Tor,
7538 don't fill up internal memory buffers with all the data we want
7539 to tunnel; instead, only add it if the OR connection that will
7540 eventually receive it has some room for it. (This can lead to
7541 slowdowns in tunneled dir connections; a better solution will have
7544 o Minor bugfixes (dns):
7545 - Add some defensive programming to eventdns.c in an attempt to catch
7546 possible memory-stomping bugs.
7547 - Detect and reject DNS replies containing IPv4 or IPv6 records with
7548 an incorrect number of bytes. (Previously, we would ignore the
7550 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
7551 in the correct order, and doesn't crash.
7552 - Free memory held in recently-completed DNS lookup attempts on exit.
7553 This was not a memory leak, but may have been hiding memory leaks.
7554 - Handle TTL values correctly on reverse DNS lookups.
7555 - Treat failure to parse resolv.conf as an error.
7557 o Minor bugfixes (other):
7558 - Fix crash with "tor --list-fingerprint" (reported by seeess).
7559 - When computing clock skew from directory HTTP headers, consider what
7560 time it was when we finished asking for the directory, not what
7562 - Expire socks connections if they spend too long waiting for the
7563 handshake to finish. Previously we would let them sit around for
7564 days, if the connecting application didn't close them either.
7565 - And if the socks handshake hasn't started, don't send a
7566 "DNS resolve socks failed" handshake reply; just close it.
7567 - Stop using C functions that OpenBSD's linker doesn't like.
7568 - Don't launch requests for descriptors unless we have networkstatuses
7569 from at least half of the authorities. This delays the first
7570 download slightly under pathological circumstances, but can prevent
7571 us from downloading a bunch of descriptors we don't need.
7572 - Do not log IPs with TLS failures for incoming TLS
7573 connections. (Fixes bug 382.)
7574 - If the user asks to use invalid exit nodes, be willing to use
7576 - Stop using the reserved ac_cv namespace in our configure script.
7577 - Call stat() slightly less often; use fstat() when possible.
7578 - Refactor the way we handle pending circuits when an OR connection
7579 completes or fails, in an attempt to fix a rare crash bug.
7580 - Only rewrite a conn's address based on X-Forwarded-For: headers
7581 if it's a parseable public IP address; and stop adding extra quotes
7582 to the resulting address.
7585 - Weight directory requests by advertised bandwidth. Now we can
7586 let servers enable write limiting but still allow most clients to
7587 succeed at their directory requests. (We still ignore weights when
7588 choosing a directory authority; I hope this is a feature.)
7591 - Create a new file ReleaseNotes which was the old ChangeLog. The
7592 new ChangeLog file now includes the summaries for all development
7594 - Check for addresses with invalid characters at the exit as well
7595 as at the client, and warn less verbosely when they fail. You can
7596 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
7597 - Adapt a patch from goodell to let the contrib/exitlist script
7598 take arguments rather than require direct editing.
7599 - Inform the server operator when we decide not to advertise a
7600 DirPort due to AccountingMax enabled or a low BandwidthRate. It
7601 was confusing Zax, so now we're hopefully more helpful.
7602 - Bring us one step closer to being able to establish an encrypted
7603 directory tunnel without knowing a descriptor first. Still not
7604 ready yet. As part of the change, now assume we can use a
7605 create_fast cell if we don't know anything about a router.
7606 - Allow exit nodes to use nameservers running on ports other than 53.
7607 - Servers now cache reverse DNS replies.
7608 - Add an --ignore-missing-torrc command-line option so that we can
7609 get the "use sensible defaults if the configuration file doesn't
7610 exist" behavior even when specifying a torrc location on the command
7613 o Minor features (controller):
7614 - Track reasons for OR connection failure; make these reasons
7615 available via the controller interface. (Patch from Mike Perry.)
7616 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
7617 can learn when clients are sending malformed hostnames to Tor.
7618 - Clean up documentation for controller status events.
7619 - Add a REMAP status to stream events to note that a stream's
7620 address has changed because of a cached address or a MapAddress
7624 Changes in version 0.1.2.6-alpha - 2007-01-09
7626 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
7627 connection handles more than 4 gigs in either direction, we crash.
7628 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
7629 advertised exit node, somebody might try to exit from us when
7630 we're bootstrapping and before we've built our descriptor yet.
7631 Refuse the connection rather than crashing.
7634 - Warn if we (as a server) find that we've resolved an address that we
7635 weren't planning to resolve.
7636 - Warn that using select() on any libevent version before 1.1 will be
7637 unnecessarily slow (even for select()).
7638 - Flush ERR-level controller status events just like we currently
7639 flush ERR-level log events, so that a Tor shutdown doesn't prevent
7640 the controller from learning about current events.
7642 o Minor features (more controller status events):
7643 - Implement EXTERNAL_ADDRESS server status event so controllers can
7644 learn when our address changes.
7645 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
7646 can learn when directories reject our descriptor.
7647 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
7648 can learn when a client application is speaking a non-socks protocol
7650 - Implement DANGEROUS_SOCKS client status event so controllers
7651 can learn when a client application is leaking DNS addresses.
7652 - Implement BUG general status event so controllers can learn when
7653 Tor is unhappy about its internal invariants.
7654 - Implement CLOCK_SKEW general status event so controllers can learn
7655 when Tor thinks the system clock is set incorrectly.
7656 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
7657 server status events so controllers can learn when their descriptors
7658 are accepted by a directory.
7659 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
7660 server status events so controllers can learn about Tor's progress in
7661 deciding whether it's reachable from the outside.
7662 - Implement BAD_LIBEVENT general status event so controllers can learn
7663 when we have a version/method combination in libevent that needs to
7665 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
7666 and DNS_USELESS server status events so controllers can learn
7667 about changes to DNS server status.
7669 o Minor features (directory):
7670 - Authorities no longer recommend exits as guards if this would shift
7671 too much load to the exit nodes.
7674 Changes in version 0.1.2.5-alpha - 2007-01-06
7676 - Enable write limiting as well as read limiting. Now we sacrifice
7677 capacity if we're pushing out lots of directory traffic, rather
7678 than overrunning the user's intended bandwidth limits.
7679 - Include TLS overhead when counting bandwidth usage; previously, we
7680 would count only the bytes sent over TLS, but not the bytes used
7682 - Support running the Tor service with a torrc not in the same
7683 directory as tor.exe and default to using the torrc located in
7684 the %appdata%\Tor\ of the user who installed the service. Patch
7686 - Servers now check for the case when common DNS requests are going to
7687 wildcarded addresses (i.e. all getting the same answer), and change
7688 their exit policy to reject *:* if it's happening.
7689 - Implement BEGIN_DIR cells, so we can connect to the directory
7690 server via TLS to do encrypted directory requests rather than
7691 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
7692 config options if you like.
7694 o Minor features (config and docs):
7695 - Start using the state file to store bandwidth accounting data:
7696 the bw_accounting file is now obsolete. We'll keep generating it
7697 for a while for people who are still using 0.1.2.4-alpha.
7698 - Try to batch changes to the state file so that we do as few
7699 disk writes as possible while still storing important things in
7701 - The state file and the bw_accounting file get saved less often when
7702 the AvoidDiskWrites config option is set.
7703 - Make PIDFile work on Windows (untested).
7704 - Add internal descriptions for a bunch of configuration options:
7705 accessible via controller interface and in comments in saved
7707 - Reject *:563 (NNTPS) in the default exit policy. We already reject
7708 NNTP by default, so this seems like a sensible addition.
7709 - Clients now reject hostnames with invalid characters. This should
7710 avoid some inadvertent info leaks. Add an option
7711 AllowNonRFC953Hostnames to disable this behavior, in case somebody
7712 is running a private network with hosts called @, !, and #.
7713 - Add a maintainer script to tell us which options are missing
7714 documentation: "make check-docs".
7715 - Add a new address-spec.txt document to describe our special-case
7716 addresses: .exit, .onion, and .noconnnect.
7718 o Minor features (DNS):
7719 - Ongoing work on eventdns infrastructure: now it has dns server
7720 and ipv6 support. One day Tor will make use of it.
7721 - Add client-side caching for reverse DNS lookups.
7722 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
7723 - When we change nameservers or IP addresses, reset and re-launch
7724 our tests for DNS hijacking.
7726 o Minor features (directory):
7727 - Authorities now specify server versions in networkstatus. This adds
7728 about 2% to the size of compressed networkstatus docs, and allows
7729 clients to tell which servers support BEGIN_DIR and which don't.
7730 The implementation is forward-compatible with a proposed future
7731 protocol version scheme not tied to Tor versions.
7732 - DirServer configuration lines now have an orport= option so
7733 clients can open encrypted tunnels to the authorities without
7734 having downloaded their descriptors yet. Enabled for moria1,
7735 moria2, tor26, and lefkada now in the default configuration.
7736 - Directory servers are more willing to send a 503 "busy" if they
7737 are near their write limit, especially for v1 directory requests.
7738 Now they can use their limited bandwidth for actual Tor traffic.
7739 - Clients track responses with status 503 from dirservers. After a
7740 dirserver has given us a 503, we try not to use it until an hour has
7741 gone by, or until we have no dirservers that haven't given us a 503.
7742 - When we get a 503 from a directory, and we're not a server, we don't
7743 count the failure against the total number of failures allowed
7744 for the thing we're trying to download.
7745 - Report X-Your-Address-Is correctly from tunneled directory
7746 connections; don't report X-Your-Address-Is when it's an internal
7747 address; and never believe reported remote addresses when they're
7749 - Protect against an unlikely DoS attack on directory servers.
7750 - Add a BadDirectory flag to network status docs so that authorities
7751 can (eventually) tell clients about caches they believe to be
7754 o Minor features (controller):
7755 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
7756 - Reimplement GETINFO so that info/names stays in sync with the
7758 - Implement "GETINFO fingerprint".
7759 - Implement "SETEVENTS GUARD" so controllers can get updates on
7760 entry guard status as it changes.
7762 o Minor features (clean up obsolete pieces):
7763 - Remove some options that have been deprecated since at least
7764 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
7765 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
7767 - We no longer look for identity and onion keys in "identity.key" and
7768 "onion.key" -- these were replaced by secret_id_key and
7769 secret_onion_key in 0.0.8pre1.
7770 - We no longer require unrecognized directory entries to be
7773 o Major bugfixes (security):
7774 - Stop sending the HttpProxyAuthenticator string to directory
7775 servers when directory connections are tunnelled through Tor.
7776 - Clients no longer store bandwidth history in the state file.
7777 - Do not log introduction points for hidden services if SafeLogging
7779 - When generating bandwidth history, round down to the nearest
7780 1k. When storing accounting data, round up to the nearest 1k.
7781 - When we're running as a server, remember when we last rotated onion
7782 keys, so that we will rotate keys once they're a week old even if
7783 we never stay up for a week ourselves.
7785 o Major bugfixes (other):
7786 - Fix a longstanding bug in eventdns that prevented the count of
7787 timed-out resolves from ever being reset. This bug caused us to
7788 give up on a nameserver the third time it timed out, and try it
7789 10 seconds later... and to give up on it every time it timed out
7791 - Take out the '5 second' timeout from the connection retry
7792 schedule. Now the first connect attempt will wait a full 10
7793 seconds before switching to a new circuit. Perhaps this will help
7794 a lot. Based on observations from Mike Perry.
7795 - Fix a bug on the Windows implementation of tor_mmap_file() that
7796 would prevent the cached-routers file from ever loading. Reported
7800 - Fix an assert failure when a directory authority sets
7801 AuthDirRejectUnlisted and then receives a descriptor from an
7802 unlisted router. Reported by seeess.
7803 - Avoid a double-free when parsing malformed DirServer lines.
7804 - Fix a bug when a BSD-style PF socket is first used. Patch from
7806 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
7807 to resolve an address at a given exit node even when they ask for
7809 - Servers no longer ever list themselves in their "family" line,
7810 even if configured to do so. This makes it easier to configure
7811 family lists conveniently.
7812 - When running as a server, don't fall back to 127.0.0.1 when no
7813 nameservers are configured in /etc/resolv.conf; instead, make the
7814 user fix resolv.conf or specify nameservers explicitly. (Resolves
7816 - Stop accepting certain malformed ports in configured exit policies.
7817 - Don't re-write the fingerprint file every restart, unless it has
7819 - Stop warning when a single nameserver fails: only warn when _all_ of
7820 our nameservers have failed. Also, when we only have one nameserver,
7821 raise the threshold for deciding that the nameserver is dead.
7822 - Directory authorities now only decide that routers are reachable
7823 if their identity keys are as expected.
7824 - When the user uses bad syntax in the Log config line, stop
7825 suggesting other bad syntax as a replacement.
7826 - Correctly detect ipv6 DNS capability on OpenBSD.
7828 o Minor bugfixes (controller):
7829 - Report the circuit number correctly in STREAM CLOSED events. Bug
7830 reported by Mike Perry.
7831 - Do not report bizarre values for results of accounting GETINFOs
7832 when the last second's write or read exceeds the allotted bandwidth.
7833 - Report "unrecognized key" rather than an empty string when the
7834 controller tries to fetch a networkstatus that doesn't exist.
7837 Changes in version 0.1.1.26 - 2006-12-14
7838 o Security bugfixes:
7839 - Stop sending the HttpProxyAuthenticator string to directory
7840 servers when directory connections are tunnelled through Tor.
7841 - Clients no longer store bandwidth history in the state file.
7842 - Do not log introduction points for hidden services if SafeLogging
7846 - Fix an assert failure when a directory authority sets
7847 AuthDirRejectUnlisted and then receives a descriptor from an
7848 unlisted router (reported by seeess).
7851 Changes in version 0.1.2.4-alpha - 2006-12-03
7853 - Add support for using natd; this allows FreeBSDs earlier than
7854 5.1.2 to have ipfw send connections through Tor without using
7855 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
7858 - Make all connections to addresses of the form ".noconnect"
7859 immediately get closed. This lets application/controller combos
7860 successfully test whether they're talking to the same Tor by
7861 watching for STREAM events.
7862 - Make cross.sh cross-compilation script work even when autogen.sh
7863 hasn't been run. (Patch from Michael Mohr.)
7864 - Statistics dumped by -USR2 now include a breakdown of public key
7865 operations, for profiling.
7868 - Fix a major leak when directory authorities parse their
7869 approved-routers list, a minor memory leak when we fail to pick
7870 an exit node, and a few rare leaks on errors.
7871 - Handle TransPort connections even when the server sends data before
7872 the client sends data. Previously, the connection would just hang
7873 until the client sent data. (Patch from tup based on patch from
7875 - Avoid assert failure when our cached-routers file is empty on
7879 - Don't log spurious warnings when we see a circuit close reason we
7880 don't recognize; it's probably just from a newer version of Tor.
7881 - Have directory authorities allow larger amounts of drift in uptime
7882 without replacing the server descriptor: previously, a server that
7883 restarted every 30 minutes could have 48 "interesting" descriptors
7885 - Start linking to the Tor specification and Tor reference manual
7886 correctly in the Windows installer.
7887 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7888 Tor/Privoxy we also uninstall Vidalia.
7889 - Resume building on Irix64, and fix a lot of warnings from its
7891 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
7892 when we're running as a client.
7895 Changes in version 0.1.1.25 - 2006-11-04
7897 - When a client asks us to resolve (rather than connect to)
7898 an address, and we have a cached answer, give them the cached
7899 answer. Previously, we would give them no answer at all.
7900 - We were building exactly the wrong circuits when we predict
7901 hidden service requirements, meaning Tor would have to build all
7902 its circuits on demand.
7903 - If none of our live entry guards have a high uptime, but we
7904 require a guard with a high uptime, try adding a new guard before
7905 we give up on the requirement. This patch should make long-lived
7906 connections more stable on average.
7907 - When testing reachability of our DirPort, don't launch new
7908 tests when there's already one in progress -- unreachable
7909 servers were stacking up dozens of testing streams.
7911 o Security bugfixes:
7912 - When the user sends a NEWNYM signal, clear the client-side DNS
7913 cache too. Otherwise we continue to act on previous information.
7916 - Avoid a memory corruption bug when creating a hash table for
7918 - Avoid possibility of controller-triggered crash when misusing
7919 certain commands from a v0 controller on platforms that do not
7920 handle printf("%s",NULL) gracefully.
7921 - Avoid infinite loop on unexpected controller input.
7922 - Don't log spurious warnings when we see a circuit close reason we
7923 don't recognize; it's probably just from a newer version of Tor.
7924 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7925 Tor/Privoxy we also uninstall Vidalia.
7928 Changes in version 0.1.2.3-alpha - 2006-10-29
7930 - Prepare for servers to publish descriptors less often: never
7931 discard a descriptor simply for being too old until either it is
7932 recommended by no authorities, or until we get a better one for
7933 the same router. Make caches consider retaining old recommended
7934 routers for even longer.
7935 - If most authorities set a BadExit flag for a server, clients
7936 don't think of it as a general-purpose exit. Clients only consider
7937 authorities that advertise themselves as listing bad exits.
7938 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
7939 headers for content, so that we can work better in the presence of
7940 caching HTTP proxies.
7941 - Allow authorities to list nodes as bad exits by fingerprint or by
7944 o Minor features, controller:
7945 - Add a REASON field to CIRC events; for backward compatibility, this
7946 field is sent only to controllers that have enabled the extended
7947 event format. Also, add additional reason codes to explain why
7948 a given circuit has been destroyed or truncated. (Patches from
7950 - Add a REMOTE_REASON field to extended CIRC events to tell the
7951 controller about why a remote OR told us to close a circuit.
7952 - Stream events also now have REASON and REMOTE_REASON fields,
7953 working much like those for circuit events.
7954 - There's now a GETINFO ns/... field so that controllers can ask Tor
7955 about the current status of a router.
7956 - A new event type "NS" to inform a controller when our opinion of
7957 a router's status has changed.
7958 - Add a GETINFO events/names and GETINFO features/names so controllers
7959 can tell which events and features are supported.
7960 - A new CLEARDNSCACHE signal to allow controllers to clear the
7961 client-side DNS cache without expiring circuits.
7963 o Security bugfixes:
7964 - When the user sends a NEWNYM signal, clear the client-side DNS
7965 cache too. Otherwise we continue to act on previous information.
7968 - Avoid sending junk to controllers or segfaulting when a controller
7969 uses EVENT_NEW_DESC with verbose nicknames.
7970 - Stop triggering asserts if the controller tries to extend hidden
7971 service circuits (reported by mwenge).
7972 - Avoid infinite loop on unexpected controller input.
7973 - When the controller does a "GETINFO network-status", tell it
7974 about even those routers whose descriptors are very old, and use
7975 long nicknames where appropriate.
7976 - Change NT service functions to be loaded on demand. This lets us
7977 build with MinGW without breaking Tor for Windows 98 users.
7978 - Do DirPort reachability tests less often, since a single test
7979 chews through many circuits before giving up.
7980 - In the hidden service example in torrc.sample, stop recommending
7981 esoteric and discouraged hidden service options.
7982 - When stopping an NT service, wait up to 10 sec for it to actually
7983 stop. (Patch from Matt Edman; resolves bug 295.)
7984 - Fix handling of verbose nicknames with ORCONN controller events:
7985 make them show up exactly when requested, rather than exactly when
7987 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
7988 printing a duplicate "$" in the keys we send (reported by mwenge).
7989 - Correctly set maximum connection limit on Cygwin. (This time
7991 - Try to detect Windows correctly when cross-compiling.
7992 - Detect the size of the routers file correctly even if it is
7993 corrupted (on systems without mmap) or not page-aligned (on systems
7994 with mmap). This bug was harmless.
7995 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
7996 to open a stream fails; now we do in more cases. This should
7997 make clients able to find a good exit faster in some cases, since
7998 unhandleable requests will now get an error rather than timing out.
7999 - Resolve two memory leaks when rebuilding the on-disk router cache
8000 (reported by fookoowa).
8001 - Clean up minor code warnings suggested by the MIPSpro C compiler,
8002 and reported by some Centos users.
8003 - Controller signals now work on non-Unix platforms that don't define
8004 SIGUSR1 and SIGUSR2 the way we expect.
8005 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
8006 values before failing, and always enables eventdns.
8007 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
8008 Try to fix this in configure.in by checking for most functions
8009 before we check for libevent.
8012 Changes in version 0.1.2.2-alpha - 2006-10-07
8014 - Make our async eventdns library on-by-default for Tor servers,
8015 and plan to deprecate the separate dnsworker threads.
8016 - Add server-side support for "reverse" DNS lookups (using PTR
8017 records so clients can determine the canonical hostname for a given
8018 IPv4 address). Only supported by servers using eventdns; servers
8019 now announce in their descriptors whether they support eventdns.
8020 - Specify and implement client-side SOCKS5 interface for reverse DNS
8021 lookups (see doc/socks-extensions.txt).
8022 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
8023 connect to directory servers through Tor. Previously, clients needed
8024 to find Tor exits to make private connections to directory servers.
8025 - Avoid choosing Exit nodes for entry or middle hops when the
8026 total bandwidth available from non-Exit nodes is much higher than
8027 the total bandwidth available from Exit nodes.
8028 - Workaround for name servers (like Earthlink's) that hijack failing
8029 DNS requests and replace the no-such-server answer with a "helpful"
8030 redirect to an advertising-driven search portal. Also work around
8031 DNS hijackers who "helpfully" decline to hijack known-invalid
8032 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
8033 lets you turn it off.
8034 - Send out a burst of long-range padding cells once we've established
8035 that we're reachable. Spread them over 4 circuits, so hopefully
8036 a few will be fast. This exercises our bandwidth and bootstraps
8037 us into the directory more quickly.
8039 o New/improved config options:
8040 - Add new config option "ResolvConf" to let the server operator
8041 choose an alternate resolve.conf file when using eventdns.
8042 - Add an "EnforceDistinctSubnets" option to control our "exclude
8043 servers on the same /16" behavior. It's still on by default; this
8044 is mostly for people who want to operate private test networks with
8045 all the machines on the same subnet.
8046 - If one of our entry guards is on the ExcludeNodes list, or the
8047 directory authorities don't think it's a good guard, treat it as
8048 if it were unlisted: stop using it as a guard, and throw it off
8049 the guards list if it stays that way for a long time.
8050 - Allow directory authorities to be marked separately as authorities
8051 for the v1 directory protocol, the v2 directory protocol, and
8052 as hidden service directories, to make it easier to retire old
8053 authorities. V1 authorities should set "HSAuthoritativeDir 1"
8054 to continue being hidden service authorities too.
8055 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
8057 o Minor features, controller:
8058 - Fix CIRC controller events so that controllers can learn the
8059 identity digests of non-Named servers used in circuit paths.
8060 - Let controllers ask for more useful identifiers for servers. Instead
8061 of learning identity digests for un-Named servers and nicknames
8062 for Named servers, the new identifiers include digest, nickname,
8063 and indication of Named status. Off by default; see control-spec.txt
8064 for more information.
8065 - Add a "getinfo address" controller command so it can display Tor's
8066 best guess to the user.
8067 - New controller event to alert the controller when our server
8068 descriptor has changed.
8069 - Give more meaningful errors on controller authentication failure.
8071 o Minor features, other:
8072 - When asked to resolve a hostname, don't use non-exit servers unless
8073 requested to do so. This allows servers with broken DNS to be
8074 useful to the network.
8075 - Divide eventdns log messages into warn and info messages.
8076 - Reserve the nickname "Unnamed" for routers that can't pick
8077 a hostname: any router can call itself Unnamed; directory
8078 authorities will never allocate Unnamed to any particular router;
8079 clients won't believe that any router is the canonical Unnamed.
8080 - Only include function names in log messages for info/debug messages.
8081 For notice/warn/err, the content of the message should be clear on
8082 its own, and printing the function name only confuses users.
8083 - Avoid some false positives during reachability testing: don't try
8084 to test via a server that's on the same /24 as us.
8085 - If we fail to build a circuit to an intended enclave, and it's
8086 not mandatory that we use that enclave, stop wanting it.
8087 - When eventdns is enabled, allow multithreaded builds on NetBSD and
8088 OpenBSD. (We had previously disabled threads on these platforms
8089 because they didn't have working thread-safe resolver functions.)
8091 o Major bugfixes, anonymity/security:
8092 - If a client asked for a server by name, and there's a named server
8093 in our network-status but we don't have its descriptor yet, we
8094 could return an unnamed server instead.
8095 - Fix NetBSD bug that could allow someone to force uninitialized RAM
8096 to be sent to a server's DNS resolver. This only affects NetBSD
8097 and other platforms that do not bounds-check tolower().
8098 - Reject (most) attempts to use Tor circuits with length one. (If
8099 many people start using Tor as a one-hop proxy, exit nodes become
8100 a more attractive target for compromise.)
8101 - Just because your DirPort is open doesn't mean people should be
8102 able to remotely teach you about hidden service descriptors. Now
8103 only accept rendezvous posts if you've got HSAuthoritativeDir set.
8105 o Major bugfixes, other:
8106 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
8107 - When a client asks the server to resolve (not connect to)
8108 an address, and it has a cached answer, give them the cached answer.
8109 Previously, the server would give them no answer at all.
8110 - Allow really slow clients to not hang up five minutes into their
8111 directory downloads (suggested by Adam J. Richter).
8112 - We were building exactly the wrong circuits when we anticipated
8113 hidden service requirements, meaning Tor would have to build all
8114 its circuits on demand.
8115 - Avoid crashing when we mmap a router cache file of size 0.
8116 - When testing reachability of our DirPort, don't launch new
8117 tests when there's already one in progress -- unreachable
8118 servers were stacking up dozens of testing streams.
8120 o Minor bugfixes, correctness:
8121 - If we're a directory mirror and we ask for "all" network status
8122 documents, we would discard status documents from authorities
8124 - Avoid a memory corruption bug when creating a hash table for
8126 - Avoid controller-triggered crash when misusing certain commands
8127 from a v0 controller on platforms that do not handle
8128 printf("%s",NULL) gracefully.
8129 - Don't crash when a controller sends a third argument to an
8130 "extendcircuit" request.
8131 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
8132 response; fix error code when "getinfo dir/status/" fails.
8133 - Avoid crash when telling controller stream-status and a stream
8135 - Patch from Adam Langley to fix assert() in eventdns.c.
8136 - Fix a debug log message in eventdns to say "X resolved to Y"
8137 instead of "X resolved to X".
8138 - Make eventdns give strings for DNS errors, not just error numbers.
8139 - Track unreachable entry guards correctly: don't conflate
8140 'unreachable by us right now' with 'listed as down by the directory
8141 authorities'. With the old code, if a guard was unreachable by
8142 us but listed as running, it would clog our guard list forever.
8143 - Behave correctly in case we ever have a network with more than
8144 2GB/s total advertised capacity.
8145 - Make TrackExitHosts case-insensitive, and fix the behavior of
8146 ".suffix" TrackExitHosts items to avoid matching in the middle of
8148 - Finally fix the openssl warnings from newer gccs that believe that
8149 ignoring a return value is okay, but casting a return value and
8150 then ignoring it is a sign of madness.
8151 - Prevent the contrib/exitlist script from printing the same
8152 result more than once.
8153 - Patch from Steve Hildrey: Generate network status correctly on
8154 non-versioning dirservers.
8155 - Don't listen to the X-Your-Address-Is hint if you did the lookup
8156 via Tor; otherwise you'll think you're the exit node's IP address.
8158 o Minor bugfixes, performance:
8159 - Two small performance improvements on parsing descriptors.
8160 - Major performance improvement on inserting descriptors: change
8161 algorithm from O(n^2) to O(n).
8162 - Make the common memory allocation path faster on machines where
8163 malloc(0) returns a pointer.
8164 - Start remembering X-Your-Address-Is directory hints even if you're
8165 a client, so you can become a server more smoothly.
8166 - Avoid duplicate entries on MyFamily line in server descriptor.
8168 o Packaging, features:
8169 - Remove architecture from OS X builds. The official builds are
8170 now universal binaries.
8171 - The Debian package now uses --verify-config when (re)starting,
8172 to distinguish configuration errors from other errors.
8173 - Update RPMs to require libevent 1.1b.
8175 o Packaging, bugfixes:
8176 - Patches so Tor builds with MinGW on Windows.
8177 - Patches so Tor might run on Cygwin again.
8178 - Resume building on non-gcc compilers and ancient gcc. Resume
8179 building with the -O0 compile flag. Resume building cleanly on
8181 - Run correctly on OS X platforms with case-sensitive filesystems.
8182 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
8183 - Add autoconf checks so Tor can build on Solaris x86 again.
8186 - Documented (and renamed) ServerDNSSearchDomains and
8187 ServerDNSResolvConfFile options.
8188 - Be clearer that the *ListenAddress directives can be repeated
8192 Changes in version 0.1.1.24 - 2006-09-29
8194 - Allow really slow clients to not hang up five minutes into their
8195 directory downloads (suggested by Adam J. Richter).
8196 - Fix major performance regression from 0.1.0.x: instead of checking
8197 whether we have enough directory information every time we want to
8198 do something, only check when the directory information has changed.
8199 This should improve client CPU usage by 25-50%.
8200 - Don't crash if, after a server has been running for a while,
8201 it can't resolve its hostname.
8204 - Allow Tor to start when RunAsDaemon is set but no logs are set.
8205 - Don't crash when the controller receives a third argument to an
8206 "extendcircuit" request.
8207 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
8208 response; fix error code when "getinfo dir/status/" fails.
8209 - Fix configure.in to not produce broken configure files with
8210 more recent versions of autoconf. Thanks to Clint for his auto*
8212 - Fix security bug on NetBSD that could allow someone to force
8213 uninitialized RAM to be sent to a server's DNS resolver. This
8214 only affects NetBSD and other platforms that do not bounds-check
8216 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
8217 methods: these are known to be buggy.
8218 - If we're a directory mirror and we ask for "all" network status
8219 documents, we would discard status documents from authorities
8223 Changes in version 0.1.2.1-alpha - 2006-08-27
8225 - Add "eventdns" async dns library from Adam Langley, tweaked to
8226 build on OSX and Windows. Only enabled if you pass the
8227 --enable-eventdns argument to configure.
8228 - Allow servers with no hostname or IP address to learn their
8229 IP address by asking the directory authorities. This code only
8230 kicks in when you would normally have exited with a "no address"
8231 error. Nothing's authenticated, so use with care.
8232 - Rather than waiting a fixed amount of time between retrying
8233 application connections, we wait only 5 seconds for the first,
8234 10 seconds for the second, and 15 seconds for each retry after
8235 that. Hopefully this will improve the expected user experience.
8236 - Patch from Tup to add support for transparent AP connections:
8237 this basically bundles the functionality of trans-proxy-tor
8238 into the Tor mainline. Now hosts with compliant pf/netfilter
8239 implementations can redirect TCP connections straight to Tor
8240 without diverting through SOCKS. Needs docs.
8241 - Busy directory servers save lots of memory by spooling server
8242 descriptors, v1 directories, and v2 networkstatus docs to buffers
8243 as needed rather than en masse. Also mmap the cached-routers
8244 files, so we don't need to keep the whole thing in memory too.
8245 - Automatically avoid picking more than one node from the same
8246 /16 network when constructing a circuit.
8247 - Revise and clean up the torrc.sample that we ship with; add
8248 a section for BandwidthRate and BandwidthBurst.
8251 - Split circuit_t into origin_circuit_t and or_circuit_t, and
8252 split connection_t into edge, or, dir, control, and base structs.
8253 These will save quite a bit of memory on busy servers, and they'll
8254 also help us track down bugs in the code and bugs in the spec.
8255 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
8256 or later. Log when we are doing this, so we can diagnose it when
8257 it fails. (Also, recommend libevent 1.1b for kqueue and
8258 win32 methods; deprecate libevent 1.0b harder; make libevent
8259 recommendation system saner.)
8260 - Start being able to build universal binaries on OS X (thanks
8262 - Export the default exit policy via the control port, so controllers
8263 don't need to guess what it is / will be later.
8264 - Add a man page entry for ProtocolWarnings.
8265 - Add TestVia config option to the man page.
8266 - Remove even more protocol-related warnings from Tor server logs,
8267 such as bad TLS handshakes and malformed begin cells.
8268 - Stop fetching descriptors if you're not a dir mirror and you
8269 haven't tried to establish any circuits lately. [This currently
8270 causes some dangerous behavior, because when you start up again
8271 you'll use your ancient server descriptors.]
8272 - New DirPort behavior: if you have your dirport set, you download
8273 descriptors aggressively like a directory mirror, whether or not
8275 - Get rid of the router_retry_connections notion. Now routers
8276 no longer try to rebuild long-term connections to directory
8277 authorities, and directory authorities no longer try to rebuild
8278 long-term connections to all servers. We still don't hang up
8279 connections in these two cases though -- we need to look at it
8280 more carefully to avoid flapping, and we likely need to wait til
8281 0.1.1.x is obsolete.
8282 - Drop compatibility with obsolete Tors that permit create cells
8283 to have the wrong circ_id_type.
8284 - Re-enable per-connection rate limiting. Get rid of the "OP
8285 bandwidth" concept. Lay groundwork for "bandwidth classes" --
8286 separate global buckets that apply depending on what sort of conn
8288 - Start publishing one minute or so after we find our ORPort
8289 to be reachable. This will help reduce the number of descriptors
8290 we have for ourselves floating around, since it's quite likely
8291 other things (e.g. DirPort) will change during that minute too.
8292 - Fork the v1 directory protocol into its own spec document,
8293 and mark dir-spec.txt as the currently correct (v2) spec.
8296 - When we find our DirPort to be reachable, publish a new descriptor
8297 so we'll tell the world (reported by pnx).
8298 - Publish a new descriptor after we hup/reload. This is important
8299 if our config has changed such that we'll want to start advertising
8300 our DirPort now, etc.
8301 - Allow Tor to start when RunAsDaemon is set but no logs are set.
8302 - When we have a state file we cannot parse, tell the user and
8303 move it aside. Now we avoid situations where the user starts
8304 Tor in 1904, Tor writes a state file with that timestamp in it,
8305 the user fixes her clock, and Tor refuses to start.
8306 - Fix configure.in to not produce broken configure files with
8307 more recent versions of autoconf. Thanks to Clint for his auto*
8309 - "tor --verify-config" now exits with -1(255) or 0 depending on
8310 whether the config options are bad or good.
8311 - Resolve bug 321 when using dnsworkers: append a period to every
8312 address we resolve at the exit node, so that we do not accidentally
8313 pick up local addresses, and so that failing searches are retried
8314 in the resolver search domains. (This is already solved for
8315 eventdns.) (This breaks Blossom servers for now.)
8316 - If we are using an exit enclave and we can't connect, e.g. because
8317 its webserver is misconfigured to not listen on localhost, then
8318 back off and try connecting from somewhere else before we fail.
8321 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
8322 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
8323 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
8324 when the IP address is mapped through MapAddress to a hostname.
8325 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
8326 useless IPv6 DNS resolves.
8327 - Patch suggested by Karsten Loesing: respond to SIGNAL command
8328 before we execute the signal, in case the signal shuts us down.
8329 - Clean up AllowInvalidNodes man page entry.
8330 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
8331 - Add more asserts to track down an assert error on a windows Tor
8332 server with connection_add being called with socket == -1.
8333 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
8334 - Fix misleading log messages: an entry guard that is "unlisted",
8335 as well as not known to be "down" (because we've never heard
8336 of it), is not therefore "up".
8337 - Remove code to special-case "-cvs" ending, since it has not
8338 actually mattered since 0.0.9.
8339 - Make our socks5 handling more robust to broken socks clients:
8340 throw out everything waiting on the buffer in between socks
8341 handshake phases, since they can't possibly (so the theory
8342 goes) have predicted what we plan to respond to them.
8345 Changes in version 0.1.1.23 - 2006-07-30
8347 - Fast Tor servers, especially exit nodes, were triggering asserts
8348 due to a bug in handling the list of pending DNS resolves. Some
8349 bugs still remain here; we're hunting them.
8350 - Entry guards could crash clients by sending unexpected input.
8351 - More fixes on reachability testing: if you find yourself reachable,
8352 then don't ever make any client requests (so you stop predicting
8353 circuits), then hup or have your clock jump, then later your IP
8354 changes, you won't think circuits are working, so you won't try to
8355 test reachability, so you won't publish.
8358 - Avoid a crash if the controller does a resetconf firewallports
8359 and then a setconf fascistfirewall=1.
8360 - Avoid an integer underflow when the dir authority decides whether
8361 a router is stable: we might wrongly label it stable, and compute
8362 a slightly wrong median stability, when a descriptor is published
8364 - Fix a place where we might trigger an assert if we can't build our
8365 own server descriptor yet.
8368 Changes in version 0.1.1.22 - 2006-07-05
8370 - Fix a big bug that was causing servers to not find themselves
8371 reachable if they changed IP addresses. Since only 0.1.1.22+
8372 servers can do reachability testing correctly, now we automatically
8373 make sure to test via one of these.
8374 - Fix to allow clients and mirrors to learn directory info from
8375 descriptor downloads that get cut off partway through.
8376 - Directory authorities had a bug in deciding if a newly published
8377 descriptor was novel enough to make everybody want a copy -- a few
8378 servers seem to be publishing new descriptors many times a minute.
8380 - Fix a rare bug that was causing some servers to complain about
8381 "closing wedged cpuworkers" and skip some circuit create requests.
8382 - Make the Exit flag in directory status documents actually work.
8385 Changes in version 0.1.1.21 - 2006-06-10
8386 o Crash and assert fixes from 0.1.1.20:
8387 - Fix a rare crash on Tor servers that have enabled hibernation.
8388 - Fix a seg fault on startup for Tor networks that use only one
8389 directory authority.
8390 - Fix an assert from a race condition that occurs on Tor servers
8391 while exiting, where various threads are trying to log that they're
8392 exiting, and delete the logs, at the same time.
8393 - Make our unit tests pass again on certain obscure platforms.
8396 - Add support for building SUSE RPM packages.
8397 - Speed up initial bootstrapping for clients: if we are making our
8398 first ever connection to any entry guard, then don't mark it down
8400 - When only one Tor server in the network is labelled as a guard,
8401 and we've already picked him, we would cycle endlessly picking him
8402 again, being unhappy about it, etc. Now we specifically exclude
8403 current guards when picking a new guard.
8404 - Servers send create cells more reliably after the TLS connection
8405 is established: we were sometimes forgetting to send half of them
8406 when we had more than one pending.
8407 - If we get a create cell that asks us to extend somewhere, but the
8408 Tor server there doesn't match the expected digest, we now send
8409 a destroy cell back, rather than silently doing nothing.
8410 - Make options->RedirectExit work again.
8411 - Make cookie authentication for the controller work again.
8412 - Stop being picky about unusual characters in the arguments to
8413 mapaddress. It's none of our business.
8414 - Add a new config option "TestVia" that lets you specify preferred
8415 middle hops to use for test circuits. Perhaps this will let me
8416 debug the reachability problems better.
8418 o Log / documentation fixes:
8419 - If we're a server and some peer has a broken TLS certificate, don't
8420 log about it unless ProtocolWarnings is set, i.e., we want to hear
8421 about protocol violations by others.
8422 - Fix spelling of VirtualAddrNetwork in man page.
8423 - Add a better explanation at the top of the autogenerated torrc file
8424 about what happened to our old torrc.
8427 Changes in version 0.1.1.20 - 2006-05-23
8429 - Downgrade a log severity where servers complain that they're
8431 - Avoid a compile warning on FreeBSD.
8432 - Remove string size limit on NEWDESC messages; solve bug 291.
8433 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
8434 more thoroughly when we're running on windows.
8437 Changes in version 0.1.1.19-rc - 2006-05-03
8439 - Regenerate our local descriptor if it's dirty and we try to use
8440 it locally (e.g. if it changes during reachability detection).
8441 - If we setconf our ORPort to 0, we continued to listen on the
8442 old ORPort and receive connections.
8443 - Avoid a second warning about machine/limits.h on Debian
8445 - Be willing to add our own routerinfo into the routerlist.
8446 Now authorities will include themselves in their directories
8447 and network-statuses.
8448 - Stop trying to upload rendezvous descriptors to every
8449 directory authority: only try the v1 authorities.
8450 - Servers no longer complain when they think they're not
8451 registered with the directory authorities. There were too many
8453 - Backport dist-rpm changes so rpms can be built without errors.
8456 - Implement an option, VirtualAddrMask, to set which addresses
8457 get handed out in response to mapaddress requests. This works
8458 around a bug in tsocks where 127.0.0.0/8 is never socksified.
8461 Changes in version 0.1.1.18-rc - 2006-04-10
8463 - Work harder to download live network-statuses from all the
8464 directory authorities we know about. Improve the threshold
8465 decision logic so we're more robust to edge cases.
8466 - When fetching rendezvous descriptors, we were willing to ask
8467 v2 authorities too, which would always return 404.
8470 - Stop listing down or invalid nodes in the v1 directory. This will
8471 reduce its bulk by about 1/3, and reduce load on directory
8473 - When deciding whether a router is Fast or Guard-worthy, consider
8474 his advertised BandwidthRate and not just the BandwidthCapacity.
8475 - No longer ship INSTALL and README files -- they are useless now.
8476 - Force rpmbuild to behave and honor target_cpu.
8477 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
8478 - Start to include translated versions of the tor-doc-*.html
8479 files, along with the screenshots. Still needs more work.
8480 - Start sending back 512 and 451 errors if mapaddress fails,
8481 rather than not sending anything back at all.
8482 - When we fail to bind or listen on an incoming or outgoing
8483 socket, we should close it before failing. otherwise we just
8484 leak it. (thanks to weasel for finding.)
8485 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
8486 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
8487 - Make NoPublish (even though deprecated) work again.
8488 - Fix a minor security flaw where a versioning auth dirserver
8489 could list a recommended version many times in a row to make
8490 clients more convinced that it's recommended.
8491 - Fix crash bug if there are two unregistered servers running
8492 with the same nickname, one of them is down, and you ask for
8493 them by nickname in your EntryNodes or ExitNodes. Also, try
8494 to pick the one that's running rather than an arbitrary one.
8495 - Fix an infinite loop we could hit if we go offline for too long.
8496 - Complain when we hit WSAENOBUFS on recv() or write() too.
8497 Perhaps this will help us hunt the bug.
8498 - If you're not a versioning dirserver, don't put the string
8499 "client-versions \nserver-versions \n" in your network-status.
8500 - Lower the minimum required number of file descriptors to 1000,
8501 so we can have some overhead for Valgrind on Linux, where the
8502 default ulimit -n is 1024.
8505 - Add tor.dizum.com as the fifth authoritative directory server.
8506 - Add a new config option FetchUselessDescriptors, off by default,
8507 for when you plan to run "exitlist" on your client and you want
8508 to know about even the non-running descriptors.
8511 Changes in version 0.1.1.17-rc - 2006-03-28
8513 - Clients and servers since 0.1.1.10-alpha have been expiring
8514 connections whenever they are idle for 5 minutes and they *do*
8515 have circuits on them. Oops. With this new version, clients will
8516 discard their previous entry guard choices and avoid choosing
8517 entry guards running these flawed versions.
8518 - Fix memory leak when uncompressing concatenated zlib streams. This
8519 was causing substantial leaks over time on Tor servers.
8520 - The v1 directory was including servers as much as 48 hours old,
8521 because that's how the new routerlist->routers works. Now only
8522 include them if they're 20 hours old or less.
8525 - Resume building on irix64, netbsd 2.0, etc.
8526 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
8528 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
8529 and it is confusing some users.
8530 - Mirrors stop caching the v1 directory so often.
8531 - Make the max number of old descriptors that a cache will hold
8532 rise with the number of directory authorities, so we can scale.
8533 - Change our win32 uname() hack to be more forgiving about what
8534 win32 versions it thinks it's found.
8537 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
8539 - When the controller's *setconf commands fail, collect an error
8540 message in a string and hand it back to the controller.
8541 - Make the v2 dir's "Fast" flag based on relative capacity, just
8542 like "Stable" is based on median uptime. Name everything in the
8543 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
8544 - Log server fingerprint on startup, so new server operators don't
8545 have to go hunting around their filesystem for it.
8546 - Return a robots.txt on our dirport to discourage google indexing.
8547 - Let the controller ask for GETINFO dir/status/foo so it can ask
8548 directly rather than connecting to the dir port. Only works when
8549 dirport is set for now.
8551 o New config options rather than constants in the code:
8552 - SocksTimeout: How long do we let a socks connection wait
8553 unattached before we fail it?
8554 - CircuitBuildTimeout: Cull non-open circuits that were born
8555 at least this many seconds ago.
8556 - CircuitIdleTimeout: Cull open clean circuits that were born
8557 at least this many seconds ago.
8560 Changes in version 0.1.1.16-rc - 2006-03-18
8561 o Bugfixes on 0.1.1.15-rc:
8562 - Fix assert when the controller asks to attachstream a connect-wait
8563 or resolve-wait stream.
8564 - Now do address rewriting when the controller asks us to attach
8565 to a particular circuit too. This will let Blossom specify
8566 "moria2.exit" without having to learn what moria2's IP address is.
8567 - Make the "tor --verify-config" command-line work again, so people
8568 can automatically check if their torrc will parse.
8569 - Authoritative dirservers no longer require an open connection from
8570 a server to consider him "reachable". We need this change because
8571 when we add new auth dirservers, old servers won't know not to
8573 - Let Tor build on Sun CC again.
8574 - Fix an off-by-one buffer size in dirserv.c that magically never
8575 hit our three authorities but broke sjmurdoch's own tor network.
8576 - If we as a directory mirror don't know of any v1 directory
8577 authorities, then don't try to cache any v1 directories.
8578 - Stop warning about unknown servers in our family when they are
8579 given as hex digests.
8580 - Stop complaining as quickly to the server operator that he
8581 hasn't registered his nickname/key binding.
8582 - Various cleanups so we can add new V2 Auth Dirservers.
8583 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
8584 reflect the updated flags in our v2 dir protocol.
8585 - Resume allowing non-printable characters for exit streams (both
8586 for connecting and for resolving). Now we tolerate applications
8587 that don't follow the RFCs. But continue to block malformed names
8590 o Bugfixes on 0.1.0.x:
8591 - Fix assert bug in close_logs(): when we close and delete logs,
8592 remove them all from the global "logfiles" list.
8593 - Fix minor integer overflow in calculating when we expect to use up
8594 our bandwidth allocation before hibernating.
8595 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
8596 there are multiple SSLs installed with different versions.
8597 - When we try to be a server and Address is not explicitly set and
8598 our hostname resolves to a private IP address, try to use an
8599 interface address if it has a public address. Now Windows machines
8600 that think of themselves as localhost can work by default.
8603 - Let the controller ask for GETINFO dir/server/foo so it can ask
8604 directly rather than connecting to the dir port.
8605 - Let the controller tell us about certain router descriptors
8606 that it doesn't want Tor to use in circuits. Implement
8607 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
8608 - New config option SafeSocks to reject all application connections
8609 using unsafe socks protocols. Defaults to off.
8612 Changes in version 0.1.1.15-rc - 2006-03-11
8613 o Bugfixes and cleanups:
8614 - When we're printing strings from the network, don't try to print
8615 non-printable characters. This protects us against shell escape
8616 sequence exploits, and also against attacks to fool humans into
8617 misreading their logs.
8618 - Fix a bug where Tor would fail to establish any connections if you
8619 left it off for 24 hours and then started it: we were happy with
8620 the obsolete network statuses, but they all referred to router
8621 descriptors that were too old to fetch, so we ended up with no
8622 valid router descriptors.
8623 - Fix a seg fault in the controller's "getinfo orconn-status"
8624 command while listing status on incoming handshaking connections.
8625 Introduce a status name "NEW" for these connections.
8626 - If we get a linelist or linelist_s config option from the torrc
8627 (e.g. ExitPolicy) and it has no value, warn and skip rather than
8628 silently resetting it to its default.
8629 - Don't abandon entry guards until they've been down or gone for
8631 - Cleaner and quieter log messages.
8634 - New controller signal NEWNYM that makes new application requests
8636 - Add a new circuit purpose 'controller' to let the controller ask
8637 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
8638 controller command to let you specify the purpose if you're
8639 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
8640 command to let you change a circuit's purpose after it's been
8642 - Accept "private:*" in routerdesc exit policies; not generated yet
8643 because older Tors do not understand it.
8644 - Add BSD-style contributed startup script "rc.subr" from Peter
8648 Changes in version 0.1.1.14-alpha - 2006-02-20
8649 o Bugfixes on 0.1.1.x:
8650 - Don't die if we ask for a stdout or stderr log (even implicitly)
8651 and we're set to RunAsDaemon -- just warn.
8652 - We still had a few bugs in the OR connection rotation code that
8653 caused directory servers to slowly aggregate connections to other
8654 fast Tor servers. This time for sure!
8655 - Make log entries on Win32 include the name of the function again.
8656 - We were treating a pair of exit policies if they were equal even
8657 if one said accept and the other said reject -- causing us to
8658 not always publish a new descriptor since we thought nothing
8660 - Retry pending server downloads as well as pending networkstatus
8661 downloads when we unexpectedly get a socks request.
8662 - We were ignoring the IS_FAST flag in the directory status,
8663 meaning we were willing to pick trivial-bandwidth nodes for "fast"
8665 - If the controller's SAVECONF command fails (e.g. due to file
8666 permissions), let the controller know that it failed.
8669 - If we're trying to be a Tor server and running Windows 95/98/ME
8670 as a server, explain that we'll likely crash.
8671 - When we're a server, a client asks for an old-style directory,
8672 and our write bucket is empty, don't give it to him. This way
8673 small servers can continue to serve the directory *sometimes*,
8674 without getting overloaded.
8675 - Compress exit policies even more -- look for duplicate lines
8677 - Clients now honor the "guard" flag in the router status when
8678 picking entry guards, rather than looking at is_fast or is_stable.
8679 - Retain unrecognized lines in $DATADIR/state file, so that we can
8680 be forward-compatible.
8681 - Generate 18.0.0.0/8 address policy format in descs when we can;
8682 warn when the mask is not reducible to a bit-prefix.
8683 - Let the user set ControlListenAddress in the torrc. This can be
8684 dangerous, but there are some cases (like a secured LAN) where it
8686 - Split ReachableAddresses into ReachableDirAddresses and
8687 ReachableORAddresses, so we can restrict Dir conns to port 80
8688 and OR conns to port 443.
8689 - Now we can target arch and OS in rpm builds (contributed by
8690 Phobos). Also make the resulting dist-rpm filename match the
8692 - New config options to help controllers: FetchServerDescriptors
8693 and FetchHidServDescriptors for whether to fetch server
8694 info and hidserv info or let the controller do it, and
8695 PublishServerDescriptor and PublishHidServDescriptors.
8696 - Also let the controller set the __AllDirActionsPrivate config
8697 option if you want all directory fetches/publishes to happen via
8698 Tor (it assumes your controller bootstraps your circuits).
8701 Changes in version 0.1.0.17 - 2006-02-17
8702 o Crash bugfixes on 0.1.0.x:
8703 - When servers with a non-zero DirPort came out of hibernation,
8704 sometimes they would trigger an assert.
8706 o Other important bugfixes:
8707 - On platforms that don't have getrlimit (like Windows), we were
8708 artificially constraining ourselves to a max of 1024
8709 connections. Now just assume that we can handle as many as 15000
8710 connections. Hopefully this won't cause other problems.
8712 o Backported features:
8713 - When we're a server, a client asks for an old-style directory,
8714 and our write bucket is empty, don't give it to him. This way
8715 small servers can continue to serve the directory *sometimes*,
8716 without getting overloaded.
8717 - Whenever you get a 503 in response to a directory fetch, try
8718 once more. This will become important once servers start sending
8719 503's whenever they feel busy.
8720 - Fetch a new directory every 120 minutes, not every 40 minutes.
8721 Now that we have hundreds of thousands of users running the old
8722 directory algorithm, it's starting to hurt a lot.
8723 - Bump up the period for forcing a hidden service descriptor upload
8724 from 20 minutes to 1 hour.
8727 Changes in version 0.1.1.13-alpha - 2006-02-09
8728 o Crashes in 0.1.1.x:
8729 - When you tried to setconf ORPort via the controller, Tor would
8730 crash. So people using TorCP to become a server were sad.
8731 - Solve (I hope) the stack-smashing bug that we were seeing on fast
8732 servers. The problem appears to be something do with OpenSSL's
8733 random number generation, or how we call it, or something. Let me
8734 know if the crashes continue.
8735 - Turn crypto hardware acceleration off by default, until we find
8736 somebody smart who can test it for us. (It appears to produce
8737 seg faults in at least some cases.)
8738 - Fix a rare assert error when we've tried all intro points for
8739 a hidden service and we try fetching the service descriptor again:
8740 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
8743 - Fix a major load balance bug: we were round-robining in 16 KB
8744 chunks, and servers with bandwidthrate of 20 KB, while downloading
8745 a 600 KB directory, would starve their other connections. Now we
8746 try to be a bit more fair.
8747 - Dir authorities and mirrors were never expiring the newest
8748 descriptor for each server, causing memory and directory bloat.
8749 - Fix memory-bloating and connection-bloating bug on servers: We
8750 were never closing any connection that had ever had a circuit on
8751 it, because we were checking conn->n_circuits == 0, yet we had a
8752 bug that let it go negative.
8753 - Make Tor work using squid as your http proxy again -- squid
8754 returns an error if you ask for a URL that's too long, and it uses
8755 a really generic error message. Plus, many people are behind a
8756 transparent squid so they don't even realize it.
8757 - On platforms that don't have getrlimit (like Windows), we were
8758 artificially constraining ourselves to a max of 1024
8759 connections. Now just assume that we can handle as many as 15000
8760 connections. Hopefully this won't cause other problems.
8761 - Add a new config option ExitPolicyRejectPrivate which defaults to
8762 1. This means all exit policies will begin with rejecting private
8763 addresses, unless the server operator explicitly turns it off.
8766 - Clients no longer download descriptors for non-running
8768 - Before we add new directory authorities, we should make it
8769 clear that only v1 authorities should receive/publish hidden
8770 service descriptors.
8773 - As soon as we've fetched some more directory info, immediately
8774 try to download more server descriptors. This way we don't have
8775 a 10 second pause during initial bootstrapping.
8776 - Remove even more loud log messages that the server operator can't
8778 - When we're running an obsolete or un-recommended version, make
8779 the log message more clear about what the problem is and what
8780 versions *are* still recommended.
8781 - Provide a more useful warn message when our onion queue gets full:
8782 the CPU is too slow or the exit policy is too liberal.
8783 - Don't warn when we receive a 503 from a dirserver/cache -- this
8784 will pave the way for them being able to refuse if they're busy.
8785 - When we fail to bind a listener, try to provide a more useful
8786 log message: e.g., "Is Tor already running?"
8787 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
8788 Goldberg can prove things about our handshake protocol more
8790 - MaxConn has been obsolete for a while now. Document the ConnLimit
8791 config option, which is a *minimum* number of file descriptors
8792 that must be available else Tor refuses to start.
8793 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
8794 if you log to syslog and want something other than LOG_DAEMON.
8795 - Make dirservers generate a separate "guard" flag to mean,
8796 "would make a good entry guard". Make clients parse it and vote
8797 on it. Not used by clients yet.
8798 - Implement --with-libevent-dir option to ./configure. Also, improve
8799 search techniques to find libevent, and use those for openssl too.
8800 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
8801 - Only start testing reachability once we've established a
8802 circuit. This will make startup on dirservers less noisy.
8803 - Don't try to upload hidden service descriptors until we have
8804 established a circuit.
8805 - Fix the controller's "attachstream 0" command to treat conn like
8806 it just connected, doing address remapping, handling .exit and
8807 .onion idioms, and so on. Now we're more uniform in making sure
8808 that the controller hears about new and closing connections.
8811 Changes in version 0.1.1.12-alpha - 2006-01-11
8812 o Bugfixes on 0.1.1.x:
8813 - The fix to close duplicate server connections was closing all
8814 Tor client connections if they didn't establish a circuit
8815 quickly enough. Oops.
8816 - Fix minor memory issue (double-free) that happened on exit.
8818 o Bugfixes on 0.1.0.x:
8819 - Tor didn't warn when it failed to open a log file.
8822 Changes in version 0.1.1.11-alpha - 2006-01-10
8823 o Crashes in 0.1.1.x:
8824 - Include all the assert/crash fixes from 0.1.0.16.
8825 - If you start Tor and then quit very quickly, there were some
8826 races that tried to free things that weren't allocated yet.
8827 - Fix a rare memory stomp if you're running hidden services.
8828 - Fix segfault when specifying DirServer in config without nickname.
8829 - Fix a seg fault when you finish connecting to a server but at
8830 that moment you dump his server descriptor.
8831 - Extendcircuit and Attachstream controller commands would
8832 assert/crash if you don't give them enough arguments.
8833 - Fix an assert error when we're out of space in the connection_list
8834 and we try to post a hidden service descriptor (reported by weasel).
8835 - If you specify a relative torrc path and you set RunAsDaemon in
8836 your torrc, then it chdir()'s to the new directory. If you HUP,
8837 it tries to load the new torrc location, fails, and exits.
8838 The fix: no longer allow a relative path to torrc using -f.
8841 - Implement "entry guards": automatically choose a handful of entry
8842 nodes and stick with them for all circuits. Only pick new guards
8843 when the ones you have are unsuitable, and if the old guards
8844 become suitable again, switch back. This will increase security
8845 dramatically against certain end-point attacks. The EntryNodes
8846 config option now provides some hints about which entry guards you
8847 want to use most; and StrictEntryNodes means to only use those.
8848 - New directory logic: download by descriptor digest, not by
8849 fingerprint. Caches try to download all listed digests from
8850 authorities; clients try to download "best" digests from caches.
8851 This avoids partitioning and isolating attacks better.
8852 - Make the "stable" router flag in network-status be the median of
8853 the uptimes of running valid servers, and make clients pay
8854 attention to the network-status flags. Thus the cutoff adapts
8855 to the stability of the network as a whole, making IRC, IM, etc
8856 connections more reliable.
8859 - Tor servers with dynamic IP addresses were needing to wait 18
8860 hours before they could start doing reachability testing using
8861 the new IP address and ports. This is because they were using
8862 the internal descriptor to learn what to test, yet they were only
8863 rebuilding the descriptor once they decided they were reachable.
8864 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
8865 to download certain server descriptors, throw them away, and then
8866 fetch them again after 30 minutes. Now mirrors throw away these
8867 server descriptors so clients can't get them.
8868 - We were leaving duplicate connections to other ORs open for a week,
8869 rather than closing them once we detect a duplicate. This only
8870 really affected authdirservers, but it affected them a lot.
8871 - Spread the authdirservers' reachability testing over the entire
8872 testing interval, so we don't try to do 500 TLS's at once every
8876 - If the network is down, and we try to connect to a conn because
8877 we have a circuit in mind, and we timeout (30 seconds) because the
8878 network never answers, we were expiring the circuit, but we weren't
8879 obsoleting the connection or telling the entry_guards functions.
8880 - Some Tor servers process billions of cells per day. These statistics
8881 need to be uint64_t's.
8882 - Check for integer overflows in more places, when adding elements
8883 to smartlists. This could possibly prevent a buffer overflow
8884 on malicious huge inputs. I don't see any, but I haven't looked
8886 - ReachableAddresses kept growing new "reject *:*" lines on every
8888 - When you "setconf log" via the controller, it should remove all
8889 logs. We were automatically adding back in a "log notice stdout".
8890 - Newly bootstrapped Tor networks couldn't establish hidden service
8891 circuits until they had nodes with high uptime. Be more tolerant.
8892 - We were marking servers down when they could not answer every piece
8893 of the directory request we sent them. This was far too harsh.
8894 - Fix the torify (tsocks) config file to not use Tor for localhost
8896 - Directory authorities now go to the proper authority when asking for
8897 a networkstatus, even when they want a compressed one.
8898 - Fix a harmless bug that was causing Tor servers to log
8899 "Got an end because of misc error, but we're not an AP. Closing."
8900 - Authorities were treating their own descriptor changes as cosmetic,
8901 meaning the descriptor available in the network-status and the
8902 descriptor that clients downloaded were different.
8903 - The OS X installer was adding a symlink for tor_resolve but
8904 the binary was called tor-resolve (reported by Thomas Hardly).
8905 - Workaround a problem with some http proxies where they refuse GET
8906 requests that specify "Content-Length: 0" (reported by Adrian).
8907 - Fix wrong log message when you add a "HiddenServiceNodes" config
8908 line without any HiddenServiceDir line (reported by Chris Thomas).
8911 - Write the TorVersion into the state file so we have a prayer of
8912 keeping forward and backward compatibility.
8913 - Revive the FascistFirewall config option rather than eliminating it:
8914 now it's a synonym for ReachableAddresses *:80,*:443.
8915 - Clients choose directory servers from the network status lists,
8916 not from their internal list of router descriptors. Now they can
8917 go to caches directly rather than needing to go to authorities
8919 - Directory authorities ignore router descriptors that have only
8920 cosmetic differences: do this for 0.1.0.x servers now too.
8921 - Add a new flag to network-status indicating whether the server
8922 can answer v2 directory requests too.
8923 - Authdirs now stop whining so loudly about bad descriptors that
8924 they fetch from other dirservers. So when there's a log complaint,
8925 it's for sure from a freshly uploaded descriptor.
8926 - Reduce memory requirements in our structs by changing the order
8928 - There used to be two ways to specify your listening ports in a
8929 server descriptor: on the "router" line and with a separate "ports"
8930 line. Remove support for the "ports" line.
8931 - New config option "AuthDirRejectUnlisted" for auth dirservers as
8932 a panic button: if we get flooded with unusable servers we can
8933 revert to only listing servers in the approved-routers file.
8934 - Auth dir servers can now mark a fingerprint as "!reject" or
8935 "!invalid" in the approved-routers file (as its nickname), to
8936 refuse descriptors outright or include them but marked as invalid.
8937 - Servers store bandwidth history across restarts/crashes.
8938 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
8939 get a better idea of why their circuits failed. Not used yet.
8940 - Directory mirrors now cache up to 16 unrecognized network-status
8941 docs. Now we can add new authdirservers and they'll be cached too.
8942 - When picking a random directory, prefer non-authorities if any
8944 - New controller option "getinfo desc/all-recent" to fetch the
8945 latest server descriptor for every router that Tor knows about.
8948 Changes in version 0.1.0.16 - 2006-01-02
8949 o Crash bugfixes on 0.1.0.x:
8950 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8951 corrupting the heap, losing FDs, or crashing when we need to resize
8952 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8953 - It turns out sparc64 platforms crash on unaligned memory access
8954 too -- so detect and avoid this.
8955 - Handle truncated compressed data correctly (by detecting it and
8957 - Fix possible-but-unlikely free(NULL) in control.c.
8958 - When we were closing connections, there was a rare case that
8959 stomped on memory, triggering seg faults and asserts.
8960 - Avoid potential infinite recursion when building a descriptor. (We
8961 don't know that it ever happened, but better to fix it anyway.)
8962 - We were neglecting to unlink marked circuits from soon-to-close OR
8963 connections, which caused some rare scribbling on freed memory.
8964 - Fix a memory stomping race bug when closing the joining point of two
8965 rendezvous circuits.
8966 - Fix an assert in time parsing found by Steven Murdoch.
8968 o Other bugfixes on 0.1.0.x:
8969 - When we're doing reachability testing, provide more useful log
8970 messages so the operator knows what to expect.
8971 - Do not check whether DirPort is reachable when we are suppressing
8972 advertising it because of hibernation.
8973 - When building with -static or on Solaris, we sometimes needed -ldl.
8974 - When we're deciding whether a stream has enough circuits around
8975 that can handle it, count the freshly dirty ones and not the ones
8976 that are so dirty they won't be able to handle it.
8977 - When we're expiring old circuits, we had a logic error that caused
8978 us to close new rendezvous circuits rather than old ones.
8979 - Give a more helpful log message when you try to change ORPort via
8980 the controller: you should upgrade Tor if you want that to work.
8981 - We were failing to parse Tor versions that start with "Tor ".
8982 - Tolerate faulty streams better: when a stream fails for reason
8983 exitpolicy, stop assuming that the router is lying about his exit
8984 policy. When a stream fails for reason misc, allow it to retry just
8985 as if it was resolvefailed. When a stream has failed three times,
8986 reset its failure count so we can try again and get all three tries.
8989 Changes in version 0.1.1.10-alpha - 2005-12-11
8990 o Correctness bugfixes on 0.1.0.x:
8991 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8992 corrupting the heap, losing FDs, or crashing when we need to resize
8993 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8994 - Stop doing the complex voodoo overkill checking for insecure
8995 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
8996 - When we were closing connections, there was a rare case that
8997 stomped on memory, triggering seg faults and asserts.
8998 - We were neglecting to unlink marked circuits from soon-to-close OR
8999 connections, which caused some rare scribbling on freed memory.
9000 - When we're deciding whether a stream has enough circuits around
9001 that can handle it, count the freshly dirty ones and not the ones
9002 that are so dirty they won't be able to handle it.
9003 - Recover better from TCP connections to Tor servers that are
9004 broken but don't tell you (it happens!); and rotate TLS
9005 connections once a week.
9006 - When we're expiring old circuits, we had a logic error that caused
9007 us to close new rendezvous circuits rather than old ones.
9008 - Fix a scary-looking but apparently harmless bug where circuits
9009 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
9010 servers, and never switch to state CIRCUIT_STATE_OPEN.
9011 - When building with -static or on Solaris, we sometimes needed to
9013 - Give a useful message when people run Tor as the wrong user,
9014 rather than telling them to start chowning random directories.
9015 - We were failing to inform the controller about new .onion streams.
9017 o Security bugfixes on 0.1.0.x:
9018 - Refuse server descriptors if the fingerprint line doesn't match
9019 the included identity key. Tor doesn't care, but other apps (and
9020 humans) might actually be trusting the fingerprint line.
9021 - We used to kill the circuit when we receive a relay command we
9022 don't recognize. Now we just drop it.
9023 - Start obeying our firewall options more rigorously:
9024 . If we can't get to a dirserver directly, try going via Tor.
9025 . Don't ever try to connect (as a client) to a place our
9026 firewall options forbid.
9027 . If we specify a proxy and also firewall options, obey the
9028 firewall options even when we're using the proxy: some proxies
9029 can only proxy to certain destinations.
9030 - Fix a bug found by Lasse Overlier: when we were making internal
9031 circuits (intended to be cannibalized later for rendezvous and
9032 introduction circuits), we were picking them so that they had
9033 useful exit nodes. There was no need for this, and it actually
9034 aids some statistical attacks.
9035 - Start treating internal circuits and exit circuits separately.
9036 It's important to keep them separate because internal circuits
9037 have their last hops picked like middle hops, rather than like
9038 exit hops. So exiting on them will break the user's expectations.
9040 o Bugfixes on 0.1.1.x:
9041 - Take out the mis-feature where we tried to detect IP address
9042 flapping for people with DynDNS, and chose not to upload a new
9043 server descriptor sometimes.
9044 - Try to be compatible with OpenSSL 0.9.6 again.
9045 - Log fix: when the controller is logging about .onion addresses,
9046 sometimes it didn't include the ".onion" part of the address.
9047 - Don't try to modify options->DirServers internally -- if the
9048 user didn't specify any, just add the default ones directly to
9049 the trusted dirserver list. This fixes a bug where people running
9050 controllers would use SETCONF on some totally unrelated config
9051 option, and Tor would start yelling at them about changing their
9053 - Let the controller's redirectstream command specify a port, in
9054 case the controller wants to change that too.
9055 - When we requested a pile of server descriptors, we sometimes
9056 accidentally launched a duplicate request for the first one.
9057 - Bugfix for trackhostexits: write down the fingerprint of the
9058 chosen exit, not its nickname, because the chosen exit might not
9060 - When parsing foo.exit, if foo is unknown, and we are leaving
9061 circuits unattached, set the chosen_exit field and leave the
9062 address empty. This matters because controllers got confused
9064 - Directory authorities no longer try to download server
9065 descriptors that they know they will reject.
9067 o Features and updates:
9068 - Replace balanced trees with hash tables: this should make stuff
9069 significantly faster.
9070 - Resume using the AES counter-mode implementation that we ship,
9071 rather than OpenSSL's. Ours is significantly faster.
9072 - Many other CPU and memory improvements.
9073 - Add a new config option FastFirstHopPK (on by default) so clients
9074 do a trivial crypto handshake for their first hop, since TLS has
9075 already taken care of confidentiality and authentication.
9076 - Add a new config option TestSocks so people can see if their
9077 applications are using socks4, socks4a, socks5-with-ip, or
9078 socks5-with-hostname. This way they don't have to keep mucking
9079 with tcpdump and wondering if something got cached somewhere.
9080 - Warn when listening on a public address for socks. I suspect a
9081 lot of people are setting themselves up as open socks proxies,
9082 and they have no idea that jerks on the Internet are using them,
9083 since they simply proxy the traffic into the Tor network.
9084 - Add "private:*" as an alias in configuration for policies. Now
9085 you can simplify your exit policy rather than needing to list
9086 every single internal or nonroutable network space.
9087 - Add a new controller event type that allows controllers to get
9088 all server descriptors that were uploaded to a router in its role
9089 as authoritative dirserver.
9090 - Start shipping socks-extensions.txt, tor-doc-unix.html,
9091 tor-doc-server.html, and stylesheet.css in the tarball.
9092 - Stop shipping tor-doc.html in the tarball.
9095 Changes in version 0.1.1.9-alpha - 2005-11-15
9096 o Usability improvements:
9097 - Start calling it FooListenAddress rather than FooBindAddress,
9098 since few of our users know what it means to bind an address
9100 - Reduce clutter in server logs. We're going to try to make
9101 them actually usable now. New config option ProtocolWarnings that
9102 lets you hear about how _other Tors_ are breaking the protocol. Off
9104 - Divide log messages into logging domains. Once we put some sort
9105 of interface on this, it will let people looking at more verbose
9106 log levels specify the topics they want to hear more about.
9107 - Make directory servers return better http 404 error messages
9108 instead of a generic "Servers unavailable".
9109 - Check for even more Windows version flags when writing the platform
9110 string in server descriptors, and note any we don't recognize.
9111 - Clean up more of the OpenSSL memory when exiting, so we can detect
9112 memory leaks better.
9113 - Make directory authorities be non-versioning, non-naming by
9114 default. Now we can add new directory servers without requiring
9115 their operators to pay close attention.
9116 - When logging via syslog, include the pid whenever we provide
9117 a log entry. Suggested by Todd Fries.
9119 o Performance improvements:
9120 - Directory servers now silently throw away new descriptors that
9121 haven't changed much if the timestamps are similar. We do this to
9122 tolerate older Tor servers that upload a new descriptor every 15
9123 minutes. (It seemed like a good idea at the time.)
9124 - Inline bottleneck smartlist functions; use fast versions by default.
9125 - Add a "Map from digest to void*" abstraction digestmap_t so we
9126 can do less hex encoding/decoding. Use it in router_get_by_digest()
9127 to resolve a performance bottleneck.
9128 - Allow tor_gzip_uncompress to extract as much as possible from
9129 truncated compressed data. Try to extract as many
9130 descriptors as possible from truncated http responses (when
9131 DIR_PURPOSE_FETCH_ROUTERDESC).
9132 - Make circ->onionskin a pointer, not a static array. moria2 was using
9133 125000 circuit_t's after it had been up for a few weeks, which
9134 translates to 20+ megs of wasted space.
9135 - The private half of our EDH handshake keys are now chosen out
9136 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
9138 o Security improvements:
9139 - Start making directory caches retain old routerinfos, so soon
9140 clients can start asking by digest of descriptor rather than by
9141 fingerprint of server.
9142 - Add half our entropy from RAND_poll in OpenSSL. This knows how
9143 to use egd (if present), openbsd weirdness (if present), vms/os2
9144 weirdness (if we ever port there), and more in the future.
9146 o Bugfixes on 0.1.0.x:
9147 - Do round-robin writes of at most 16 kB per write. This might be
9148 more fair on loaded Tor servers, and it might resolve our Windows
9149 crash bug. It might also slow things down.
9150 - Our TLS handshakes were generating a single public/private
9151 keypair for the TLS context, rather than making a new one for
9152 each new connections. Oops. (But we were still rotating them
9153 periodically, so it's not so bad.)
9154 - When we were cannibalizing a circuit with a particular exit
9155 node in mind, we weren't checking to see if that exit node was
9156 already present earlier in the circuit. Oops.
9157 - When a Tor server's IP changes (e.g. from a dyndns address),
9158 upload a new descriptor so clients will learn too.
9159 - Really busy servers were keeping enough circuits open on stable
9160 connections that they were wrapping around the circuit_id
9161 space. (It's only two bytes.) This exposed a bug where we would
9162 feel free to reuse a circuit_id even if it still exists but has
9163 been marked for close. Try to fix this bug. Some bug remains.
9164 - If we would close a stream early (e.g. it asks for a .exit that
9165 we know would refuse it) but the LeaveStreamsUnattached config
9166 option is set by the controller, then don't close it.
9168 o Bugfixes on 0.1.1.8-alpha:
9169 - Fix a big pile of memory leaks, some of them serious.
9170 - Do not try to download a routerdesc if we would immediately reject
9172 - Resume inserting a newline between all router descriptors when
9173 generating (old style) signed directories, since our spec says
9175 - When providing content-type application/octet-stream for
9176 server descriptors using .z, we were leaving out the
9177 content-encoding header. Oops. (Everything tolerated this just
9178 fine, but that doesn't mean we need to be part of the problem.)
9179 - Fix a potential seg fault in getconf and getinfo using version 1
9180 of the controller protocol.
9181 - Avoid crash: do not check whether DirPort is reachable when we
9182 are suppressing it because of hibernation.
9183 - Make --hash-password not crash on exit.
9186 Changes in version 0.1.1.8-alpha - 2005-10-07
9187 o New features (major):
9188 - Clients don't download or use the directory anymore. Now they
9189 download and use network-statuses from the trusted dirservers,
9190 and fetch individual server descriptors as needed from mirrors.
9191 See dir-spec.txt for all the gory details.
9192 - Be more conservative about whether to advertise our DirPort.
9193 The main change is to not advertise if we're running at capacity
9194 and either a) we could hibernate or b) our capacity is low and
9195 we're using a default DirPort.
9196 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
9198 o New features (minor):
9199 - Try to be smart about when to retry network-status and
9200 server-descriptor fetches. Still needs some tuning.
9201 - Stop parsing, storing, or using running-routers output (but
9202 mirrors still cache and serve it).
9203 - Consider a threshold of versioning dirservers (dirservers who have
9204 an opinion about which Tor versions are still recommended) before
9205 deciding whether to warn the user that he's obsolete.
9206 - Dirservers can now reject/invalidate by key and IP, with the
9207 config options "AuthDirInvalid" and "AuthDirReject". This is
9208 useful since currently we automatically list servers as running
9209 and usable even if we know they're jerks.
9210 - Provide dire warnings to any users who set DirServer; move it out
9211 of torrc.sample and into torrc.complete.
9212 - Add MyFamily to torrc.sample in the server section.
9213 - Add nicknames to the DirServer line, so we can refer to them
9214 without requiring all our users to memorize their IP addresses.
9215 - When we get an EOF or a timeout on a directory connection, note
9216 how many bytes of serverdesc we are dropping. This will help
9217 us determine whether it is smart to parse incomplete serverdesc
9219 - Add a new function to "change pseudonyms" -- that is, to stop
9220 using any currently-dirty circuits for new streams, so we don't
9221 link new actions to old actions. Currently it's only called on
9222 HUP (or SIGNAL RELOAD).
9223 - On sighup, if UseHelperNodes changed to 1, use new circuits.
9224 - Start using RAND_bytes rather than RAND_pseudo_bytes from
9225 OpenSSL. Also, reseed our entropy every hour, not just at
9226 startup. And entropy in 512-bit chunks, not 160-bit chunks.
9228 o Fixes on 0.1.1.7-alpha:
9229 - Nobody ever implemented EVENT_ADDRMAP for control protocol
9230 version 0, so don't let version 0 controllers ask for it.
9231 - If you requested something with too many newlines via the
9232 v1 controller protocol, you could crash tor.
9233 - Fix a number of memory leaks, including some pretty serious ones.
9234 - Re-enable DirPort testing again, so Tor servers will be willing
9235 to advertise their DirPort if it's reachable.
9236 - On TLS handshake, only check the other router's nickname against
9237 its expected nickname if is_named is set.
9239 o Fixes forward-ported from 0.1.0.15:
9240 - Don't crash when we don't have any spare file descriptors and we
9241 try to spawn a dns or cpu worker.
9242 - Make the numbers in read-history and write-history into uint64s,
9243 so they don't overflow and publish negatives in the descriptor.
9246 - For the OS X package's modified privoxy config file, comment
9247 out the "logfile" line so we don't log everything passed
9249 - We were whining about using socks4 or socks5-with-local-lookup
9250 even when it's an IP in the "virtual" range we designed exactly
9252 - We were leaking some memory every time the client changes IPs.
9253 - Never call free() on tor_malloc()d memory. This will help us
9254 use dmalloc to detect memory leaks.
9255 - Check for named servers when looking them up by nickname;
9256 warn when we'recalling a non-named server by its nickname;
9257 don't warn twice about the same name.
9258 - Try to list MyFamily elements by key, not by nickname, and warn
9259 if we've not heard of the server.
9260 - Make windows platform detection (uname equivalent) smarter.
9261 - It turns out sparc64 doesn't like unaligned access either.
9264 Changes in version 0.1.0.15 - 2005-09-23
9265 o Bugfixes on 0.1.0.x:
9266 - Reject ports 465 and 587 (spam targets) in default exit policy.
9267 - Don't crash when we don't have any spare file descriptors and we
9268 try to spawn a dns or cpu worker.
9269 - Get rid of IgnoreVersion undocumented config option, and make us
9270 only warn, never exit, when we're running an obsolete version.
9271 - Don't try to print a null string when your server finds itself to
9272 be unreachable and the Address config option is empty.
9273 - Make the numbers in read-history and write-history into uint64s,
9274 so they don't overflow and publish negatives in the descriptor.
9275 - Fix a minor memory leak in smartlist_string_remove().
9276 - We were only allowing ourselves to upload a server descriptor at
9277 most every 20 minutes, even if it changed earlier than that.
9278 - Clean up log entries that pointed to old URLs.
9281 Changes in version 0.1.1.7-alpha - 2005-09-14
9282 o Fixes on 0.1.1.6-alpha:
9283 - Exit servers were crashing when people asked them to make a
9284 connection to an address not in their exit policy.
9285 - Looking up a non-existent stream for a v1 control connection would
9287 - Fix a seg fault if we ask a dirserver for a descriptor by
9288 fingerprint but he doesn't know about him.
9289 - SETCONF was appending items to linelists, not clearing them.
9290 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
9291 out and refuse the setconf if it would fail.
9292 - Downgrade the dirserver log messages when whining about
9296 - Add Peter Palfrader's check-tor script to tor/contrib/
9297 It lets you easily check whether a given server (referenced by
9298 nickname) is reachable by you.
9299 - Numerous changes to move towards client-side v2 directories. Not
9303 - If the user gave tor an odd number of command-line arguments,
9304 we were silently ignoring the last one. Now we complain and fail.
9305 [This wins the oldest-bug prize -- this bug has been present since
9306 November 2002, as released in Tor 0.0.0.]
9307 - Do not use unaligned memory access on alpha, mips, or mipsel.
9308 It *works*, but is very slow, so we treat them as if it doesn't.
9309 - Retry directory requests if we fail to get an answer we like
9310 from a given dirserver (we were retrying before, but only if
9311 we fail to connect).
9312 - When writing the RecommendedVersions line, sort them first.
9313 - When the client asked for a rendezvous port that the hidden
9314 service didn't want to provide, we were sending an IP address
9315 back along with the end cell. Fortunately, it was zero. But stop
9317 - Correct "your server is reachable" log entries to indicate that
9318 it was self-testing that told us so.
9321 Changes in version 0.1.1.6-alpha - 2005-09-09
9322 o Fixes on 0.1.1.5-alpha:
9323 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
9324 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
9325 - Fix bug with tor_memmem finding a match at the end of the string.
9326 - Make unit tests run without segfaulting.
9327 - Resolve some solaris x86 compile warnings.
9328 - Handle duplicate lines in approved-routers files without warning.
9329 - Fix bug where as soon as a server refused any requests due to his
9330 exit policy (e.g. when we ask for localhost and he tells us that's
9331 127.0.0.1 and he won't do it), we decided he wasn't obeying his
9332 exit policy using him for any exits.
9333 - Only do openssl hardware accelerator stuff if openssl version is
9336 o New controller features/fixes:
9337 - Add a "RESETCONF" command so you can set config options like
9338 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
9339 a config option in the torrc with no value, then it clears it
9340 entirely (rather than setting it to its default).
9341 - Add a "GETINFO config-file" to tell us where torrc is.
9342 - Avoid sending blank lines when GETINFO replies should be empty.
9343 - Add a QUIT command for the controller (for using it manually).
9344 - Fix a bug in SAVECONF that was adding default dirservers and
9345 other redundant entries to the torrc file.
9347 o Start on the new directory design:
9348 - Generate, publish, cache, serve new network-status format.
9349 - Publish individual descriptors (by fingerprint, by "all", and by
9351 - Publish client and server recommended versions separately.
9352 - Allow tor_gzip_uncompress() to handle multiple concatenated
9353 compressed strings. Serve compressed groups of router
9354 descriptors. The compression logic here could be more
9356 - Distinguish v1 authorities (all currently trusted directories)
9357 from v2 authorities (all trusted directories).
9358 - Change DirServers config line to note which dirs are v1 authorities.
9359 - Add configuration option "V1AuthoritativeDirectory 1" which
9360 moria1, moria2, and tor26 should set.
9361 - Remove option when getting directory cache to see whether they
9362 support running-routers; they all do now. Replace it with one
9363 to see whether caches support v2 stuff.
9366 - Dirservers now do their own external reachability testing of each
9367 Tor server, and only list them as running if they've been found to
9368 be reachable. We also send back warnings to the server's logs if
9369 it uploads a descriptor that we already believe is unreachable.
9370 - Implement exit enclaves: if we know an IP address for the
9371 destination, and there's a running Tor server at that address
9372 which allows exit to the destination, then extend the circuit to
9373 that exit first. This provides end-to-end encryption and end-to-end
9374 authentication. Also, if the user wants a .exit address or enclave,
9375 use 4 hops rather than 3, and cannibalize a general circ for it
9377 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
9378 controller. Also, rotate dns and cpu workers if the controller
9379 changes options that will affect them; and initialize the dns
9380 worker cache tree whether or not we start out as a server.
9381 - Only upload a new server descriptor when options change, 18
9382 hours have passed, uptime is reset, or bandwidth changes a lot.
9383 - Check [X-]Forwarded-For headers in HTTP requests when generating
9384 log messages. This lets people run dirservers (and caches) behind
9385 Apache but still know which IP addresses are causing warnings.
9387 o Config option changes:
9388 - Replace (Fascist)Firewall* config options with a new
9389 ReachableAddresses option that understands address policies.
9390 For example, "ReachableAddresses *:80,*:443"
9391 - Get rid of IgnoreVersion undocumented config option, and make us
9392 only warn, never exit, when we're running an obsolete version.
9393 - Make MonthlyAccountingStart config option truly obsolete now.
9396 - Reject ports 465 and 587 in the default exit policy, since
9397 people have started using them for spam too.
9398 - It turns out we couldn't bootstrap a network since we added
9399 reachability detection in 0.1.0.1-rc. Good thing the Tor network
9400 has never gone down. Add an AssumeReachable config option to let
9401 servers and dirservers bootstrap. When we're trying to build a
9402 high-uptime or high-bandwidth circuit but there aren't enough
9403 suitable servers, try being less picky rather than simply failing.
9404 - Our logic to decide if the OR we connected to was the right guy
9405 was brittle and maybe open to a mitm for unverified routers.
9406 - We weren't cannibalizing circuits correctly for
9407 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
9408 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
9409 build those from scratch. This should make hidden services faster.
9410 - Predict required circuits better, with an eye toward making hidden
9411 services faster on the service end.
9412 - Retry streams if the exit node sends back a 'misc' failure. This
9413 should result in fewer random failures. Also, after failing
9414 from resolve failed or misc, reset the num failures, so we give
9415 it a fair shake next time we try.
9416 - Clean up the rendezvous warn log msgs, and downgrade some to info.
9417 - Reduce severity on logs about dns worker spawning and culling.
9418 - When we're shutting down and we do something like try to post a
9419 server descriptor or rendezvous descriptor, don't complain that
9420 we seem to be unreachable. Of course we are, we're shutting down.
9421 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
9422 We don't use them yet, but maybe one day our DNS resolver will be
9423 able to discover them.
9424 - Make ContactInfo mandatory for authoritative directory servers.
9425 - Require server descriptors to list IPv4 addresses -- hostnames
9426 are no longer allowed. This also fixes some potential security
9427 problems with people providing hostnames as their address and then
9428 preferentially resolving them to partition users.
9429 - Change log line for unreachability to explicitly suggest /etc/hosts
9430 as the culprit. Also make it clearer what IP address and ports we're
9431 testing for reachability.
9432 - Put quotes around user-supplied strings when logging so users are
9433 more likely to realize if they add bad characters (like quotes)
9435 - Let auth dir servers start without specifying an Address config
9437 - Make unit tests (and other invocations that aren't the real Tor)
9438 run without launching listeners, creating subdirectories, and so on.
9441 Changes in version 0.1.1.5-alpha - 2005-08-08
9442 o Bugfixes included in 0.1.0.14.
9444 o Bugfixes on 0.1.0.x:
9445 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
9446 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
9447 it would silently using ignore the 6668.
9450 Changes in version 0.1.0.14 - 2005-08-08
9451 o Bugfixes on 0.1.0.x:
9452 - Fix the other half of the bug with crypto handshakes
9454 - Fix an assert trigger if you send a 'signal term' via the
9455 controller when it's listening for 'event info' messages.
9458 Changes in version 0.1.1.4-alpha - 2005-08-04
9459 o Bugfixes included in 0.1.0.13.
9462 - Improve tor_gettimeofday() granularity on windows.
9463 - Make clients regenerate their keys when their IP address changes.
9464 - Implement some more GETINFO goodness: expose helper nodes, config
9465 options, getinfo keys.
9468 Changes in version 0.1.0.13 - 2005-08-04
9469 o Bugfixes on 0.1.0.x:
9470 - Fix a critical bug in the security of our crypto handshakes.
9471 - Fix a size_t underflow in smartlist_join_strings2() that made
9472 it do bad things when you hand it an empty smartlist.
9473 - Fix Windows installer to ship Tor license (thanks to Aphex for
9474 pointing out this oversight) and put a link to the doc directory
9476 - Explicitly set no-unaligned-access for sparc: it turns out the
9477 new gcc's let you compile broken code, but that doesn't make it
9481 Changes in version 0.1.1.3-alpha - 2005-07-23
9482 o Bugfixes on 0.1.1.2-alpha:
9483 - Fix a bug in handling the controller's "post descriptor"
9485 - Fix several bugs in handling the controller's "extend circuit"
9487 - Fix a bug in handling the controller's "stream status" event.
9488 - Fix an assert failure if we have a controller listening for
9489 circuit events and we go offline.
9490 - Re-allow hidden service descriptors to publish 0 intro points.
9491 - Fix a crash when generating your hidden service descriptor if
9492 you don't have enough intro points already.
9494 o New features on 0.1.1.2-alpha:
9495 - New controller function "getinfo accounting", to ask how
9496 many bytes we've used in this time period.
9497 - Experimental support for helper nodes: a lot of the risk from
9498 a small static adversary comes because users pick new random
9499 nodes every time they rebuild a circuit. Now users will try to
9500 stick to the same small set of entry nodes if they can. Not
9501 enabled by default yet.
9503 o Bugfixes on 0.1.0.12:
9504 - If you're an auth dir server, always publish your dirport,
9505 even if you haven't yet found yourself to be reachable.
9506 - Fix a size_t underflow in smartlist_join_strings2() that made
9507 it do bad things when you hand it an empty smartlist.
9510 Changes in version 0.1.0.12 - 2005-07-18
9511 o New directory servers:
9512 - tor26 has changed IP address.
9514 o Bugfixes on 0.1.0.x:
9515 - Fix a possible double-free in tor_gzip_uncompress().
9516 - When --disable-threads is set, do not search for or link against
9518 - Don't trigger an assert if an authoritative directory server
9519 claims its dirport is 0.
9520 - Fix bug with removing Tor as an NT service: some people were
9521 getting "The service did not return an error." Thanks to Matt
9525 Changes in version 0.1.1.2-alpha - 2005-07-15
9526 o New directory servers:
9527 - tor26 has changed IP address.
9529 o Bugfixes on 0.1.0.x, crashes/leaks:
9530 - Port the servers-not-obeying-their-exit-policies fix from
9532 - Fix an fd leak in start_daemon().
9533 - On Windows, you can't always reopen a port right after you've
9534 closed it. So change retry_listeners() to only close and re-open
9535 ports that have changed.
9536 - Fix a possible double-free in tor_gzip_uncompress().
9538 o Bugfixes on 0.1.0.x, usability:
9539 - When tor_socketpair() fails in Windows, give a reasonable
9540 Windows-style errno back.
9541 - Let people type "tor --install" as well as "tor -install" when
9543 want to make it an NT service.
9544 - NT service patch from Matt Edman to improve error messages.
9545 - When the controller asks for a config option with an abbreviated
9546 name, give the full name in our response.
9547 - Correct the man page entry on TrackHostExitsExpire.
9548 - Looks like we were never delivering deflated (i.e. compressed)
9549 running-routers lists, even when asked. Oops.
9550 - When --disable-threads is set, do not search for or link against
9553 o Bugfixes on 0.1.1.x:
9554 - Fix a seg fault with autodetecting which controller version is
9558 - New hidden service descriptor format: put a version in it, and
9559 let people specify introduction/rendezvous points that aren't
9560 in "the directory" (which is subjective anyway).
9561 - Allow the DEBUG controller event to work again. Mark certain log
9562 entries as "don't tell this to controllers", so we avoid cycles.
9565 Changes in version 0.1.0.11 - 2005-06-30
9566 o Bugfixes on 0.1.0.x:
9567 - Fix major security bug: servers were disregarding their
9568 exit policies if clients behaved unexpectedly.
9569 - Make OS X init script check for missing argument, so we don't
9570 confuse users who invoke it incorrectly.
9571 - Fix a seg fault in "tor --hash-password foo".
9572 - The MAPADDRESS control command was broken.
9575 Changes in version 0.1.1.1-alpha - 2005-06-29
9577 - Make OS X init script check for missing argument, so we don't
9578 confuse users who invoke it incorrectly.
9579 - Fix a seg fault in "tor --hash-password foo".
9580 - Fix a possible way to DoS dirservers.
9581 - When we complain that your exit policy implicitly allows local or
9582 private address spaces, name them explicitly so operators can
9584 - Make the log message less scary when all the dirservers are
9585 temporarily unreachable.
9586 - We were printing the number of idle dns workers incorrectly when
9590 - Revised controller protocol (version 1) that uses ascii rather
9591 than binary. Add supporting libraries in python and java so you
9592 can use the controller from your applications without caring how
9594 - Spiffy new support for crypto hardware accelerators. Can somebody
9598 Changes in version 0.0.9.10 - 2005-06-16
9599 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
9600 - Refuse relay cells that claim to have a length larger than the
9601 maximum allowed. This prevents a potential attack that could read
9602 arbitrary memory (e.g. keys) from an exit server's process
9606 Changes in version 0.1.0.10 - 2005-06-14
9607 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
9608 libevent before 1.1a.
9611 Changes in version 0.1.0.9-rc - 2005-06-09
9613 - Reset buf->highwater every time buf_shrink() is called, not just on
9614 a successful shrink. This was causing significant memory bloat.
9615 - Fix buffer overflow when checking hashed passwords.
9616 - Security fix: if seeding the RNG on Win32 fails, quit.
9617 - Allow seeding the RNG on Win32 even when you're not running as
9619 - Disable threading on Solaris too. Something is wonky with it,
9620 cpuworkers, and reentrant libs.
9621 - Reenable the part of the code that tries to flush as soon as an
9622 OR outbuf has a full TLS record available. Perhaps this will make
9623 OR outbufs not grow as huge except in rare cases, thus saving lots
9624 of CPU time plus memory.
9625 - Reject malformed .onion addresses rather then passing them on as
9626 normal web requests.
9627 - Adapt patch from Adam Langley: fix possible memory leak in
9628 tor_lookup_hostname().
9629 - Initialize libevent later in the startup process, so the logs are
9630 already established by the time we start logging libevent warns.
9631 - Use correct errno on win32 if libevent fails.
9632 - Check and warn about known-bad/slow libevent versions.
9633 - Pay more attention to the ClientOnly config option.
9634 - Have torctl.in/tor.sh.in check for location of su binary (needed
9636 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
9637 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
9638 HttpProxyAuthenticator
9639 - Stop warning about sigpipes in the logs. We're going to
9640 pretend that getting these occassionally is normal and fine.
9641 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
9643 installer screens; and don't put stuff into StartupItems unless
9644 the user asks you to.
9645 - Require servers that use the default dirservers to have public IP
9646 addresses. We have too many servers that are configured with private
9647 IPs and their admins never notice the log entries complaining that
9648 their descriptors are being rejected.
9649 - Add OSX uninstall instructions. An actual uninstall script will
9653 Changes in version 0.1.0.8-rc - 2005-05-23
9655 - It turns out that kqueue on OS X 10.3.9 was causing kernel
9656 panics. Disable kqueue on all OS X Tors.
9657 - Fix RPM: remove duplicate line accidentally added to the rpm
9659 - Disable threads on openbsd too, since its gethostaddr is not
9661 - Tolerate libevent 0.8 since it still works, even though it's
9663 - Enable building on Red Hat 9.0 again.
9664 - Allow the middle hop of the testing circuit to be running any
9665 version, now that most of them have the bugfix to let them connect
9666 to unknown servers. This will allow reachability testing to work
9667 even when 0.0.9.7-0.0.9.9 become obsolete.
9668 - Handle relay cells with rh.length too large. This prevents
9669 a potential attack that could read arbitrary memory (maybe even
9670 keys) from the exit server's process.
9671 - We screwed up the dirport reachability testing when we don't yet
9672 have a cached version of the directory. Hopefully now fixed.
9673 - Clean up router_load_single_router() (used by the controller),
9674 so it doesn't seg fault on error.
9675 - Fix a minor memory leak when somebody establishes an introduction
9676 point at your Tor server.
9677 - If a socks connection ends because read fails, don't warn that
9678 you're not sending a socks reply back.
9681 - Add HttpProxyAuthenticator config option too, that works like
9682 the HttpsProxyAuthenticator config option.
9683 - Encode hashed controller passwords in hex instead of base64,
9684 to make it easier to write controllers.
9687 Changes in version 0.1.0.7-rc - 2005-05-17
9689 - Fix a bug in the OS X package installer that prevented it from
9690 installing on Tiger.
9691 - Fix a script bug in the OS X package installer that made it
9692 complain during installation.
9693 - Find libevent even if it's hiding in /usr/local/ and your
9694 CFLAGS and LDFLAGS don't tell you to look there.
9695 - Be able to link with libevent as a shared library (the default
9696 after 1.0d), even if it's hiding in /usr/local/lib and even
9697 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
9698 assuming you're running gcc. Otherwise fail and give a useful
9700 - Fix a bug in the RPM packager: set home directory for _tor to
9701 something more reasonable when first installing.
9702 - Free a minor amount of memory that is still reachable on exit.
9705 Changes in version 0.1.0.6-rc - 2005-05-14
9707 - Implement --disable-threads configure option. Disable threads on
9708 netbsd by default, because it appears to have no reentrant resolver
9710 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
9711 release (1.1) detects and disables kqueue if it's broken.
9712 - Append default exit policy before checking for implicit internal
9713 addresses. Now we don't log a bunch of complaints on startup
9714 when using the default exit policy.
9715 - Some people were putting "Address " in their torrc, and they had
9716 a buggy resolver that resolved " " to 0.0.0.0. Oops.
9717 - If DataDir is ~/.tor, and that expands to /.tor, then default to
9718 LOCALSTATEDIR/tor instead.
9719 - Fix fragmented-message bug in TorControl.py.
9720 - Resolve a minor bug which would prevent unreachable dirports
9721 from getting suppressed in the published descriptor.
9722 - When the controller gave us a new descriptor, we weren't resolving
9723 it immediately, so Tor would think its address was 0.0.0.0 until
9724 we fetched a new directory.
9725 - Fix an uppercase/lowercase case error in suppressing a bogus
9726 libevent warning on some Linuxes.
9729 - Begin scrubbing sensitive strings from logs by default. Turn off
9730 the config option SafeLogging if you need to do debugging.
9731 - Switch to a new buffer management algorithm, which tries to avoid
9732 reallocing and copying quite as much. In first tests it looks like
9733 it uses *more* memory on average, but less cpu.
9734 - First cut at support for "create-fast" cells. Clients can use
9735 these when extending to their first hop, since the TLS already
9736 provides forward secrecy and authentication. Not enabled on
9738 - When dirservers refuse a router descriptor, we now log its
9739 contactinfo, platform, and the poster's IP address.
9740 - Call tor_free_all instead of connections_free_all after forking, to
9741 save memory on systems that need to fork.
9742 - Whine at you if you're a server and you don't set your contactinfo.
9743 - Implement --verify-config command-line option to check if your torrc
9744 is valid without actually launching Tor.
9745 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
9746 rather than just rejecting it.
9749 Changes in version 0.1.0.5-rc - 2005-04-27
9751 - Stop trying to print a null pointer if an OR conn fails because
9752 we didn't like its cert.
9754 - Switch our internal buffers implementation to use a ring buffer,
9755 to hopefully improve performance for fast servers a lot.
9756 - Add HttpsProxyAuthenticator support (basic auth only), based
9757 on patch from Adam Langley.
9758 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
9759 the fast servers that have been joining lately.
9760 - Give hidden service accesses extra time on the first attempt,
9761 since 60 seconds is often only barely enough. This might improve
9763 - Improve performance for dirservers: stop re-parsing the whole
9764 directory every time you regenerate it.
9765 - Add more debugging info to help us find the weird dns freebsd
9766 pthreads bug; cleaner debug messages to help track future issues.
9769 Changes in version 0.0.9.9 - 2005-04-23
9770 o Bugfixes on 0.0.9.x:
9771 - If unofficial Tor clients connect and send weird TLS certs, our
9772 Tor server triggers an assert. This release contains a minimal
9773 backport from the broader fix that we put into 0.1.0.4-rc.
9776 Changes in version 0.1.0.4-rc - 2005-04-23
9778 - If unofficial Tor clients connect and send weird TLS certs, our
9779 Tor server triggers an assert. Stop asserting, and start handling
9780 TLS errors better in other situations too.
9781 - When the controller asks us to tell it about all the debug-level
9782 logs, it turns out we were generating debug-level logs while
9783 telling it about them, which turns into a bad loop. Now keep
9784 track of whether you're sending a debug log to the controller,
9785 and don't log when you are.
9786 - Fix the "postdescriptor" feature of the controller interface: on
9787 non-complete success, only say "done" once.
9789 - Clients are now willing to load balance over up to 2mB, not 1mB,
9790 of advertised bandwidth capacity.
9791 - Add a NoPublish config option, so you can be a server (e.g. for
9792 testing running Tor servers in other Tor networks) without
9793 publishing your descriptor to the primary dirservers.
9796 Changes in version 0.1.0.3-rc - 2005-04-08
9797 o Improvements on 0.1.0.2-rc:
9798 - Client now retries when streams end early for 'hibernating' or
9799 'resource limit' reasons, rather than failing them.
9800 - More automated handling for dirserver operators:
9801 - Automatically approve nodes running 0.1.0.2-rc or later,
9802 now that the the reachability detection stuff is working.
9803 - Now we allow two unverified servers with the same nickname
9804 but different keys. But if a nickname is verified, only that
9805 nickname+key are allowed.
9806 - If you're an authdirserver connecting to an address:port,
9807 and it's not the OR you were expecting, forget about that
9808 descriptor. If he *was* the one you were expecting, then forget
9809 about all other descriptors for that address:port.
9810 - Allow servers to publish descriptors from 12 hours in the future.
9811 Corollary: only whine about clock skew from the dirserver if
9812 he's a trusted dirserver (since now even verified servers could
9813 have quite wrong clocks).
9814 - Adjust maximum skew and age for rendezvous descriptors: let skew
9815 be 48 hours rather than 90 minutes.
9816 - Efficiency improvements:
9817 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
9818 it much faster to look up a circuit for each relay cell.
9819 - Remove most calls to assert_all_pending_dns_resolves_ok(),
9820 since they're eating our cpu on exit nodes.
9821 - Stop wasting time doing a case insensitive comparison for every
9822 dns name every time we do any lookup. Canonicalize the names to
9823 lowercase and be done with it.
9824 - Start sending 'truncated' cells back rather than destroy cells,
9825 if the circuit closes in front of you. This means we won't have
9826 to abandon partially built circuits.
9827 - Only warn once per nickname from add_nickname_list_to_smartlist
9828 per failure, so an entrynode or exitnode choice that's down won't
9830 - Put a note in the torrc about abuse potential with the default
9832 - Revise control spec and implementation to allow all log messages to
9833 be sent to controller with their severities intact (suggested by
9834 Matt Edman). Update TorControl to handle new log event types.
9835 - Provide better explanation messages when controller's POSTDESCRIPTOR
9837 - Stop putting nodename in the Platform string in server descriptors.
9838 It doesn't actually help, and it is confusing/upsetting some people.
9840 o Bugfixes on 0.1.0.2-rc:
9841 - We were printing the host mask wrong in exit policies in server
9842 descriptors. This isn't a critical bug though, since we were still
9843 obeying the exit policy internally.
9844 - Fix Tor when compiled with libevent but without pthreads: move
9845 connection_unregister() from _connection_free() to
9847 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
9848 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
9849 when we look through the connection array, we'll find any of the
9850 cpu/dnsworkers. This is no good.
9852 o Bugfixes on 0.0.9.8:
9853 - Fix possible bug on threading platforms (e.g. win32) which was
9854 leaking a file descriptor whenever a cpuworker or dnsworker died.
9855 - When using preferred entry or exit nodes, ignore whether the
9856 circuit wants uptime or capacity. They asked for the nodes, they
9858 - chdir() to your datadirectory at the *end* of the daemonize process,
9859 not the beginning. This was a problem because the first time you
9860 run tor, if your datadir isn't there, and you have runasdaemon set
9861 to 1, it will try to chdir to it before it tries to create it. Oops.
9862 - Handle changed router status correctly when dirserver reloads
9863 fingerprint file. We used to be dropping all unverified descriptors
9864 right then. The bug was hidden because we would immediately
9865 fetch a directory from another dirserver, which would include the
9866 descriptors we just dropped.
9867 - When we're connecting to an OR and he's got a different nickname/key
9868 than we were expecting, only complain loudly if we're an OP or a
9869 dirserver. Complaining loudly to the OR admins just confuses them.
9870 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
9871 artificially capped at 500kB.
9874 Changes in version 0.0.9.8 - 2005-04-07
9875 o Bugfixes on 0.0.9.x:
9876 - We have a bug that I haven't found yet. Sometimes, very rarely,
9877 cpuworkers get stuck in the 'busy' state, even though the cpuworker
9878 thinks of itself as idle. This meant that no new circuits ever got
9879 established. Here's a workaround to kill any cpuworker that's been
9880 busy for more than 100 seconds.
9883 Changes in version 0.1.0.2-rc - 2005-04-01
9884 o Bugfixes on 0.1.0.1-rc:
9885 - Fixes on reachability detection:
9886 - Don't check for reachability while hibernating.
9887 - If ORPort is reachable but DirPort isn't, still publish the
9888 descriptor, but zero out DirPort until it's found reachable.
9889 - When building testing circs for ORPort testing, use only
9890 high-bandwidth nodes, so fewer circuits fail.
9891 - Complain about unreachable ORPort separately from unreachable
9892 DirPort, so the user knows what's going on.
9893 - Make sure we only conclude ORPort reachability if we didn't
9894 initiate the conn. Otherwise we could falsely conclude that
9895 we're reachable just because we connected to the guy earlier
9896 and he used that same pipe to extend to us.
9897 - Authdirservers shouldn't do ORPort reachability detection,
9898 since they're in clique mode, so it will be rare to find a
9899 server not already connected to them.
9900 - When building testing circuits, always pick middle hops running
9901 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
9902 bug. (This is a kludge; it will go away when 0.0.9.x becomes
9904 - When we decide we're reachable, actually publish our descriptor
9906 - Fix bug in redirectstream in the controller.
9907 - Fix the state descriptor strings so logs don't claim edge streams
9908 are in a different state than they actually are.
9909 - Use recent libevent features when possible (this only really affects
9910 win32 and osx right now, because the new libevent with these
9911 features hasn't been released yet). Add code to suppress spurious
9913 - Prevent possible segfault in connection_close_unattached_ap().
9914 - Fix newlines on torrc in win32.
9915 - Improve error msgs when tor-resolve fails.
9917 o Improvements on 0.0.9.x:
9918 - New experimental script tor/contrib/ExerciseServer.py (needs more
9919 work) that uses the controller interface to build circuits and
9920 fetch pages over them. This will help us bootstrap servers that
9921 have lots of capacity but haven't noticed it yet.
9922 - New experimental script tor/contrib/PathDemo.py (needs more work)
9923 that uses the controller interface to let you choose whole paths
9925 "<hostname>.<path,separated by dots>.<length of path>.path"
9926 - When we've connected to an OR and handshaked but didn't like
9927 the result, we were closing the conn without sending destroy
9928 cells back for pending circuits. Now send those destroys.
9931 Changes in version 0.0.9.7 - 2005-04-01
9932 o Bugfixes on 0.0.9.x:
9933 - Fix another race crash bug (thanks to Glenn Fink for reporting).
9934 - Compare identity to identity, not to nickname, when extending to
9935 a router not already in the directory. This was preventing us from
9936 extending to unknown routers. Oops.
9937 - Make sure to create OS X Tor user in <500 range, so we aren't
9938 creating actual system users.
9939 - Note where connection-that-hasn't-sent-end was marked, and fix
9940 a few really loud instances of this harmless bug (it's fixed more
9944 Changes in version 0.1.0.1-rc - 2005-03-28
9946 - Add reachability testing. Your Tor server will automatically try
9947 to see if its ORPort and DirPort are reachable from the outside,
9948 and it won't upload its descriptor until it decides they are.
9949 - Handle unavailable hidden services better. Handle slow or busy
9950 hidden services better.
9951 - Add support for CONNECTing through https proxies, with "HttpsProxy"
9953 - New exit policy: accept most low-numbered ports, rather than
9954 rejecting most low-numbered ports.
9955 - More Tor controller support (still experimental). See
9956 http://tor.eff.org/doc/control-spec.txt for all the new features,
9957 including signals to emulate unix signals from any platform;
9958 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
9959 closestream; closecircuit; etc.
9960 - Make nt services work and start on startup on win32 (based on
9961 patch by Matt Edman).
9962 - Add a new AddressMap config directive to rewrite incoming socks
9963 addresses. This lets you, for example, declare an implicit
9964 required exit node for certain sites.
9965 - Add a new TrackHostExits config directive to trigger addressmaps
9966 for certain incoming socks addresses -- for sites that break when
9967 your exit keeps changing (based on patch by Mike Perry).
9968 - Redo the client-side dns cache so it's just an addressmap too.
9969 - Notice when our IP changes, and reset stats/uptime/reachability.
9970 - When an application is using socks5, give him the whole variety of
9971 potential socks5 responses (connect refused, host unreachable, etc),
9972 rather than just "success" or "failure".
9973 - A more sane version numbering system. See
9974 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
9975 - New contributed script "exitlist": a simple python script to
9976 parse directories and find Tor nodes that exit to listed
9978 - New contributed script "privoxy-tor-toggle" to toggle whether
9979 Privoxy uses Tor. Seems to be configured for Debian by default.
9980 - Report HTTP reasons to client when getting a response from directory
9981 servers -- so you can actually know what went wrong.
9982 - New config option MaxAdvertisedBandwidth which lets you advertise
9983 a low bandwidthrate (to not attract as many circuits) while still
9984 allowing a higher bandwidthrate in reality.
9986 o Robustness/stability fixes:
9987 - Make Tor use Niels Provos's libevent instead of its current
9988 poll-but-sometimes-select mess. This will let us use faster async
9989 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
9991 - pthread support now too. This was forced because when we forked,
9992 we ended up wasting a lot of duplicate ram over time. Also switch
9993 to foo_r versions of some library calls to allow reentry and
9995 - Better handling for heterogeneous / unreliable nodes:
9996 - Annotate circuits w/ whether they aim to contain high uptime nodes
9997 and/or high capacity nodes. When building circuits, choose
9999 - This means that every single node in an intro rend circuit,
10000 not just the last one, will have a minimum uptime.
10001 - New config option LongLivedPorts to indicate application streams
10002 that will want high uptime circuits.
10003 - Servers reset uptime when a dir fetch entirely fails. This
10004 hopefully reflects stability of the server's network connectivity.
10005 - If somebody starts his tor server in Jan 2004 and then fixes his
10006 clock, don't make his published uptime be a year.
10007 - Reset published uptime when you wake up from hibernation.
10008 - Introduce a notion of 'internal' circs, which are chosen without
10009 regard to the exit policy of the last hop. Intro and rendezvous
10010 circs must be internal circs, to avoid leaking information. Resolve
10011 and connect streams can use internal circs if they want.
10012 - New circuit pooling algorithm: make sure to have enough circs around
10013 to satisfy any predicted ports, and also make sure to have 2 internal
10014 circs around if we've required internal circs lately (and with high
10015 uptime if we've seen that lately too).
10016 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
10017 which describes how often we retry making new circuits if current
10018 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
10019 how long we're willing to make use of an already-dirty circuit.
10020 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
10021 circ as necessary, if there are any completed ones lying around
10022 when we try to launch one.
10023 - Make hidden services try to establish a rendezvous for 30 seconds,
10024 rather than for n (where n=3) attempts to build a circuit.
10025 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
10026 "ShutdownWaitLength".
10027 - Try to be more zealous about calling connection_edge_end when
10028 things go bad with edge conns in connection.c.
10029 - Revise tor-spec to add more/better stream end reasons.
10030 - Revise all calls to connection_edge_end to avoid sending "misc",
10031 and to take errno into account where possible.
10034 - Fix a race condition that can trigger an assert, when we have a
10035 pending create cell and an OR connection fails right then.
10036 - Fix several double-mark-for-close bugs, e.g. where we were finding
10037 a conn for a cell even if that conn is already marked for close.
10038 - Make sequence of log messages when starting on win32 with no config
10039 file more reasonable.
10040 - When choosing an exit node for a new non-internal circ, don't take
10041 into account whether it'll be useful for any pending x.onion
10042 addresses -- it won't.
10043 - Turn addr_policy_compare from a tristate to a quadstate; this should
10044 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
10045 for google.com" problem.
10046 - Make "platform" string in descriptor more accurate for Win32 servers,
10047 so it's not just "unknown platform".
10048 - Fix an edge case in parsing config options (thanks weasel).
10049 If they say "--" on the commandline, it's not an option.
10050 - Reject odd-looking addresses at the client (e.g. addresses that
10051 contain a colon), rather than having the server drop them because
10053 - tor-resolve requests were ignoring .exit if there was a working circuit
10054 they could use instead.
10055 - REUSEADDR on normal platforms means you can rebind to the port
10056 right after somebody else has let it go. But REUSEADDR on win32
10057 means to let you bind to the port _even when somebody else
10058 already has it bound_! So, don't do that on Win32.
10059 - Change version parsing logic: a version is "obsolete" if it is not
10060 recommended and (1) there is a newer recommended version in the
10061 same series, or (2) there are no recommended versions in the same
10062 series, but there are some recommended versions in a newer series.
10063 A version is "new" if it is newer than any recommended version in
10065 - Stop most cases of hanging up on a socks connection without sending
10069 - Require BandwidthRate to be at least 20kB/s for servers.
10070 - When a dirserver causes you to give a warn, mention which dirserver
10072 - New config option DirAllowPrivateAddresses for authdirservers.
10073 Now by default they refuse router descriptors that have non-IP or
10074 private-IP addresses.
10075 - Stop publishing socksport in the directory, since it's not
10076 actually meant to be public. For compatibility, publish a 0 there
10078 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
10079 smart" value, that is low for servers and high for clients.
10080 - If our clock jumps forward by 100 seconds or more, assume something
10081 has gone wrong with our network and abandon all not-yet-used circs.
10082 - Warn when exit policy implicitly allows local addresses.
10083 - If we get an incredibly skewed timestamp from a dirserver mirror
10084 that isn't a verified OR, don't warn -- it's probably him that's
10086 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
10087 cookies to disk and doesn't log each web request to disk. (Thanks
10088 to Brett Carrington for pointing this out.)
10089 - When a client asks us for a dir mirror and we don't have one,
10090 launch an attempt to get a fresh one.
10091 - If we're hibernating and we get a SIGINT, exit immediately.
10092 - Add --with-dmalloc ./configure option, to track memory leaks.
10093 - And try to free all memory on closing, so we can detect what
10095 - Cache local dns resolves correctly even when they're .exit
10097 - Give a better warning when some other server advertises an
10098 ORPort that is actually an apache running ssl.
10099 - Add "opt hibernating 1" to server descriptor to make it clearer
10100 whether the server is hibernating.
10103 Changes in version 0.0.9.6 - 2005-03-24
10104 o Bugfixes on 0.0.9.x (crashes and asserts):
10105 - Add new end stream reasons to maintainance branch. Fix bug where
10106 reason (8) could trigger an assert. Prevent bug from recurring.
10107 - Apparently win32 stat wants paths to not end with a slash.
10108 - Fix assert triggers in assert_cpath_layer_ok(), where we were
10109 blowing away the circuit that conn->cpath_layer points to, then
10110 checking to see if the circ is well-formed. Backport check to make
10111 sure we dont use the cpath on a closed connection.
10112 - Prevent circuit_resume_edge_reading_helper() from trying to package
10113 inbufs for marked-for-close streams.
10114 - Don't crash on hup if your options->address has become unresolvable.
10115 - Some systems (like OS X) sometimes accept() a connection and tell
10116 you the remote host is 0.0.0.0:0. If this happens, due to some
10117 other mis-features, we get confused; so refuse the conn for now.
10119 o Bugfixes on 0.0.9.x (other):
10120 - Fix harmless but scary "Unrecognized content encoding" warn message.
10121 - Add new stream error reason: TORPROTOCOL reason means "you are not
10122 speaking a version of Tor I understand; say bye-bye to your stream."
10123 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
10124 into the future, now that we are more tolerant of skew. This
10125 resolves a bug where a Tor server would refuse to cache a directory
10126 because all the directories it gets are too far in the future;
10127 yet the Tor server never logs any complaints about clock skew.
10128 - Mac packaging magic: make man pages useable, and do not overwrite
10129 existing torrc files.
10130 - Make OS X log happily to /var/log/tor/tor.log
10133 Changes in version 0.0.9.5 - 2005-02-22
10134 o Bugfixes on 0.0.9.x:
10135 - Fix an assert race at exit nodes when resolve requests fail.
10136 - Stop picking unverified dir mirrors--it only leads to misery.
10137 - Patch from Matt Edman to make NT services work better. Service
10138 support is still not compiled into the executable by default.
10139 - Patch from Dmitri Bely so the Tor service runs better under
10140 the win32 SYSTEM account.
10141 - Make tor-resolve actually work (?) on Win32.
10142 - Fix a sign bug when getrlimit claims to have 4+ billion
10143 file descriptors available.
10144 - Stop refusing to start when bandwidthburst == bandwidthrate.
10145 - When create cells have been on the onion queue more than five
10146 seconds, just send back a destroy and take them off the list.
10149 Changes in version 0.0.9.4 - 2005-02-03
10150 o Bugfixes on 0.0.9:
10151 - Fix an assert bug that took down most of our servers: when
10152 a server claims to have 1 GB of bandwidthburst, don't
10154 - Don't crash as badly if we have spawned the max allowed number
10155 of dnsworkers, or we're out of file descriptors.
10156 - Block more file-sharing ports in the default exit policy.
10157 - MaxConn is now automatically set to the hard limit of max
10158 file descriptors we're allowed (ulimit -n), minus a few for
10160 - Give a clearer message when servers need to raise their
10161 ulimit -n when they start running out of file descriptors.
10162 - SGI Compatibility patches from Jan Schaumann.
10163 - Tolerate a corrupt cached directory better.
10164 - When a dirserver hasn't approved your server, list which one.
10165 - Go into soft hibernation after 95% of the bandwidth is used,
10166 not 99%. This is especially important for daily hibernators who
10167 have a small accounting max. Hopefully it will result in fewer
10168 cut connections when the hard hibernation starts.
10169 - Load-balance better when using servers that claim more than
10170 800kB/s of capacity.
10171 - Make NT services work (experimental, only used if compiled in).
10174 Changes in version 0.0.9.3 - 2005-01-21
10175 o Bugfixes on 0.0.9:
10176 - Backport the cpu use fixes from main branch, so busy servers won't
10177 need as much processor time.
10178 - Work better when we go offline and then come back, or when we
10179 run Tor at boot before the network is up. We do this by
10180 optimistically trying to fetch a new directory whenever an
10181 application request comes in and we think we're offline -- the
10182 human is hopefully a good measure of when the network is back.
10183 - Backport some minimal hidserv bugfixes: keep rend circuits open as
10184 long as you keep using them; actually publish hidserv descriptors
10185 shortly after they change, rather than waiting 20-40 minutes.
10186 - Enable Mac startup script by default.
10187 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
10188 - When you update AllowUnverifiedNodes or FirewallPorts via the
10189 controller's setconf feature, we were always appending, never
10191 - When you update HiddenServiceDir via setconf, it was screwing up
10192 the order of reading the lines, making it fail.
10193 - Do not rewrite a cached directory back to the cache; otherwise we
10194 will think it is recent and not fetch a newer one on startup.
10195 - Workaround for webservers that lie about Content-Encoding: Tor
10196 now tries to autodetect compressed directories and compression
10197 itself. This lets us Proxypass dir fetches through apache.
10200 Changes in version 0.0.9.2 - 2005-01-04
10201 o Bugfixes on 0.0.9 (crashes and asserts):
10202 - Fix an assert on startup when the disk is full and you're logging
10204 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
10205 style address, then we'd crash.
10206 - Fix an assert trigger when the running-routers string we get from
10207 a dirserver is broken.
10208 - Make worker threads start and run on win32. Now win32 servers
10210 - Bandaid (not actually fix, but now it doesn't crash) an assert
10211 where the dns worker dies mysteriously and the main Tor process
10212 doesn't remember anything about the address it was resolving.
10214 o Bugfixes on 0.0.9 (Win32):
10215 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
10216 name out of the warning/assert messages.
10217 - Fix a superficial "unhandled error on read" bug on win32.
10218 - The win32 installer no longer requires a click-through for our
10219 license, since our Free Software license grants rights but does not
10221 - Win32: When connecting to a dirserver fails, try another one
10222 immediately. (This was already working for non-win32 Tors.)
10223 - Stop trying to parse $HOME on win32 when hunting for default
10225 - Make tor-resolve.c work on win32 by calling network_init().
10227 o Bugfixes on 0.0.9 (other):
10228 - Make 0.0.9.x build on Solaris again.
10229 - Due to a fencepost error, we were blowing away the \n when reporting
10230 confvalue items in the controller. So asking for multiple config
10231 values at once couldn't work.
10232 - When listing circuits that are pending on an opening OR connection,
10233 if we're an OR we were listing circuits that *end* at us as
10234 being pending on every listener, dns/cpu worker, etc. Stop that.
10235 - Dirservers were failing to create 'running-routers' or 'directory'
10236 strings if we had more than some threshold of routers. Fix them so
10237 they can handle any number of routers.
10238 - Fix a superficial "Duplicate mark for close" bug.
10239 - Stop checking for clock skew for OR connections, even for servers.
10240 - Fix a fencepost error that was chopping off the last letter of any
10241 nickname that is the maximum allowed nickname length.
10242 - Update URLs in log messages so they point to the new website.
10243 - Fix a potential problem in mangling server private keys while
10244 writing to disk (not triggered yet, as far as we know).
10245 - Include the licenses for other free software we include in Tor,
10246 now that we're shipping binary distributions more regularly.
10249 Changes in version 0.0.9.1 - 2004-12-15
10250 o Bugfixes on 0.0.9:
10251 - Make hibernation actually work.
10252 - Make HashedControlPassword config option work.
10253 - When we're reporting event circuit status to a controller,
10254 don't use the stream status code.
10257 Changes in version 0.0.9 - 2004-12-12
10259 - Clean up manpage and torrc.sample file.
10260 - Clean up severities and text of log warnings.
10262 - Make servers trigger an assert when they enter hibernation.
10265 Changes in version 0.0.9rc7 - 2004-12-08
10266 o Bugfixes on 0.0.9rc:
10267 - Fix a stack-trashing crash when an exit node begins hibernating.
10268 - Avoid looking at unallocated memory while considering which
10269 ports we need to build circuits to cover.
10270 - Stop a sigpipe: when an 'end' cell races with eof from the app,
10271 we shouldn't hold-open-until-flush if the eof arrived first.
10272 - Fix a bug with init_cookie_authentication() in the controller.
10273 - When recommending new-format log lines, if the upper bound is
10274 LOG_ERR, leave it implicit.
10276 o Bugfixes on 0.0.8.1:
10277 - Fix a whole slew of memory leaks.
10278 - Fix isspace() and friends so they still make Solaris happy
10279 but also so they don't trigger asserts on win32.
10280 - Fix parse_iso_time on platforms without strptime (eg win32).
10281 - win32: tolerate extra "readable" events better.
10282 - win32: when being multithreaded, leave parent fdarray open.
10283 - Make unit tests work on win32.
10286 Changes in version 0.0.9rc6 - 2004-12-06
10287 o Bugfixes on 0.0.9pre:
10288 - Clean up some more integer underflow opportunities (not exploitable
10290 - While hibernating, hup should not regrow our listeners.
10291 - Send an end to the streams we close when we hibernate, rather
10292 than just chopping them off.
10293 - React to eof immediately on non-open edge connections.
10295 o Bugfixes on 0.0.8.1:
10296 - Calculate timeout for waiting for a connected cell from the time
10297 we sent the begin cell, not from the time the stream started. If
10298 it took a long time to establish the circuit, we would time out
10299 right after sending the begin cell.
10300 - Fix router_compare_addr_to_addr_policy: it was not treating a port
10301 of * as always matching, so we were picking reject *:* nodes as
10302 exit nodes too. Oops.
10305 - New circuit building strategy: keep a list of ports that we've
10306 used in the past 6 hours, and always try to have 2 circuits open
10307 or on the way that will handle each such port. Seed us with port
10308 80 so web users won't complain that Tor is "slow to start up".
10309 - Make kill -USR1 dump more useful stats about circuits.
10310 - When warning about retrying or giving up, print the address, so
10311 the user knows which one it's talking about.
10312 - If you haven't used a clean circuit in an hour, throw it away,
10313 just to be on the safe side. (This means after 6 hours a totally
10314 unused Tor client will have no circuits open.)
10317 Changes in version 0.0.9rc5 - 2004-12-01
10318 o Bugfixes on 0.0.8.1:
10319 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
10320 - Let resolve conns retry/expire also, rather than sticking around
10322 - If we are using select, make sure we stay within FD_SETSIZE.
10324 o Bugfixes on 0.0.9pre:
10325 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
10326 but doesn't seem to be currently; thanks to Ilja van Sprundel for
10328 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
10329 instead. Impose minima and maxima for all *Period options; impose
10330 even tighter maxima for fetching if we are a caching dirserver.
10331 Clip rather than rejecting.
10332 - Fetch cached running-routers from servers that serve it (that is,
10333 authdirservers and servers running 0.0.9rc5-cvs or later.)
10336 - Accept *:706 (silc) in default exit policy.
10337 - Implement new versioning format for post 0.1.
10338 - Support "foo.nickname.exit" addresses, to let Alice request the
10339 address "foo" as viewed by exit node "nickname". Based on a patch
10341 - Make tor --version --version dump the cvs Id of every file.
10344 Changes in version 0.0.9rc4 - 2004-11-28
10345 o Bugfixes on 0.0.8.1:
10346 - Make windows sockets actually non-blocking (oops), and handle
10347 win32 socket errors better.
10349 o Bugfixes on 0.0.9rc1:
10350 - Actually catch the -USR2 signal.
10353 Changes in version 0.0.9rc3 - 2004-11-25
10354 o Bugfixes on 0.0.8.1:
10355 - Flush the log file descriptor after we print "Tor opening log file",
10356 so we don't see those messages days later.
10358 o Bugfixes on 0.0.9rc1:
10359 - Make tor-resolve work again.
10360 - Avoid infinite loop in tor-resolve if tor hangs up on it.
10361 - Fix an assert trigger for clients/servers handling resolves.
10364 Changes in version 0.0.9rc2 - 2004-11-24
10365 o Bugfixes on 0.0.9rc1:
10366 - I broke socks5 support while fixing the eof bug.
10367 - Allow unitless bandwidths and intervals; they default to bytes
10369 - New servers don't start out hibernating; they are active until
10370 they run out of bytes, so they have a better estimate of how
10371 long it takes, and so their operators can know they're working.
10374 Changes in version 0.0.9rc1 - 2004-11-23
10375 o Bugfixes on 0.0.8.1:
10376 - Finally fix a bug that's been plaguing us for a year:
10377 With high load, circuit package window was reaching 0. Whenever
10378 we got a circuit-level sendme, we were reading a lot on each
10379 socket, but only writing out a bit. So we would eventually reach
10380 eof. This would be noticed and acted on even when there were still
10381 bytes sitting in the inbuf.
10382 - When poll() is interrupted, we shouldn't believe the revents values.
10384 o Bugfixes on 0.0.9pre6:
10385 - Fix hibernate bug that caused pre6 to be broken.
10386 - Don't keep rephist info for routers that haven't had activity for
10387 24 hours. (This matters now that clients have keys, since we track
10389 - Never call close_temp_logs while validating log options.
10390 - Fix backslash-escaping on tor.sh.in and torctl.in.
10393 - Implement weekly/monthly/daily accounting: now you specify your
10394 hibernation properties by
10395 AccountingMax N bytes|KB|MB|GB|TB
10396 AccountingStart day|week|month [day] HH:MM
10397 Defaults to "month 1 0:00".
10398 - Let bandwidth and interval config options be specified as 5 bytes,
10399 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
10400 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
10401 get back to normal.)
10402 - If your requested entry or exit node has advertised bandwidth 0,
10404 - Be more greedy about filling up relay cells -- we try reading again
10405 once we've processed the stuff we read, in case enough has arrived
10406 to fill the last cell completely.
10407 - Apply NT service patch from Osamu Fujino. Still needs more work.
10410 Changes in version 0.0.9pre6 - 2004-11-15
10411 o Bugfixes on 0.0.8.1:
10412 - Fix assert failure on malformed socks4a requests.
10413 - Use identity comparison, not nickname comparison, to choose which
10414 half of circuit-ID-space each side gets to use. This is needed
10415 because sometimes we think of a router as a nickname, and sometimes
10416 as a hex ID, and we can't predict what the other side will do.
10417 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
10418 write() call will fail and we handle it there.
10419 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
10420 and smartlist_len, which are two major profiling offenders.
10422 o Bugfixes on 0.0.9pre5:
10423 - Fix a bug in read_all that was corrupting config files on windows.
10424 - When we're raising the max number of open file descriptors to
10425 'unlimited', don't log that we just raised it to '-1'.
10426 - Include event code with events, as required by control-spec.txt.
10427 - Don't give a fingerprint when clients do --list-fingerprint:
10428 it's misleading, because it will never be the same again.
10429 - Stop using strlcpy in tor_strndup, since it was slowing us
10431 - Remove warn on startup about missing cached-directory file.
10432 - Make kill -USR1 work again.
10433 - Hibernate if we start tor during the "wait for wakeup-time" phase
10434 of an accounting interval. Log our hibernation plans better.
10435 - Authoritative dirservers now also cache their directory, so they
10436 have it on start-up.
10439 - Fetch running-routers; cache running-routers; compress
10440 running-routers; serve compressed running-routers.z
10441 - Add NSI installer script contributed by J Doe.
10442 - Commit VC6 and VC7 workspace/project files.
10443 - Commit a tor.spec for making RPM files, with help from jbash.
10444 - Add contrib/torctl.in contributed by Glenn Fink.
10445 - Implement the control-spec's SAVECONF command, to write your
10446 configuration to torrc.
10447 - Get cookie authentication for the controller closer to working.
10448 - Include control-spec.txt in the tarball.
10449 - When set_conf changes our server descriptor, upload a new copy.
10450 But don't upload it too often if there are frequent changes.
10451 - Document authentication config in man page, and document signals
10453 - Clean up confusing parts of man page and torrc.sample.
10454 - Make expand_filename handle ~ and ~username.
10455 - Use autoconf to enable largefile support where necessary. Use
10456 ftello where available, since ftell can fail at 2GB.
10457 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
10458 log more informatively.
10459 - Give a slightly more useful output for "tor -h".
10460 - Refuse application socks connections to port 0.
10461 - Check clock skew for verified servers, but allow unverified
10462 servers and clients to have any clock skew.
10463 - Break DirFetchPostPeriod into:
10464 - DirFetchPeriod for fetching full directory,
10465 - StatusFetchPeriod for fetching running-routers,
10466 - DirPostPeriod for posting server descriptor,
10467 - RendPostPeriod for posting hidden service descriptors.
10468 - Make sure the hidden service descriptors are at a random offset
10469 from each other, to hinder linkability.
10472 Changes in version 0.0.9pre5 - 2004-11-09
10473 o Bugfixes on 0.0.9pre4:
10474 - Fix a seg fault in unit tests (doesn't affect main program).
10475 - Fix an assert bug where a hidden service provider would fail if
10476 the first hop of his rendezvous circuit was down.
10477 - Hidden service operators now correctly handle version 1 style
10478 INTRODUCE1 cells (nobody generates them still, so not a critical
10480 - If do_hup fails, actually notice.
10481 - Handle more errnos from accept() without closing the listener.
10482 Some OpenBSD machines were closing their listeners because
10483 they ran out of file descriptors.
10484 - Send resolve cells to exit routers that are running a new
10485 enough version of the resolve code to work right.
10486 - Better handling of winsock includes on non-MSV win32 compilers.
10487 - Some people had wrapped their tor client/server in a script
10488 that would restart it whenever it died. This did not play well
10489 with our "shut down if your version is obsolete" code. Now people
10490 don't fetch a new directory if their local cached version is
10492 - Make our autogen.sh work on ksh as well as bash.
10495 - Hibernation: New config option "AccountingMaxKB" lets you
10496 set how many KBytes per month you want to allow your server to
10497 consume. Rather than spreading those bytes out evenly over the
10498 month, we instead hibernate for some of the month and pop up
10499 at a deterministic time, work until the bytes are consumed, then
10500 hibernate again. Config option "MonthlyAccountingStart" lets you
10501 specify which day of the month your billing cycle starts on.
10502 - Control interface: a separate program can now talk to your
10503 client/server over a socket, and get/set config options, receive
10504 notifications of circuits and streams starting/finishing/dying,
10505 bandwidth used, etc. The next step is to get some GUIs working.
10506 Let us know if you want to help out. See doc/control-spec.txt .
10507 - Ship a contrib/tor-control.py as an example script to interact
10508 with the control port.
10509 - "tor --hash-password zzyxz" will output a salted password for
10510 use in authenticating to the control interface.
10511 - New log format in config:
10512 "Log minsev[-maxsev] stdout|stderr|syslog" or
10513 "Log minsev[-maxsev] file /var/foo"
10516 - DirPolicy config option, to let people reject incoming addresses
10517 from their dirserver.
10518 - "tor --list-fingerprint" will list your identity key fingerprint
10520 - Add "pass" target for RedirectExit, to make it easier to break
10521 out of a sequence of RedirectExit rules.
10522 - Clients now generate a TLS cert too, in preparation for having
10523 them act more like real nodes.
10524 - Ship src/win32/ in the tarball, so people can use it to build.
10525 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
10527 - New "router-status" line in directory, to better bind each verified
10528 nickname to its identity key.
10529 - Deprecate unofficial config option abbreviations, and abbreviations
10530 not on the command line.
10531 - Add a pure-C tor-resolve implementation.
10532 - Use getrlimit and friends to ensure we can reach MaxConn (currently
10533 1024) file descriptors.
10535 o Code security improvements, inspired by Ilja:
10536 - Replace sprintf with snprintf. (I think they were all safe, but
10538 - Replace strcpy/strncpy with strlcpy in more places.
10539 - Avoid strcat; use snprintf or strlcat instead.
10540 - snprintf wrapper with consistent (though not C99) overflow behavior.
10543 Changes in version 0.0.9pre4 - 2004-10-17
10544 o Bugfixes on 0.0.9pre3:
10545 - If the server doesn't specify an exit policy, use the real default
10546 exit policy, not reject *:*.
10547 - Ignore fascistfirewall when uploading/downloading hidden service
10548 descriptors, since we go through Tor for those; and when using
10549 an HttpProxy, since we assume it can reach them all.
10550 - When looking for an authoritative dirserver, use only the ones
10551 configured at boot. Don't bother looking in the directory.
10552 - The rest of the fix for get_default_conf_file() on older win32.
10553 - Make 'Routerfile' config option obsolete.
10556 - New 'MyFamily nick1,...' config option for a server to
10557 specify other servers that shouldn't be used in the same circuit
10558 with it. Only believed if nick1 also specifies us.
10559 - New 'NodeFamily nick1,nick2,...' config option for a client to
10560 specify nodes that it doesn't want to use in the same circuit.
10561 - New 'Redirectexit pattern address:port' config option for a
10562 server to redirect exit connections, e.g. to a local squid.
10565 Changes in version 0.0.9pre3 - 2004-10-13
10566 o Bugfixes on 0.0.8.1:
10567 - Better torrc example lines for dirbindaddress and orbindaddress.
10568 - Improved bounds checking on parsed ints (e.g. config options and
10569 the ones we find in directories.)
10570 - Better handling of size_t vs int, so we're more robust on 64
10572 - Fix the rest of the bug where a newly started OR would appear
10573 as unverified even after we've added his fingerprint and hupped
10575 - Fix a bug from 0.0.7: when read() failed on a stream, we would
10576 close it without sending back an end. So 'connection refused'
10577 would simply be ignored and the user would get no response.
10579 o Bugfixes on 0.0.9pre2:
10580 - Serving the cached-on-disk directory to people is bad. We now
10581 provide no directory until we've fetched a fresh one.
10582 - Workaround for bug on windows where cached-directories get crlf
10584 - Make get_default_conf_file() work on older windows too.
10585 - If we write a *:* exit policy line in the descriptor, don't write
10586 any more exit policy lines.
10589 - Use only 0.0.9pre1 and later servers for resolve cells.
10590 - Make the dirservers file obsolete.
10591 - Include a dir-signing-key token in directories to tell the
10592 parsing entity which key is being used to sign.
10593 - Remove the built-in bulky default dirservers string.
10594 - New config option "Dirserver %s:%d [fingerprint]", which can be
10595 repeated as many times as needed. If no dirservers specified,
10596 default to moria1,moria2,tor26.
10597 - Make moria2 advertise a dirport of 80, so people behind firewalls
10598 will be able to get a directory.
10599 - Http proxy support
10600 - Dirservers translate requests for http://%s:%d/x to /x
10601 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
10602 be routed through this host.
10603 - Clients ask for /tor/x rather than /x for new enough dirservers.
10604 This way we can one day coexist peacefully with apache.
10605 - Clients specify a "Host: %s%d" http header, to be compatible
10606 with more proxies, and so running squid on an exit node can work.
10609 Changes in version 0.0.8.1 - 2004-10-13
10611 - Fix a seg fault that can be triggered remotely for Tor
10612 clients/servers with an open dirport.
10613 - Fix a rare assert trigger, where routerinfos for entries in
10614 our cpath would expire while we're building the path.
10615 - Fix a bug in OutboundBindAddress so it (hopefully) works.
10616 - Fix a rare seg fault for people running hidden services on
10617 intermittent connections.
10618 - Fix a bug in parsing opt keywords with objects.
10619 - Fix a stale pointer assert bug when a stream detaches and
10621 - Fix a string format vulnerability (probably not exploitable)
10622 in reporting stats locally.
10623 - Fix an assert trigger: sometimes launching circuits can fail
10624 immediately, e.g. because too many circuits have failed recently.
10625 - Fix a compile warning on 64 bit platforms.
10628 Changes in version 0.0.9pre2 - 2004-10-03
10630 - Make fetching a cached directory work for 64-bit platforms too.
10631 - Make zlib.h a required header, not an optional header.
10634 Changes in version 0.0.9pre1 - 2004-10-01
10636 - Stop using separate defaults for no-config-file and
10637 empty-config-file. Now you have to explicitly turn off SocksPort,
10638 if you don't want it open.
10639 - Fix a bug in OutboundBindAddress so it (hopefully) works.
10640 - Improve man page to mention more of the 0.0.8 features.
10641 - Fix a rare seg fault for people running hidden services on
10642 intermittent connections.
10643 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
10645 - Fix more dns related bugs: send back resolve_failed and end cells
10646 more reliably when the resolve fails, rather than closing the
10647 circuit and then trying to send the cell. Also attach dummy resolve
10648 connections to a circuit *before* calling dns_resolve(), to fix
10649 a bug where cached answers would never be sent in RESOLVED cells.
10650 - When we run out of disk space, or other log writing error, don't
10651 crash. Just stop logging to that log and continue.
10652 - We were starting to daemonize before we opened our logs, so if
10653 there were any problems opening logs, we would complain to stderr,
10654 which wouldn't work, and then mysteriously exit.
10655 - Fix a rare bug where sometimes a verified OR would connect to us
10656 before he'd uploaded his descriptor, which would cause us to
10657 assign conn->nickname as though he's unverified. Now we look through
10658 the fingerprint list to see if he's there.
10659 - Fix a rare assert trigger, where routerinfos for entries in
10660 our cpath would expire while we're building the path.
10663 - Clients can ask dirservers for /dir.z to get a compressed version
10664 of the directory. Only works for servers running 0.0.9, of course.
10665 - Make clients cache directories and use them to seed their router
10666 lists at startup. This means clients have a datadir again.
10667 - Configuration infrastructure support for warning on obsolete
10669 - Respond to content-encoding headers by trying to uncompress as
10671 - Reply with a deflated directory when a client asks for "dir.z".
10672 We could use allow-encodings instead, but allow-encodings isn't
10673 specified in HTTP 1.0.
10674 - Raise the max dns workers from 50 to 100.
10675 - Discourage people from setting their dirfetchpostperiod more often
10676 than once per minute.
10677 - Protect dirservers from overzealous descriptor uploading -- wait
10678 10 seconds after directory gets dirty, before regenerating.
10681 Changes in version 0.0.8 - 2004-08-25
10682 o Port it to SunOS 5.9 / Athena
10685 Changes in version 0.0.8rc2 - 2004-08-20
10686 o Make it compile on cygwin again.
10687 o When picking unverified routers, skip those with low uptime and/or
10688 low bandwidth, depending on what properties you care about.
10691 Changes in version 0.0.8rc1 - 2004-08-18
10692 o Changes from 0.0.7.3:
10694 - Fix assert triggers: if the other side returns an address 0.0.0.0,
10695 don't put it into the client dns cache.
10696 - If a begin failed due to exit policy, but we believe the IP address
10697 should have been allowed, switch that router to exitpolicy reject *:*
10698 until we get our next directory.
10700 - Clients choose nodes proportional to advertised bandwidth.
10701 - Avoid using nodes with low uptime as introduction points.
10702 - Handle servers with dynamic IP addresses: don't replace
10703 options->Address with the resolved one at startup, and
10704 detect our address right before we make a routerinfo each time.
10705 - 'FascistFirewall' option to pick dirservers and ORs on specific
10706 ports; plus 'FirewallPorts' config option to tell FascistFirewall
10707 which ports are open. (Defaults to 80,443)
10708 - Be more aggressive about trying to make circuits when the network
10709 has changed (e.g. when you unsuspend your laptop).
10710 - Check for time skew on http headers; report date in response to
10712 - If the entrynode config line has only one node, don't pick it as
10714 - Add strict{entry|exit}nodes config options. If set to 1, then
10715 we refuse to build circuits that don't include the specified entry
10717 - OutboundBindAddress config option, to bind to a specific
10718 IP address for outgoing connect()s.
10719 - End truncated log entries (e.g. directories) with "[truncated]".
10721 o Patches to 0.0.8preX:
10723 - Patches to compile and run on win32 again (maybe)?
10724 - Fix crash when looking for ~/.torrc with no $HOME set.
10725 - Fix a race bug in the unit tests.
10726 - Handle verified/unverified name collisions better when new
10727 routerinfo's arrive in a directory.
10728 - Sometimes routers were getting entered into the stats before
10729 we'd assigned their identity_digest. Oops.
10730 - Only pick and establish intro points after we've gotten a
10733 - AllowUnverifiedNodes config option to let circuits choose no-name
10734 routers in entry,middle,exit,introduction,rendezvous positions.
10735 Allow middle and rendezvous positions by default.
10736 - Add a man page for tor-resolve.
10739 Changes in version 0.0.7.3 - 2004-08-12
10740 o Stop dnsworkers from triggering an assert failure when you
10741 ask them to resolve the host "".
10744 Changes in version 0.0.8pre3 - 2004-08-09
10745 o Changes from 0.0.7.2:
10746 - Allow multiple ORs with same nickname in routerlist -- now when
10747 people give us one identity key for a nickname, then later
10748 another, we don't constantly complain until the first expires.
10749 - Remember used bandwidth (both in and out), and publish 15-minute
10750 snapshots for the past day into our descriptor.
10751 - You can now fetch $DIRURL/running-routers to get just the
10752 running-routers line, not the whole descriptor list. (But
10753 clients don't use this yet.)
10754 - When people mistakenly use Tor as an http proxy, point them
10755 at the tor-doc.html rather than the INSTALL.
10756 - Remove our mostly unused -- and broken -- hex_encode()
10757 function. Use base16_encode() instead. (Thanks to Timo Lindfors
10758 for pointing out this bug.)
10759 - Rotate onion keys every 12 hours, not every 2 hours, so we have
10760 fewer problems with people using the wrong key.
10761 - Change the default exit policy to reject the default edonkey,
10762 kazaa, gnutella ports.
10763 - Add replace_file() to util.[ch] to handle win32's rename().
10765 o Changes from 0.0.8preX:
10766 - Fix two bugs in saving onion keys to disk when rotating, so
10767 hopefully we'll get fewer people using old onion keys.
10768 - Fix an assert error that was making SocksPolicy not work.
10769 - Be willing to expire routers that have an open dirport -- it's
10770 just the authoritative dirservers we want to not forget.
10771 - Reject tor-resolve requests for .onion addresses early, so we
10772 don't build a whole rendezvous circuit and then fail.
10773 - When you're warning a server that he's unverified, don't cry
10774 wolf unpredictably.
10775 - Fix a race condition: don't try to extend onto a connection
10776 that's still handshaking.
10777 - For servers in clique mode, require the conn to be open before
10778 you'll choose it for your path.
10779 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
10780 end relay cell, etc.
10781 - Measure bandwidth capacity over the last 24 hours, not just 12
10782 - Bugfix: authoritative dirservers were making and signing a new
10783 directory for each client, rather than reusing the cached one.
10786 Changes in version 0.0.8pre2 - 2004-08-04
10787 o Changes from 0.0.7.2:
10789 - Check directory signature _before_ you decide whether you're
10790 you're running an obsolete version and should exit.
10791 - Check directory signature _before_ you parse the running-routers
10792 list to decide who's running or verified.
10793 - Bugfixes and features:
10794 - Check return value of fclose while writing to disk, so we don't
10795 end up with broken files when servers run out of disk space.
10796 - Log a warning if the user uses an unsafe socks variant, so people
10797 are more likely to learn about privoxy or socat.
10798 - Dirservers now include RFC1123-style dates in the HTTP headers,
10799 which one day we will use to better detect clock skew.
10801 o Changes from 0.0.8pre1:
10802 - Make it compile without warnings again on win32.
10803 - Log a warning if you're running an unverified server, to let you
10804 know you might want to get it verified.
10805 - Only pick a default nickname if you plan to be a server.
10808 Changes in version 0.0.8pre1 - 2004-07-23
10810 - Made our unit tests compile again on OpenBSD 3.5, and tor
10811 itself compile again on OpenBSD on a sparc64.
10812 - We were neglecting milliseconds when logging on win32, so
10813 everything appeared to happen at the beginning of each second.
10815 o Protocol changes:
10816 - 'Extend' relay cell payloads now include the digest of the
10817 intended next hop's identity key. Now we can verify that we're
10818 extending to the right router, and also extend to routers we
10819 hadn't heard of before.
10822 - Tor nodes can now act as relays (with an advertised ORPort)
10823 without being manually verified by the dirserver operators.
10824 - Uploaded descriptors of unverified routers are now accepted
10825 by the dirservers, and included in the directory.
10826 - Verified routers are listed by nickname in the running-routers
10827 list; unverified routers are listed as "$<fingerprint>".
10828 - We now use hash-of-identity-key in most places rather than
10829 nickname or addr:port, for improved security/flexibility.
10830 - To avoid Sybil attacks, paths still use only verified servers.
10831 But now we have a chance to play around with hybrid approaches.
10832 - Nodes track bandwidth usage to estimate capacity (not used yet).
10833 - ClientOnly option for nodes that never want to become servers.
10834 - Directory caching.
10835 - "AuthoritativeDir 1" option for the official dirservers.
10836 - Now other nodes (clients and servers) will cache the latest
10837 directory they've pulled down.
10838 - They can enable their DirPort to serve it to others.
10839 - Clients will pull down a directory from any node with an open
10840 DirPort, and check the signature/timestamp correctly.
10841 - Authoritative dirservers now fetch directories from other
10842 authdirservers, to stay better synced.
10843 - Running-routers list tells who's down also, along with noting
10844 if they're verified (listed by nickname) or unverified (listed
10846 - Allow dirservers to serve running-router list separately.
10847 This isn't used yet.
10848 - ORs connect-on-demand to other ORs
10849 - If you get an extend cell to an OR you're not connected to,
10850 connect, handshake, and forward the create cell.
10851 - The authoritative dirservers stay connected to everybody,
10852 and everybody stays connected to 0.0.7 servers, but otherwise
10853 clients/servers expire unused connections after 5 minutes.
10854 - When servers get a sigint, they delay 30 seconds (refusing new
10855 connections) then exit. A second sigint causes immediate exit.
10856 - File and name management:
10857 - Look for .torrc if no CONFDIR "torrc" is found.
10858 - If no datadir is defined, then choose, make, and secure ~/.tor
10860 - If torrc not found, exitpolicy reject *:*.
10861 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
10862 - If no nickname is defined, derive default from hostname.
10863 - Rename secret key files, e.g. identity.key -> secret_id_key,
10864 to discourage people from mailing their identity key to tor-ops.
10865 - Refuse to build a circuit before the directory has arrived --
10866 it won't work anyway, since you won't know the right onion keys
10868 - Try other dirservers immediately if the one you try is down. This
10869 should tolerate down dirservers better now.
10870 - Parse tor version numbers so we can do an is-newer-than check
10871 rather than an is-in-the-list check.
10872 - New socks command 'resolve', to let us shim gethostbyname()
10874 - A 'tor_resolve' script to access the socks resolve functionality.
10875 - A new socks-extensions.txt doc file to describe our
10876 interpretation and extensions to the socks protocols.
10877 - Add a ContactInfo option, which gets published in descriptor.
10878 - Publish OR uptime in descriptor (and thus in directory) too.
10879 - Write tor version at the top of each log file
10880 - New docs in the tarball:
10882 - Document that you should proxy your SSL traffic too.
10885 Changes in version 0.0.7.2 - 2004-07-07
10886 o A better fix for the 0.0.0.0 problem, that will hopefully
10887 eliminate the remaining related assertion failures.
10890 Changes in version 0.0.7.1 - 2004-07-04
10891 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
10892 since internally we use 0.0.0.0 to signify "not yet resolved".
10895 Changes in version 0.0.7 - 2004-06-07
10896 o Updated the man page to reflect the new features.
10899 Changes in version 0.0.7rc2 - 2004-06-06
10900 o Changes from 0.0.7rc1:
10901 - Make it build on Win32 again.
10902 o Changes from 0.0.6.2:
10903 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
10907 Changes in version 0.0.7rc1 - 2004-06-02
10909 - On sighup, we were adding another log without removing the first
10910 one. So log messages would get duplicated n times for n sighups.
10911 - Several cases of using a connection after we'd freed it. The
10912 problem was that connections that are pending resolve are in both
10913 the pending_resolve tree, and also the circuit's resolving_streams
10914 list. When you want to remove one, you must remove it from both.
10915 - Fix a double-mark-for-close where an end cell arrived for a
10916 resolving stream, and then the resolve failed.
10917 - Check directory signatures based on name of signer, not on whom
10918 we got the directory from. This will let us cache directories more
10921 - Crank up some of our constants to handle more users.
10924 Changes in version 0.0.7pre1 - 2004-06-02
10925 o Fixes for crashes and other obnoxious bugs:
10926 - Fix an epipe bug: sometimes when directory connections failed
10927 to connect, we would give them a chance to flush before closing
10929 - When we detached from a circuit because of resolvefailed, we
10930 would immediately try the same circuit twice more, and then
10931 give up on the resolve thinking we'd tried three different
10933 - Limit the number of intro circuits we'll attempt to build for a
10934 hidden service per 15-minute period.
10935 - Check recommended-software string *early*, before actually parsing
10936 the directory. Thus we can detect an obsolete version and exit,
10937 even if the new directory format doesn't parse.
10938 o Fixes for security bugs:
10939 - Remember which nodes are dirservers when you startup, and if a
10940 random OR enables his dirport, don't automatically assume he's
10941 a trusted dirserver.
10943 - Directory connections were asking the wrong poll socket to
10944 start writing, and not asking themselves to start writing.
10945 - When we detached from a circuit because we sent a begin but
10946 didn't get a connected, we would use it again the first time;
10947 but after that we would correctly switch to a different one.
10948 - Stop warning when the first onion decrypt attempt fails; they
10949 will sometimes legitimately fail now that we rotate keys.
10950 - Override unaligned-access-ok check when $host_cpu is ia64 or
10951 arm. Apparently they allow it but the kernel whines.
10952 - Dirservers try to reconnect periodically too, in case connections
10954 - Fix some memory leaks in directory servers.
10955 - Allow backslash in Win32 filenames.
10956 - Made Tor build complain-free on FreeBSD, hopefully without
10957 breaking other BSD builds. We'll see.
10959 - Doxygen markup on all functions and global variables.
10960 - Make directory functions update routerlist, not replace it. So
10961 now directory disagreements are not so critical a problem.
10962 - Remove the upper limit on number of descriptors in a dirserver's
10963 directory (not that we were anywhere close).
10964 - Allow multiple logfiles at different severity ranges.
10965 - Allow *BindAddress to specify ":port" rather than setting *Port
10966 separately. Allow multiple instances of each BindAddress config
10967 option, so you can bind to multiple interfaces if you want.
10968 - Allow multiple exit policy lines, which are processed in order.
10969 Now we don't need that huge line with all the commas in it.
10970 - Enable accept/reject policies on SOCKS connections, so you can bind
10971 to 0.0.0.0 but still control who can use your OP.
10974 Changes in version 0.0.6.2 - 2004-05-16
10975 o Our integrity-checking digest was checking only the most recent cell,
10976 not the previous cells like we'd thought.
10977 Thanks to Stefan Mark for finding the flaw!
10980 Changes in version 0.0.6.1 - 2004-05-06
10981 o Fix two bugs in our AES counter-mode implementation (this affected
10982 onion-level stream encryption, but not TLS-level). It turns
10983 out we were doing something much more akin to a 16-character
10984 polyalphabetic cipher. Oops.
10985 Thanks to Stefan Mark for finding the flaw!
10986 o Retire moria3 as a directory server, and add tor26 as a directory
10990 Changes in version 0.0.6 - 2004-05-02
10991 [version bump only]
10994 Changes in version 0.0.6rc4 - 2004-05-01
10995 o Update the built-in dirservers list to use the new directory format
10996 o Fix a rare seg fault: if a node offering a hidden service attempts
10997 to build a circuit to Alice's rendezvous point and fails before it
10998 reaches the last hop, it retries with a different circuit, but
11000 o Handle windows socket errors correctly.
11003 Changes in version 0.0.6rc3 - 2004-04-28
11004 o Don't expire non-general excess circuits (if we had enough
11005 circuits open, we were expiring rendezvous circuits -- even
11006 when they had a stream attached. oops.)
11007 o Fetch randomness from /dev/urandom better (not via fopen/fread)
11008 o Better debugging for tls errors
11009 o Some versions of openssl have an SSL_pending function that erroneously
11010 returns bytes when there is a non-application record pending.
11011 o Set Content-Type on the directory and hidserv descriptor.
11012 o Remove IVs from cipher code, since AES-ctr has none.
11013 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
11014 o We were using an array of length zero in a few places.
11015 o win32's gethostbyname can't resolve an IP to an IP.
11016 o win32's close can't close a socket.
11019 Changes in version 0.0.6rc2 - 2004-04-26
11020 o Fix a bug where we were closing tls connections intermittently.
11021 It turns out openssl keeps its errors around -- so if an error
11022 happens, and you don't ask about it, and then another openssl
11023 operation happens and succeeds, and you ask if there was an error,
11024 it tells you about the first error. Fun fun.
11025 o Fix a bug that's been lurking since 27 may 03 (!)
11026 When passing back a destroy cell, we would use the wrong circ id.
11027 'Mostly harmless', but still worth fixing.
11028 o Since we don't support truncateds much, don't bother sending them;
11029 just close the circ.
11030 o check for <machine/limits.h> so we build on NetBSD again (I hope).
11031 o don't crash if a conn that sent a begin has suddenly lost its circuit
11032 (this was quite rare).
11035 Changes in version 0.0.6rc1 - 2004-04-25
11036 o We now rotate link (tls context) keys and onion keys.
11037 o CREATE cells now include oaep padding, so you can tell
11038 if you decrypted them correctly.
11039 o Add bandwidthburst to server descriptor.
11040 o Directories now say which dirserver signed them.
11041 o Use a tor_assert macro that logs failed assertions too.
11044 Changes in version 0.0.6pre5 - 2004-04-18
11045 o changes from 0.0.6pre4:
11046 - make tor build on broken freebsd 5.2 installs
11047 - fix a failed assert when you try an intro point, get a nack, and try
11048 a second one and it works.
11049 - when alice uses a port that the hidden service doesn't accept,
11050 it now sends back an end cell (denied by exit policy). otherwise
11051 alice would just have to wait to time out.
11052 - fix another rare bug: when we had tried all the intro
11053 points for a hidden service, we fetched the descriptor
11054 again, but we left our introcirc thinking it had already
11055 sent an intro, so it kept waiting for a response...
11056 - bugfix: when you sleep your hidden-service laptop, as soon
11057 as it wakes up it tries to upload a service descriptor, but
11058 socketpair fails for some reason (localhost not up yet?).
11059 now we simply give up on that upload, and we'll try again later.
11060 i'd still like to find the bug though.
11061 - if an intro circ waiting for an ack dies before getting one, then
11063 - we were reusing stale service descriptors and refetching usable
11067 Changes in version 0.0.6pre4 - 2004-04-14
11068 o changes from 0.0.6pre3:
11069 - when bob fails to connect to the rendezvous point, and his
11070 circ didn't fail because of the rendezvous point itself, then
11071 he retries a couple of times
11072 - we expire introduction and rendezvous circs more thoroughly
11073 (sometimes they were hanging around forever)
11074 - we expire unattached rendezvous streams that have been around
11075 too long (they were sticking around forever).
11076 - fix a measly fencepost error that was crashing everybody with
11080 Changes in version 0.0.6pre3 - 2004-04-14
11081 o changes from 0.0.6pre2:
11082 - make hup work again
11083 - fix some memory leaks for dirservers
11084 - allow more skew in rendezvous descriptor timestamps, to help
11085 handle people like blanu who don't know what time it is
11086 - normal circs are 3 hops, but some rend/intro circs are 4, if
11087 the initiator doesn't get to choose the last hop
11088 - send acks for introductions, so alice can know whether to try
11090 - bob publishes intro points more correctly
11091 o changes from 0.0.5:
11092 - fix an assert trigger that's been plaguing us since the days
11093 of 0.0.2prexx (thanks weasel!)
11094 - retry stream correctly when we fail to connect because of
11095 exit-policy-reject (should try another) or can't-resolve-address
11096 (also should try another, because dns on random internet servers
11098 - when we hup a dirserver and we've *removed* a server from the
11099 approved-routers list, now we remove that server from the
11100 in-memory directories too
11103 Changes in version 0.0.6pre2 - 2004-04-08
11104 o We fixed our base32 implementation. Now it works on all architectures.
11107 Changes in version 0.0.6pre1 - 2004-04-08
11109 - Hidden services and rendezvous points are implemented. Go to
11110 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
11111 hidden services. (This only works via a socks4a proxy such as
11112 Privoxy, and currently it's quite slow.)
11115 Changes in version 0.0.5 - 2004-03-30
11116 [version bump only]
11119 Changes in version 0.0.5rc3 - 2004-03-29
11120 o Install torrc as torrc.sample -- we no longer clobber your
11122 o Re-enable recommendedversion checking (we broke it in rc2, oops)
11123 o Add in a 'notice' log level for things the operator should hear
11124 but that aren't warnings
11127 Changes in version 0.0.5rc2 - 2004-03-29
11128 o Hold socks connection open until reply is flushed (if possible)
11129 o Make exit nodes resolve IPs to IPs immediately, rather than asking
11130 the dns farm to do it.
11131 o Fix c99 aliasing warnings in rephist.c
11132 o Don't include server descriptors that are older than 24 hours in the
11134 o Give socks 'reject' replies their whole 15s to attempt to flush,
11135 rather than seeing the 60s timeout and assuming the flush had failed.
11136 o Clean automake droppings from the cvs repository
11139 Changes in version 0.0.5rc1 - 2004-03-28
11140 o Fix mangled-state bug in directory fetching (was causing sigpipes).
11141 o Only build circuits after we've fetched the directory: clients were
11142 using only the directory servers before they'd fetched a directory.
11143 This also means longer startup time; so it goes.
11144 o Fix an assert trigger where an OP would fail to handshake, and we'd
11145 expect it to have a nickname.
11146 o Work around a tsocks bug: do a socks reject when AP connection dies
11147 early, else tsocks goes into an infinite loop.
11150 Changes in version 0.0.4 - 2004-03-26
11151 o When connecting to a dirserver or OR and the network is down,
11155 Changes in version 0.0.3 - 2004-03-26
11156 o Warn and fail if server chose a nickname with illegal characters
11157 o Port to Solaris and Sparc:
11158 - include missing header fcntl.h
11159 - have autoconf find -lsocket -lnsl automatically
11160 - deal with hardware word alignment
11161 - make uname() work (solaris has a different return convention)
11162 - switch from using signal() to sigaction()
11163 o Preliminary work on reputation system:
11164 - Keep statistics on success/fail of connect attempts; they're published
11165 by kill -USR1 currently.
11166 - Add a RunTesting option to try to learn link state by creating test
11167 circuits, even when SocksPort is off.
11168 - Remove unused open circuits when there are too many.
11171 Changes in version 0.0.2 - 2004-03-19
11172 - Include strlcpy and strlcat for safer string ops
11173 - define INADDR_NONE so we compile (but still not run) on solaris
11176 Changes in version 0.0.2pre27 - 2004-03-14
11178 - Allow internal tor networks (we were rejecting internal IPs,
11179 now we allow them if they're set explicitly).
11180 - And fix a few endian issues.
11183 Changes in version 0.0.2pre26 - 2004-03-14
11185 - If a stream times out after 15s without a connected cell, don't
11186 try that circuit again: try a new one.
11187 - Retry streams at most 4 times. Then give up.
11188 - When a dirserver gets a descriptor from an unknown router, it
11189 logs its fingerprint (so the dirserver operator can choose to
11190 accept it even without mail from the server operator).
11191 - Inform unapproved servers when we reject their descriptors.
11192 - Make tor build on Windows again. It works as a client, who knows
11194 - Clearer instructions in the torrc for how to set up a server.
11195 - Be more efficient about reading fd's when our global token bucket
11196 (used for rate limiting) becomes empty.
11198 - Stop asserting that computers always go forward in time. It's
11200 - When we sent a cell (e.g. destroy) and then marked an OR connection
11201 expired, we might close it before finishing a flush if the other
11202 side isn't reading right then.
11203 - Don't allow dirservers to start if they haven't defined
11204 RecommendedVersions
11205 - We were caching transient dns failures. Oops.
11206 - Prevent servers from publishing an internal IP as their address.
11207 - Address a strcat vulnerability in circuit.c
11210 Changes in version 0.0.2pre25 - 2004-03-04
11212 - Put the OR's IP in its router descriptor, not its fqdn. That way
11213 we'll stop being stalled by gethostbyname for nodes with flaky dns,
11216 - If the user typed in an address that didn't resolve, the server
11220 Changes in version 0.0.2pre24 - 2004-03-03
11222 - Fix an assertion failure in dns.c, where we were trying to dequeue
11223 a pending dns resolve even if it wasn't pending
11224 - Fix a spurious socks5 warning about still trying to write after the
11225 connection is finished.
11226 - Hold certain marked_for_close connections open until they're finished
11227 flushing, rather than losing bytes by closing them too early.
11228 - Correctly report the reason for ending a stream
11229 - Remove some duplicate calls to connection_mark_for_close
11230 - Put switch_id and start_daemon earlier in the boot sequence, so it
11231 will actually try to chdir() to options.DataDirectory
11232 - Make 'make test' exit(1) if a test fails; fix some unit tests
11233 - Make tor fail when you use a config option it doesn't know about,
11234 rather than warn and continue.
11235 - Make --version work
11236 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
11239 Changes in version 0.0.2pre23 - 2004-02-29
11241 - Print a statement when the first circ is finished, so the user
11242 knows it's working.
11243 - If a relay cell is unrecognized at the end of the circuit,
11244 send back a destroy. (So attacks to mutate cells are more
11246 - New config option 'excludenodes' to avoid certain nodes for circuits.
11247 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
11248 so you can collect coredumps there.
11250 - Fix a bug in tls flushing where sometimes data got wedged and
11251 didn't flush until more data got sent. Hopefully this bug was
11252 a big factor in the random delays we were seeing.
11253 - Make 'connected' cells include the resolved IP, so the client
11254 dns cache actually gets populated.
11255 - Disallow changing from ORPort=0 to ORPort>0 on hup.
11256 - When we time-out on a stream and detach from the circuit, send an
11257 end cell down it first.
11258 - Only warn about an unknown router (in exitnodes, entrynodes,
11259 excludenodes) after we've fetched a directory.
11262 Changes in version 0.0.2pre22 - 2004-02-26
11264 - Servers publish less revealing uname information in descriptors.
11265 - More memory tracking and assertions, to crash more usefully when
11267 - If the default torrc isn't there, just use some default defaults.
11268 Plus provide an internal dirservers file if they don't have one.
11269 - When the user tries to use Tor as an http proxy, give them an http
11270 501 failure explaining that we're a socks proxy.
11271 - Dump a new router.desc on hup, to help confused people who change
11272 their exit policies and then wonder why router.desc doesn't reflect
11274 - Clean up the generic tor.sh init script that we ship with.
11276 - If the exit stream is pending on the resolve, and a destroy arrives,
11277 then the stream wasn't getting removed from the pending list. I
11278 think this was the one causing recent server crashes.
11279 - Use a more robust poll on OSX 10.3, since their poll is flaky.
11280 - When it couldn't resolve any dirservers, it was useless from then on.
11281 Now it reloads the RouterFile (or default dirservers) if it has no
11283 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
11284 many users don't even *have* a /usr/local/sbin/.
11287 Changes in version 0.0.2pre21 - 2004-02-18
11289 - There's a ChangeLog file that actually reflects the changelog.
11290 - There's a 'torify' wrapper script, with an accompanying
11291 tor-tsocks.conf, that simplifies the process of using tsocks for
11292 tor. It even has a man page.
11293 - The tor binary gets installed to sbin rather than bin now.
11294 - Retry streams where the connected cell hasn't arrived in 15 seconds
11295 - Clean up exit policy handling -- get the default out of the torrc,
11296 so we can update it without forcing each server operator to fix
11298 - Allow imaps and pop3s in default exit policy
11300 - Prevent picking middleman nodes as the last node in the circuit
11303 Changes in version 0.0.2pre20 - 2004-01-30
11305 - We now have a deb package, and it's in debian unstable. Go to
11306 it, apt-getters. :)
11307 - I've split the TotalBandwidth option into BandwidthRate (how many
11308 bytes per second you want to allow, long-term) and
11309 BandwidthBurst (how many bytes you will allow at once before the cap
11310 kicks in). This better token bucket approach lets you, say, set
11311 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
11312 performance while not exceeding your monthly bandwidth quota.
11313 - Push out a tls record's worth of data once you've got it, rather
11314 than waiting until you've read everything waiting to be read. This
11315 may improve performance by pipelining better. We'll see.
11316 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
11317 from failed circuits (if they haven't been connected yet) and attach
11319 - Expire old streams that haven't managed to connect. Some day we'll
11320 have them reattach to new circuits instead.
11323 - Fix several memory leaks that were causing servers to become bloated
11325 - Fix a few very rare assert triggers. A few more remain.
11326 - Setuid to User _before_ complaining about running as root.
11329 Changes in version 0.0.2pre19 - 2004-01-07
11331 - Fix deadlock condition in dns farm. We were telling a child to die by
11332 closing the parent's file descriptor to him. But newer children were
11333 inheriting the open file descriptor from the parent, and since they
11334 weren't closing it, the socket never closed, so the child never read
11335 eof, so he never knew to exit. Similarly, dns workers were holding
11336 open other sockets, leading to all sorts of chaos.
11337 - New cleaner daemon() code for forking and backgrounding.
11338 - If you log to a file, it now prints an entry at the top of the
11339 logfile so you know it's working.
11340 - The onionskin challenge length was 30 bytes longer than necessary.
11341 - Started to patch up the spec so it's not quite so out of date.
11344 Changes in version 0.0.2pre18 - 2004-01-02
11346 - Fix endian issues with the 'integrity' field in the relay header.
11347 - Fix a potential bug where connections in state
11348 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
11351 Changes in version 0.0.2pre17 - 2003-12-30
11353 - Made --debuglogfile (or any second log file, actually) work.
11354 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
11355 adversary could force us into an infinite loop.
11358 - Each onionskin handshake now includes a hash of the computed key,
11359 to prove the server's identity and help perfect forward secrecy.
11360 - Changed cell size from 256 to 512 bytes (working toward compatibility
11362 - Changed cell length to 2 bytes, and moved it to the relay header.
11363 - Implemented end-to-end integrity checking for the payloads of
11365 - Separated streamid from 'recognized' (otherwise circuits will get
11366 messed up when we try to have streams exit from the middle). We
11367 use the integrity-checking to confirm that a cell is addressed to
11369 - Randomize the initial circid and streamid values, so an adversary who
11370 breaks into a node can't learn how many circuits or streams have
11374 Changes in version 0.0.2pre16 - 2003-12-14
11376 - Fixed a bug that made HUP trigger an assert
11377 - Fixed a bug where a circuit that immediately failed wasn't being
11378 counted as a failed circuit in counting retries.
11381 - Now we close the circuit when we get a truncated cell: otherwise we're
11382 open to an anonymity attack where a bad node in the path truncates
11383 the circuit and then we open streams at him.
11384 - Add port ranges to exit policies
11385 - Add a conservative default exit policy
11386 - Warn if you're running tor as root
11387 - on HUP, retry OR connections and close/rebind listeners
11388 - options.EntryNodes: try these nodes first when picking the first node
11389 - options.ExitNodes: if your best choices happen to include any of
11390 your preferred exit nodes, you choose among just those preferred
11392 - options.ExcludedNodes: nodes that are never picked in path building
11395 Changes in version 0.0.2pre15 - 2003-12-03
11396 o Robustness and bugfixes:
11397 - Sometimes clients would cache incorrect DNS resolves, which would
11398 really screw things up.
11399 - An OP that goes offline would slowly leak all its sockets and stop
11401 - A wide variety of bugfixes in exit node selection, exit policy
11402 handling, and processing pending streams when a new circuit is
11404 - Pick nodes for a path only from those the directory says are up
11405 - Choose randomly from all running dirservers, not always the first one
11406 - Increase allowed http header size for directory fetch.
11407 - Stop writing to stderr (if we're daemonized it will be closed).
11408 - Enable -g always, so cores will be more useful to me.
11409 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
11412 - Wrote a man page. It lists commonly used options.
11415 - Change default loglevel to warn.
11416 - Make PidFile default to null rather than littering in your CWD.
11417 - OnionRouter config option is now obsolete. Instead it just checks
11419 - Moved to a single unified torrc file for both clients and servers.
11422 Changes in version 0.0.2pre14 - 2003-11-29
11423 o Robustness and bugfixes:
11424 - Force the admin to make the DataDirectory himself
11425 - to get ownership/permissions right
11426 - so clients no longer make a DataDirectory and then never use it
11427 - fix bug where a client who was offline for 45 minutes would never
11428 pull down a directory again
11429 - fix (or at least hide really well) the dns assert bug that was
11430 causing server crashes
11431 - warnings and improved robustness wrt clockskew for certs
11432 - use the native daemon(3) to daemonize, when available
11433 - exit if bind() fails
11434 - exit if neither socksport nor orport is defined
11435 - include our own tor_timegm (Win32 doesn't have its own)
11436 - bugfix for win32 with lots of connections
11437 - fix minor bias in PRNG
11438 - make dirserver more robust to corrupt cached directory
11441 - Wrote the design document (woo)
11443 o Circuit building and exit policies:
11444 - Circuits no longer try to use nodes that the directory has told them
11446 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
11447 bitcounts (18.0.0.0/8).
11448 - Make AP connections standby for a circuit if no suitable circuit
11449 exists, rather than failing
11450 - Circuits choose exit node based on addr/port, exit policies, and
11451 which AP connections are standing by
11452 - Bump min pathlen from 2 to 3
11453 - Relay end cells have a payload to describe why the stream ended.
11454 - If the stream failed because of exit policy, try again with a new
11456 - Clients have a dns cache to remember resolved addresses.
11457 - Notice more quickly when we have no working circuits
11460 - APPort is now called SocksPort
11461 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
11463 - RecommendedVersions is now a config variable rather than
11464 hardcoded (for dirservers)
11465 - Reloads config on HUP
11466 - Usage info on -h or --help
11467 - If you set User and Group config vars, it'll setu/gid to them.
11470 Changes in version 0.0.2pre13 - 2003-10-19
11471 o General stability:
11472 - SSL_write no longer fails when it returns WANTWRITE and the number
11473 of bytes in the buf has changed by the next SSL_write call.
11474 - Fix segfault fetching directory when network is down
11475 - Fix a variety of minor memory leaks
11476 - Dirservers reload the fingerprints file on HUP, so I don't have
11477 to take down the network when I approve a new router
11478 - Default server config file has explicit Address line to specify fqdn
11481 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
11482 - Make listener connections not ever alloc bufs
11484 o Autoconf improvements:
11485 - don't clobber an external CFLAGS in ./configure
11486 - Make install now works
11487 - create var/lib/tor on make install
11488 - autocreate a tor.sh initscript to help distribs
11489 - autocreate the torrc and sample-server-torrc with correct paths
11491 o Log files and Daemonizing now work:
11492 - If --DebugLogFile is specified, log to it at -l debug
11493 - If --LogFile is specified, use it instead of commandline
11494 - If --RunAsDaemon is set, tor forks and backgrounds on startup