1 Changes in version 0.2.3.3-alpha - 2011-09-01
2 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
3 security, and provides client-side support for the microdescriptor
4 and optimistic data features introduced earlier in the 0.2.3.x
5 series. It also includes numerous critical bugfixes in the (optional)
6 bufferevent-based networking backend.
8 o Major features (stream isolation):
9 - You can now configure Tor so that streams from different
10 applications are isolated on different circuits, to prevent an
11 attacker who sees your streams as they leave an exit node from
12 linking your sessions to one another. To do this, choose some way
13 to distinguish the applications: have them connect to different
14 SocksPorts, or have one of them use SOCKS4 while the other uses
15 SOCKS5, or have them pass different authentication strings to the
16 SOCKS proxy. Then, use the new SocksPort syntax to configure the
17 degree of isolation you need. This implements Proposal 171.
18 - There's a new syntax for specifying multiple client ports (such as
19 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
20 multiple *Port entries with full addr:port syntax on each.
21 The old *ListenAddress format is still supported, but you can't
22 mix it with the new *Port syntax.
24 o Major features (other):
25 - Enable microdescriptor fetching by default for clients. This allows
26 clients to download a much smaller amount of directory information.
27 To disable it (and go back to the old-style consensus and
28 descriptors), set "UseMicrodescriptors 0" in your torrc file.
29 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
30 "PortForwarding" config option), now supports Windows.
31 - When using an exit relay running 0.2.3.x, clients can now
32 "optimistically" send data before the exit relay reports that
33 the stream has opened. This saves a round trip when starting
34 connections where the client speaks first (such as web browsing).
35 This behavior is controlled by a consensus parameter (currently
36 disabled). To turn it on or off manually, use the "OptimisticData"
37 torrc option. Implements proposal 181; code by Ian Goldberg.
39 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
40 - When using IOCP on Windows, we need to enable Libevent windows
42 - The IOCP backend now works even when the user has not specified
43 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
44 Fixes part of bug 3752.
45 - Correctly record the bytes we've read and written when using
46 bufferevents, so that we can include them in our bandwidth history
47 and advertised bandwidth. Fixes bug 3803.
48 - Apply rate-limiting only at the bottom of a chain of filtering
49 bufferevents. This prevents us from filling up internal read
50 buffers and violating rate-limits when filtering bufferevents
51 are enabled. Fixes part of bug 3804.
52 - Add high-watermarks to the output buffers for filtered
53 bufferevents. This prevents us from filling up internal write
54 buffers and wasting CPU cycles when filtering bufferevents are
55 enabled. Fixes part of bug 3804.
56 - Correctly notice when data has been written from a bufferevent
57 without flushing it completely. Fixes bug 3805.
58 - Fix a bug where server-side tunneled bufferevent-based directory
59 streams would get closed prematurely. Fixes bug 3814.
60 - Fix a use-after-free error with per-connection rate-limiting
61 buckets. Fixes bug 3888.
63 o Major bugfixes (also part of 0.2.2.31-rc):
64 - If we're configured to write our ControlPorts to disk, only write
65 them after switching UID and creating the data directory. This way,
66 we don't fail when starting up with a nonexistent DataDirectory
67 and a ControlPortWriteToFile setting based on that directory. Fixes
68 bug 3747; bugfix on Tor 0.2.2.26-beta.
71 - Added a new CONF_CHANGED event so that controllers can be notified
72 of any configuration changes made by other controllers, or by the
73 user. Implements ticket 1692.
74 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
75 leak when using bufferevents, and lets Libevent worry about how to
76 best copy data out of a buffer.
77 - Replace files in stats/ rather than appending to them. Now that we
78 include statistics in extra-info descriptors, it makes no sense to
79 keep old statistics forever. Implements ticket 2930.
81 o Minor features (build compatibility):
82 - Limited, experimental support for building with nmake and MSVC.
83 - Provide a substitute implementation of lround() for MSVC, which
84 apparently lacks it. Patch from Gisle Vanem.
86 o Minor features (also part of 0.2.2.31-rc):
87 - Update to the August 2 2011 Maxmind GeoLite Country database.
89 o Minor bugfixes (on 0.2.3.x-alpha):
90 - Fix a spurious warning when parsing SOCKS requests with
91 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
92 - Get rid of a harmless warning that could happen on relays running
93 with bufferevents. The warning was caused by someone doing an http
94 request to a relay's orport. Also don't warn for a few related
95 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
97 o Minor bugfixes (on 2.2.x and earlier):
98 - The "--quiet" and "--hush" options now apply not only to Tor's
99 behavior before logs are configured, but also to Tor's behavior in
100 the absense of configured logs. Fixes bug 3550; bugfix on
103 o Minor bugfixes (also part of 0.2.2.31-rc):
104 - Write several files in text mode, on OSes that distinguish text
105 mode from binary mode (namely, Windows). These files are:
106 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
107 that collect those statistics; 'client_keys' and 'hostname' for
108 hidden services that use authentication; and (in the tor-gencert
109 utility) newly generated identity and signing keys. Previously,
110 we wouldn't specify text mode or binary mode, leading to an
111 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
112 the DirRecordUsageByCountry option which would have triggered
113 the assertion failure was added), although this assertion failure
114 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
115 - Selectively disable deprecation warnings on OS X because Lion
116 started deprecating the shipped copy of openssl. Fixes bug 3643.
117 - Remove an extra pair of quotation marks around the error
118 message in control-port STATUS_GENERAL BUG events. Bugfix on
119 0.1.2.6-alpha; fixes bug 3732.
120 - When unable to format an address as a string, report its value
121 as "???" rather than reusing the last formatted address. Bugfix
124 o Code simplifications and refactoring:
125 - Rewrite the listener-selection logic so that parsing which ports
126 we want to listen on is now separate from binding to the ports
130 - Building Tor with bufferevent support now requires Libevent
131 2.0.13-stable or later. Previous versions of Libevent had bugs in
132 SSL-related bufferevents and related issues that would make Tor
133 work badly with bufferevents. Requiring 2.0.13-stable also allows
134 Tor with bufferevents to take advantage of Libevent APIs
135 introduced after 2.0.8-rc.
138 Changes in version 0.2.2.32 - 2011-08-27
139 The Tor 0.2.2 release series is dedicated to the memory of Andreas
140 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
141 a founder of the PETS community, a leader in our field, a mentor,
142 and a friend. He left us with these words: "I had the possibility
143 to contribute to this world that is not as it should be. I hope I
144 could help in some areas to make the world a better place, and that
145 I could also encourage other people to be engaged in improving the
146 world. Please, stay engaged. This world needs you, your love, your
147 initiative -- now I cannot be part of that anymore."
149 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
150 ready. More than two years in the making, this release features improved
151 client performance and hidden service reliability, better compatibility
152 for Android, correct behavior for bridges that listen on more than
153 one address, more extensible and flexible directory object handling,
154 better reporting of network statistics, improved code security, and
155 many many other features and bugfixes.
158 Changes in version 0.2.2.31-rc - 2011-08-17
159 Tor 0.2.2.31-rc is the second and hopefully final release candidate
160 for the Tor 0.2.2.x series.
163 - Remove an extra pair of quotation marks around the error
164 message in control-port STATUS_GENERAL BUG events. Bugfix on
165 0.1.2.6-alpha; fixes bug 3732.
166 - If we're configured to write our ControlPorts to disk, only write
167 them after switching UID and creating the data directory. This way,
168 we don't fail when starting up with a nonexistent DataDirectory
169 and a ControlPortWriteToFile setting based on that directory. Fixes
170 bug 3747; bugfix on Tor 0.2.2.26-beta.
173 - Update to the August 2 2011 Maxmind GeoLite Country database.
176 - Allow GETINFO fingerprint to return a fingerprint even when
177 we have not yet built a router descriptor. Fixes bug 3577;
178 bugfix on 0.2.0.1-alpha.
179 - Write several files in text mode, on OSes that distinguish text
180 mode from binary mode (namely, Windows). These files are:
181 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
182 that collect those statistics; 'client_keys' and 'hostname' for
183 hidden services that use authentication; and (in the tor-gencert
184 utility) newly generated identity and signing keys. Previously,
185 we wouldn't specify text mode or binary mode, leading to an
186 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
187 the DirRecordUsageByCountry option which would have triggered
188 the assertion failure was added), although this assertion failure
189 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
190 - Selectively disable deprecation warnings on OS X because Lion
191 started deprecating the shipped copy of openssl. Fixes bug 3643.
192 - When unable to format an address as a string, report its value
193 as "???" rather than reusing the last formatted address. Bugfix
197 Changes in version 0.2.3.2-alpha - 2011-07-18
198 Tor 0.2.3.2-alpha introduces two new experimental features:
199 microdescriptors and pluggable transports. It also continues cleaning
200 up a variety of recently introduced features.
203 - Clients can now use microdescriptors instead of regular descriptors
204 to build circuits. Microdescriptors are authority-generated
205 summaries of regular descriptors' contents, designed to change
206 very rarely (see proposal 158 for details). This feature is
207 designed to save bandwidth, especially for clients on slow internet
208 connections. It's off by default for now, since nearly no caches
209 support it, but it will be on-by-default for clients in a future
210 version. You can use the UseMicrodescriptors option to turn it on.
211 - Tor clients using bridges can now be configured to use a separate
212 'transport' proxy for each bridge. This approach helps to resist
213 censorship by allowing bridges to use protocol obfuscation
214 plugins. It implements part of proposal 180. Implements ticket 2841.
215 - While we're trying to bootstrap, record how many TLS connections
216 fail in each state, and report which states saw the most failures
217 in response to any bootstrap failures. This feature may speed up
218 diagnosis of censorship events. Implements ticket 3116.
220 o Major bugfixes (on 0.2.3.1-alpha):
221 - When configuring a large set of nodes in EntryNodes (as with
222 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
223 random subset to be guards, and choose them in random
224 order. Fixes bug 2798.
225 - Tor could crash when remembering a consensus in a non-used consensus
226 flavor without having a current consensus set. Fixes bug 3361.
227 - Comparing an unknown address to a microdescriptor's shortened exit
228 policy would always give a "rejected" result. Fixes bug 3599.
229 - Using microdescriptors as a client no longer prevents Tor from
230 uploading and downloading hidden service descriptors. Fixes
234 - Allow nameservers with IPv6 address. Resolves bug 2574.
235 - Accept attempts to include a password authenticator in the
236 handshake, as supported by SOCKS5. This handles SOCKS clients that
237 don't know how to omit a password when authenticating. Resolves
239 - When configuring a large set of nodes in EntryNodes, and there are
240 enough of them listed as Guard so that we don't need to consider
241 the non-guard entries, prefer the ones listed with the Guard flag.
242 - Check for and recover from inconsistency in the microdescriptor
243 cache. This will make it harder for us to accidentally free a
244 microdescriptor without removing it from the appropriate data
245 structures. Fixes issue 3135; issue noted by "wanoskarnet".
246 - Log SSL state transitions at log level DEBUG, log domain
247 HANDSHAKE. This can be useful for debugging censorship events.
248 Implements ticket 3264.
249 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
250 implements ticket 3439.
252 o Minor bugfixes (on 0.2.3.1-alpha):
253 - Do not free all general-purpose regular descriptors just
254 because microdescriptor use is enabled. Fixes bug 3113.
255 - Correctly link libevent_openssl when --enable-static-libevent
256 is passed to configure. Fixes bug 3118.
257 - Bridges should not complain during their heartbeat log messages that
258 they are unlisted in the consensus: that's more or less the point
259 of being a bridge. Fixes bug 3183.
260 - Report a SIGNAL event to controllers when acting on a delayed
261 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
262 event to the controller if we acted on a SIGNAL NEWNYM command
263 immediately, and otherwise not report a SIGNAL event for the
264 command at all. Fixes bug 3349.
265 - Fix a crash when handling the SIGNAL controller command or
266 reporting ERR-level status events with bufferevents enabled. Found
267 by Robert Ransom. Fixes bug 3367.
268 - Always ship the tor-fw-helper manpage in our release tarballs.
269 Fixes bug 3389. Reported by Stephen Walker.
270 - Fix a class of double-mark-for-close bugs when bufferevents
271 are enabled. Fixes bug 3403.
272 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
273 - Add SIGNAL to the list returned by the 'GETINFO events/names'
274 control-port command. Fixes part of bug 3465.
275 - Prevent using negative indices during unit test runs when read_all()
276 fails. Spotted by coverity.
277 - Fix a rare memory leak when checking the nodelist without it being
278 present. Found by coverity.
279 - Only try to download a microdescriptor-flavored consensus from
280 a directory cache that provides them.
282 o Minor bugfixes (on 0.2.2.x and earlier):
283 - Assert that hidden-service-related operations are not performed
284 using single-hop circuits. Previously, Tor would assert that
285 client-side streams are not attached to single-hop circuits,
286 but not that other sensitive operations on the client and service
287 side are not performed using single-hop circuits. Fixes bug 3332;
289 - Don't publish a new relay descriptor when we reload our onion key,
290 unless the onion key has actually changed. Fixes bug 3263 and
291 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
292 - Allow GETINFO fingerprint to return a fingerprint even when
293 we have not yet built a router descriptor. Fixes bug 3577;
294 bugfix on 0.2.0.1-alpha.
295 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
296 on 0.2.2.4-alpha; fixes bug 3427.
298 o Code simplification and refactoring:
299 - Use tor_sscanf() in place of scanf() in more places through the
300 code. This makes us a little more locale-independent, and
301 should help shut up code-analysis tools that can't tell
302 a safe sscanf string from a dangerous one.
303 - Use tt_assert(), not tor_assert(), for checking for test failures.
304 This makes the unit tests more able to go on in the event that
306 - Split connection_about_to_close() into separate functions for each
310 - On Windows, we now define the _WIN32_WINNT macros only if they
311 are not already defined. This lets the person building Tor decide,
312 if they want, to require a later version of Windows.
315 Changes in version 0.2.2.30-rc - 2011-07-07
316 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
317 series. It fixes a few smaller bugs, but generally appears stable.
318 Please test it and let us know whether it is!
321 - Send a SUCCEEDED stream event to the controller when a reverse
322 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
323 discovered by katmagic.
324 - Always NUL-terminate the sun_path field of a sockaddr_un before
325 passing it to the kernel. (Not a security issue: kernels are
326 smart enough to reject bad sockaddr_uns.) Found by Coverity;
327 CID #428. Bugfix on Tor 0.2.0.3-alpha.
328 - Don't stack-allocate the list of supplementary GIDs when we're
329 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
330 could take up to 256K, which is way too much stack. Found by
331 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
332 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
333 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
334 fixes part of bug 3465.
335 - Fix a memory leak when receiving a descriptor for a hidden
336 service we didn't ask for. Found by Coverity; CID #30. Bugfix
340 - Update to the July 1 2011 Maxmind GeoLite Country database.
343 Changes in version 0.2.2.29-beta - 2011-06-20
344 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
345 have bridge lines in their torrc but don't want to use them; gets
346 us closer to having the control socket feature working on Debian;
347 and fixes a variety of smaller bugs.
350 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
351 When we changed the default behavior to "use bridges if any
352 are listed in the torrc", we surprised users who had bridges
353 in their torrc files but who didn't actually want to use them.
354 Partial resolution for bug 3354.
357 - Don't attach new streams to old rendezvous circuits after SIGNAL
358 NEWNYM. Previously, we would keep using an existing rendezvous
359 circuit if it remained open (i.e. if it were kept open by a
360 long-lived stream, or if a new stream were attached to it before
361 Tor could notice that it was old and no longer in use). Bugfix on
362 0.1.1.15-rc; fixes bug 3375.
365 - Fix a bug when using ControlSocketsGroupWritable with User. The
366 directory's group would be checked against the current group, not
367 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
368 bugfix on 0.2.2.26-beta.
369 - Make connection_printf_to_buf()'s behaviour sane. Its callers
370 expect it to emit a CRLF iff the format string ends with CRLF;
371 it actually emitted a CRLF iff (a) the format string ended with
372 CRLF or (b) the resulting string was over 1023 characters long or
373 (c) the format string did not end with CRLF *and* the resulting
374 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
375 fixes part of bug 3407.
376 - Make send_control_event_impl()'s behaviour sane. Its callers
377 expect it to always emit a CRLF at the end of the string; it
378 might have emitted extra control characters as well. Bugfix on
379 0.1.1.9-alpha; fixes another part of bug 3407.
380 - Make crypto_rand_int() check the value of its input correctly.
381 Previously, it accepted values up to UINT_MAX, but could return a
382 negative number if given a value above INT_MAX+1. Found by George
383 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
384 - Avoid a segfault when reading a malformed circuit build state
385 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
387 - When asked about a DNS record type we don't support via a
388 client DNSPort, reply with NOTIMPL rather than an empty
389 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
390 - Fix a rare memory leak during stats writing. Found by coverity.
393 - Update to the June 1 2011 Maxmind GeoLite Country database.
395 o Code simplifications and refactoring:
396 - Remove some dead code as indicated by coverity.
397 - Remove a few dead assignments during router parsing. Found by
399 - Add some forgotten return value checks during unit tests. Found
401 - Don't use 1-bit wide signed bit fields. Found by coverity.
404 Changes in version 0.2.2.28-beta - 2011-06-04
405 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
406 fixed a big bug in whether relays stay in the consensus consistently,
407 we moved closer to handling bridges and hidden services correctly,
408 and we started the process of better handling the dreaded "my Vidalia
409 died, and now my Tor demands a password when I try to reconnect to it"
413 - Don't decide to make a new descriptor when receiving a HUP signal.
414 This bug has caused a lot of 0.2.2.x relays to disappear from the
415 consensus periodically. Fixes the most common case of triggering
416 bug 1810; bugfix on 0.2.2.7-alpha.
417 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
418 - Don't try to build descriptors if "ORPort auto" is set and we
419 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
421 - Resolve a crash that occurred when setting BridgeRelay to 1 with
422 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
423 - Apply circuit timeouts to opened hidden-service-related circuits
424 based on the correct start time. Previously, we would apply the
425 circuit build timeout based on time since the circuit's creation;
426 it was supposed to be applied based on time since the circuit
427 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
428 - Use the same circuit timeout for client-side introduction
429 circuits as for other four-hop circuits, rather than the timeout
430 for single-hop directory-fetch circuits; the shorter timeout may
431 have been appropriate with the static circuit build timeout in
432 0.2.1.x and earlier, but caused many hidden service access attempts
433 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
434 on 0.2.2.2-alpha; fixes another part of bug 1297.
435 - In ticket 2511 we fixed a case where you could use an unconfigured
436 bridge if you had configured it as a bridge the last time you ran
437 Tor. Now fix another edge case: if you had configured it as a bridge
438 but then switched to a different bridge via the controller, you
439 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
443 - Add an __OwningControllerProcess configuration option and a
444 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
445 that when it exits, Tor will shut down. Implements feature 3049.
446 - If "UseBridges 1" is set and no bridges are configured, Tor will
447 now refuse to build any circuits until some bridges are set.
448 If "UseBridges auto" is set, Tor will use bridges if they are
449 configured and we are not running as a server, but otherwise will
450 make circuits as usual. The new default is "auto". Patch by anonym,
451 so the Tails LiveCD can stop automatically revealing you as a Tor
455 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
456 - Remove a trailing asterisk from "exit-policy/default" in the
457 output of the control port command "GETINFO info/names". Bugfix
459 - Use a wide type to hold sockets when built for 64-bit Windows builds.
461 - Warn when the user configures two HiddenServiceDir lines that point
462 to the same directory. Bugfix on 0.0.6 (the version introducing
463 HiddenServiceDir); fixes bug 3289.
464 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
465 part of bug 2748; bugfix on 0.2.0.10-alpha.
466 - Log malformed requests for rendezvous descriptors as protocol
467 warnings, not warnings. Also, use a more informative log message
468 in case someone sees it at log level warning without prior
469 info-level messages. Fixes the other part of bug 2748; bugfix
471 - Clear the table recording the time of the last request for each
472 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
473 Previously, we would clear our HS descriptor cache on SIGNAL
474 NEWNYM, but if we had previously retrieved a descriptor (or tried
475 to) from every directory responsible for it, we would refuse to
476 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
478 - Fix a log message that said "bits" while displaying a value in
479 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
481 - When checking for 1024-bit keys, check for 1024 bits, not 128
482 bytes. This allows Tor to correctly discard keys of length 1017
483 through 1023. Bugfix on 0.0.9pre5.
486 - Relays now log the reason for publishing a new relay descriptor,
487 so we have a better chance of hunting down instances of bug 1810.
488 Resolves ticket 3252.
489 - Revise most log messages that refer to nodes by nickname to
490 instead use the "$key=nickname at address" format. This should be
491 more useful, especially since nicknames are less and less likely
492 to be unique. Resolves ticket 3045.
493 - Log (at info level) when purging pieces of hidden-service-client
494 state because of SIGNAL NEWNYM.
497 - Remove undocumented option "-F" from tor-resolve: it hasn't done
498 anything since 0.2.1.16-rc.
501 Changes in version 0.2.2.27-beta - 2011-05-18
502 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
503 release, and also adds a few more general bugfixes.
506 - Fix a crash bug when changing bridges in a running Tor process.
507 Fixes bug 3213; bugfix on 0.2.2.26-beta.
508 - When the controller configures a new bridge, don't wait 10 to 60
509 seconds before trying to fetch its descriptor. Bugfix on
510 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
513 - Require that onion keys have exponent 65537 in microdescriptors too.
514 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
515 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
516 Changed the limit to 512 characters by removing base64 newlines.
517 Fixes bug 2752. Fix by Michael Yakubovich.
518 - When a client starts or stops using bridges, never use a circuit
519 that was built before the configuration change. This behavior could
520 put at risk a user who uses bridges to ensure that her traffic
521 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
525 Changes in version 0.2.2.26-beta - 2011-05-17
526 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
527 also introduces a new "socksport auto" approach that should make it
528 easier to run multiple Tors on the same system, and does a lot of
529 cleanup to get us closer to a release candidate.
531 o Security/privacy fixes:
532 - Replace all potentially sensitive memory comparison operations
533 with versions whose runtime does not depend on the data being
534 compared. This will help resist a class of attacks where an
535 adversary can use variations in timing information to learn
536 sensitive data. Fix for one case of bug 3122. (Safe memcmp
537 implementation by Robert Ransom based partially on code by DJB.)
538 - When receiving a hidden service descriptor, check that it is for
539 the hidden service we wanted. Previously, Tor would store any
540 hidden service descriptors that a directory gave it, whether it
541 wanted them or not. This wouldn't have let an attacker impersonate
542 a hidden service, but it did let directories pre-seed a client
543 with descriptors that it didn't want. Bugfix on 0.0.6.
544 - On SIGHUP, do not clear out all TrackHostExits mappings, client
545 DNS cache entries, and virtual address mappings: that's what
546 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
549 - The options SocksPort, ControlPort, and so on now all accept a
550 value "auto" that opens a socket on an OS-selected port. A
551 new ControlPortWriteToFile option tells Tor to write its
552 actual control port or ports to a chosen file. If the option
553 ControlPortFileGroupReadable is set, the file is created as
554 group-readable. Now users can run two Tor clients on the same
555 system without needing to manually mess with parameters. Resolves
557 - Set SO_REUSEADDR on all sockets, not just listeners. This should
558 help busy exit nodes avoid running out of useable ports just
559 because all the ports have been used in the near past. Resolves
563 - New "GETINFO net/listeners/(type)" controller command to return
564 a list of addresses and ports that are bound for listeners for a
565 given connection type. This is useful when the user has configured
566 "SocksPort auto" and the controller needs to know which port got
567 chosen. Resolves another part of ticket 3076.
568 - Add a new ControlSocketsGroupWritable configuration option: when
569 it is turned on, ControlSockets are group-writeable by the default
570 group of the current user. Patch by Jérémy Bobbio; implements
572 - Tor now refuses to create a ControlSocket in a directory that is
573 world-readable (or group-readable if ControlSocketsGroupWritable
574 is 0). This is necessary because some operating systems do not
575 enforce permissions on an AF_UNIX sockets. Permissions on the
576 directory holding the socket, however, seems to work everywhere.
577 - Rate-limit a warning about failures to download v2 networkstatus
578 documents. Resolves part of bug 1352.
579 - Backport code from 0.2.3.x that allows directory authorities to
580 clean their microdescriptor caches. Needed to resolve bug 2230.
581 - When an HTTPS proxy reports "403 Forbidden", we now explain
582 what it means rather than calling it an unexpected status code.
583 Closes bug 2503. Patch from Michael Yakubovich.
584 - Update to the May 1 2011 Maxmind GeoLite Country database.
587 - Authorities now clean their microdesc cache periodically and when
588 reading from disk initially, not only when adding new descriptors.
589 This prevents a bug where we could lose microdescriptors. Bugfix
590 on 0.2.2.6-alpha. Fixes bug 2230.
591 - Do not crash when our configuration file becomes unreadable, for
592 example due to a permissions change, between when we start up
593 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
595 - Avoid a bug that would keep us from replacing a microdescriptor
596 cache on Windows. (We would try to replace the file while still
597 holding it open. That's fine on Unix, but Windows doesn't let us
598 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
599 - Add missing explanations for the authority-related torrc options
600 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
601 man page. Resolves issue 2379.
602 - As an authority, do not upload our own vote or signature set to
603 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
604 it would get flagged as a duplicate. Resolves bug 3026.
605 - Accept hidden service descriptors if we think we might be a hidden
606 service directory, regardless of what our consensus says. This
607 helps robustness, since clients and hidden services can sometimes
608 have a more up-to-date view of the network consensus than we do,
609 and if they think that the directory authorities list us a HSDir,
610 we might actually be one. Related to bug 2732; bugfix on
612 - When a controller changes TrackHostExits, remove mappings for
613 hosts that should no longer have their exits tracked. Bugfix on
615 - When a controller changes VirtualAddrNetwork, remove any mappings
616 for hosts that were automapped to the old network. Bugfix on
618 - When a controller changes one of the AutomapHosts* options, remove
619 any mappings for hosts that should no longer be automapped. Bugfix
621 - Do not reset the bridge descriptor download status every time we
622 re-parse our configuration or get a configuration change. Fixes
623 bug 3019; bugfix on 0.2.0.3-alpha.
625 o Minor bugfixes (code cleanup):
626 - When loading the microdesc journal, remember its current size.
627 In 0.2.2, this helps prevent the microdesc journal from growing
628 without limit on authorities (who are the only ones to use it in
629 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
630 Fix posted by "cypherpunks."
631 - The microdesc journal is supposed to get rebuilt only if it is
632 at least _half_ the length of the store, not _twice_ the length
633 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
634 - Fix a potential null-pointer dereference while computing a
635 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
637 - Avoid a possible null-pointer dereference when rebuilding the mdesc
638 cache without actually having any descriptors to cache. Bugfix on
639 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
640 - If we fail to compute the identity digest of a v3 legacy keypair,
641 warn, and don't use a buffer-full of junk instead. Bugfix on
642 0.2.1.1-alpha; fixes bug 3106.
643 - Resolve an untriggerable issue in smartlist_string_num_isin(),
644 where if the function had ever in the future been used to check
645 for the presence of a too-large number, it would have given an
646 incorrect result. (Fortunately, we only used it for 16-bit
647 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
648 - Require that introduction point keys and onion handshake keys
649 have a public exponent of 65537. Starts to fix bug 3207; bugfix
653 - Caches no longer download and serve v2 networkstatus documents
654 unless FetchV2Networkstatus flag is set: these documents haven't
655 haven't been used by clients or relays since 0.2.0.x. Resolves
659 Changes in version 0.2.3.1-alpha - 2011-05-05
660 Tor 0.2.3.1-alpha adds some new experimental features, including support
661 for an improved network IO backend, IOCP networking on Windows,
662 microdescriptor caching, "fast-start" support for streams, and automatic
663 home router configuration. There are also numerous internal improvements
664 to try to make the code easier for developers to work with.
666 This is the first alpha release in a new series, so expect there to be
667 bugs. Users who would rather test out a more stable branch should
668 stay with 0.2.2.x for now.
671 - Tor can now optionally build with the "bufferevents" buffered IO
672 backend provided by Libevent 2. To use this feature, make sure you
673 have the latest possible version of Libevent, and pass the
674 --enable-bufferevents flag to configure when building Tor from
675 source. This feature will make our networking code more flexible,
676 let us stack layers on each other, and let us use more efficient
677 zero-copy transports where available.
678 - As an experimental feature, Tor can use IOCP for networking on Windows.
679 Once this code is tuned and optimized, it promises much better
680 performance than the select-based backend we've used in the past. To
681 try this feature, you must build Tor with Libevent 2, configure Tor
682 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
683 your torrc. There are known bugs here: only try this if you can help
684 debug it as it breaks.
685 - The EntryNodes option can now include country codes like {de} or IP
686 addresses or network masks. Previously we had disallowed these options
687 because we didn't have an efficient way to keep the list up to
688 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
689 - Exit nodes now accept and queue data on not-yet-connected streams.
690 Previously, the client wasn't allowed to send data until the stream was
691 connected, which slowed down all connections. This change will enable
692 clients to perform a "fast-start" on streams and send data without
693 having to wait for a confirmation that the stream has opened. (Patch
694 from Ian Goldberg; implements the server side of Proposal 174.)
695 - Tor now has initial support for automatic port mapping on the many
696 home routers that support NAT-PMP or UPnP. (Not yet supported on
697 Windows). To build the support code, you'll need to have libnatpnp
698 library and/or the libminiupnpc library, and you'll need to enable the
699 feature specifically by passing "--enable-upnp" and/or
700 "--enable-natpnp" to configure. To turn it on, use the new
701 PortForwarding option.
702 - Caches now download, cache, and serve multiple "flavors" of the
703 consensus, including a flavor that describes microdescriptors.
704 - Caches now download, cache, and serve microdescriptors -- small
705 summaries of router descriptors that are authenticated by all of the
706 directory authorities. Once enough caches are running this code,
707 clients will be able to save significant amounts of directory bandwidth
708 by downloading microdescriptors instead of router descriptors.
711 - Make logging resolution configurable with a new LogTimeGranularity
712 option, and change the default from 1 millisecond to 1 second.
713 Implements enhancement 1668.
714 - We log which torrc file we're using on startup. Implements ticket
716 - Ordinarily, Tor does not count traffic from private addresses (like
717 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
718 There is now a new option, CountPrivateBandwidth, to disable this
719 behavior. Patch from Daniel Cagara.
720 - New --enable-static-tor configure option for building Tor as
721 statically as possible. Idea, general hackery and thoughts from
722 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
724 - If you set the NumCPUs option to 0, Tor will now try to detect how
725 many CPUs you have. This is the new default behavior.
726 - Turn on directory request statistics by default and include them in
727 extra-info descriptors. Don't break if we have no GeoIP database.
728 - Relays that set "ConnDirectionStatistics 1" write statistics on the
729 bidirectional use of connections to disk every 24 hours.
730 - Add a GeoIP file digest to the extra-info descriptor. Implements
732 - The NodeFamily option -- which let you declare that you want to
733 consider nodes to be part of a family whether they list themselves
734 that way or not -- now allows IP address ranges and country codes.
735 - Add a new 'Heartbeat' log message type to periodically log a message
736 describing Tor's status at level Notice. This feature is meant for
737 operators who log at notice, and want to make sure that their Tor
738 server is still working. Implementation by George Kadianakis.
740 o Minor bugfixes (on 0.2.2.25-alpha):
741 - When loading the microdesc journal, remember its current size.
742 In 0.2.2, this helps prevent the microdesc journal from growing
743 without limit on authorities (who are the only ones to use it in
744 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
745 Fix posted by "cypherpunks."
746 - The microdesc journal is supposed to get rebuilt only if it is
747 at least _half_ the length of the store, not _twice_ the length
748 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
749 - If as an authority we fail to compute the identity digest of a v3
750 legacy keypair, warn, and don't use a buffer-full of junk instead.
751 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
752 - Authorities now clean their microdesc cache periodically and when
753 reading from disk initially, not only when adding new descriptors.
754 This prevents a bug where we could lose microdescriptors. Bugfix
757 o Minor features (controller):
758 - Add a new SIGNAL event to the controller interface so that
759 controllers can be notified when Tor handles a signal. Resolves
760 issue 1955. Patch by John Brooks.
761 - Add a new GETINFO option to get total bytes read and written. Patch
762 from pipe, revised by atagar. Resolves ticket 2345.
763 - Implement some GETINFO controller fields to provide information about
764 the Tor process's pid, euid, username, and resource limits.
767 - Our build system requires automake 1.6 or later to create the
768 Makefile.in files. Previously, you could have used 1.4.
769 This only affects developers and people building Tor from git;
770 people who build Tor from the source distribution without changing
771 the Makefile.am files should be fine.
772 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
773 so on. This is more robust against some of the failure modes
774 associated with running the autotools pieces on their own.
776 o Minor packaging issues:
777 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
778 already created. Patch from Andreas Stieger. Fixes bug 2573.
780 o Code simplifications and refactoring:
781 - A major revision to our internal node-selecting and listing logic.
782 Tor already had at least two major ways to look at the question of
783 "which Tor servers do we know about": a list of router descriptors,
784 and a list of entries in the current consensus. With
785 microdescriptors, we're adding a third. Having so many systems
786 without an abstraction layer over them was hurting the codebase.
787 Now, we have a new "node_t" abstraction that presents a consistent
788 interface to a client's view of a Tor node, and holds (nearly) all
789 of the mutable state formerly in routerinfo_t and routerstatus_t.
790 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
791 no longer link against Libevent: they never used it, but
792 our library structure used to force them to link it.
795 - Remove some old code to work around even older versions of Tor that
796 used forked processes to handle DNS requests. Such versions of Tor
797 are no longer in use as servers.
799 o Documentation fixes:
800 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
801 - Add missing documentation for the authority-related torrc options
802 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
806 Changes in version 0.2.2.25-alpha - 2011-04-29
807 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
808 robust, routers no longer overreport their bandwidth, Win7 should crash
809 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
810 now prevents hidden service-related activity from being linkable. It
811 provides more information to Vidalia so you can see if your bridge is
812 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
813 StrictNodes configuration options to make them more reliable, more
814 understandable, and more regularly applied. If you use those options,
815 please see the revised documentation for them in the manual page.
818 - Relays were publishing grossly inflated bandwidth values because
819 they were writing their state files wrong--now they write the
820 correct value. Also, resume reading bandwidth history from the
821 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
822 - Improve hidden service robustness: When we find that we have
823 extended a hidden service's introduction circuit to a relay not
824 listed as an introduction point in the HS descriptor we currently
825 have, retry with an introduction point from the current
826 descriptor. Previously we would just give up. Fixes bugs 1024 and
827 1930; bugfix on 0.2.0.10-alpha.
828 - Clients now stop trying to use an exit node associated with a given
829 destination by TrackHostExits if they fail to reach that exit node.
830 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
831 - Fix crash bug on platforms where gmtime and localtime can return
832 NULL. Windows 7 users were running into this one. Fixes part of bug
833 2077. Bugfix on all versions of Tor. Found by boboper.
835 o Security and stability fixes:
836 - Don't double-free a parsable, but invalid, microdescriptor, even if
837 it is followed in the blob we're parsing by an unparsable
838 microdescriptor. Fixes an issue reported in a comment on bug 2954.
839 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
840 - If the Nickname configuration option isn't given, Tor would pick a
841 nickname based on the local hostname as the nickname for a relay.
842 Because nicknames are not very important in today's Tor and the
843 "Unnamed" nickname has been implemented, this is now problematic
844 behavior: It leaks information about the hostname without being
845 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
846 introduced the Unnamed nickname. Reported by tagnaq.
847 - Fix an uncommon assertion failure when running with DNSPort under
848 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
849 - Avoid linkability based on cached hidden service descriptors: forget
850 all hidden service descriptors cached as a client when processing a
851 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
854 - Export GeoIP information on bridge usage to controllers even if we
855 have not yet been running for 24 hours. Now Vidalia bridge operators
856 can get more accurate and immediate feedback about their
857 contributions to the network.
859 o Major features and bugfixes (node selection):
860 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
861 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
862 options. Previously, we had been ambiguous in describing what
863 counted as an "exit" node, and what operations exactly "StrictNodes
864 0" would permit. This created confusion when people saw nodes built
865 through unexpected circuits, and made it hard to tell real bugs from
866 surprises. Now the intended behavior is:
867 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
868 a node that delivers user traffic outside the Tor network.
869 . "Entry", in the context of EntryNodes, means a node used as the
870 first hop of a multihop circuit. It doesn't include direct
871 connections to directory servers.
872 . "ExcludeNodes" applies to all nodes.
873 . "StrictNodes" changes the behavior of ExcludeNodes only. When
874 StrictNodes is set, Tor should avoid all nodes listed in
875 ExcludeNodes, even when it will make user requests fail. When
876 StrictNodes is *not* set, then Tor should follow ExcludeNodes
877 whenever it can, except when it must use an excluded node to
878 perform self-tests, connect to a hidden service, provide a
879 hidden service, fulfill a .exit request, upload directory
880 information, or fetch directory information.
881 Collectively, the changes to implement the behavior fix bug 1090.
882 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
883 a node is listed in both, it's treated as excluded.
884 - ExcludeNodes now applies to directory nodes -- as a preference if
885 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
886 Don't exclude all the directory authorities and set StrictNodes to 1
887 unless you really want your Tor to break.
888 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
889 - ExcludeExitNodes now overrides .exit requests.
890 - We don't use bridges listed in ExcludeNodes.
891 - When StrictNodes is 1:
892 . We now apply ExcludeNodes to hidden service introduction points
893 and to rendezvous points selected by hidden service users. This
894 can make your hidden service less reliable: use it with caution!
895 . If we have used ExcludeNodes on ourself, do not try relay
896 reachability self-tests.
897 . If we have excluded all the directory authorities, we will not
898 even try to upload our descriptor if we're a relay.
899 . Do not honor .exit requests to an excluded node.
900 - Remove a misfeature that caused us to ignore the Fast/Stable flags
901 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
902 - When the set of permitted nodes changes, we now remove any mappings
903 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
905 - We never cannibalize a circuit that had excluded nodes on it, even
906 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
907 - Revert a change where we would be laxer about attaching streams to
908 circuits than when building the circuits. This was meant to prevent
909 a set of bugs where streams were never attachable, but our improved
910 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
911 - Keep track of how many times we launch a new circuit to handle a
912 given stream. Too many launches could indicate an inconsistency
913 between our "launch a circuit to handle this stream" logic and our
914 "attach this stream to one of the available circuits" logic.
915 - Improve log messages related to excluded nodes.
918 - Fix a spurious warning when moving from a short month to a long
919 month on relays with month-based BandwidthAccounting. Bugfix on
920 0.2.2.17-alpha; fixes bug 3020.
921 - When a client finds that an origin circuit has run out of 16-bit
922 stream IDs, we now mark it as unusable for new streams. Previously,
923 we would try to close the entire circuit. Bugfix on 0.0.6.
924 - Add a forgotten cast that caused a compile warning on OS X 10.6.
925 Bugfix on 0.2.2.24-alpha.
926 - Be more careful about reporting the correct error from a failed
927 connect() system call. Under some circumstances, it was possible to
928 look at an incorrect value for errno when sending the end reason.
929 Bugfix on 0.1.0.1-rc.
930 - Correctly handle an "impossible" overflow cases in connection byte
931 counting, where we write or read more than 4GB on an edge connection
932 in a single second. Bugfix on 0.1.2.8-beta.
933 - Correct the warning displayed when a rendezvous descriptor exceeds
934 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
936 - Clients and hidden services now use HSDir-flagged relays for hidden
937 service descriptor downloads and uploads even if the relays have no
938 DirPort set and the client has disabled TunnelDirConns. This will
939 eventually allow us to give the HSDir flag to relays with no
940 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
941 - Downgrade "no current certificates known for authority" message from
942 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
943 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
944 2917. Bugfix on 0.1.1.1-alpha.
945 - Only limit the lengths of single HS descriptors, even when multiple
946 HS descriptors are published to an HSDir relay in a single POST
947 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
948 - Write the current time into the LastWritten line in our state file,
949 rather than the time from the previous write attempt. Also, stop
950 trying to use a time of -1 in our log statements. Fixes bug 3039;
951 bugfix on 0.2.2.14-alpha.
952 - Be more consistent in our treatment of file system paths. "~" should
953 get expanded to the user's home directory in the Log config option.
954 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
955 feature for the -f and --DataDirectory options.
958 - Make sure every relay writes a state file at least every 12 hours.
959 Previously, a relay could go for weeks without writing its state
960 file, and on a crash could lose its bandwidth history, capacity
961 estimates, client country statistics, and so on. Addresses bug 3012.
962 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
963 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
964 clients are already deprecated because of security bugs.
965 - Don't allow v0 hidden service authorities to act as clients.
966 Required by fix for bug 3000.
967 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
969 - Ensure that no empty [dirreq-](read|write)-history lines are added
970 to an extrainfo document. Implements ticket 2497.
972 o Code simplification and refactoring:
973 - Remove workaround code to handle directory responses from servers
974 that had bug 539 (they would send HTTP status 503 responses _and_
975 send a body too). Since only server versions before
976 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
977 keep the workaround in place.
978 - Remove the old 'fuzzy time' logic. It was supposed to be used for
979 handling calculations where we have a known amount of clock skew and
980 an allowed amount of unknown skew. But we only used it in three
981 places, and we never adjusted the known/unknown skew values. This is
982 still something we might want to do someday, but if we do, we'll
983 want to do it differently.
984 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
985 None of the cases where we did this before were wrong, but by making
986 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
987 - Use GetTempDir to find the proper temporary directory location on
988 Windows when generating temporary files for the unit tests. Patch by
992 Changes in version 0.2.2.24-alpha - 2011-04-08
993 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
994 prevented Tor clients from effectively using "multihomed" bridges,
995 that is, bridges that listen on multiple ports or IP addresses so users
996 can continue to use some of their addresses even if others get blocked.
999 - Fix a bug where bridge users who configure the non-canonical
1000 address of a bridge automatically switch to its canonical
1001 address. If a bridge listens at more than one address, it should be
1002 able to advertise those addresses independently and any non-blocked
1003 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
1005 - If you configured Tor to use bridge A, and then quit and
1006 configured Tor to use bridge B instead, it would happily continue
1007 to use bridge A if it's still reachable. While this behavior is
1008 a feature if your goal is connectivity, in some scenarios it's a
1009 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
1010 - Directory authorities now use data collected from their own
1011 uptime observations when choosing whether to assign the HSDir flag
1012 to relays, instead of trusting the uptime value the relay reports in
1013 its descriptor. This change helps prevent an attack where a small
1014 set of nodes with frequently-changing identity keys can blackhole
1015 a hidden service. (Only authorities need upgrade; others will be
1016 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
1019 - When we restart our relay, we might get a successful connection
1020 from the outside before we've started our reachability tests,
1021 triggering a warning: "ORPort found reachable, but I have no
1022 routerinfo yet. Failing to inform controller of success." This
1023 bug was harmless unless Tor is running under a controller
1024 like Vidalia, in which case the controller would never get a
1025 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1027 - Make directory authorities more accurate at recording when
1028 relays that have failed several reachability tests became
1029 unreachable, so we can provide more accuracy at assigning Stable,
1030 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
1031 - Fix an issue that prevented static linking of libevent on
1032 some platforms (notably Linux). Fixes bug 2698; bugfix on
1033 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
1034 the --with-static-libevent configure option).
1035 - We now ask the other side of a stream (the client or the exit)
1036 for more data on that stream when the amount of queued data on
1037 that stream dips low enough. Previously, we wouldn't ask the
1038 other side for more data until either it sent us more data (which
1039 it wasn't supposed to do if it had exhausted its window!) or we
1040 had completely flushed all our queued data. This flow control fix
1041 should improve throughput. Fixes bug 2756; bugfix on the earliest
1042 released versions of Tor (svn commit r152).
1043 - Avoid a double-mark-for-free warning when failing to attach a
1044 transparent proxy connection. (We thought we had fixed this in
1045 0.2.2.23-alpha, but it turns out our fix was checking the wrong
1046 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
1047 bug) and 0.2.2.23-alpha (the incorrect fix).
1048 - When warning about missing zlib development packages during compile,
1049 give the correct package names. Bugfix on 0.2.0.1-alpha.
1052 - Directory authorities now log the source of a rejected POSTed v3
1054 - Make compilation with clang possible when using
1055 --enable-gcc-warnings by removing two warning options that clang
1056 hasn't implemented yet and by fixing a few warnings. Implements
1058 - When expiring circuits, use microsecond timers rather than
1059 one-second timers. This can avoid an unpleasant situation where a
1060 circuit is launched near the end of one second and expired right
1061 near the beginning of the next, and prevent fluctuations in circuit
1063 - Use computed circuit-build timeouts to decide when to launch
1064 parallel introduction circuits for hidden services. (Previously,
1065 we would retry after 15 seconds.)
1066 - Update to the April 1 2011 Maxmind GeoLite Country database.
1069 - Create the /var/run/tor directory on startup on OpenSUSE if it is
1070 not already created. Patch from Andreas Stieger. Fixes bug 2573.
1072 o Documentation changes:
1073 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
1074 - Resolve all doxygen warnings except those for missing documentation.
1076 - Add doxygen documentation for more functions, fields, and types.
1079 Changes in version 0.2.2.23-alpha - 2011-03-08
1080 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
1081 they restart they don't lose their bandwidth capacity estimate. This
1082 release also fixes a diverse set of user-facing bugs, ranging from
1083 relays overrunning their rate limiting to clients falsely warning about
1084 clock skew to bridge descriptor leaks by our bridge directory authority.
1087 - Stop sending a CLOCK_SKEW controller status event whenever
1088 we fetch directory information from a relay that has a wrong clock.
1089 Instead, only inform the controller when it's a trusted authority
1090 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
1091 the rest of bug 1074.
1092 - Fix an assert in parsing router descriptors containing IPv6
1093 addresses. This one took down the directory authorities when
1094 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1095 - Make the bridge directory authority refuse to answer directory
1096 requests for "all" descriptors. It used to include bridge
1097 descriptors in its answer, which was a major information leak.
1098 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1099 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
1100 Tor would ignore their RelayBandwidthBurst setting,
1101 potentially using more bandwidth than expected. Bugfix on
1102 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
1103 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
1104 hidserv" in her torrc. The 'hidserv' argument never controlled
1105 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
1108 - Relays now save observed peak bandwidth throughput rates to their
1109 state file (along with total usage, which was already saved)
1110 so that they can determine their correct estimated bandwidth on
1111 restart. Resolves bug 1863, where Tor relays would reset their
1112 estimated bandwidth to 0 after restarting.
1113 - Directory authorities now take changes in router IP address and
1114 ORPort into account when determining router stability. Previously,
1115 if a router changed its IP or ORPort, the authorities would not
1116 treat it as having any downtime for the purposes of stability
1117 calculation, whereas clients would experience downtime since the
1118 change could take a while to propagate to them. Resolves issue 1035.
1119 - Enable Address Space Layout Randomization (ASLR) and Data Execution
1120 Prevention (DEP) by default on Windows to make it harder for
1121 attackers to exploit vulnerabilities. Patch from John Brooks.
1123 o Minor bugfixes (on 0.2.1.x and earlier):
1124 - Fix a rare crash bug that could occur when a client was configured
1125 with a large number of bridges. Fixes bug 2629; bugfix on
1126 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1127 - Avoid a double mark-for-free warning when failing to attach a
1128 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
1130 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
1131 found by "cypherpunks". This bug was introduced before the first
1132 Tor release, in svn commit r110.
1133 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
1134 don't mention them in the manpage. Fixes bug 2450; issue
1135 spotted by keb and G-Lo.
1136 - Fix a bug in bandwidth history state parsing that could have been
1137 triggered if a future version of Tor ever changed the timing
1138 granularity at which bandwidth history is measured. Bugfix on
1140 - When a relay decides that its DNS is too broken for it to serve
1141 as an exit server, it advertised itself as a non-exit, but
1142 continued to act as an exit. This could create accidental
1143 partitioning opportunities for users. Instead, if a relay is
1144 going to advertise reject *:* as its exit policy, it should
1145 really act with exit policy "reject *:*". Fixes bug 2366.
1146 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
1147 - In the special case where you configure a public exit relay as your
1148 bridge, Tor would be willing to use that exit relay as the last
1149 hop in your circuit as well. Now we fail that circuit instead.
1150 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
1151 - Fix a bug with our locking implementation on Windows that couldn't
1152 correctly detect when a file was already locked. Fixes bug 2504,
1153 bugfix on 0.2.1.6-alpha.
1154 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
1155 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
1157 - Set target port in get_interface_address6() correctly. Bugfix
1158 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
1159 - Directory authorities are now more robust to hops back in time
1160 when calculating router stability. Previously, if a run of uptime
1161 or downtime appeared to be negative, the calculation could give
1162 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
1164 - Fix an assert that got triggered when using the TestingTorNetwork
1165 configuration option and then issuing a GETINFO config-text control
1166 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
1168 o Minor bugfixes (on 0.2.2.x):
1169 - Clients should not weight BadExit nodes as Exits in their node
1170 selection. Similarly, directory authorities should not count BadExit
1171 bandwidth as Exit bandwidth when computing bandwidth-weights.
1172 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
1173 - Correctly clear our dir_read/dir_write history when there is an
1174 error parsing any bw history value from the state file. Bugfix on
1176 - Resolve a bug in verifying signatures of directory objects
1177 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
1178 Fixes bug 2409. Found by "piebeer".
1179 - Bridge authorities no longer crash on SIGHUP when they try to
1180 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
1184 - Log less aggressively about circuit timeout changes, and improve
1185 some other circuit timeout messages. Resolves bug 2004.
1186 - Log a little more clearly about the times at which we're no longer
1187 accepting new connections. Resolves bug 2181.
1188 - Reject attempts at the client side to open connections to private
1189 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
1190 a randomly chosen exit node. Attempts to do so are always
1191 ill-defined, generally prevented by exit policies, and usually
1192 in error. This will also help to detect loops in transparent
1193 proxy configurations. You can disable this feature by setting
1194 "ClientRejectInternalAddresses 0" in your torrc.
1195 - Always treat failure to allocate an RSA key as an unrecoverable
1197 - Update to the March 1 2011 Maxmind GeoLite Country database.
1199 o Minor features (log subsystem):
1200 - Add documentation for configuring logging at different severities in
1201 different log domains. We've had this feature since 0.2.1.1-alpha,
1202 but for some reason it never made it into the manpage. Fixes
1204 - Make it simpler to specify "All log domains except for A and B".
1205 Previously you needed to say "[*,~A,~B]". Now you can just say
1207 - Add a "LogMessageDomains 1" option to include the domains of log
1208 messages along with the messages. Without this, there's no way
1209 to use log domains without reading the source or doing a lot
1212 o Packaging changes:
1213 - Stop shipping the Tor specs files and development proposal documents
1214 in the tarball. They are now in a separate git repository at
1215 git://git.torproject.org/torspec.git
1218 Changes in version 0.2.1.30 - 2011-02-23
1219 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
1220 change is a slight tweak to Tor's TLS handshake that makes relays
1221 and bridges that run this new version reachable from Iran again.
1222 We don't expect this tweak will win the arms race long-term, but it
1223 buys us time until we roll out a better solution.
1226 - Stop sending a CLOCK_SKEW controller status event whenever
1227 we fetch directory information from a relay that has a wrong clock.
1228 Instead, only inform the controller when it's a trusted authority
1229 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
1230 the rest of bug 1074.
1231 - Fix a bounds-checking error that could allow an attacker to
1232 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
1234 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
1235 Tor would ignore their RelayBandwidthBurst setting,
1236 potentially using more bandwidth than expected. Bugfix on
1237 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
1238 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
1239 hidserv" in her torrc. The 'hidserv' argument never controlled
1240 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
1243 - Adjust our TLS Diffie-Hellman parameters to match those used by
1245 - Update to the February 1 2011 Maxmind GeoLite Country database.
1248 - Check for and reject overly long directory certificates and
1249 directory tokens before they have a chance to hit any assertions.
1250 Bugfix on 0.2.1.28. Found by "doorss".
1251 - Bring the logic that gathers routerinfos and assesses the
1252 acceptability of circuits into line. This prevents a Tor OP from
1253 getting locked in a cycle of choosing its local OR as an exit for a
1254 path (due to a .exit request) and then rejecting the circuit because
1255 its OR is not listed yet. It also prevents Tor clients from using an
1256 OR running in the same instance as an exit (due to a .exit request)
1257 if the OR does not meet the same requirements expected of an OR
1258 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1260 o Packaging changes:
1261 - Stop shipping the Tor specs files and development proposal documents
1262 in the tarball. They are now in a separate git repository at
1263 git://git.torproject.org/torspec.git
1264 - Do not include Git version tags as though they are SVN tags when
1265 generating a tarball from inside a repository that has switched
1266 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1269 Changes in version 0.2.2.22-alpha - 2011-01-25
1270 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
1271 main other change is a slight tweak to Tor's TLS handshake that makes
1272 relays and bridges that run this new version reachable from Iran again.
1273 We don't expect this tweak will win the arms race long-term, but it
1274 will buy us a bit more time until we roll out a better solution.
1277 - Fix a bounds-checking error that could allow an attacker to
1278 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
1280 - Don't assert when changing from bridge to relay or vice versa
1281 via the controller. The assert happened because we didn't properly
1282 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
1283 bug 2433. Reported by bastik.
1286 - Adjust our TLS Diffie-Hellman parameters to match those used by
1288 - Provide a log message stating which geoip file we're parsing
1289 instead of just stating that we're parsing the geoip file.
1290 Implements ticket 2432.
1293 - Check for and reject overly long directory certificates and
1294 directory tokens before they have a chance to hit any assertions.
1295 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
1298 Changes in version 0.2.2.21-alpha - 2011-01-15
1299 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
1300 continues our recent code security audit work. The main fix resolves
1301 a remote heap overflow vulnerability that can allow remote code
1302 execution (CVE-2011-0427). Other fixes address a variety of assert
1303 and crash bugs, most of which we think are hard to exploit remotely.
1305 o Major bugfixes (security), also included in 0.2.1.29:
1306 - Fix a heap overflow bug where an adversary could cause heap
1307 corruption. This bug probably allows remote code execution
1308 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1310 - Prevent a denial-of-service attack by disallowing any
1311 zlib-compressed data whose compression factor is implausibly
1312 high. Fixes part of bug 2324; reported by "doorss".
1313 - Zero out a few more keys in memory before freeing them. Fixes
1314 bug 2384 and part of bug 2385. These key instances found by
1315 "cypherpunks", based on Andrew Case's report about being able
1316 to find sensitive data in Tor's memory space if you have enough
1317 permissions. Bugfix on 0.0.2pre9.
1319 o Major bugfixes (crashes), also included in 0.2.1.29:
1320 - Prevent calls to Libevent from inside Libevent log handlers.
1321 This had potential to cause a nasty set of crashes, especially
1322 if running Libevent with debug logging enabled, and running
1323 Tor with a controller watching for low-severity log messages.
1324 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1325 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1326 underflow errors there too. Fixes the other part of bug 2324.
1327 - Fix a bug where we would assert if we ever had a
1328 cached-descriptors.new file (or another file read directly into
1329 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1330 on 0.2.1.25. Found by doorss.
1331 - Fix some potential asserts and parsing issues with grossly
1332 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1335 o Minor bugfixes (other), also included in 0.2.1.29:
1336 - Fix a bug with handling misformed replies to reverse DNS lookup
1337 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1338 bug reported by doorss.
1339 - Fix compilation on mingw when a pthreads compatibility library
1340 has been installed. (We don't want to use it, so we shouldn't
1341 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1342 - Fix a bug where we would declare that we had run out of virtual
1343 addresses when the address space was only half-exhausted. Bugfix
1345 - Correctly handle the case where AutomapHostsOnResolve is set but
1346 no virtual addresses are available. Fixes bug 2328; bugfix on
1347 0.1.2.1-alpha. Bug found by doorss.
1348 - Correctly handle wrapping around when we run out of virtual
1349 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
1351 o Minor features, also included in 0.2.1.29:
1352 - Update to the January 1 2011 Maxmind GeoLite Country database.
1353 - Introduce output size checks on all of our decryption functions.
1355 o Build changes, also included in 0.2.1.29:
1356 - Tor does not build packages correctly with Automake 1.6 and earlier;
1357 added a check to Makefile.am to make sure that we're building with
1358 Automake 1.7 or later.
1359 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1360 because we built it with a too-old version of automake. Thus that
1361 release broke ./configure --enable-openbsd-malloc, which is popular
1362 among really fast exit relays on Linux.
1364 o Major bugfixes, new in 0.2.2.21-alpha:
1365 - Prevent crash/heap corruption when the cbtnummodes consensus
1366 parameter is set to 0 or large values. Fixes bug 2317; bugfix
1369 o Major features, new in 0.2.2.21-alpha:
1370 - Introduce minimum/maximum values that clients will believe
1371 from the consensus. Now we'll have a better chance to avoid crashes
1372 or worse when a consensus param has a weird value.
1374 o Minor features, new in 0.2.2.21-alpha:
1375 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
1376 used on bridges, and it makes bridge scanning somewhat easier.
1377 - If writing the state file to disk fails, wait up to an hour before
1378 retrying again, rather than trying again each second. Fixes bug
1379 2346; bugfix on Tor 0.1.1.3-alpha.
1380 - Make Libevent log messages get delivered to controllers later,
1381 and not from inside the Libevent log handler. This prevents unsafe
1382 reentrant Libevent calls while still letting the log messages
1384 - Detect platforms that brokenly use a signed size_t, and refuse to
1385 build there. Found and analyzed by doorss and rransom.
1386 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
1389 o Minor bugfixes, new in 0.2.2.21-alpha:
1390 - Handle SOCKS messages longer than 128 bytes long correctly, rather
1391 than waiting forever for them to finish. Fixes bug 2330; bugfix
1392 on 0.2.0.16-alpha. Found by doorss.
1393 - Add assertions to check for overflow in arguments to
1394 base32_encode() and base32_decode(); fix a signed-unsigned
1395 comparison there too. These bugs are not actually reachable in Tor,
1396 but it's good to prevent future errors too. Found by doorss.
1397 - Correctly detect failures to create DNS requests when using Libevent
1398 versions before v2. (Before Libevent 2, we used our own evdns
1399 implementation. Its return values for Libevent's evdns_resolve_*()
1400 functions are not consistent with those from Libevent.) Fixes bug
1401 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
1403 o Documentation, new in 0.2.2.21-alpha:
1404 - Document the default socks host and port (127.0.0.1:9050) for
1408 Changes in version 0.2.1.29 - 2011-01-15
1409 Tor 0.2.1.29 continues our recent code security audit work. The main
1410 fix resolves a remote heap overflow vulnerability that can allow remote
1411 code execution. Other fixes address a variety of assert and crash bugs,
1412 most of which we think are hard to exploit remotely.
1414 o Major bugfixes (security):
1415 - Fix a heap overflow bug where an adversary could cause heap
1416 corruption. This bug probably allows remote code execution
1417 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
1419 - Prevent a denial-of-service attack by disallowing any
1420 zlib-compressed data whose compression factor is implausibly
1421 high. Fixes part of bug 2324; reported by "doorss".
1422 - Zero out a few more keys in memory before freeing them. Fixes
1423 bug 2384 and part of bug 2385. These key instances found by
1424 "cypherpunks", based on Andrew Case's report about being able
1425 to find sensitive data in Tor's memory space if you have enough
1426 permissions. Bugfix on 0.0.2pre9.
1428 o Major bugfixes (crashes):
1429 - Prevent calls to Libevent from inside Libevent log handlers.
1430 This had potential to cause a nasty set of crashes, especially
1431 if running Libevent with debug logging enabled, and running
1432 Tor with a controller watching for low-severity log messages.
1433 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
1434 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
1435 underflow errors there too. Fixes the other part of bug 2324.
1436 - Fix a bug where we would assert if we ever had a
1437 cached-descriptors.new file (or another file read directly into
1438 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
1439 on 0.2.1.25. Found by doorss.
1440 - Fix some potential asserts and parsing issues with grossly
1441 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
1444 o Minor bugfixes (other):
1445 - Fix a bug with handling misformed replies to reverse DNS lookup
1446 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
1447 bug reported by doorss.
1448 - Fix compilation on mingw when a pthreads compatibility library
1449 has been installed. (We don't want to use it, so we shouldn't
1450 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
1451 - Fix a bug where we would declare that we had run out of virtual
1452 addresses when the address space was only half-exhausted. Bugfix
1454 - Correctly handle the case where AutomapHostsOnResolve is set but
1455 no virtual addresses are available. Fixes bug 2328; bugfix on
1456 0.1.2.1-alpha. Bug found by doorss.
1457 - Correctly handle wrapping around to when we run out of virtual
1458 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
1459 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
1460 because we built it with a too-old version of automake. Thus that
1461 release broke ./configure --enable-openbsd-malloc, which is popular
1462 among really fast exit relays on Linux.
1465 - Update to the January 1 2011 Maxmind GeoLite Country database.
1466 - Introduce output size checks on all of our decryption functions.
1469 - Tor does not build packages correctly with Automake 1.6 and earlier;
1470 added a check to Makefile.am to make sure that we're building with
1471 Automake 1.7 or later.
1474 Changes in version 0.2.2.20-alpha - 2010-12-17
1475 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
1476 exploitable bugs. We also fix a variety of other significant bugs,
1477 change the IP address for one of our directory authorities, and update
1478 the minimum version that Tor relays must run to join the network.
1481 - Fix a remotely exploitable bug that could be used to crash instances
1482 of Tor remotely by overflowing on the heap. Remote-code execution
1483 hasn't been confirmed, but can't be ruled out. Everyone should
1484 upgrade. Bugfix on the 0.1.1 series and later.
1485 - Fix a bug that could break accounting on 64-bit systems with large
1486 time_t values, making them hibernate for impossibly long intervals.
1487 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
1488 - Fix a logic error in directory_fetches_from_authorities() that
1489 would cause all _non_-exits refusing single-hop-like circuits
1490 to fetch from authorities, when we wanted to have _exits_ fetch
1491 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
1493 - Fix a stream fairness bug that would cause newer streams on a given
1494 circuit to get preference when reading bytes from the origin or
1495 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
1496 introduced before the first Tor release, in svn revision r152.
1498 o Directory authority changes:
1499 - Change IP address and ports for gabelmoo (v3 directory authority).
1502 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
1503 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
1504 - Fix an off-by-one error in calculating some controller command
1505 argument lengths. Fortunately, this mistake is harmless since
1506 the controller code does redundant NUL termination too. Found by
1507 boboper. Bugfix on 0.1.1.1-alpha.
1508 - Do not dereference NULL if a bridge fails to build its
1509 extra-info descriptor. Found by an anonymous commenter on
1510 Trac. Bugfix on 0.2.2.19-alpha.
1513 - Update to the December 1 2010 Maxmind GeoLite Country database.
1514 - Directory authorities now reject relays running any versions of
1515 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
1516 known bugs that keep RELAY_EARLY cells from working on rendezvous
1517 circuits. Followup to fix for bug 2081.
1518 - Directory authorities now reject relays running any version of Tor
1519 older than 0.2.0.26-rc. That version is the earliest that fetches
1520 current directory information correctly. Fixes bug 2156.
1521 - Report only the top 10 ports in exit-port stats in order not to
1522 exceed the maximum extra-info descriptor length of 50 KB. Implements
1526 Changes in version 0.2.1.28 - 2010-12-17
1527 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
1528 exploitable bugs. We also took this opportunity to change the IP address
1529 for one of our directory authorities, and to update the geoip database
1533 - Fix a remotely exploitable bug that could be used to crash instances
1534 of Tor remotely by overflowing on the heap. Remote-code execution
1535 hasn't been confirmed, but can't be ruled out. Everyone should
1536 upgrade. Bugfix on the 0.1.1 series and later.
1538 o Directory authority changes:
1539 - Change IP address and ports for gabelmoo (v3 directory authority).
1542 - Update to the December 1 2010 Maxmind GeoLite Country database.
1545 Changes in version 0.2.1.27 - 2010-11-23
1546 Yet another OpenSSL security patch broke its compatibility with Tor:
1547 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
1548 also took this opportunity to fix several crash bugs, integrate a new
1549 directory authority, and update the bundled GeoIP database.
1552 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1553 No longer set the tlsext_host_name extension on server SSL objects;
1554 but continue to set it on client SSL objects. Our goal in setting
1555 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1556 bugfix on 0.2.1.1-alpha.
1557 - Do not log messages to the controller while shrinking buffer
1558 freelists. Doing so would sometimes make the controller connection
1559 try to allocate a buffer chunk, which would mess up the internals
1560 of the freelist and cause an assertion failure. Fixes bug 1125;
1561 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1562 - Learn our external IP address when we're a relay or bridge, even if
1563 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1564 where we introduced bridge relays that don't need to publish to
1565 be useful. Fixes bug 2050.
1566 - Do even more to reject (and not just ignore) annotations on
1567 router descriptors received anywhere but from the cache. Previously
1568 we would ignore such annotations at first, but cache them to disk
1569 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1570 - When you're using bridges and your network goes away and your
1571 bridges get marked as down, recover when you attempt a new socks
1572 connection (if the network is back), rather than waiting up to an
1573 hour to try fetching new descriptors for your bridges. Bugfix on
1574 0.2.0.3-alpha; fixes bug 1981.
1577 - Move to the November 2010 Maxmind GeoLite country db (rather
1578 than the June 2009 ip-to-country GeoIP db) for our statistics that
1579 count how many users relays are seeing from each country. Now we'll
1580 have more accurate data, especially for many African countries.
1582 o New directory authorities:
1583 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
1587 - Fix an assertion failure that could occur in directory caches or
1588 bridge users when using a very short voting interval on a testing
1589 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
1591 - Enforce multiplicity rules when parsing annotations. Bugfix on
1592 0.2.0.8-alpha. Found by piebeer.
1593 - Allow handshaking OR connections to take a full KeepalivePeriod
1594 seconds to handshake. Previously, we would close them after
1595 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1596 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1598 - When building with --enable-gcc-warnings on OpenBSD, disable
1599 warnings in system headers. This makes --enable-gcc-warnings
1600 pass on OpenBSD 4.8.
1603 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
1604 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
1605 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
1606 Servers can start sending this code when enough clients recognize
1607 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
1608 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
1609 Patch from mingw-san.
1612 - Remove the old debian/ directory from the main Tor distribution.
1613 The official Tor-for-debian git repository lives at the URL
1614 https://git.torproject.org/debian/tor.git
1615 - Stop shipping the old doc/website/ directory in the tarball. We
1616 changed the website format in late 2010, and what we shipped in
1617 0.2.1.26 really wasn't that useful anyway.
1620 Changes in version 0.2.2.19-alpha - 2010-11-22
1621 Yet another OpenSSL security patch broke its compatibility with Tor:
1622 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
1625 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
1626 No longer set the tlsext_host_name extension on server SSL objects;
1627 but continue to set it on client SSL objects. Our goal in setting
1628 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
1629 bugfix on 0.2.1.1-alpha.
1632 - Try harder not to exceed the maximum length of 50 KB when writing
1633 statistics to extra-info descriptors. This bug was triggered by very
1634 fast relays reporting exit-port, entry, and dirreq statistics.
1635 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
1636 - Publish a router descriptor even if generating an extra-info
1637 descriptor fails. Previously we would not publish a router
1638 descriptor without an extra-info descriptor; this can cause fast
1639 exit relays collecting exit-port statistics to drop from the
1640 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
1643 Changes in version 0.2.2.18-alpha - 2010-11-16
1644 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
1645 us lately, makes unpublished bridge relays able to detect their IP
1646 address, and fixes a wide variety of other bugs to get us much closer
1647 to a stable release.
1650 - Do even more to reject (and not just ignore) annotations on
1651 router descriptors received anywhere but from the cache. Previously
1652 we would ignore such annotations at first, but cache them to disk
1653 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
1654 - Do not log messages to the controller while shrinking buffer
1655 freelists. Doing so would sometimes make the controller connection
1656 try to allocate a buffer chunk, which would mess up the internals
1657 of the freelist and cause an assertion failure. Fixes bug 1125;
1658 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
1659 - Learn our external IP address when we're a relay or bridge, even if
1660 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
1661 where we introduced bridge relays that don't need to publish to
1662 be useful. Fixes bug 2050.
1663 - Maintain separate TLS contexts and certificates for incoming and
1664 outgoing connections in bridge relays. Previously we would use the
1665 same TLS contexts and certs for incoming and outgoing connections.
1666 Bugfix on 0.2.0.3-alpha; addresses bug 988.
1667 - Maintain separate identity keys for incoming and outgoing TLS
1668 contexts in bridge relays. Previously we would use the same
1669 identity keys for incoming and outgoing TLS contexts. Bugfix on
1670 0.2.0.3-alpha; addresses the other half of bug 988.
1671 - Avoid an assertion failure when we as an authority receive a
1672 duplicate upload of a router descriptor that we already have,
1673 but which we previously considered an obsolete descriptor.
1674 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
1675 - Avoid a crash bug triggered by looking at a dangling pointer while
1676 setting the network status consensus. Found by Robert Ransom.
1677 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
1678 - Fix a logic error where servers that _didn't_ act as exits would
1679 try to keep their server lists more aggressively up to date than
1680 exits, when it was supposed to be the other way around. Bugfix
1683 o Minor bugfixes (on Tor 0.2.1.x and earlier):
1684 - When we're trying to guess whether we know our IP address as
1685 a relay, we would log various ways that we failed to guess
1686 our address, but never log that we ended up guessing it
1687 successfully. Now add a log line to help confused and anxious
1688 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
1689 - Bring the logic that gathers routerinfos and assesses the
1690 acceptability of circuits into line. This prevents a Tor OP from
1691 getting locked in a cycle of choosing its local OR as an exit for a
1692 path (due to a .exit request) and then rejecting the circuit because
1693 its OR is not listed yet. It also prevents Tor clients from using an
1694 OR running in the same instance as an exit (due to a .exit request)
1695 if the OR does not meet the same requirements expected of an OR
1696 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
1697 - Correctly describe errors that occur when generating a TLS object.
1698 Previously we would attribute them to a failure while generating a
1699 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
1701 - Enforce multiplicity rules when parsing annotations. Bugfix on
1702 0.2.0.8-alpha. Found by piebeer.
1703 - Fix warnings that newer versions of autoconf produced during
1704 ./autogen.sh. These warnings appear to be harmless in our case,
1705 but they were extremely verbose. Fixes bug 2020.
1707 o Minor bugfixes (on Tor 0.2.2.x):
1708 - Enable protection of small arrays whenever we build with gcc
1709 hardening features, not only when also building with warnings
1710 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
1713 - Make hidden services work better in private Tor networks by not
1714 requiring any uptime to join the hidden service descriptor
1715 DHT. Implements ticket 2088.
1716 - Rate-limit the "your application is giving Tor only an IP address"
1717 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
1718 - When AllowSingleHopExits is set, print a warning to explain to the
1719 relay operator why most clients are avoiding her relay.
1720 - Update to the November 1 2010 Maxmind GeoLite Country database.
1722 o Code simplifications and refactoring:
1723 - When we fixed bug 1038 we had to put in a restriction not to send
1724 RELAY_EARLY cells on rend circuits. This was necessary as long
1725 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
1726 active. Now remove this obsolete check. Resolves bug 2081.
1727 - Some options used different conventions for uppercasing of acronyms
1728 when comparing manpage and source. Fix those in favor of the
1729 manpage, as it makes sense to capitalize acronyms.
1730 - Remove the torrc.complete file. It hasn't been kept up to date
1731 and users will have better luck checking out the manpage.
1732 - Remove the obsolete "NoPublish" option; it has been flagged
1733 as obsolete and has produced a warning since 0.1.1.18-rc.
1734 - Remove everything related to building the expert bundle for OS X.
1735 It has confused many users, doesn't work right on OS X 10.6,
1736 and is hard to get rid of once installed. Resolves bug 1274.
1739 Changes in version 0.2.2.17-alpha - 2010-09-30
1740 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
1741 to use one-hop circuits (which can put the exit relays at higher risk,
1742 plus unbalance the network); fixes a big bug in bandwidth accounting
1743 for relays that want to limit their monthly bandwidth use; fixes a
1744 big pile of bugs in how clients tolerate temporary network failure;
1745 and makes our adaptive circuit build timeout feature (which improves
1746 client performance if your network is fast while not breaking things
1747 if your network is slow) better handle bad networks.
1750 - Exit relays now try harder to block exit attempts from unknown
1751 relays, to make it harder for people to use them as one-hop proxies
1752 a la tortunnel. Controlled by the refuseunknownexits consensus
1753 parameter (currently enabled), or you can override it on your
1754 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
1756 o Major bugfixes (0.2.1.x and earlier):
1757 - Fix a bug in bandwidth accounting that could make us use twice
1758 the intended bandwidth when our interval start changes due to
1759 daylight saving time. Now we tolerate skew in stored vs computed
1760 interval starts: if the start of the period changes by no more than
1761 50% of the period's duration, we remember bytes that we transferred
1762 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
1763 - Always search the Windows system directory for system DLLs, and
1764 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
1765 - When you're using bridges and your network goes away and your
1766 bridges get marked as down, recover when you attempt a new socks
1767 connection (if the network is back), rather than waiting up to an
1768 hour to try fetching new descriptors for your bridges. Bugfix on
1769 0.2.0.3-alpha; fixes bug 1981.
1771 o Major bugfixes (on 0.2.2.x):
1772 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
1774 - Fix a segfault that could happen when operating a bridge relay with
1775 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
1776 - The consensus bandwidth-weights (used by clients to choose fast
1777 relays) entered an unexpected edge case in September where
1778 Exits were much scarcer than Guards, resulting in bad weight
1779 recommendations. Now we compute them using new constraints that
1780 should succeed in all cases. Also alter directory authorities to
1781 not include the bandwidth-weights line if they fail to produce
1782 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
1783 - When weighting bridges during path selection, we used to trust
1784 the bandwidths they provided in their descriptor, only capping them
1785 at 10MB/s. This turned out to be problematic for two reasons:
1786 Bridges could claim to handle a lot more traffic then they
1787 actually would, thus making more clients pick them and have a
1788 pretty effective DoS attack. The other issue is that new bridges
1789 that might not have a good estimate for their bw capacity yet
1790 would not get used at all unless no other bridges are available
1791 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
1793 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
1794 - Ignore cannibalized circuits when recording circuit build times.
1795 This should provide for a minor performance improvement for hidden
1796 service users using 0.2.2.14-alpha, and should remove two spurious
1797 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
1798 - Simplify the logic that causes us to decide if the network is
1799 unavailable for purposes of recording circuit build times. If we
1800 receive no cells whatsoever for the entire duration of a circuit's
1801 full measured lifetime, the network is probably down. Also ignore
1802 one-hop directory fetching circuit timeouts when calculating our
1803 circuit build times. These changes should hopefully reduce the
1804 cases where we see ridiculous circuit build timeouts for people
1805 with spotty wireless connections. Fixes part of bug 1772; bugfix
1807 - Prevent the circuit build timeout from becoming larger than
1808 the maximum build time we have ever seen. Also, prevent the time
1809 period for measurement circuits from becoming larger than twice that
1810 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
1813 - When we run out of directory information such that we can't build
1814 circuits, but then get enough that we can build circuits, log when
1815 we actually construct a circuit, so the user has a better chance of
1816 knowing what's going on. Fixes bug 1362.
1817 - Be more generous with how much bandwidth we'd use up (with
1818 accounting enabled) before entering "soft hibernation". Previously,
1819 we'd refuse new connections and circuits once we'd used up 95% of
1820 our allotment. Now, we use up 95% of our allotment, AND make sure
1821 that we have no more than 500MB (or 3 hours of expected traffic,
1822 whichever is lower) remaining before we enter soft hibernation.
1823 - If we've configured EntryNodes and our network goes away and/or all
1824 our entrynodes get marked down, optimistically retry them all when
1825 a new socks application request appears. Fixes bug 1882.
1826 - Add some more defensive programming for architectures that can't
1827 handle unaligned integer accesses. We don't know of any actual bugs
1828 right now, but that's the best time to fix them. Fixes bug 1943.
1829 - Support line continuations in the torrc config file. If a line
1830 ends with a single backslash character, the newline is ignored, and
1831 the configuration value is treated as continuing on the next line.
1834 o Minor bugfixes (on 0.2.1.x and earlier):
1835 - For bandwidth accounting, calculate our expected bandwidth rate
1836 based on the time during which we were active and not in
1837 soft-hibernation during the last interval. Previously, we were
1838 also considering the time spent in soft-hibernation. If this
1839 was a long time, we would wind up underestimating our bandwidth
1840 by a lot, and skewing our wakeup time towards the start of the
1841 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
1843 o Minor bugfixes (on 0.2.2.x):
1844 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
1845 which were disabled by the circuit build timeout changes in
1846 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
1847 - Make sure we don't warn about missing bandwidth weights when
1848 choosing bridges or other relays not in the consensus. Bugfix on
1849 0.2.2.10-alpha; fixes bug 1805.
1850 - In our logs, do not double-report signatures from unrecognized
1851 authorities both as "from unknown authority" and "not
1852 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
1855 Changes in version 0.2.2.16-alpha - 2010-09-17
1856 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
1857 evident at exit relays), and also continues to resolve all the little
1858 bugs that have been filling up trac lately.
1860 o Major bugfixes (stream-level fairness):
1861 - When receiving a circuit-level SENDME for a blocked circuit, try
1862 to package cells fairly from all the streams that had previously
1863 been blocked on that circuit. Previously, we had started with the
1864 oldest stream, and allowed each stream to potentially exhaust
1865 the circuit's package window. This gave older streams on any
1866 given circuit priority over newer ones. Fixes bug 1937. Detected
1867 originally by Camilo Viecco. This bug was introduced before the
1868 first Tor release, in svn commit r152: it is the new winner of
1869 the longest-lived bug prize.
1870 - When the exit relay got a circuit-level sendme cell, it started
1871 reading on the exit streams, even if had 500 cells queued in the
1872 circuit queue already, so the circuit queue just grew and grew in
1873 some cases. We fix this by not re-enabling reading on receipt of a
1874 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
1875 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
1877 - Newly created streams were allowed to read cells onto circuits,
1878 even if the circuit's cell queue was blocked and waiting to drain.
1879 This created potential unfairness, as older streams would be
1880 blocked, but newer streams would gladly fill the queue completely.
1881 We add code to detect this situation and prevent any stream from
1882 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
1886 - Update to the September 1 2010 Maxmind GeoLite Country database.
1887 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
1888 not. This would lead to a cookie that is still not group readable.
1889 Closes bug 1843. Suggested by katmagic.
1890 - When logging a rate-limited warning, we now mention how many messages
1891 got suppressed since the last warning.
1892 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
1893 do individual connection-level rate limiting of clients. The torrc
1894 config options with the same names trump the consensus params, if
1895 both are present. Replaces the old "bwconnrate" and "bwconnburst"
1896 consensus params which were broken from 0.2.2.7-alpha through
1897 0.2.2.14-alpha. Closes bug 1947.
1898 - When a router changes IP address or port, authorities now launch
1899 a new reachability test for it. Implements ticket 1899.
1900 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
1901 2 no signature, 4 required" messages about consensus signatures
1902 easier to read, and make sure they get logged at the same severity
1903 as the messages explaining which keys are which. Fixes bug 1290.
1904 - Don't warn when we have a consensus that we can't verify because
1905 of missing certificates, unless those certificates are ones
1906 that we have been trying and failing to download. Fixes bug 1145.
1907 - If you configure your bridge with a known identity fingerprint,
1908 and the bridge authority is unreachable (as it is in at least
1909 one country now), fall back to directly requesting the descriptor
1910 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
1912 - When building with --enable-gcc-warnings on OpenBSD, disable
1913 warnings in system headers. This makes --enable-gcc-warnings
1914 pass on OpenBSD 4.8.
1916 o Minor bugfixes (on 0.2.1.x and earlier):
1917 - Authorities will now attempt to download consensuses if their
1918 own efforts to make a live consensus have failed. This change
1919 means authorities that restart will fetch a valid consensus, and
1920 it means authorities that didn't agree with the current consensus
1921 will still fetch and serve it if it has enough signatures. Bugfix
1922 on 0.2.0.9-alpha; fixes bug 1300.
1923 - Ensure DNS requests launched by "RESOLVE" commands from the
1924 controller respect the __LeaveStreamsUnattached setconf options. The
1925 same goes for requests launched via DNSPort or transparent
1926 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
1927 - Allow handshaking OR connections to take a full KeepalivePeriod
1928 seconds to handshake. Previously, we would close them after
1929 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
1930 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
1932 - Rate-limit "Failed to hand off onionskin" warnings.
1933 - Never relay a cell for a circuit we have already destroyed.
1934 Between marking a circuit as closeable and finally closing it,
1935 it may have been possible for a few queued cells to get relayed,
1936 even though they would have been immediately dropped by the next
1937 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
1938 - Never queue a cell for a circuit that's already been marked
1940 - Never vote for a server as "Running" if we have a descriptor for
1941 it claiming to be hibernating, and that descriptor was published
1942 more recently than our last contact with the server. Bugfix on
1943 0.2.0.3-alpha; fixes bug 911.
1944 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
1947 o Minor bugfixes (on 0.2.2.x):
1948 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
1949 down if a directory fetch fails and you've configured either
1950 bridges or EntryNodes. The intent was to mark the relay as down
1951 _unless_ you're using bridges or EntryNodes, since if you are
1952 then you could quickly run out of entry points.
1953 - Fix the Windows directory-listing code. A bug introduced in
1954 0.2.2.14-alpha could make Windows directory servers forget to load
1955 some of their cached v2 networkstatus files.
1956 - Really allow clients to use relays as bridges. Fixes bug 1776;
1957 bugfix on 0.2.2.15-alpha.
1958 - Demote a warn to info that happens when the CellStatistics option
1959 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
1960 Reported by Moritz Bartl.
1961 - On Windows, build correctly either with or without Unicode support.
1962 This is necessary so that Tor can support fringe platforms like
1963 Windows 98 (which has no Unicode), or Windows CE (which has no
1964 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
1967 - Add a unit test for cross-platform directory-listing code.
1970 Changes in version 0.2.2.15-alpha - 2010-08-18
1971 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
1972 fixes a variety of other bugs that were preventing performance
1973 experiments from moving forward, fixes several bothersome memory leaks,
1974 and generally closes a lot of smaller bugs that have been filling up
1978 - Stop assigning the HSDir flag to relays that disable their
1979 DirPort (and thus will refuse to answer directory requests). This
1980 fix should dramatically improve the reachability of hidden services:
1981 hidden services and hidden service clients pick six HSDir relays
1982 to store and retrieve the hidden service descriptor, and currently
1983 about half of the HSDir relays will refuse to work. Bugfix on
1984 0.2.0.10-alpha; fixes part of bug 1693.
1985 - The PerConnBWRate and Burst config options, along with the
1986 bwconnrate and bwconnburst consensus params, initialized each conn's
1987 token bucket values only when the connection is established. Now we
1988 update them if the config options change, and update them every time
1989 we get a new consensus. Otherwise we can encounter an ugly edge
1990 case where we initialize an OR conn to client-level bandwidth,
1991 but then later the relay joins the consensus and we leave it
1992 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
1993 - Fix a regression that caused Tor to rebind its ports if it receives
1994 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
1997 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
1998 should give us approximately 40-50% more Guard-flagged nodes,
1999 improving the anonymity the Tor network can provide and also
2000 decreasing the dropoff in throughput that relays experience when
2001 they first get the Guard flag.
2002 - Allow enabling or disabling the *Statistics config options while
2006 - Update to the August 1 2010 Maxmind GeoLite Country database.
2007 - Have the controller interface give a more useful message than
2008 "Internal Error" in response to failed GETINFO requests.
2009 - Warn when the same option is provided more than once in a torrc
2010 file, on the command line, or in a single SETCONF statement, and
2011 the option is one that only accepts a single line. Closes bug 1384.
2012 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
2013 Patch from mingw-san.
2014 - Add support for the country code "{??}" in torrc options like
2015 ExcludeNodes, to indicate all routers of unknown country. Closes
2017 - Relays report the number of bytes spent on answering directory
2018 requests in extra-info descriptors similar to {read,write}-history.
2019 Implements enhancement 1790.
2021 o Minor bugfixes (on 0.2.1.x and earlier):
2022 - Complain if PublishServerDescriptor is given multiple arguments that
2023 include 0 or 1. This configuration will be rejected in the future.
2024 Bugfix on 0.2.0.1-alpha; closes bug 1107.
2025 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
2026 Bugfix on 0.2.0.13-alpha; closes bug 928.
2027 - Change "Application request when we're believed to be offline."
2028 notice to "Application request when we haven't used client
2029 functionality lately.", to clarify that it's not an error. Bugfix
2030 on 0.0.9.3; fixes bug 1222.
2031 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
2032 would return "551 Internal error" rather than "552 Unrecognized key
2033 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
2034 - Users can't configure a regular relay to be their bridge. It didn't
2035 work because when Tor fetched the bridge descriptor, it found
2036 that it already had it, and didn't realize that the purpose of the
2037 descriptor had changed. Now we replace routers with a purpose other
2038 than bridge with bridge descriptors when fetching them. Bugfix on
2039 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
2040 refetch the descriptor with router purpose 'general', disabling
2042 - Fix a rare bug in rend_fn unit tests: we would fail a test when
2043 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
2044 on 0.2.0.10-alpha; fixes bug 1808.
2045 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
2046 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
2047 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
2048 Servers can start sending this code when enough clients recognize
2049 it. Also update the spec to reflect this new reason. Bugfix on
2050 0.1.0.1-rc; fixes part of bug 1793.
2051 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
2052 when we switch from being a public relay to a bridge. Otherwise
2053 there will still be clients that see the relay in their consensus,
2054 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
2056 - Instead of giving an assertion failure on an internal mismatch
2057 on estimated freelist size, just log a BUG warning and try later.
2058 Mitigates but does not fix bug 1125.
2059 - Fix an assertion failure that could occur in caches or bridge users
2060 when using a very short voting interval on a testing network.
2061 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
2063 o Minor bugfixes (on 0.2.2.x):
2064 - Alter directory authorities to always consider Exit-flagged nodes
2065 as potential Guard nodes in their votes. The actual decision to
2066 use Exits as Guards is done in the consensus bandwidth weights.
2067 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
2068 - When the controller is reporting the purpose of circuits that
2069 didn't finish building before the circuit build timeout, it was
2070 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
2071 - Our libevent version parsing code couldn't handle versions like
2072 1.4.14b-stable and incorrectly warned the user about using an
2073 old and broken version of libevent. Treat 1.4.14b-stable like
2074 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
2076 - Don't use substitution references like $(VAR:MOD) when
2077 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
2078 '$(:x)' to 'x' rather than the empty string. This bites us in
2079 doc/ when configured with --disable-asciidoc. Bugfix on
2080 0.2.2.9-alpha; fixes bug 1773.
2081 - Remove a spurious hidden service server-side log notice about
2082 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
2084 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
2086 - Correctly report written bytes on linked connections. Found while
2087 implementing 1790. Bugfix on 0.2.2.4-alpha.
2088 - Fix three memory leaks: one in circuit_build_times_parse_state(),
2089 one in dirvote_add_signatures_to_pending_consensus(), and one every
2090 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
2091 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
2093 o Code simplifications and refactoring:
2094 - Take a first step towards making or.h smaller by splitting out
2095 function definitions for all source files in src/or/. Leave
2096 structures and defines in or.h for now.
2097 - Remove a bunch of unused function declarations as well as a block of
2098 #if 0'd code from the unit tests. Closes bug 1824.
2099 - New unit tests for exit-port history statistics; refactored exit
2100 statistics code to be more easily tested.
2101 - Remove the old debian/ directory from the main Tor distribution.
2102 The official Tor-for-debian git repository lives at the URL
2103 https://git.torproject.org/debian/tor.git
2106 Changes in version 0.2.2.14-alpha - 2010-07-12
2107 Tor 0.2.2.14-alpha greatly improves client-side handling of
2108 circuit build timeouts, which are used to estimate speed and improve
2109 performance. We also move to a much better GeoIP database, port Tor to
2110 Windows CE, introduce new compile flags that improve code security,
2111 add an eighth v3 directory authority, and address a lot of more
2115 - Tor directory authorities no longer crash when started with a
2116 cached-microdesc-consensus file in their data directory. Bugfix
2117 on 0.2.2.6-alpha; fixes bug 1532.
2118 - Treat an unset $HOME like an empty $HOME rather than triggering an
2119 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
2120 - Ignore negative and large circuit build timeout values that can
2121 happen during a suspend or hibernate. These values caused various
2122 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
2123 - Alter calculation of Pareto distribution parameter 'Xm' for
2124 Circuit Build Timeout learning to use the weighted average of the
2125 top N=3 modes (because we have three entry guards). Considering
2126 multiple modes should improve the timeout calculation in some cases,
2127 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
2129 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
2130 right censored distribution model. This approach improves over the
2131 synthetic timeout generation approach that was producing insanely
2132 high timeout values. Now we calculate build timeouts using truncated
2133 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
2134 - Do not close circuits that are under construction when they reach
2135 the circuit build timeout. Instead, leave them building (but do not
2136 use them) for up until the time corresponding to the 95th percentile
2137 on the Pareto CDF or 60 seconds, whichever is greater. This is done
2138 to provide better data for the new Pareto model. This percentile
2139 can be controlled by the consensus.
2142 - Move to the June 2010 Maxmind GeoLite country db (rather than the
2143 June 2009 ip-to-country GeoIP db) for our statistics that count
2144 how many users relays are seeing from each country. Now we have
2145 more accurate data for many African countries.
2146 - Port Tor to build and run correctly on Windows CE systems, using
2147 the wcecompat library. Contributed by Valerio Lupi.
2148 - New "--enable-gcc-hardening" ./configure flag (off by default)
2149 to turn on gcc compile time hardening options. It ensures
2150 that signed ints have defined behavior (-fwrapv), enables
2151 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
2152 with canaries (-fstack-protector-all), turns on ASLR protection if
2153 supported by the kernel (-fPIE, -pie), and adds additional security
2154 related warnings. Verified to work on Mac OS X and Debian Lenny.
2155 - New "--enable-linker-hardening" ./configure flag (off by default)
2156 to turn on ELF specific hardening features (relro, now). This does
2157 not work with Mac OS X or any other non-ELF binary format.
2159 o New directory authorities:
2160 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
2164 - New config option "WarnUnsafeSocks 0" disables the warning that
2165 occurs whenever Tor receives a socks handshake using a version of
2166 the socks protocol that can only provide an IP address (rather
2167 than a hostname). Setups that do DNS locally over Tor are fine,
2168 and we shouldn't spam the logs in that case.
2169 - Convert the HACKING file to asciidoc, and add a few new sections
2170 to it, explaining how we use Git, how we make changelogs, and
2171 what should go in a patch.
2172 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
2173 event, to give information on the current rate of circuit timeouts
2174 over our stored history.
2175 - Add ability to disable circuit build time learning via consensus
2176 parameter and via a LearnCircuitBuildTimeout config option. Also
2177 automatically disable circuit build time calculation if we are
2178 either a AuthoritativeDirectory, or if we fail to write our state
2179 file. Fixes bug 1296.
2180 - More gracefully handle corrupt state files, removing asserts
2181 in favor of saving a backup and resetting state.
2182 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
2186 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2188 - When a2x fails, mention that the user could disable manpages instead
2189 of trying to fix their asciidoc installation.
2190 - Where available, use Libevent 2.0's periodic timers so that our
2191 once-per-second cleanup code gets called even more closely to
2192 once per second than it would otherwise. Fixes bug 943.
2193 - If you run a bridge that listens on multiple IP addresses, and
2194 some user configures a bridge address that uses a different IP
2195 address than your bridge writes in its router descriptor, and the
2196 user doesn't specify an identity key, their Tor would discard the
2197 descriptor because "it isn't one of our configured bridges", and
2198 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
2199 Bugfix on 0.2.0.3-alpha.
2200 - If OpenSSL fails to make a duplicate of a private or public key, log
2201 an error message and try to exit cleanly. May help with debugging
2202 if bug 1209 ever remanifests.
2203 - Save a couple bytes in memory allocation every time we escape
2204 certain characters in a string. Patch from Florian Zumbiehl.
2205 - Make it explicit that we don't cannibalize one-hop circuits. This
2206 happens in the wild, but doesn't turn out to be a problem because
2207 we fortunately don't use those circuits. Many thanks to outofwords
2208 for the initial analysis and to swissknife who confirmed that
2209 two-hop circuits are actually created.
2210 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
2211 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
2212 - Eliminate a case where a circuit build time warning was displayed
2213 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
2216 Changes in version 0.2.1.26 - 2010-05-02
2217 Tor 0.2.1.26 addresses the recent connection and memory overload
2218 problems we've been seeing on relays, especially relays with their
2219 DirPort open. If your relay has been crashing, or you turned it off
2220 because it used too many resources, give this release a try.
2222 This release also fixes yet another instance of broken OpenSSL libraries
2223 that was causing some relays to drop out of the consensus.
2226 - Teach relays to defend themselves from connection overload. Relays
2227 now close idle circuits early if it looks like they were intended
2228 for directory fetches. Relays are also more aggressive about closing
2229 TLS connections that have no circuits on them. Such circuits are
2230 unlikely to be re-used, and tens of thousands of them were piling
2231 up at the fast relays, causing the relays to run out of sockets
2232 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
2233 their directory fetches over TLS).
2234 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
2235 that claim to be earlier than 0.9.8m, but which have in reality
2236 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
2237 behavior. Possible fix for some cases of bug 1346.
2238 - Directory mirrors were fetching relay descriptors only from v2
2239 directory authorities, rather than v3 authorities like they should.
2240 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
2241 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
2244 - Finally get rid of the deprecated and now harmful notion of "clique
2245 mode", where directory authorities maintain TLS connections to
2249 - In the util/threads test, no longer free the test_mutex before all
2250 worker threads have finished. Bugfix on 0.2.1.6-alpha.
2251 - The master thread could starve the worker threads quite badly on
2252 certain systems, causing them to run only partially in the allowed
2253 window. This resulted in test failures. Now the master thread sleeps
2254 occasionally for a few microseconds while the two worker-threads
2255 compete for the mutex. Bugfix on 0.2.0.1-alpha.
2258 Changes in version 0.2.2.13-alpha - 2010-04-24
2259 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
2260 problems we've been seeing on relays, especially relays with their
2261 DirPort open. If your relay has been crashing, or you turned it off
2262 because it used too many resources, give this release a try.
2265 - Teach relays to defend themselves from connection overload. Relays
2266 now close idle circuits early if it looks like they were intended
2267 for directory fetches. Relays are also more aggressive about closing
2268 TLS connections that have no circuits on them. Such circuits are
2269 unlikely to be re-used, and tens of thousands of them were piling
2270 up at the fast relays, causing the relays to run out of sockets
2271 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
2272 their directory fetches over TLS).
2275 - Finally get rid of the deprecated and now harmful notion of "clique
2276 mode", where directory authorities maintain TLS connections to
2278 - Directory authorities now do an immediate reachability check as soon
2279 as they hear about a new relay. This change should slightly reduce
2280 the time between setting up a relay and getting listed as running
2281 in the consensus. It should also improve the time between setting
2282 up a bridge and seeing use by bridge users.
2283 - Directory authorities no longer launch a TLS connection to every
2284 relay as they startup. Now that we have 2k+ descriptors cached,
2285 the resulting network hiccup is becoming a burden. Besides,
2286 authorities already avoid voting about Running for the first half
2287 hour of their uptime.
2290 Changes in version 0.2.2.12-alpha - 2010-04-20
2291 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
2292 handle and vote on descriptors. It was causing relays to drop out of
2296 - Many relays have been falling out of the consensus lately because
2297 not enough authorities know about their descriptor for them to get
2298 a majority of votes. When we deprecated the v2 directory protocol,
2299 we got rid of the only way that v3 authorities can hear from each
2300 other about other descriptors. Now authorities examine every v3
2301 vote for new descriptors, and fetch them from that authority. Bugfix
2303 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
2304 and a warning in or.h related to bandwidth_weight_rule_t that
2305 prevented clean compile on OS X. Fixes bug 1363; bugfix on
2307 - Fix a segfault on relays when DirReqStatistics is enabled
2308 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
2312 - Demote a confusing TLS warning that relay operators might get when
2313 someone tries to talk to their OrPort. It is neither the operator's
2314 fault nor can they do anything about it. Fixes bug 1364; bugfix
2318 Changes in version 0.2.2.11-alpha - 2010-04-15
2319 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
2320 libraries that was causing some relays to drop out of the consensus.
2323 - Directory mirrors were fetching relay descriptors only from v2
2324 directory authorities, rather than v3 authorities like they should.
2325 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
2326 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
2327 - Fix a parsing error that made every possible value of
2328 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
2329 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
2330 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
2331 about the option without breaking older ones.
2332 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
2333 that claim to be earlier than 0.9.8m, but which have in reality
2334 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
2335 behavior. Possible fix for some cases of bug 1346.
2338 - Experiment with a more aggressive approach to preventing clients
2339 from making one-hop exit streams. Exit relays who want to try it
2340 out can set "RefuseUnknownExits 1" in their torrc, and then look
2341 for "Attempt by %s to open a stream" log messages. Let us know
2343 - Add support for statically linking zlib by specifying
2344 --enable-static-zlib, to go with our support for statically linking
2345 openssl and libevent. Resolves bug 1358.
2348 - Fix a segfault that happens whenever a Tor client that is using
2349 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
2351 - When we cleaned up the contrib/tor-exit-notice.html file, we left
2352 out the first line. Fixes bug 1295.
2353 - When building the manpage from a tarball, we required asciidoc, but
2354 the asciidoc -> roff/html conversion was already done for the
2355 tarball. Make 'make' complain only when we need asciidoc (either
2356 because we're compiling directly from git, or because we altered
2357 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
2358 - When none of the directory authorities vote on any params, Tor
2359 segfaulted when trying to make the consensus from the votes. We
2360 didn't trigger the bug in practice, because authorities do include
2361 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
2364 - In the util/threads test, no longer free the test_mutex before all
2365 worker threads have finished. Bugfix on 0.2.1.6-alpha.
2366 - The master thread could starve the worker threads quite badly on
2367 certain systems, causing them to run only partially in the allowed
2368 window. This resulted in test failures. Now the master thread sleeps
2369 occasionally for a few microseconds while the two worker-threads
2370 compete for the mutex. Bugfix on 0.2.0.1-alpha.
2373 Changes in version 0.2.2.10-alpha - 2010-03-07
2374 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
2375 could prevent relays from guessing their IP address correctly. It also
2376 starts the groundwork for another client-side performance boost, since
2377 currently we're not making efficient use of relays that have both the
2378 Guard flag and the Exit flag.
2381 - Fix a regression from our patch for bug 1244 that caused relays
2382 to guess their IP address incorrectly if they didn't set Address
2383 in their torrc and/or their address fails to resolve. Bugfix on
2384 0.2.2.9-alpha; fixes bug 1269.
2386 o Major features (performance):
2387 - Directory authorities now compute consensus weightings that instruct
2388 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
2389 and no flag. Clients that use these weightings will distribute
2390 network load more evenly across these different relay types. The
2391 weightings are in the consensus so we can change them globally in
2392 the future. Extra thanks to "outofwords" for finding some nasty
2393 security bugs in the first implementation of this feature.
2395 o Minor features (performance):
2396 - Always perform router selections using weighted relay bandwidth,
2397 even if we don't need a high capacity circuit at the time. Non-fast
2398 circuits now only differ from fast ones in that they can use relays
2399 not marked with the Fast flag. This "feature" could turn out to
2400 be a horrible bug; we should investigate more before it goes into
2404 - Allow disabling building of the manpages. Skipping the manpage
2405 speeds up the build considerably.
2407 o Minor bugfixes (on 0.2.2.x):
2408 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
2409 Bugfix on 0.2.2.9-alpha.
2410 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
2411 config option. Bugfix on 0.2.2.7-alpha.
2412 - Ship the asciidoc-helper file in the tarball, so that people can
2413 build from source if they want to, and touching the .1.txt files
2414 doesn't break the build. Bugfix on 0.2.2.9-alpha.
2416 o Minor bugfixes (on 0.2.1.x or earlier):
2417 - Fix a dereference-then-NULL-check sequence when publishing
2418 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
2420 - Fix another dereference-then-NULL-check sequence. Bugfix on
2421 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
2422 - Make sure we treat potentially not NUL-terminated strings correctly.
2423 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
2425 o Code simplifications and refactoring:
2426 - Fix some urls in the exit notice file and make it XHTML1.1 strict
2427 compliant. Based on a patch from Christian Kujau.
2428 - Don't use sed in asciidoc-helper anymore.
2429 - Make the build process fail if asciidoc cannot be found and
2430 building with asciidoc isn't disabled.
2433 Changes in version 0.2.2.9-alpha - 2010-02-22
2434 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
2435 location of a directory authority, and cleans up a bunch of small bugs.
2437 o Directory authority changes:
2438 - Change IP address for dannenberg (v3 directory authority), and
2439 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
2440 service directory authority) from the list.
2443 - Make Tor work again on the latest OS X: when deciding whether to
2444 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2445 version at run-time, not compile time. We need to do this because
2446 Apple doesn't update its dev-tools headers when it updates its
2447 libraries in a security patch.
2448 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2449 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2450 a memory leak when requesting a hidden service descriptor we've
2451 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2453 - Authorities could be tricked into giving out the Exit flag to relays
2454 that didn't allow exiting to any ports. This bug could screw
2455 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
2456 1238. Bug discovered by Martin Kowalczyk.
2457 - When freeing a session key, zero it out completely. We only zeroed
2458 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
2459 patched by ekir. Fixes bug 1254.
2462 - Fix static compilation by listing the openssl libraries in the right
2463 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
2464 - Resume handling .exit hostnames in a special way: originally we
2465 stripped the .exit part and used the requested exit relay. In
2466 0.2.2.1-alpha we stopped treating them in any special way, meaning
2467 if you use a .exit address then Tor will pass it on to the exit
2468 relay. Now we reject the .exit stream outright, since that behavior
2469 might be more expected by the user. Found and diagnosed by Scott
2470 Bennett and Downie on or-talk.
2471 - Don't spam the controller with events when we have no file
2472 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
2473 for log messages was already solved from bug 748.)
2474 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
2476 - Make the DNSPort option work with libevent 2.x. Don't alter the
2477 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
2478 - Emit a GUARD DROPPED controller event for a case we missed.
2479 - Make more fields in the controller protocol case-insensitive, since
2480 control-spec.txt said they were.
2481 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2482 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2483 - Fix a spec conformance issue: the network-status-version token
2484 must be the first token in a v3 consensus or vote. Discovered by
2485 parakeep. Bugfix on 0.2.0.3-alpha.
2487 o Code simplifications and refactoring:
2488 - Generate our manpage and HTML documentation using Asciidoc. This
2489 change should make it easier to maintain the documentation, and
2491 - Remove the --enable-iphone option. According to reports from Marco
2492 Bonetti, Tor builds fine without any special tweaking on recent
2493 iPhone SDK versions.
2494 - Removed some unnecessary files from the source distribution. The
2495 AUTHORS file has now been merged into the people page on the
2496 website. The roadmaps and design doc can now be found in the
2497 projects directory in svn.
2498 - Enabled various circuit build timeout constants to be controlled
2499 by consensus parameters. Also set better defaults for these
2500 parameters based on experimentation on broadband and simulated
2504 - The 'EXTENDCIRCUIT' control port command can now be used with
2505 a circ id of 0 and no path. This feature will cause Tor to build
2506 a new 'fast' general purpose circuit using its own path selection
2508 - Added a BUILDTIMEOUT_SET controller event to describe changes
2509 to the circuit build timeout.
2510 - Future-proof the controller protocol a bit by ignoring keyword
2511 arguments we do not recognize.
2512 - Expand homedirs passed to tor-checkkey. This should silence a
2513 coverity complaint about passing a user-supplied string into
2514 open() without checking it.
2517 Changes in version 0.2.1.25 - 2010-03-16
2518 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
2519 prevent relays from guessing their IP address correctly. It also fixes
2520 several minor potential security bugs.
2523 - Fix a regression from our patch for bug 1244 that caused relays
2524 to guess their IP address incorrectly if they didn't set Address
2525 in their torrc and/or their address fails to resolve. Bugfix on
2526 0.2.1.23; fixes bug 1269.
2527 - When freeing a session key, zero it out completely. We only zeroed
2528 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
2529 patched by ekir. Fixes bug 1254.
2532 - Fix a dereference-then-NULL-check sequence when publishing
2533 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
2535 - Fix another dereference-then-NULL-check sequence. Bugfix on
2536 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
2537 - Make sure we treat potentially not NUL-terminated strings correctly.
2538 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
2542 Changes in version 0.2.1.24 - 2010-02-21
2543 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
2547 - Work correctly out-of-the-box with even more vendor-patched versions
2548 of OpenSSL. In particular, make it so Debian and OS X don't need
2549 customized patches to run/build.
2552 Changes in version 0.2.1.23 - 2010-02-13
2553 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
2554 again on the latest OS X, and updates the location of a directory
2557 o Major bugfixes (performance):
2558 - We were selecting our guards uniformly at random, and then weighting
2559 which of our guards we'd use uniformly at random. This imbalance
2560 meant that Tor clients were severely limited on throughput (and
2561 probably latency too) by the first hop in their circuit. Now we
2562 select guards weighted by currently advertised bandwidth. We also
2563 automatically discard guards picked using the old algorithm. Fixes
2564 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2567 - Make Tor work again on the latest OS X: when deciding whether to
2568 use strange flags to turn TLS renegotiation on, detect the OpenSSL
2569 version at run-time, not compile time. We need to do this because
2570 Apple doesn't update its dev-tools headers when it updates its
2571 libraries in a security patch.
2572 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
2573 that could happen on 32-bit platforms with 64-bit time_t. Also fix
2574 a memory leak when requesting a hidden service descriptor we've
2575 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
2578 o Directory authority changes:
2579 - Change IP address for dannenberg (v3 directory authority), and
2580 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
2581 service directory authority) from the list.
2584 - Refactor resolve_my_address() to not use gethostbyname() anymore.
2585 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
2588 - Avoid a mad rush at the beginning of each month when each client
2589 rotates half of its guards. Instead we spread the rotation out
2590 throughout the month, but we still avoid leaving a precise timestamp
2591 in the state file about when we first picked the guard. Improves
2592 over the behavior introduced in 0.1.2.17.
2595 Changes in version 0.2.2.8-alpha - 2010-01-26
2596 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
2597 causing bridge relays to disappear. If you're running a bridge,
2601 - Fix a memory corruption bug on bridges that occured during the
2602 inclusion of stats data in extra-info descriptors. Also fix the
2603 interface for geoip_get_bridge_stats* to prevent similar bugs in
2604 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
2605 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
2608 - Ignore OutboundBindAddress when connecting to localhost.
2609 Connections to localhost need to come _from_ localhost, or else
2610 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
2614 Changes in version 0.2.2.7-alpha - 2010-01-19
2615 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
2616 as laying the groundwork for further relay-side performance fixes. It
2617 also starts cleaning up client behavior with respect to the EntryNodes,
2618 ExitNodes, and StrictNodes config options.
2620 This release also rotates two directory authority keys, due to a
2621 security breach of some of the Torproject servers.
2623 o Directory authority changes:
2624 - Rotate keys (both v3 identity and relay identity) for moria1
2627 o Major features (performance):
2628 - We were selecting our guards uniformly at random, and then weighting
2629 which of our guards we'd use uniformly at random. This imbalance
2630 meant that Tor clients were severely limited on throughput (and
2631 probably latency too) by the first hop in their circuit. Now we
2632 select guards weighted by currently advertised bandwidth. We also
2633 automatically discard guards picked using the old algorithm. Fixes
2634 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
2635 - When choosing which cells to relay first, relays can now favor
2636 circuits that have been quiet recently, to provide lower latency
2637 for low-volume circuits. By default, relays enable or disable this
2638 feature based on a setting in the consensus. You can override
2639 this default by using the new "CircuitPriorityHalflife" config
2640 option. Design and code by Ian Goldberg, Can Tang, and Chris
2642 - Add separate per-conn write limiting to go with the per-conn read
2643 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
2644 but never per-conn write limits.
2645 - New consensus params "bwconnrate" and "bwconnburst" to let us
2646 rate-limit client connections as they enter the network. It's
2647 controlled in the consensus so we can turn it on and off for
2648 experiments. It's starting out off. Based on proposal 163.
2650 o Major features (relay selection options):
2651 - Switch to a StrictNodes config option, rather than the previous
2652 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
2653 "StrictExcludeNodes" option.
2654 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
2655 change during a config reload, mark and discard all our origin
2656 circuits. This fix should address edge cases where we change the
2657 config options and but then choose a circuit that we created before
2659 - If EntryNodes or ExitNodes are set, be more willing to use an
2660 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
2662 - Make EntryNodes config option much more aggressive even when
2663 StrictNodes is not set. Before it would prepend your requested
2664 entrynodes to your list of guard nodes, but feel free to use others
2665 after that. Now it chooses only from your EntryNodes if any of
2666 those are available, and only falls back to others if a) they're
2667 all down and b) StrictNodes is not set.
2668 - Now we refresh your entry guards from EntryNodes at each consensus
2669 fetch -- rather than just at startup and then they slowly rot as
2670 the network changes.
2673 - Stop bridge directory authorities from answering dbg-stability.txt
2674 directory queries, which would let people fetch a list of all
2675 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2678 - Log a notice when we get a new control connection. Now it's easier
2679 for security-conscious users to recognize when a local application
2680 is knocking on their controller door. Suggested by bug 1196.
2681 - New config option "CircuitStreamTimeout" to override our internal
2682 timeout schedule for how many seconds until we detach a stream from
2683 a circuit and try a new circuit. If your network is particularly
2684 slow, you might want to set this to a number like 60.
2685 - New controller command "getinfo config-text". It returns the
2686 contents that Tor would write if you send it a SAVECONF command,
2687 so the controller can write the file to disk itself.
2688 - New options for SafeLogging to allow scrubbing only log messages
2689 generated while acting as a relay.
2690 - Ship the bridges spec file in the tarball too.
2691 - Avoid a mad rush at the beginning of each month when each client
2692 rotates half of its guards. Instead we spread the rotation out
2693 throughout the month, but we still avoid leaving a precise timestamp
2694 in the state file about when we first picked the guard. Improves
2695 over the behavior introduced in 0.1.2.17.
2697 o Minor bugfixes (compiling):
2698 - Fix compilation on OS X 10.3, which has a stub mlockall() but
2699 hides it. Bugfix on 0.2.2.6-alpha.
2700 - Fix compilation on Solaris by removing support for the
2701 DisableAllSwap config option. Solaris doesn't have an rlimit for
2702 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
2705 o Minor bugfixes (crashes):
2706 - Do not segfault when writing buffer stats when we haven't observed
2707 a single circuit to report about. Found by Fabian Lanze. Bugfix on
2709 - If we're in the pathological case where there's no exit bandwidth
2710 but there is non-exit bandwidth, or no guard bandwidth but there
2711 is non-guard bandwidth, don't crash during path selection. Bugfix
2713 - Fix an impossible-to-actually-trigger buffer overflow in relay
2714 descriptor generation. Bugfix on 0.1.0.15.
2716 o Minor bugfixes (privacy):
2717 - Fix an instance where a Tor directory mirror might accidentally
2718 log the IP address of a misbehaving Tor client. Bugfix on
2720 - Don't list Windows capabilities in relay descriptors. We never made
2721 use of them, and maybe it's a bad idea to publish them. Bugfix
2724 o Minor bugfixes (other):
2725 - Resolve an edge case in path weighting that could make us misweight
2726 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
2727 - Fix statistics on client numbers by country as seen by bridges that
2728 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
2729 intervals instead of variable 12-to-48-hour intervals.
2730 - After we free an internal connection structure, overwrite it
2731 with a different memory value than we use for overwriting a freed
2732 internal circuit structure. Should help with debugging. Suggested
2734 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
2738 - Remove the HSAuthorityRecordStats option that version 0 hidden
2739 service authorities could have used to track statistics of overall
2740 hidden service usage.
2743 Changes in version 0.2.1.22 - 2010-01-19
2744 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
2745 authorities -- it would tell you its whole history of bridge descriptors
2746 if you make the right directory request. This stable update also
2747 rotates two of the seven v3 directory authority keys and locations.
2749 o Directory authority changes:
2750 - Rotate keys (both v3 identity and relay identity) for moria1
2754 - Stop bridge directory authorities from answering dbg-stability.txt
2755 directory queries, which would let people fetch a list of all
2756 bridge identities they track. Bugfix on 0.2.1.6-alpha.
2759 Changes in version 0.2.1.21 - 2009-12-21
2760 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
2761 library. If you use Tor on Linux / Unix and you're getting SSL
2762 renegotiation errors, upgrading should help. We also recommend an
2763 upgrade if you're an exit relay.
2766 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2767 handshake from working unless we explicitly tell OpenSSL that we
2768 are using SSL renegotiation safely. We are, of course, but OpenSSL
2769 0.9.8l won't work unless we say we are.
2770 - Avoid crashing if the client is trying to upload many bytes and the
2771 circuit gets torn down at the same time, or if the flip side
2772 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
2775 - Do not refuse to learn about authority certs and v2 networkstatus
2776 documents that are older than the latest consensus. This bug might
2777 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2778 Spotted and fixed by xmux.
2779 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
2780 trigger platform-specific option misparsing case found by Coverity
2782 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
2783 trigger assert. Fixes bug 1173.
2786 Changes in version 0.2.2.6-alpha - 2009-11-19
2787 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
2788 support for the new lower-footprint "microdescriptor" directory design,
2789 future-proofing our consensus format against new hash functions or
2790 other changes, and an Android port. It also makes Tor compatible with
2791 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
2794 - Directory authorities can now create, vote on, and serve multiple
2795 parallel formats of directory data as part of their voting process.
2796 Partially implements Proposal 162: "Publish the consensus in
2798 - Directory authorities can now agree on and publish small summaries
2799 of router information that clients can use in place of regular
2800 server descriptors. This transition will eventually allow clients
2801 to use far less bandwidth for downloading information about the
2802 network. Begins the implementation of Proposal 158: "Clients
2803 download consensus + microdescriptors".
2804 - The directory voting system is now extensible to use multiple hash
2805 algorithms for signatures and resource selection. Newer formats
2806 are signed with SHA256, with a possibility for moving to a better
2807 hash algorithm in the future.
2808 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
2809 current and future memory pages via mlockall(). On supported
2810 platforms (modern Linux and probably BSD but not Windows or OS X),
2811 this should effectively disable any and all attempts to page out
2812 memory. This option requires that you start your Tor as root --
2813 if you use DisableAllSwap, please consider using the User option
2814 to properly reduce the privileges of your Tor.
2815 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
2816 to help Tor build correctly for Android phones.
2819 - Work around a security feature in OpenSSL 0.9.8l that prevents our
2820 handshake from working unless we explicitly tell OpenSSL that we
2821 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
2822 won't work unless we say we are.
2825 - Fix a crash bug when trying to initialize the evdns module in
2826 Libevent 2. Bugfix on 0.2.1.16-rc.
2827 - Stop logging at severity 'warn' when some other Tor client tries
2828 to establish a circuit with us using weak DH keys. It's a protocol
2829 violation, but that doesn't mean ordinary users need to hear about
2830 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
2831 - Do not refuse to learn about authority certs and v2 networkstatus
2832 documents that are older than the latest consensus. This bug might
2833 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
2834 Spotted and fixed by xmux.
2835 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
2836 - If all authorities restart at once right before a consensus vote,
2837 nobody will vote about "Running", and clients will get a consensus
2838 with no usable relays. Instead, authorities refuse to build a
2839 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
2840 - If your relay can't keep up with the number of incoming create
2841 cells, it would log one warning per failure into your logs. Limit
2842 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
2843 - Bridges now use "reject *:*" as their default exit policy. Bugfix
2844 on 0.2.0.3-alpha; fixes bug 1113.
2845 - Fix a memory leak on directory authorities during voting that was
2846 introduced in 0.2.2.1-alpha. Found via valgrind.
2849 Changes in version 0.2.1.20 - 2009-10-15
2850 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
2851 services at once, prepares for more performance improvements, and
2852 fixes a bunch of smaller bugs.
2854 The Windows and OS X bundles also include a more recent Vidalia,
2855 and switch from Privoxy to Polipo.
2857 The OS X installers are now drag and drop. It's best to un-install
2858 Tor/Vidalia and then install this new bundle, rather than upgrade. If
2859 you want to upgrade, you'll need to update the paths for Tor and Polipo
2860 in the Vidalia Settings window.
2863 - Send circuit or stream sendme cells when our window has decreased
2864 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
2865 by Karsten when testing the "reduce circuit window" performance
2866 patch. Bugfix on the 54th commit on Tor -- from July 2002,
2867 before the release of Tor 0.0.0. This is the new winner of the
2869 - Fix a remotely triggerable memory leak when a consensus document
2870 contains more than one signature from the same voter. Bugfix on
2872 - Avoid segfault in rare cases when finishing an introduction circuit
2873 as a client and finding out that we don't have an introduction key
2874 for it. Fixes bug 1073. Reported by Aaron Swartz.
2877 - Tor now reads the "circwindow" parameter out of the consensus,
2878 and uses that value for its circuit package window rather than the
2879 default of 1000 cells. Begins the implementation of proposal 168.
2881 o New directory authorities:
2882 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
2884 - Move moria1 and tonga to alternate IP addresses.
2887 - Fix a signed/unsigned compile warning in 0.2.1.19.
2888 - Fix possible segmentation fault on directory authorities. Bugfix on
2890 - Fix an extremely rare infinite recursion bug that could occur if
2891 we tried to log a message after shutting down the log subsystem.
2892 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
2893 - Fix an obscure bug where hidden services on 64-bit big-endian
2894 systems might mis-read the timestamp in v3 introduce cells, and
2895 refuse to connect back to the client. Discovered by "rotor".
2896 Bugfix on 0.2.1.6-alpha.
2897 - We were triggering a CLOCK_SKEW controller status event whenever
2898 we connect via the v2 connection protocol to any relay that has
2899 a wrong clock. Instead, we should only inform the controller when
2900 it's a trusted authority that claims our clock is wrong. Bugfix
2901 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
2902 - We were telling the controller about CHECKING_REACHABILITY and
2903 REACHABILITY_FAILED status events whenever we launch a testing
2904 circuit or notice that one has failed. Instead, only tell the
2905 controller when we want to inform the user of overall success or
2906 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
2908 - Don't warn when we're using a circuit that ends with a node
2909 excluded in ExcludeExitNodes, but the circuit is not used to access
2910 the outside world. This should help fix bug 1090. Bugfix on
2912 - Work around a small memory leak in some versions of OpenSSL that
2913 stopped the memory used by the hostname TLS extension from being
2917 - Add a "getinfo status/accepted-server-descriptor" controller
2918 command, which is the recommended way for controllers to learn
2919 whether our server descriptor has been successfully received by at
2920 least on directory authority. Un-recommend good-server-descriptor
2921 getinfo and status events until we have a better design for them.
2924 Changes in version 0.2.2.5-alpha - 2009-10-11
2925 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
2928 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
2930 o Directory authorities:
2931 - Temporarily (just for this release) move dizum to an alternate
2935 Changes in version 0.2.2.4-alpha - 2009-10-10
2936 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
2937 introduces a new unit test framework, shifts directry authority
2938 addresses around to reduce the impact from recent blocking events,
2939 and fixes a few smaller bugs.
2942 - Fix several more asserts in the circuit_build_times code, for
2943 example one that causes Tor to fail to start once we have
2944 accumulated 5000 build times in the state file. Bugfixes on
2945 0.2.2.2-alpha; fixes bug 1108.
2947 o New directory authorities:
2948 - Move moria1 and Tonga to alternate IP addresses.
2951 - Log SSL state transitions at debug level during handshake, and
2952 include SSL states in error messages. This may help debug future
2953 SSL handshake issues.
2954 - Add a new "Handshake" log domain for activities that happen
2955 during the TLS handshake.
2956 - Revert to the "June 3 2009" ip-to-country file. The September one
2957 seems to have removed most US IP addresses.
2958 - Directory authorities now reject Tor relays with versions less than
2959 0.1.2.14. This step cuts out four relays from the current network,
2960 none of which are very big.
2963 - Fix a couple of smaller issues with gathering statistics. Bugfixes
2965 - Fix two memory leaks in the error case of
2966 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
2967 - Don't count one-hop circuits when we're estimating how long it
2968 takes circuits to build on average. Otherwise we'll set our circuit
2969 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
2970 - Directory authorities no longer change their opinion of, or vote on,
2971 whether a router is Running, unless they have themselves been
2972 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
2975 o Code simplifications and refactoring:
2976 - Revise our unit tests to use the "tinytest" framework, so we
2977 can run tests in their own processes, have smarter setup/teardown
2978 code, and so on. The unit test code has moved to its own
2979 subdirectory, and has been split into multiple modules.
2982 Changes in version 0.2.2.3-alpha - 2009-09-23
2983 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
2986 - Fix an overzealous assert in our new circuit build timeout code.
2987 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
2990 - If the networkstatus consensus tells us that we should use a
2991 negative circuit package window, ignore it. Otherwise we'll
2992 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
2995 Changes in version 0.2.2.2-alpha - 2009-09-21
2996 Tor 0.2.2.2-alpha introduces our latest performance improvement for
2997 clients: Tor tracks the average time it takes to build a circuit, and
2998 avoids using circuits that take too long to build. For fast connections,
2999 this feature can cut your expected latency in half. For slow or flaky
3000 connections, it could ruin your Tor experience. Let us know if it does!
3003 - Tor now tracks how long it takes to build client-side circuits
3004 over time, and adapts its timeout to local network performance.
3005 Since a circuit that takes a long time to build will also provide
3006 bad performance, we get significant latency improvements by
3007 discarding the slowest 20% of circuits. Specifically, Tor creates
3008 circuits more aggressively than usual until it has enough data
3009 points for a good timeout estimate. Implements proposal 151.
3010 We are especially looking for reports (good and bad) from users with
3011 both EDGE and broadband connections that can move from broadband
3012 to EDGE and find out if the build-time data in the .tor/state gets
3013 reset without loss of Tor usability. You should also see a notice
3014 log message telling you that Tor has reset its timeout.
3015 - Directory authorities can now vote on arbitary integer values as
3016 part of the consensus process. This is designed to help set
3017 network-wide parameters. Implements proposal 167.
3018 - Tor now reads the "circwindow" parameter out of the consensus,
3019 and uses that value for its circuit package window rather than the
3020 default of 1000 cells. Begins the implementation of proposal 168.
3023 - Fix a remotely triggerable memory leak when a consensus document
3024 contains more than one signature from the same voter. Bugfix on
3028 - Fix an extremely rare infinite recursion bug that could occur if
3029 we tried to log a message after shutting down the log subsystem.
3030 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
3031 - Fix parsing for memory or time units given without a space between
3032 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
3033 - A networkstatus vote must contain exactly one signature. Spec
3034 conformance issue. Bugfix on 0.2.0.3-alpha.
3035 - Fix an obscure bug where hidden services on 64-bit big-endian
3036 systems might mis-read the timestamp in v3 introduce cells, and
3037 refuse to connect back to the client. Discovered by "rotor".
3038 Bugfix on 0.2.1.6-alpha.
3039 - We were triggering a CLOCK_SKEW controller status event whenever
3040 we connect via the v2 connection protocol to any relay that has
3041 a wrong clock. Instead, we should only inform the controller when
3042 it's a trusted authority that claims our clock is wrong. Bugfix
3043 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
3044 - We were telling the controller about CHECKING_REACHABILITY and
3045 REACHABILITY_FAILED status events whenever we launch a testing
3046 circuit or notice that one has failed. Instead, only tell the
3047 controller when we want to inform the user of overall success or
3048 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
3050 - Don't warn when we're using a circuit that ends with a node
3051 excluded in ExcludeExitNodes, but the circuit is not used to access
3052 the outside world. This should help fix bug 1090, but more problems
3053 remain. Bugfix on 0.2.1.6-alpha.
3054 - Work around a small memory leak in some versions of OpenSSL that
3055 stopped the memory used by the hostname TLS extension from being
3057 - Make our 'torify' script more portable; if we have only one of
3058 'torsocks' or 'tsocks' installed, don't complain to the user;
3059 and explain our warning about tsocks better.
3062 - Add a "getinfo status/accepted-server-descriptor" controller
3063 command, which is the recommended way for controllers to learn
3064 whether our server descriptor has been successfully received by at
3065 least on directory authority. Un-recommend good-server-descriptor
3066 getinfo and status events until we have a better design for them.
3067 - Update to the "September 4 2009" ip-to-country file.
3070 Changes in version 0.2.2.1-alpha - 2009-08-26
3071 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
3072 Tor clients to bootstrap on networks where only port 80 is reachable,
3073 makes it more straightforward to support hardware crypto accelerators,
3074 and starts the groundwork for gathering stats safely at relays.
3077 - Start the process of disabling ".exit" address notation, since it
3078 can be used for a variety of esoteric application-level attacks
3079 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
3082 o New directory authorities:
3083 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
3087 - New AccelName and AccelDir options add support for dynamic OpenSSL
3088 hardware crypto acceleration engines.
3089 - Tor now supports tunneling all of its outgoing connections over
3090 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
3091 configuration options. Code by Christopher Davis.
3094 - Send circuit or stream sendme cells when our window has decreased
3095 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
3096 by Karsten when testing the "reduce circuit window" performance
3097 patch. Bugfix on the 54th commit on Tor -- from July 2002,
3098 before the release of Tor 0.0.0. This is the new winner of the
3101 o New options for gathering stats safely:
3102 - Directory mirrors that set "DirReqStatistics 1" write statistics
3103 about directory requests to disk every 24 hours. As compared to the
3104 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
3105 1) stats are written to disk exactly every 24 hours; 2) estimated
3106 shares of v2 and v3 requests are determined as mean values, not at
3107 the end of a measurement period; 3) unresolved requests are listed
3108 with country code '??'; 4) directories also measure download times.
3109 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
3110 number of exit streams and transferred bytes per port to disk every
3112 - Relays that set "CellStatistics 1" write statistics on how long
3113 cells spend in their circuit queues to disk every 24 hours.
3114 - Entry nodes that set "EntryStatistics 1" write statistics on the
3115 rough number and origins of connecting clients to disk every 24
3117 - Relays that write any of the above statistics to disk and set
3118 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
3119 their extra-info documents.
3122 - New --digests command-line switch to output the digests of the
3123 source files Tor was built with.
3124 - The "torify" script now uses torsocks where available.
3125 - The memarea code now uses a sentinel value at the end of each area
3126 to make sure nothing writes beyond the end of an area. This might
3127 help debug some conceivable causes of bug 930.
3128 - Time and memory units in the configuration file can now be set to
3129 fractional units. For example, "2.5 GB" is now a valid value for
3131 - Certain Tor clients (such as those behind check.torproject.org) may
3132 want to fetch the consensus in an extra early manner. To enable this
3133 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
3134 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
3135 as only certain clients who must have this information sooner should
3137 - Instead of adding the svn revision to the Tor version string, report
3138 the git commit (when we're building from a git checkout).
3141 - If any of the v3 certs we download are unparseable, we should
3142 actually notice the failure so we don't retry indefinitely. Bugfix
3143 on 0.2.0.x; reported by "rotator".
3144 - If the cached cert file is unparseable, warn but don't exit.
3145 - Fix possible segmentation fault on directory authorities. Bugfix on
3147 - When Tor fails to parse a descriptor of any kind, dump it to disk.
3148 Might help diagnosing bug 1051.
3150 o Deprecated and removed features:
3151 - The controller no longer accepts the old obsolete "addr-mappings/"
3152 or "unregistered-servers-" GETINFO values.
3153 - Hidden services no longer publish version 0 descriptors, and clients
3154 do not request or use version 0 descriptors. However, the old hidden
3155 service authorities still accept and serve version 0 descriptors
3156 when contacted by older hidden services/clients.
3157 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
3158 always on; using them is necessary for correct forward-compatible
3160 - Remove support for .noconnect style addresses. Nobody was using
3161 them, and they provided another avenue for detecting Tor users
3162 via application-level web tricks.
3164 o Packaging changes:
3165 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
3166 installer bundles. See
3167 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
3168 for details of what's new in Vidalia 0.2.3.
3169 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
3170 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
3171 configuration file, rather than the old Privoxy.
3172 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
3173 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
3174 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
3175 better compatibility with OS X 10.6, aka Snow Leopard.
3176 - OS X Vidalia Bundle: The multi-package installer is now replaced
3177 by a simple drag and drop to the /Applications folder. This change
3178 occurred with the upgrade to Vidalia 0.2.3.
3181 Changes in version 0.2.1.19 - 2009-07-28
3182 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
3183 services on Tor 0.2.1.3-alpha through 0.2.1.18.
3186 - Make accessing hidden services on 0.2.1.x work right again.
3187 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
3188 part of patch provided by "optimist".
3191 - When a relay/bridge is writing out its identity key fingerprint to
3192 the "fingerprint" file and to its logs, write it without spaces. Now
3193 it will look like the fingerprints in our bridges documentation,
3194 and confuse fewer users.
3197 - Relays no longer publish a new server descriptor if they change
3198 their MaxAdvertisedBandwidth config option but it doesn't end up
3199 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
3200 fixes bug 1026. Patch from Sebastian.
3201 - Avoid leaking memory every time we get a create cell but we have
3202 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
3203 fixes bug 1034. Reported by BarkerJr.
3206 Changes in version 0.2.1.18 - 2009-07-24
3207 Tor 0.2.1.18 lays the foundations for performance improvements,
3208 adds status events to help users diagnose bootstrap problems, adds
3209 optional authentication/authorization for hidden services, fixes a
3210 variety of potential anonymity problems, and includes a huge pile of
3211 other features and bug fixes.
3214 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
3217 Changes in version 0.2.1.17-rc - 2009-07-07
3218 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
3219 candidate for the 0.2.1.x series. It lays the groundwork for further
3220 client performance improvements, and also fixes a big bug with directory
3221 authorities that were causing them to assign Guard and Stable flags
3224 The Windows bundles also finally include the geoip database that we
3225 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
3226 should actually install Torbutton rather than giving you a cryptic
3227 failure message (oops).
3230 - Clients now use the bandwidth values in the consensus, rather than
3231 the bandwidth values in each relay descriptor. This approach opens
3232 the door to more accurate bandwidth estimates once the directory
3233 authorities start doing active measurements. Implements more of
3237 - When Tor clients restart after 1-5 days, they discard all their
3238 cached descriptors as too old, but they still use the cached
3239 consensus document. This approach is good for robustness, but
3240 bad for performance: since they don't know any bandwidths, they
3241 end up choosing at random rather than weighting their choice by
3242 speed. Fixed by the above feature of putting bandwidths in the
3243 consensus. Bugfix on 0.2.0.x.
3244 - Directory authorities were neglecting to mark relays down in their
3245 internal histories if the relays fall off the routerlist without
3246 ever being found unreachable. So there were relays in the histories
3247 that haven't been seen for eight months, and are listed as being
3248 up for eight months. This wreaked havoc on the "median wfu"
3249 and "median mtbf" calculations, in turn making Guard and Stable
3250 flags very wrong, hurting network performance. Fixes bugs 696 and
3251 969. Bugfix on 0.2.0.6-alpha.
3254 - Serve the DirPortFrontPage page even when we have been approaching
3255 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
3256 - The control port would close the connection before flushing long
3257 replies, such as the network consensus, if a QUIT command was issued
3258 before the reply had completed. Now, the control port flushes all
3259 pending replies before closing the connection. Also fixed a spurious
3260 warning when a QUIT command is issued after a malformed or rejected
3261 AUTHENTICATE command, but before the connection was closed. Patch
3262 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
3263 - When we can't find an intro key for a v2 hidden service descriptor,
3264 fall back to the v0 hidden service descriptor and log a bug message.
3265 Workaround for bug 1024.
3266 - Fix a log message that did not respect the SafeLogging option.
3270 - If we're a relay and we change our IP address, be more verbose
3271 about the reason that made us change. Should help track down
3272 further bugs for relays on dynamic IP addresses.
3275 Changes in version 0.2.0.35 - 2009-06-24
3277 - Avoid crashing in the presence of certain malformed descriptors.
3278 Found by lark, and by automated fuzzing.
3279 - Fix an edge case where a malicious exit relay could convince a
3280 controller that the client's DNS question resolves to an internal IP
3281 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
3284 - Finally fix the bug where dynamic-IP relays disappear when their
3285 IP address changes: directory mirrors were mistakenly telling
3286 them their old address if they asked via begin_dir, so they
3287 never got an accurate answer about their new address, so they
3288 just vanished after a day. For belt-and-suspenders, relays that
3289 don't set Address in their config now avoid using begin_dir for
3290 all direct connections. Should fix bugs 827, 883, and 900.
3291 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
3292 that would occur on some exit nodes when DNS failures and timeouts
3293 occurred in certain patterns. Fix for bug 957.
3296 - When starting with a cache over a few days old, do not leak
3297 memory for the obsolete router descriptors in it. Bugfix on
3298 0.2.0.33; fixes bug 672.
3299 - Hidden service clients didn't use a cached service descriptor that
3300 was older than 15 minutes, but wouldn't fetch a new one either,
3301 because there was already one in the cache. Now, fetch a v2
3302 descriptor unless the same descriptor was added to the cache within
3303 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
3306 Changes in version 0.2.1.16-rc - 2009-06-20
3307 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
3308 a bunch of minor bugs.
3311 - Fix an edge case where a malicious exit relay could convince a
3312 controller that the client's DNS question resolves to an internal IP
3313 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
3315 o Major performance improvements (on 0.2.0.x):
3316 - Disable and refactor some debugging checks that forced a linear scan
3317 over the whole server-side DNS cache. These accounted for over 50%
3318 of CPU time on a relatively busy exit node's gprof profile. Found
3320 - Disable some debugging checks that appeared in exit node profile
3324 - Update to the "June 3 2009" ip-to-country file.
3325 - Do not have tor-resolve automatically refuse all .onion addresses;
3326 if AutomapHostsOnResolve is set in your torrc, this will work fine.
3328 o Minor bugfixes (on 0.2.0.x):
3329 - Log correct error messages for DNS-related network errors on
3331 - Fix a race condition that could cause crashes or memory corruption
3332 when running as a server with a controller listening for log
3334 - Avoid crashing when we have a policy specified in a DirPolicy or
3335 SocksPolicy or ReachableAddresses option with ports set on it,
3336 and we re-load the policy. May fix bug 996.
3337 - Hidden service clients didn't use a cached service descriptor that
3338 was older than 15 minutes, but wouldn't fetch a new one either,
3339 because there was already one in the cache. Now, fetch a v2
3340 descriptor unless the same descriptor was added to the cache within
3341 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
3343 o Minor bugfixes (on 0.2.1.x):
3344 - Don't warn users about low port and hibernation mix when they
3345 provide a *ListenAddress directive to fix that. Bugfix on
3347 - When switching back and forth between bridge mode, do not start
3348 gathering GeoIP data until two hours have passed.
3349 - Do not complain that the user has requested an excluded node as
3350 an exit when the node is not really an exit. This could happen
3351 because the circuit was for testing, or an introduction point.
3355 Changes in version 0.2.1.15-rc - 2009-05-25
3356 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
3357 series. It fixes a major bug on fast exit relays, as well as a variety
3360 o Major bugfixes (on 0.2.0.x):
3361 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
3362 that would occur on some exit nodes when DNS failures and timeouts
3363 occurred in certain patterns. Fix for bug 957.
3365 o Minor bugfixes (on 0.2.0.x):
3366 - Actually return -1 in the error case for read_bandwidth_usage().
3367 Harmless bug, since we currently don't care about the return value
3368 anywhere. Bugfix on 0.2.0.9-alpha.
3369 - Provide a more useful log message if bug 977 (related to buffer
3370 freelists) ever reappears, and do not crash right away.
3371 - Fix an assertion failure on 64-bit platforms when we allocated
3372 memory right up to the end of a memarea, then realigned the memory
3373 one step beyond the end. Fixes a possible cause of bug 930.
3374 - Protect the count of open sockets with a mutex, so we can't
3375 corrupt it when two threads are closing or opening sockets at once.
3376 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
3377 - Don't allow a bridge to publish its router descriptor to a
3378 non-bridge directory authority. Fixes part of bug 932.
3379 - When we change to or from being a bridge, reset our counts of
3380 client usage by country. Fixes bug 932.
3381 - Fix a bug that made stream bandwidth get misreported to the
3383 - Stop using malloc_usable_size() to use more area than we had
3384 actually allocated: it was safe, but made valgrind really unhappy.
3385 - Fix a memory leak when v3 directory authorities load their keys
3386 and cert from disk. Bugfix on 0.2.0.1-alpha.
3388 o Minor bugfixes (on 0.2.1.x):
3389 - Fix use of freed memory when deciding to mark a non-addable
3390 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
3393 Changes in version 0.2.1.14-rc - 2009-04-12
3394 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
3395 series. It begins fixing some major performance problems, and also
3396 finally addresses the bug that was causing relays on dynamic IP
3397 addresses to fall out of the directory.
3400 - Clients replace entry guards that were chosen more than a few months
3401 ago. This change should significantly improve client performance,
3402 especially once more people upgrade, since relays that have been
3403 a guard for a long time are currently overloaded.
3405 o Major bugfixes (on 0.2.0):
3406 - Finally fix the bug where dynamic-IP relays disappear when their
3407 IP address changes: directory mirrors were mistakenly telling
3408 them their old address if they asked via begin_dir, so they
3409 never got an accurate answer about their new address, so they
3410 just vanished after a day. For belt-and-suspenders, relays that
3411 don't set Address in their config now avoid using begin_dir for
3412 all direct connections. Should fix bugs 827, 883, and 900.
3413 - Relays were falling out of the networkstatus consensus for
3414 part of a day if they changed their local config but the
3415 authorities discarded their new descriptor as "not sufficiently
3416 different". Now directory authorities accept a descriptor as changed
3417 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
3419 - Avoid crashing in the presence of certain malformed descriptors.
3420 Found by lark, and by automated fuzzing.
3423 - When generating circuit events with verbose nicknames for
3424 controllers, try harder to look up nicknames for routers on a
3425 circuit. (Previously, we would look in the router descriptors we had
3426 for nicknames, but not in the consensus.) Partial fix for bug 941.
3427 - If the bridge config line doesn't specify a port, assume 443.
3428 This makes bridge lines a bit smaller and easier for users to
3430 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
3431 bytes (aka 20KB/s), to match our documentation. Also update
3432 directory authorities so they always assign the Fast flag to relays
3433 with 20KB/s of capacity. Now people running relays won't suddenly
3434 find themselves not seeing any use, if the network gets faster
3436 - Update to the "April 3 2009" ip-to-country file.
3439 - Avoid trying to print raw memory to the logs when we decide to
3440 give up on downloading a given relay descriptor. Bugfix on
3442 - In tor-resolve, when the Tor client to use is specified by
3443 <hostname>:<port>, actually use the specified port rather than
3444 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
3445 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
3446 - When starting with a cache over a few days old, do not leak
3447 memory for the obsolete router descriptors in it. Bugfix on
3449 - Avoid double-free on list of successfully uploaded hidden
3450 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
3451 - Change memarea_strndup() implementation to work even when
3452 duplicating a string at the end of a page. This bug was
3453 harmless for now, but could have meant crashes later. Fix by
3454 lark. Bugfix on 0.2.1.1-alpha.
3455 - Limit uploaded directory documents to be 16M rather than 500K.
3456 The directory authorities were refusing v3 consensus votes from
3457 other authorities, since the votes are now 504K. Fixes bug 959;
3458 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
3459 - Directory authorities should never send a 503 "busy" response to
3460 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
3464 Changes in version 0.2.1.13-alpha - 2009-03-09
3465 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
3466 cleanups. We're finally getting close to a release candidate.
3469 - Correctly update the list of which countries we exclude as
3470 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
3471 lark. Bugfix on 0.2.1.6-alpha.
3473 o Minor bugfixes (on 0.2.0.x and earlier):
3474 - Automatically detect MacOSX versions earlier than 10.4.0, and
3475 disable kqueue from inside Tor when running with these versions.
3476 We previously did this from the startup script, but that was no
3477 help to people who didn't use the startup script. Resolves bug 863.
3478 - When we had picked an exit node for a connection, but marked it as
3479 "optional", and it turned out we had no onion key for the exit,
3480 stop wanting that exit and try again. This situation may not
3481 be possible now, but will probably become feasible with proposal
3482 158. Spotted by rovv. Fixes another case of bug 752.
3483 - Clients no longer cache certificates for authorities they do not
3484 recognize. Bugfix on 0.2.0.9-alpha.
3485 - When we can't transmit a DNS request due to a network error, retry
3486 it after a while, and eventually transmit a failing response to
3487 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
3488 - If the controller claimed responsibility for a stream, but that
3489 stream never finished making its connection, it would live
3490 forever in circuit_wait state. Now we close it after SocksTimeout
3491 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
3492 - Drop begin cells to a hidden service if they come from the middle
3493 of a circuit. Patch from lark.
3494 - When we erroneously receive two EXTEND cells for the same circuit
3495 ID on the same connection, drop the second. Patch from lark.
3496 - Fix a crash that occurs on exit nodes when a nameserver request
3497 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
3498 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
3500 - Do not assume that a stack-allocated character array will be
3501 64-bit aligned on platforms that demand that uint64_t access is
3502 aligned. Possible fix for bug 604.
3503 - Parse dates and IPv4 addresses in a locale- and libc-independent
3504 manner, to avoid platform-dependent behavior on malformed input.
3505 - Build correctly when configured to build outside the main source
3506 path. Patch from Michael Gold.
3507 - We were already rejecting relay begin cells with destination port
3508 of 0. Now also reject extend cells with destination port or address
3509 of 0. Suggested by lark.
3511 o Minor bugfixes (on 0.2.1.x):
3512 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
3513 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
3514 - If we're an exit node, scrub the IP address to which we are exiting
3515 in the logs. Bugfix on 0.2.1.8-alpha.
3518 - On Linux, use the prctl call to re-enable core dumps when the user
3520 - New controller event NEWCONSENSUS that lists the networkstatus
3521 lines for every recommended relay. Now controllers like Torflow
3522 can keep up-to-date on which relays they should be using.
3523 - Update to the "February 26 2009" ip-to-country file.
3526 Changes in version 0.2.0.34 - 2009-02-08
3527 Tor 0.2.0.34 features several more security-related fixes. You should
3528 upgrade, especially if you run an exit relay (remote crash) or a
3529 directory authority (remote infinite loop), or you're on an older
3530 (pre-XP) or not-recently-patched Windows (remote exploit).
3532 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
3533 have many known flaws, and nobody should be using them. You should
3534 upgrade. If you're using a Linux or BSD and its packages are obsolete,
3535 stop using those packages and upgrade anyway.
3538 - Fix an infinite-loop bug on handling corrupt votes under certain
3539 circumstances. Bugfix on 0.2.0.8-alpha.
3540 - Fix a temporary DoS vulnerability that could be performed by
3541 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3542 - Avoid a potential crash on exit nodes when processing malformed
3543 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
3544 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
3545 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
3548 - Fix compilation on systems where time_t is a 64-bit integer.
3549 Patch from Matthias Drochner.
3550 - Don't consider expiring already-closed client connections. Fixes
3551 bug 893. Bugfix on 0.0.2pre20.
3554 Changes in version 0.2.1.12-alpha - 2009-02-08
3555 Tor 0.2.1.12-alpha features several more security-related fixes. You
3556 should upgrade, especially if you run an exit relay (remote crash) or
3557 a directory authority (remote infinite loop), or you're on an older
3558 (pre-XP) or not-recently-patched Windows (remote exploit). It also
3559 includes a big pile of minor bugfixes and cleanups.
3562 - Fix an infinite-loop bug on handling corrupt votes under certain
3563 circumstances. Bugfix on 0.2.0.8-alpha.
3564 - Fix a temporary DoS vulnerability that could be performed by
3565 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
3566 - Avoid a potential crash on exit nodes when processing malformed
3567 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
3570 - Let controllers actually ask for the "clients_seen" event for
3571 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
3572 reported by Matt Edman.
3573 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
3575 - Fix a bug in address parsing that was preventing bridges or hidden
3576 service targets from being at IPv6 addresses.
3577 - Solve a bug that kept hardware crypto acceleration from getting
3578 enabled when accounting was turned on. Fixes bug 907. Bugfix on
3580 - Remove a bash-ism from configure.in to build properly on non-Linux
3581 platforms. Bugfix on 0.2.1.1-alpha.
3582 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
3583 headers. Bugfix on 0.2.0.10-alpha.
3584 - Don't consider expiring already-closed client connections. Fixes
3585 bug 893. Bugfix on 0.0.2pre20.
3586 - Fix another interesting corner-case of bug 891 spotted by rovv:
3587 Previously, if two hosts had different amounts of clock drift, and
3588 one of them created a new connection with just the wrong timing,
3589 the other might decide to deprecate the new connection erroneously.
3590 Bugfix on 0.1.1.13-alpha.
3591 - Resolve a very rare crash bug that could occur when the user forced
3592 a nameserver reconfiguration during the middle of a nameserver
3593 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
3594 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
3595 Bugfix on 0.2.1.7-alpha.
3596 - If we're using bridges and our network goes away, be more willing
3597 to forgive our bridges and try again when we get an application
3598 request. Bugfix on 0.2.0.x.
3601 - Support platforms where time_t is 64 bits long. (Congratulations,
3602 NetBSD!) Patch from Matthias Drochner.
3603 - Add a 'getinfo status/clients-seen' controller command, in case
3604 controllers want to hear clients_seen events but connect late.
3607 - Disable GCC's strict alias optimization by default, to avoid the
3608 likelihood of its introducing subtle bugs whenever our code violates
3609 the letter of C99's alias rules.
3612 Changes in version 0.2.0.33 - 2009-01-21
3613 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
3614 useful to users. It also finally fixes a bug where a relay or client
3615 that's been off for many days would take a long time to bootstrap.
3617 This update also fixes an important security-related bug reported by
3618 Ilja van Sprundel. You should upgrade. (We'll send out more details
3619 about the bug once people have had some time to upgrade.)
3622 - Fix a heap-corruption bug that may be remotely triggerable on
3623 some platforms. Reported by Ilja van Sprundel.
3626 - When a stream at an exit relay is in state "resolving" or
3627 "connecting" and it receives an "end" relay cell, the exit relay
3628 would silently ignore the end cell and not close the stream. If
3629 the client never closes the circuit, then the exit relay never
3630 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
3632 - When sending CREATED cells back for a given circuit, use a 64-bit
3633 connection ID to find the right connection, rather than an addr:port
3634 combination. Now that we can have multiple OR connections between
3635 the same ORs, it is no longer possible to use addr:port to uniquely
3636 identify a connection.
3637 - Bridge relays that had DirPort set to 0 would stop fetching
3638 descriptors shortly after startup, and then briefly resume
3639 after a new bandwidth test and/or after publishing a new bridge
3640 descriptor. Bridge users that try to bootstrap from them would
3641 get a recent networkstatus but would get descriptors from up to
3642 18 hours earlier, meaning most of the descriptors were obsolete
3643 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3644 - Prevent bridge relays from serving their 'extrainfo' document
3645 to anybody who asks, now that extrainfo docs include potentially
3646 sensitive aggregated client geoip summaries. Bugfix on
3648 - If the cached networkstatus consensus is more than five days old,
3649 discard it rather than trying to use it. In theory it could be
3650 useful because it lists alternate directory mirrors, but in practice
3651 it just means we spend many minutes trying directory mirrors that
3652 are long gone from the network. Also discard router descriptors as
3653 we load them if they are more than five days old, since the onion
3654 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
3657 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
3658 could make gcc generate non-functional binary search code. Bugfix
3660 - Build correctly on platforms without socklen_t.
3661 - Compile without warnings on solaris.
3662 - Avoid potential crash on internal error during signature collection.
3663 Fixes bug 864. Patch from rovv.
3664 - Correct handling of possible malformed authority signing key
3665 certificates with internal signature types. Fixes bug 880.
3666 Bugfix on 0.2.0.3-alpha.
3667 - Fix a hard-to-trigger resource leak when logging credential status.
3669 - When we can't initialize DNS because the network is down, do not
3670 automatically stop Tor from starting. Instead, we retry failed
3671 dns_init() every 10 minutes, and change the exit policy to reject
3672 *:* until one succeeds. Fixes bug 691.
3673 - Use 64 bits instead of 32 bits for connection identifiers used with
3674 the controller protocol, to greatly reduce risk of identifier reuse.
3675 - When we're choosing an exit node for a circuit, and we have
3676 no pending streams, choose a good general exit rather than one that
3677 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
3678 - Fix another case of assuming, when a specific exit is requested,
3679 that we know more than the user about what hosts it allows.
3680 Fixes one case of bug 752. Patch from rovv.
3681 - Clip the MaxCircuitDirtiness config option to a minimum of 10
3682 seconds. Warn the user if lower values are given in the
3683 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
3684 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
3685 user if lower values are given in the configuration. Bugfix on
3686 0.1.1.17-rc. Patch by Sebastian.
3687 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
3688 the cache because we already had a v0 descriptor with the same ID.
3689 Bugfix on 0.2.0.18-alpha.
3690 - Fix a race condition when freeing keys shared between main thread
3691 and CPU workers that could result in a memory leak. Bugfix on
3692 0.1.0.1-rc. Fixes bug 889.
3693 - Send a valid END cell back when a client tries to connect to a
3694 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
3695 840. Patch from rovv.
3696 - Check which hops rendezvous stream cells are associated with to
3697 prevent possible guess-the-streamid injection attacks from
3698 intermediate hops. Fixes another case of bug 446. Based on patch
3700 - If a broken client asks a non-exit router to connect somewhere,
3701 do not even do the DNS lookup before rejecting the connection.
3702 Fixes another case of bug 619. Patch from rovv.
3703 - When a relay gets a create cell it can't decrypt (e.g. because it's
3704 using the wrong onion key), we were dropping it and letting the
3705 client time out. Now actually answer with a destroy cell. Fixes
3706 bug 904. Bugfix on 0.0.2pre8.
3708 o Minor bugfixes (hidden services):
3709 - Do not throw away existing introduction points on SIGHUP. Bugfix on
3710 0.0.6pre1. Patch by Karsten. Fixes bug 874.
3713 - Report the case where all signatures in a detached set are rejected
3714 differently than the case where there is an error handling the
3716 - When we realize that another process has modified our cached
3717 descriptors, print out a more useful error message rather than
3718 triggering an assertion. Fixes bug 885. Patch from Karsten.
3719 - Implement the 0x20 hack to better resist DNS poisoning: set the
3720 case on outgoing DNS requests randomly, and reject responses that do
3721 not match the case correctly. This logic can be disabled with the
3722 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
3723 of servers that do not reliably preserve case in replies. See
3724 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
3726 - Check DNS replies for more matching fields to better resist DNS
3728 - Never use OpenSSL compression: it wastes RAM and CPU trying to
3729 compress cells, which are basically all encrypted, compressed, or
3733 Changes in version 0.2.1.11-alpha - 2009-01-20
3734 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
3735 week it will take a long time to bootstrap again" bug. It also fixes
3736 an important security-related bug reported by Ilja van Sprundel. You
3737 should upgrade. (We'll send out more details about the bug once people
3738 have had some time to upgrade.)
3741 - Fix a heap-corruption bug that may be remotely triggerable on
3742 some platforms. Reported by Ilja van Sprundel.
3745 - Discard router descriptors as we load them if they are more than
3746 five days old. Otherwise if Tor is off for a long time and then
3747 starts with cached descriptors, it will try to use the onion
3748 keys in those obsolete descriptors when building circuits. Bugfix
3749 on 0.2.0.x. Fixes bug 887.
3752 - Try to make sure that the version of Libevent we're running with
3753 is binary-compatible with the one we built with. May address bug
3755 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
3756 for bug 905. Bugfix on 0.2.1.7-alpha.
3757 - Add a new --enable-local-appdata configuration switch to change
3758 the default location of the datadir on win32 from APPDATA to
3759 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
3760 entirely. Patch from coderman.
3763 - Make outbound DNS packets respect the OutboundBindAddress setting.
3764 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
3765 - When our circuit fails at the first hop (e.g. we get a destroy
3766 cell back), avoid using that OR connection anymore, and also
3767 tell all the one-hop directory requests waiting for it that they
3768 should fail. Bugfix on 0.2.1.3-alpha.
3769 - In the torify(1) manpage, mention that tsocks will leak your
3773 Changes in version 0.2.1.10-alpha - 2009-01-06
3774 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
3775 would make the bridge relay not so useful if it had DirPort set to 0,
3776 and one that could let an attacker learn a little bit of information
3777 about the bridge's users), and a bug that would cause your Tor relay
3778 to ignore a circuit create request it can't decrypt (rather than reply
3779 with an error). It also fixes a wide variety of other bugs.
3782 - If the cached networkstatus consensus is more than five days old,
3783 discard it rather than trying to use it. In theory it could
3784 be useful because it lists alternate directory mirrors, but in
3785 practice it just means we spend many minutes trying directory
3786 mirrors that are long gone from the network. Helps bug 887 a bit;
3788 - Bridge relays that had DirPort set to 0 would stop fetching
3789 descriptors shortly after startup, and then briefly resume
3790 after a new bandwidth test and/or after publishing a new bridge
3791 descriptor. Bridge users that try to bootstrap from them would
3792 get a recent networkstatus but would get descriptors from up to
3793 18 hours earlier, meaning most of the descriptors were obsolete
3794 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
3795 - Prevent bridge relays from serving their 'extrainfo' document
3796 to anybody who asks, now that extrainfo docs include potentially
3797 sensitive aggregated client geoip summaries. Bugfix on
3801 - New controller event "clients_seen" to report a geoip-based summary
3802 of which countries we've seen clients from recently. Now controllers
3803 like Vidalia can show bridge operators that they're actually making
3805 - Build correctly against versions of OpenSSL 0.9.8 or later built
3806 without support for deprecated functions.
3807 - Update to the "December 19 2008" ip-to-country file.
3809 o Minor bugfixes (on 0.2.0.x):
3810 - Authorities now vote for the Stable flag for any router whose
3811 weighted MTBF is at least 5 days, regardless of the mean MTBF.
3812 - Do not remove routers as too old if we do not have any consensus
3813 document. Bugfix on 0.2.0.7-alpha.
3814 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
3815 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
3816 - When an exit relay resolves a stream address to a local IP address,
3817 do not just keep retrying that same exit relay over and
3818 over. Instead, just close the stream. Addresses bug 872. Bugfix
3819 on 0.2.0.32. Patch from rovv.
3820 - If a hidden service sends us an END cell, do not consider
3821 retrying the connection; just close it. Patch from rovv.
3822 - When we made bridge authorities stop serving bridge descriptors over
3823 unencrypted links, we also broke DirPort reachability testing for
3824 bridges. So bridges with a non-zero DirPort were printing spurious
3825 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
3826 - When a relay gets a create cell it can't decrypt (e.g. because it's
3827 using the wrong onion key), we were dropping it and letting the
3828 client time out. Now actually answer with a destroy cell. Fixes
3829 bug 904. Bugfix on 0.0.2pre8.
3830 - Squeeze 2-5% out of client performance (according to oprofile) by
3831 improving the implementation of some policy-manipulation functions.
3833 o Minor bugfixes (on 0.2.1.x):
3834 - Make get_interface_address() function work properly again; stop
3835 guessing the wrong parts of our address as our address.
3836 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
3837 send on that circuit. Otherwise we might violate the proposal-110
3838 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
3840 - When we're sending non-EXTEND cells to the first hop in a circuit,
3841 for example to use an encrypted directory connection, we don't need
3842 to use RELAY_EARLY cells: the first hop knows what kind of cell
3843 it is, and nobody else can even see the cell type. Conserving
3844 RELAY_EARLY cells makes it easier to cannibalize circuits like
3846 - Stop logging nameserver addresses in reverse order.
3847 - If we are retrying a directory download slowly over and over, do
3848 not automatically give up after the 254th failure. Bugfix on
3850 - Resume reporting accurate "stream end" reasons to the local control
3851 port. They were lost in the changes for Proposal 148. Bugfix on
3854 o Deprecated and removed features:
3855 - The old "tor --version --version" command, which would print out
3856 the subversion "Id" of most of the source files, is now removed. It
3857 turned out to be less useful than we'd expected, and harder to
3860 o Code simplifications and refactoring:
3861 - Change our header file guard macros to be less likely to conflict
3862 with system headers. Adam Langley noticed that we were conflicting
3863 with log.h on Android.
3864 - Tool-assisted documentation cleanup. Nearly every function or
3865 static variable in Tor should have its own documentation now.
3868 Changes in version 0.2.1.9-alpha - 2008-12-25
3869 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
3871 o New directory authorities:
3872 - gabelmoo (the authority run by Karsten Loesing) now has a new
3876 - Never use a connection with a mismatched address to extend a
3877 circuit, unless that connection is canonical. A canonical
3878 connection is one whose address is authenticated by the router's
3879 identity key, either in a NETINFO cell or in a router descriptor.
3880 - Avoid a possible memory corruption bug when receiving hidden service
3881 descriptors. Bugfix on 0.2.1.6-alpha.
3884 - Fix a logic error that would automatically reject all but the first
3885 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
3886 part of bug 813/868. Bug spotted by coderman.
3887 - When a stream at an exit relay is in state "resolving" or
3888 "connecting" and it receives an "end" relay cell, the exit relay
3889 would silently ignore the end cell and not close the stream. If
3890 the client never closes the circuit, then the exit relay never
3891 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
3893 - When we can't initialize DNS because the network is down, do not
3894 automatically stop Tor from starting. Instead, retry failed
3895 dns_init() every 10 minutes, and change the exit policy to reject
3896 *:* until one succeeds. Fixes bug 691.
3899 - Give a better error message when an overzealous init script says
3900 "sudo -u username tor --user username". Makes Bug 882 easier for
3902 - When a directory authority gives us a new guess for our IP address,
3903 log which authority we used. Hopefully this will help us debug
3904 the recent complaints about bad IP address guesses.
3905 - Detect svn revision properly when we're using git-svn.
3906 - Try not to open more than one descriptor-downloading connection
3907 to an authority at once. This should reduce load on directory
3908 authorities. Fixes bug 366.
3909 - Add cross-certification to newly generated certificates, so that
3910 a signing key is enough information to look up a certificate.
3911 Partial implementation of proposal 157.
3912 - Start serving certificates by <identity digest, signing key digest>
3913 pairs. Partial implementation of proposal 157.
3914 - Clients now never report any stream end reason except 'MISC'.
3915 Implements proposal 148.
3916 - On platforms with a maximum syslog string length, truncate syslog
3917 messages to that length ourselves, rather than relying on the
3918 system to do it for us.
3919 - Optimize out calls to time(NULL) that occur for every IO operation,
3920 or for every cell. On systems where time() is a slow syscall,
3921 this fix will be slightly helpful.
3922 - Exit servers can now answer resolve requests for ip6.arpa addresses.
3923 - When we download a descriptor that we then immediately (as
3924 a directory authority) reject, do not retry downloading it right
3925 away. Should save some bandwidth on authorities. Fix for bug
3926 888. Patch by Sebastian Hahn.
3927 - When a download gets us zero good descriptors, do not notify
3928 Tor that new directory information has arrived.
3929 - Avoid some nasty corner cases in the logic for marking connections
3930 as too old or obsolete or noncanonical for circuits. Partial
3933 o Minor features (controller):
3934 - New CONSENSUS_ARRIVED event to note when a new consensus has
3935 been fetched and validated.
3936 - When we realize that another process has modified our cached
3937 descriptors file, print out a more useful error message rather
3938 than triggering an assertion. Fixes bug 885. Patch from Karsten.
3939 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
3940 controllers to prevent SIGHUP from reloading the
3941 configuration. Fixes bug 856.
3944 - Resume using the correct "REASON=" stream when telling the
3945 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
3946 - When a canonical connection appears later in our internal list
3947 than a noncanonical one for a given OR ID, always use the
3948 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
3950 - Clip the MaxCircuitDirtiness config option to a minimum of 10
3951 seconds. Warn the user if lower values are given in the
3952 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
3953 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
3954 user if lower values are given in the configuration. Bugfix on
3955 0.1.1.17-rc. Patch by Sebastian.
3956 - Fix a race condition when freeing keys shared between main thread
3957 and CPU workers that could result in a memory leak. Bugfix on
3958 0.1.0.1-rc. Fixes bug 889.
3960 o Minor bugfixes (hidden services):
3961 - Do not throw away existing introduction points on SIGHUP (bugfix on
3962 0.0.6pre1); also, do not stall hidden services because we're
3963 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
3964 by John Brooks. Patch by Karsten. Fixes bug 874.
3965 - Fix a memory leak when we decline to add a v2 rendezvous
3966 descriptor to the cache because we already had a v0 descriptor
3967 with the same ID. Bugfix on 0.2.0.18-alpha.
3969 o Deprecated and removed features:
3970 - RedirectExits has been removed. It was deprecated since
3972 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
3973 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
3974 - Cell pools are now always enabled; --disable-cell-pools is ignored.
3976 o Code simplifications and refactoring:
3977 - Rename the confusing or_is_obsolete field to the more appropriate
3978 is_bad_for_new_circs, and move it to or_connection_t where it
3980 - Move edge-only flags from connection_t to edge_connection_t: not
3981 only is this better coding, but on machines of plausible alignment,
3982 it should save 4-8 bytes per connection_t. "Every little bit helps."
3983 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
3984 for consistency; keep old option working for backward compatibility.
3985 - Simplify the code for finding connections to use for a circuit.
3988 Changes in version 0.2.1.8-alpha - 2008-12-08
3989 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
3990 builds better on unusual platforms like Solaris and old OS X, and
3991 fixes a variety of other issues.
3994 - New DirPortFrontPage option that takes an html file and publishes
3995 it as "/" on the DirPort. Now relay operators can provide a
3996 disclaimer without needing to set up a separate webserver. There's
3997 a sample disclaimer in contrib/tor-exit-notice.html.
4000 - When the client is choosing entry guards, now it selects at most
4001 one guard from a given relay family. Otherwise we could end up with
4002 all of our entry points into the network run by the same operator.
4003 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
4006 - Fix a DOS opportunity during the voting signature collection process
4007 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
4008 - Fix a possible segfault when establishing an exit connection. Bugfix
4012 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
4014 - Made Tor a little less aggressive about deleting expired
4015 certificates. Partial fix for bug 854.
4016 - Stop doing unaligned memory access that generated bus errors on
4017 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
4018 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
4019 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
4020 - Make USR2 log-level switch take effect immediately. Bugfix on
4022 - If one win32 nameserver fails to get added, continue adding the
4023 rest, and don't automatically fail.
4024 - Use fcntl() for locking when flock() is not available. Should fix
4025 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
4026 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
4027 could make gcc generate non-functional binary search code. Bugfix
4029 - Build correctly on platforms without socklen_t.
4030 - Avoid potential crash on internal error during signature collection.
4031 Fixes bug 864. Patch from rovv.
4032 - Do not use C's stdio library for writing to log files. This will
4033 improve logging performance by a minute amount, and will stop
4034 leaking fds when our disk is full. Fixes bug 861.
4035 - Stop erroneous use of O_APPEND in cases where we did not in fact
4036 want to re-seek to the end of a file before every last write().
4037 - Correct handling of possible malformed authority signing key
4038 certificates with internal signature types. Fixes bug 880. Bugfix
4040 - Fix a hard-to-trigger resource leak when logging credential status.
4044 - Directory mirrors no longer fetch the v1 directory or
4045 running-routers files. They are obsolete, and nobody asks for them
4046 anymore. This is the first step to making v1 authorities obsolete.
4048 o Minor features (controller):
4049 - Return circuit purposes in response to GETINFO circuit-status. Fixes
4053 Changes in version 0.2.0.32 - 2008-11-20
4054 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
4055 packages (and maybe other packages) noticed by Theo de Raadt, fixes
4056 a smaller security flaw that might allow an attacker to access local
4057 services, further improves hidden service performance, and fixes a
4058 variety of other issues.
4061 - The "User" and "Group" config options did not clear the
4062 supplementary group entries for the Tor process. The "User" option
4063 is now more robust, and we now set the groups to the specified
4064 user's primary group. The "Group" option is now ignored. For more
4065 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
4066 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
4067 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
4068 - The "ClientDNSRejectInternalAddresses" config option wasn't being
4069 consistently obeyed: if an exit relay refuses a stream because its
4070 exit policy doesn't allow it, we would remember what IP address
4071 the relay said the destination address resolves to, even if it's
4072 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
4075 - Fix a DOS opportunity during the voting signature collection process
4076 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
4078 o Major bugfixes (hidden services):
4079 - When fetching v0 and v2 rendezvous service descriptors in parallel,
4080 we were failing the whole hidden service request when the v0
4081 descriptor fetch fails, even if the v2 fetch is still pending and
4082 might succeed. Similarly, if the last v2 fetch fails, we were
4083 failing the whole hidden service request even if a v0 fetch is
4084 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
4085 - When extending a circuit to a hidden service directory to upload a
4086 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
4087 requests failed, because the router descriptor has not been
4088 downloaded yet. In these cases, do not attempt to upload the
4089 rendezvous descriptor, but wait until the router descriptor is
4090 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
4091 descriptor from a hidden service directory for which the router
4092 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
4096 - Fix several infrequent memory leaks spotted by Coverity.
4097 - When testing for libevent functions, set the LDFLAGS variable
4098 correctly. Found by Riastradh.
4099 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
4100 bootstrapping with tunneled directory connections. Bugfix on
4101 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
4102 - When asked to connect to A.B.exit:80, if we don't know the IP for A
4103 and we know that server B rejects most-but-not all connections to
4104 port 80, we would previously reject the connection. Now, we assume
4105 the user knows what they were asking for. Fixes bug 752. Bugfix
4106 on 0.0.9rc5. Diagnosed by BarkerJr.
4107 - If we overrun our per-second write limits a little, count this as
4108 having used up our write allocation for the second, and choke
4109 outgoing directory writes. Previously, we had only counted this when
4110 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
4111 Bugfix on 0.2.0.x (??).
4112 - Remove the old v2 directory authority 'lefkada' from the default
4113 list. It has been gone for many months.
4114 - Stop doing unaligned memory access that generated bus errors on
4115 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
4116 - Make USR2 log-level switch take effect immediately. Bugfix on
4119 o Minor bugfixes (controller):
4120 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
4121 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
4124 Changes in version 0.2.1.7-alpha - 2008-11-08
4125 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
4126 packages (and maybe other packages) noticed by Theo de Raadt, fixes
4127 a smaller security flaw that might allow an attacker to access local
4128 services, adds better defense against DNS poisoning attacks on exit
4129 relays, further improves hidden service performance, and fixes a
4130 variety of other issues.
4133 - The "ClientDNSRejectInternalAddresses" config option wasn't being
4134 consistently obeyed: if an exit relay refuses a stream because its
4135 exit policy doesn't allow it, we would remember what IP address
4136 the relay said the destination address resolves to, even if it's
4137 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
4138 - The "User" and "Group" config options did not clear the
4139 supplementary group entries for the Tor process. The "User" option
4140 is now more robust, and we now set the groups to the specified
4141 user's primary group. The "Group" option is now ignored. For more
4142 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
4143 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
4144 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
4145 - Do not use or believe expired v3 authority certificates. Patch
4146 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
4149 - Now NodeFamily and MyFamily config options allow spaces in
4150 identity fingerprints, so it's easier to paste them in.
4151 Suggested by Lucky Green.
4152 - Implement the 0x20 hack to better resist DNS poisoning: set the
4153 case on outgoing DNS requests randomly, and reject responses that do
4154 not match the case correctly. This logic can be disabled with the
4155 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
4156 of servers that do not reliably preserve case in replies. See
4157 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
4159 - Preserve case in replies to DNSPort requests in order to support
4160 the 0x20 hack for resisting DNS poisoning attacks.
4162 o Hidden service performance improvements:
4163 - When the client launches an introduction circuit, retry with a
4164 new circuit after 30 seconds rather than 60 seconds.
4165 - Launch a second client-side introduction circuit in parallel
4166 after a delay of 15 seconds (based on work by Christian Wilms).
4167 - Hidden services start out building five intro circuits rather
4168 than three, and when the first three finish they publish a service
4169 descriptor using those. Now we publish our service descriptor much
4170 faster after restart.
4173 - Minor fix in the warning messages when you're having problems
4174 bootstrapping; also, be more forgiving of bootstrap problems when
4175 we're still making incremental progress on a given bootstrap phase.
4176 - When we're choosing an exit node for a circuit, and we have
4177 no pending streams, choose a good general exit rather than one that
4178 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
4179 - Send a valid END cell back when a client tries to connect to a
4180 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
4181 840. Patch from rovv.
4182 - If a broken client asks a non-exit router to connect somewhere,
4183 do not even do the DNS lookup before rejecting the connection.
4184 Fixes another case of bug 619. Patch from rovv.
4185 - Fix another case of assuming, when a specific exit is requested,
4186 that we know more than the user about what hosts it allows.
4187 Fixes another case of bug 752. Patch from rovv.
4188 - Check which hops rendezvous stream cells are associated with to
4189 prevent possible guess-the-streamid injection attacks from
4190 intermediate hops. Fixes another case of bug 446. Based on patch
4192 - Avoid using a negative right-shift when comparing 32-bit
4193 addresses. Possible fix for bug 845 and bug 811.
4194 - Make the assert_circuit_ok() function work correctly on circuits that
4195 have already been marked for close.
4196 - Fix read-off-the-end-of-string error in unit tests when decoding
4197 introduction points.
4198 - Fix uninitialized size field for memory area allocation: may improve
4199 memory performance during directory parsing.
4200 - Treat duplicate certificate fetches as failures, so that we do
4201 not try to re-fetch an expired certificate over and over and over.
4202 - Do not say we're fetching a certificate when we'll in fact skip it
4203 because of a pending download.
4206 Changes in version 0.2.1.6-alpha - 2008-09-30
4207 Tor 0.2.1.6-alpha further improves performance and robustness of
4208 hidden services, starts work on supporting per-country relay selection,
4209 and fixes a variety of smaller issues.
4212 - Implement proposal 121: make it possible to build hidden services
4213 that only certain clients are allowed to connect to. This is
4214 enforced at several points, so that unauthorized clients are unable
4215 to send INTRODUCE cells to the service, or even (depending on the
4216 type of authentication) to learn introduction points. This feature
4217 raises the bar for certain kinds of active attacks against hidden
4218 services. Code by Karsten Loesing.
4219 - Relays now store and serve v2 hidden service descriptors by default,
4220 i.e., the new default value for HidServDirectoryV2 is 1. This is
4221 the last step in proposal 114, which aims to make hidden service
4222 lookups more reliable.
4223 - Start work to allow node restrictions to include country codes. The
4224 syntax to exclude nodes in a country with country code XX is
4225 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
4226 refinement to decide what config options should take priority if
4227 you ask to both use a particular node and exclude it.
4228 - Allow ExitNodes list to include IP ranges and country codes, just
4229 like the Exclude*Nodes lists. Patch from Robert Hogan.
4232 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
4233 Tor to fail to start if you had it configured to use a bridge
4234 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
4235 - When extending a circuit to a hidden service directory to upload a
4236 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
4237 requests failed, because the router descriptor had not been
4238 downloaded yet. In these cases, we now wait until the router
4239 descriptor is downloaded, and then retry. Likewise, clients
4240 now skip over a hidden service directory if they don't yet have
4241 its router descriptor, rather than futilely requesting it and
4242 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
4244 - When fetching v0 and v2 rendezvous service descriptors in parallel,
4245 we were failing the whole hidden service request when the v0
4246 descriptor fetch fails, even if the v2 fetch is still pending and
4247 might succeed. Similarly, if the last v2 fetch fails, we were
4248 failing the whole hidden service request even if a v0 fetch is
4249 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
4250 - DNS replies need to have names matching their requests, but
4251 these names should be in the questions section, not necessarily
4252 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
4255 - Update to the "September 1 2008" ip-to-country file.
4256 - Allow ports 465 and 587 in the default exit policy again. We had
4257 rejected them in 0.1.0.15, because back in 2005 they were commonly
4258 misconfigured and ended up as spam targets. We hear they are better
4259 locked down these days.
4260 - Use a lockfile to make sure that two Tor processes are not
4261 simultaneously running with the same datadir.
4262 - Serve the latest v3 networkstatus consensus via the control
4263 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
4264 - Better logging about stability/reliability calculations on directory
4266 - Drop the requirement to have an open dir port for storing and
4267 serving v2 hidden service descriptors.
4268 - Directory authorities now serve a /tor/dbg-stability.txt URL to
4269 help debug WFU and MTBF calculations.
4270 - Implement most of Proposal 152: allow specialized servers to permit
4271 single-hop circuits, and clients to use those servers to build
4272 single-hop circuits when using a specialized controller. Patch
4273 from Josh Albrecht. Resolves feature request 768.
4274 - Add a -p option to tor-resolve for specifying the SOCKS port: some
4275 people find host:port too confusing.
4276 - Make TrackHostExit mappings expire a while after their last use, not
4277 after their creation. Patch from Robert Hogan.
4278 - Provide circuit purposes along with circuit events to the controller.
4281 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
4283 - Fixed some memory leaks -- some quite frequent, some almost
4284 impossible to trigger -- based on results from Coverity.
4285 - When testing for libevent functions, set the LDFLAGS variable
4286 correctly. Found by Riastradh.
4287 - Fix an assertion bug in parsing policy-related options; possible fix
4289 - Catch and report a few more bootstrapping failure cases when Tor
4290 fails to establish a TCP connection. Cleanup on 0.2.1.x.
4291 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
4292 bootstrapping with tunneled directory connections. Bugfix on
4293 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
4294 - When asked to connect to A.B.exit:80, if we don't know the IP for A
4295 and we know that server B rejects most-but-not all connections to
4296 port 80, we would previously reject the connection. Now, we assume
4297 the user knows what they were asking for. Fixes bug 752. Bugfix
4298 on 0.0.9rc5. Diagnosed by BarkerJr.
4299 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
4300 service directories if they have no advertised dir port. Bugfix
4302 - If we overrun our per-second write limits a little, count this as
4303 having used up our write allocation for the second, and choke
4304 outgoing directory writes. Previously, we had only counted this when
4305 we had met our limits precisely. Fixes bug 824. Patch by rovv.
4306 Bugfix on 0.2.0.x (??).
4307 - Avoid a "0 divided by 0" calculation when calculating router uptime
4308 at directory authorities. Bugfix on 0.2.0.8-alpha.
4309 - Make DNS resolved controller events into "CLOSED", not
4310 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
4312 - Fix a bug where an unreachable relay would establish enough
4313 reachability testing circuits to do a bandwidth test -- if
4314 we already have a connection to the middle hop of the testing
4315 circuit, then it could establish the last hop by using the existing
4316 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
4317 circuits no longer use entry guards in 0.2.1.3-alpha.
4318 - If we have correct permissions on $datadir, we complain to stdout
4319 and fail to start. But dangerous permissions on
4320 $datadir/cached-status/ would cause us to open a log and complain
4321 there. Now complain to stdout and fail to start in both cases. Fixes
4322 bug 820, reported by seeess.
4323 - Remove the old v2 directory authority 'lefkada' from the default
4324 list. It has been gone for many months.
4326 o Code simplifications and refactoring:
4327 - Revise the connection_new functions so that a more typesafe variant
4328 exists. This will work better with Coverity, and let us find any
4329 actual mistakes we're making here.
4330 - Refactor unit testing logic so that dmalloc can be used sensibly
4331 with unit tests to check for memory leaks.
4332 - Move all hidden-service related fields from connection and circuit
4333 structure to substructures: this way they won't eat so much memory.
4336 Changes in version 0.2.0.31 - 2008-09-03
4337 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
4338 a big bug we're seeing where in rare cases traffic from one Tor stream
4339 gets mixed into another stream, and fixes a variety of smaller issues.
4342 - Make sure that two circuits can never exist on the same connection
4343 with the same circuit ID, even if one is marked for close. This
4344 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
4345 - Relays now reject risky extend cells: if the extend cell includes
4346 a digest of all zeroes, or asks to extend back to the relay that
4347 sent the extend cell, tear down the circuit. Ideas suggested
4349 - If not enough of our entry guards are available so we add a new
4350 one, we might use the new one even if it overlapped with the
4351 current circuit's exit relay (or its family). Anonymity bugfix
4352 pointed out by rovv.
4355 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
4356 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
4357 - Correctly detect the presence of the linux/netfilter_ipv4.h header
4358 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
4359 - Pick size of default geoip filename string correctly on windows.
4360 Fixes bug 806. Bugfix on 0.2.0.30.
4361 - Make the autoconf script accept the obsolete --with-ssl-dir
4362 option as an alias for the actually-working --with-openssl-dir
4363 option. Fix the help documentation to recommend --with-openssl-dir.
4364 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
4365 - When using the TransPort option on OpenBSD, and using the User
4366 option to change UID and drop privileges, make sure to open
4367 /dev/pf before dropping privileges. Fixes bug 782. Patch from
4368 Christopher Davis. Bugfix on 0.1.2.1-alpha.
4369 - Try to attach connections immediately upon receiving a RENDEZVOUS2
4370 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
4371 on the client side when connecting to a hidden service. Bugfix
4372 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
4373 - When closing an application-side connection because its circuit is
4374 getting torn down, generate the stream event correctly. Bugfix on
4375 0.1.2.x. Anonymous patch.
4378 Changes in version 0.2.1.5-alpha - 2008-08-31
4379 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
4380 in a lot of the infrastructure for adding authorization to hidden
4381 services, lays the groundwork for having clients read their load
4382 balancing information out of the networkstatus consensus rather than
4383 the individual router descriptors, addresses two potential anonymity
4384 issues, and fixes a variety of smaller issues.
4387 - Convert many internal address representations to optionally hold
4389 - Generate and accept IPv6 addresses in many protocol elements.
4390 - Make resolver code handle nameservers located at ipv6 addresses.
4391 - Begin implementation of proposal 121 ("Client authorization for
4392 hidden services"): configure hidden services with client
4393 authorization, publish descriptors for them, and configure
4394 authorization data for hidden services at clients. The next
4395 step is to actually access hidden services that perform client
4397 - More progress toward proposal 141: Network status consensus
4398 documents and votes now contain bandwidth information for each
4399 router and a summary of that router's exit policy. Eventually this
4400 will be used by clients so that they do not have to download every
4401 known descriptor before building circuits.
4403 o Major bugfixes (on 0.2.0.x and before):
4404 - When sending CREATED cells back for a given circuit, use a 64-bit
4405 connection ID to find the right connection, rather than an addr:port
4406 combination. Now that we can have multiple OR connections between
4407 the same ORs, it is no longer possible to use addr:port to uniquely
4408 identify a connection.
4409 - Relays now reject risky extend cells: if the extend cell includes
4410 a digest of all zeroes, or asks to extend back to the relay that
4411 sent the extend cell, tear down the circuit. Ideas suggested
4413 - If not enough of our entry guards are available so we add a new
4414 one, we might use the new one even if it overlapped with the
4415 current circuit's exit relay (or its family). Anonymity bugfix
4416 pointed out by rovv.
4419 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
4420 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
4421 - When using the TransPort option on OpenBSD, and using the User
4422 option to change UID and drop privileges, make sure to open /dev/pf
4423 before dropping privileges. Fixes bug 782. Patch from Christopher
4424 Davis. Bugfix on 0.1.2.1-alpha.
4425 - Correctly detect the presence of the linux/netfilter_ipv4.h header
4426 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
4427 - Add a missing safe_str() call for a debug log message.
4428 - Use 64 bits instead of 32 bits for connection identifiers used with
4429 the controller protocol, to greatly reduce risk of identifier reuse.
4430 - Make the autoconf script accept the obsolete --with-ssl-dir
4431 option as an alias for the actually-working --with-openssl-dir
4432 option. Fix the help documentation to recommend --with-openssl-dir.
4433 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
4436 - Rate-limit too-many-sockets messages: when they happen, they happen
4437 a lot. Resolves bug 748.
4438 - Resist DNS poisoning a little better by making sure that names in
4439 answer sections match.
4440 - Print the SOCKS5 error message string as well as the error code
4441 when a tor-resolve request fails. Patch from Jacob.
4444 Changes in version 0.2.1.4-alpha - 2008-08-04
4445 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
4448 - The address part of exit policies was not correctly written
4449 to router descriptors. This generated router descriptors that failed
4450 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
4452 - Tor triggered a false assert when extending a circuit to a relay
4453 but we already have a connection open to that relay. Noticed by
4454 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
4457 - Fix a hidden service logging bug: in some edge cases, the router
4458 descriptor of a previously picked introduction point becomes
4459 obsolete and we need to give up on it rather than continually
4460 complaining that it has become obsolete. Observed by xiando. Bugfix
4464 - Take out the TestVia config option, since it was a workaround for
4465 a bug that was fixed in Tor 0.1.1.21.
4468 Changes in version 0.2.1.3-alpha - 2008-08-03
4469 Tor 0.2.1.3-alpha implements most of the pieces to prevent
4470 infinite-length circuit attacks (see proposal 110); fixes a bug that
4471 might cause exit relays to corrupt streams they send back; allows
4472 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
4473 ExcludeExitNodes config options; and fixes a big pile of bugs.
4475 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
4476 - Send a bootstrap problem "warn" event on the first problem if the
4477 reason is NO_ROUTE (that is, our network is down).
4480 - Implement most of proposal 110: The first K cells to be sent
4481 along a circuit are marked as special "early" cells; only K "early"
4482 cells will be allowed. Once this code is universal, we can block
4483 certain kinds of DOS attack by requiring that EXTEND commands must
4484 be sent using an "early" cell.
4487 - Try to attach connections immediately upon receiving a RENDEZVOUS2
4488 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
4489 on the client side when connecting to a hidden service. Bugfix
4490 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
4491 - Ensure that two circuits can never exist on the same connection
4492 with the same circuit ID, even if one is marked for close. This
4493 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
4496 - When relays do their initial bandwidth measurement, don't limit
4497 to just our entry guards for the test circuits. Otherwise we tend
4498 to have multiple test circuits going through a single entry guard,
4499 which makes our bandwidth test less accurate. Fixes part of bug 654;
4500 patch contributed by Josh Albrecht.
4501 - Add an ExcludeExitNodes option so users can list a set of nodes
4502 that should be be excluded from the exit node position, but
4503 allowed elsewhere. Implements proposal 151.
4504 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
4505 ExcludeNodes and ExcludeExitNodes lists.
4506 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
4507 be more efficient. Formerly it was quadratic in the number of
4508 servers; now it should be linear. Fixes bug 509.
4509 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
4510 and n_conn_id_digest fields into a separate structure that's
4511 only needed when the circuit has not yet attached to an n_conn.
4514 - Change the contrib/tor.logrotate script so it makes the new
4515 logs as "_tor:_tor" rather than the default, which is generally
4516 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
4517 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
4518 warnings (occasionally), but it can also cause the compiler to
4519 eliminate error-checking code. Suggested by Peter Gutmann.
4520 - When a hidden service is giving up on an introduction point candidate
4521 that was not included in the last published rendezvous descriptor,
4522 don't reschedule publication of the next descriptor. Fixes bug 763.
4524 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
4525 HiddenServiceExcludeNodes as obsolete: they never worked properly,
4526 and nobody claims to be using them. Fixes bug 754. Bugfix on
4527 0.1.0.1-rc. Patch from Christian Wilms.
4528 - Fix a small alignment and memory-wasting bug on buffer chunks.
4531 o Minor bugfixes (controller):
4532 - When closing an application-side connection because its circuit
4533 is getting torn down, generate the stream event correctly.
4534 Bugfix on 0.1.2.x. Anonymous patch.
4537 - Remove all backward-compatibility code to support relays running
4538 versions of Tor so old that they no longer work at all on the
4542 Changes in version 0.2.0.30 - 2008-07-15
4544 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
4545 warnings (occasionally), but it can also cause the compiler to
4546 eliminate error-checking code. Suggested by Peter Gutmann.
4549 Changes in version 0.2.0.29-rc - 2008-07-08
4550 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
4551 hidden-service performance bugs, and fixes a bunch of smaller bugs.
4554 - If you have more than one bridge but don't know their keys,
4555 you would only launch a request for the descriptor of the first one
4556 on your list. (Tor considered launching requests for the others, but
4557 found that it already had a connection on the way for $0000...0000
4558 so it didn't open another.) Bugfix on 0.2.0.x.
4559 - If you have more than one bridge but don't know their keys, and the
4560 connection to one of the bridges failed, you would cancel all
4561 pending bridge connections. (After all, they all have the same
4562 digest.) Bugfix on 0.2.0.x.
4563 - When a hidden service was trying to establish an introduction point,
4564 and Tor had built circuits preemptively for such purposes, we
4565 were ignoring all the preemptive circuits and launching a new one
4566 instead. Bugfix on 0.2.0.14-alpha.
4567 - When a hidden service was trying to establish an introduction point,
4568 and Tor *did* manage to reuse one of the preemptively built
4569 circuits, it didn't correctly remember which one it used,
4570 so it asked for another one soon after, until there were no
4571 more preemptive circuits, at which point it launched one from
4572 scratch. Bugfix on 0.0.9.x.
4573 - Make directory servers include the X-Your-Address-Is: http header in
4574 their responses even for begin_dir conns. Now clients who only
4575 ever use begin_dir connections still have a way to learn their IP
4576 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
4579 - Fix a macro/CPP interaction that was confusing some compilers:
4580 some GCCs don't like #if/#endif pairs inside macro arguments.
4582 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
4583 Fixes bug 704; fix from Steven Murdoch.
4584 - When opening /dev/null in finish_daemonize(), do not pass the
4585 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
4586 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
4587 - Correctly detect transparent proxy support on Linux hosts that
4588 require in.h to be included before netfilter_ipv4.h. Patch
4590 - Disallow session resumption attempts during the renegotiation
4591 stage of the v2 handshake protocol. Clients should never be trying
4592 session resumption at this point, but apparently some did, in
4593 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
4594 found by Geoff Goodell.
4597 Changes in version 0.2.1.2-alpha - 2008-06-20
4598 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
4599 make it easier to set up your own private Tor network; fixes several
4600 big bugs with using more than one bridge relay; fixes a big bug with
4601 offering hidden services quickly after Tor starts; and uses a better
4602 API for reporting potential bootstrapping problems to the controller.
4605 - New TestingTorNetwork config option to allow adjustment of
4606 previously constant values that, while reasonable, could slow
4607 bootstrapping. Implements proposal 135. Patch from Karsten.
4610 - If you have more than one bridge but don't know their digests,
4611 you would only learn a request for the descriptor of the first one
4612 on your list. (Tor considered launching requests for the others, but
4613 found that it already had a connection on the way for $0000...0000
4614 so it didn't open another.) Bugfix on 0.2.0.x.
4615 - If you have more than one bridge but don't know their digests,
4616 and the connection to one of the bridges failed, you would cancel
4617 all pending bridge connections. (After all, they all have the
4618 same digest.) Bugfix on 0.2.0.x.
4619 - When establishing a hidden service, introduction points that
4620 originate from cannibalized circuits are completely ignored and not
4621 included in rendezvous service descriptors. This might be another
4622 reason for delay in making a hidden service available. Bugfix
4623 from long ago (0.0.9.x?)
4626 - Allow OpenSSL to use dynamic locks if it wants.
4627 - When building a consensus, do not include routers that are down.
4628 This will cut down 30% to 40% on consensus size. Implements
4630 - In directory authorities' approved-routers files, allow
4631 fingerprints with or without space.
4632 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
4633 controller can query our current bootstrap state in case it attaches
4634 partway through and wants to catch up.
4635 - Send an initial "Starting" bootstrap status event, so we have a
4636 state to start out in.
4639 - Asking for a conditional consensus at .../consensus/<fingerprints>
4640 would crash a dirserver if it did not already have a
4641 consensus. Bugfix on 0.2.1.1-alpha.
4642 - Clean up some macro/CPP interactions: some GCC versions don't like
4643 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
4646 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
4647 - Directory authorities shouldn't complain about bootstrapping
4648 problems just because they do a lot of reachability testing and
4649 some of the connection attempts fail.
4650 - Start sending "count" and "recommendation" key/value pairs in
4651 bootstrap problem status events, so the controller can hear about
4652 problems even before Tor decides they're worth reporting for sure.
4653 - If you're using bridges, generate "bootstrap problem" warnings
4654 as soon as you run out of working bridges, rather than waiting
4655 for ten failures -- which will never happen if you have less than
4657 - If we close our OR connection because there's been a circuit
4658 pending on it for too long, we were telling our bootstrap status
4659 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
4662 Changes in version 0.2.1.1-alpha - 2008-06-13
4663 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
4664 were making the Tor process bloat especially on Linux; makes our TLS
4665 handshake blend in better; sends "bootstrap phase" status events to
4666 the controller, so it can keep the user informed of progress (and
4667 problems) fetching directory information and establishing circuits;
4668 and adds a variety of smaller features.
4671 - More work on making our TLS handshake blend in: modify the list
4672 of ciphers advertised by OpenSSL in client mode to even more
4673 closely resemble a common web browser. We cheat a little so that
4674 we can advertise ciphers that the locally installed OpenSSL doesn't
4676 - Start sending "bootstrap phase" status events to the controller,
4677 so it can keep the user informed of progress fetching directory
4678 information and establishing circuits. Also inform the controller
4679 if we think we're stuck at a particular bootstrap phase. Implements
4681 - Resume using OpenSSL's RAND_poll() for better (and more portable)
4682 cross-platform entropy collection again. We used to use it, then
4683 stopped using it because of a bug that could crash systems that
4684 called RAND_poll when they had a lot of fds open. It looks like the
4685 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
4686 at startup, and to call RAND_poll() when we reseed later only if
4687 we have a non-buggy OpenSSL version.
4690 - When we choose to abandon a new entry guard because we think our
4691 older ones might be better, close any circuits pending on that
4692 new entry guard connection. This fix should make us recover much
4693 faster when our network is down and then comes back. Bugfix on
4694 0.1.2.8-beta; found by lodger.
4696 o Memory fixes and improvements:
4697 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
4698 to avoid unused RAM in buffer chunks and memory pools.
4699 - Speed up parsing and cut down on memory fragmentation by using
4700 stack-style allocations for parsing directory objects. Previously,
4701 this accounted for over 40% of allocations from within Tor's code
4702 on a typical directory cache.
4703 - Use a Bloom filter rather than a digest-based set to track which
4704 descriptors we need to keep around when we're cleaning out old
4705 router descriptors. This speeds up the computation significantly,
4706 and may reduce fragmentation.
4707 - Reduce the default smartlist size from 32 to 16; it turns out that
4708 most smartlists hold around 8-12 elements tops.
4709 - Make dumpstats() log the fullness and size of openssl-internal
4711 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
4712 patch to their OpenSSL, turn it on to save memory on servers. This
4713 patch will (with any luck) get included in a mainline distribution
4715 - Never use OpenSSL compression: it wastes RAM and CPU trying to
4716 compress cells, which are basically all encrypted, compressed,
4720 - Stop reloading the router list from disk for no reason when we
4721 run out of reachable directory mirrors. Once upon a time reloading
4722 it would set the 'is_running' flag back to 1 for them. It hasn't
4723 done that for a long time.
4724 - In very rare situations new hidden service descriptors were
4725 published earlier than 30 seconds after the last change to the
4726 service. (We currently think that a hidden service descriptor
4727 that's been stable for 30 seconds is worth publishing.)
4730 - Allow separate log levels to be configured for different logging
4731 domains. For example, this allows one to log all notices, warnings,
4732 or errors, plus all memory management messages of level debug or
4733 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
4734 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
4735 and stop using a warning that had become unfixably verbose under
4737 - New --hush command-line option similar to --quiet. While --quiet
4738 disables all logging to the console on startup, --hush limits the
4739 output to messages of warning and error severity.
4740 - Servers support a new URL scheme for consensus downloads that
4741 allows the client to specify which authorities are trusted.
4742 The server then only sends the consensus if the client will trust
4743 it. Otherwise a 404 error is sent back. Clients use this
4744 new scheme when the server supports it (meaning it's running
4745 0.2.1.1-alpha or later). Implements proposal 134.
4746 - New configure/torrc options (--enable-geoip-stats,
4747 DirRecordUsageByCountry) to record how many IPs we've served
4748 directory info to in each country code, how many status documents
4749 total we've sent to each country code, and what share of the total
4750 directory requests we should expect to see.
4751 - Use the TLS1 hostname extension to more closely resemble browser
4753 - Lots of new unit tests.
4754 - Add a macro to implement the common pattern of iterating through
4755 two parallel lists in lockstep.
4758 Changes in version 0.2.0.28-rc - 2008-06-13
4759 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
4760 performance bug, and fixes a bunch of smaller bugs.
4763 - Fix a bug where, when we were choosing the 'end stream reason' to
4764 put in our relay end cell that we send to the exit relay, Tor
4765 clients on Windows were sometimes sending the wrong 'reason'. The
4766 anonymity problem is that exit relays may be able to guess whether
4767 the client is running Windows, thus helping partition the anonymity
4768 set. Down the road we should stop sending reasons to exit relays,
4769 or otherwise prevent future versions of this bug.
4772 - While setting up a hidden service, some valid introduction circuits
4773 were overlooked and abandoned. This might be the reason for
4774 the long delay in making a hidden service available. Bugfix on
4778 - Update to the "June 9 2008" ip-to-country file.
4779 - Run 'make test' as part of 'make dist', so we stop releasing so
4780 many development snapshots that fail their unit tests.
4783 - When we're checking if we have enough dir info for each relay
4784 to begin establishing circuits, make sure that we actually have
4785 the descriptor listed in the consensus, not just any descriptor.
4787 - Bridge relays no longer print "xx=0" in their extrainfo document
4788 for every single country code in the geoip db. Bugfix on
4790 - Only warn when we fail to load the geoip file if we were planning to
4791 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
4792 - If we change our MaxAdvertisedBandwidth and then reload torrc,
4793 Tor won't realize it should publish a new relay descriptor. Fixes
4794 bug 688, reported by mfr. Bugfix on 0.1.2.x.
4795 - When we haven't had any application requests lately, don't bother
4796 logging that we have expired a bunch of descriptors. Bugfix
4798 - Make relay cells written on a connection count as non-padding when
4799 tracking how long a connection has been in use. Bugfix on
4800 0.2.0.1-alpha. Spotted by lodger.
4801 - Fix unit tests in 0.2.0.27-rc.
4802 - Fix compile on Windows.
4805 Changes in version 0.2.0.27-rc - 2008-06-03
4806 Tor 0.2.0.27-rc adds a few features we left out of the earlier
4807 release candidates. In particular, we now include an IP-to-country
4808 GeoIP database, so controllers can easily look up what country a
4809 given relay is in, and so bridge relays can give us some sanitized
4810 summaries about which countries are making use of bridges. (See proposal
4811 126-geoip-fetching.txt for details.)
4814 - Include an IP-to-country GeoIP file in the tarball, so bridge
4815 relays can report sanitized summaries of the usage they're seeing.
4818 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
4819 Robert Hogan. Fixes the first part of bug 681.
4820 - Make bridge authorities never serve extrainfo docs.
4821 - Add support to detect Libevent versions in the 1.4.x series
4823 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
4824 - Include a new contrib/tor-exit-notice.html file that exit relay
4825 operators can put on their website to help reduce abuse queries.
4828 - When tunneling an encrypted directory connection, and its first
4829 circuit fails, do not leave it unattached and ask the controller
4830 to deal. Fixes the second part of bug 681.
4831 - Make bridge authorities correctly expire old extrainfo documents
4835 Changes in version 0.2.0.26-rc - 2008-05-13
4836 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
4837 in Debian's OpenSSL packages. All users running any 0.2.0.x version
4838 should upgrade, whether they're running Debian or not.
4840 o Major security fixes:
4841 - Use new V3 directory authority keys on the tor26, gabelmoo, and
4842 moria1 V3 directory authorities. The old keys were generated with
4843 a vulnerable version of Debian's OpenSSL package, and must be
4844 considered compromised. Other authorities' keys were not generated
4845 with an affected version of OpenSSL.
4848 - List authority signatures as "unrecognized" based on DirServer
4849 lines, not on cert cache. Bugfix on 0.2.0.x.
4852 - Add a new V3AuthUseLegacyKey option to make it easier for
4853 authorities to change their identity keys if they have to.
4856 Changes in version 0.2.0.25-rc - 2008-04-23
4857 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
4860 - Remember to initialize threading before initializing logging.
4861 Otherwise, many BSD-family implementations will crash hard on
4862 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
4865 - Authorities correctly free policies on bad servers on
4866 exit. Fixes bug 672. Bugfix on 0.2.0.x.
4869 Changes in version 0.2.0.24-rc - 2008-04-22
4870 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
4871 v3 directory authority, makes relays with dynamic IP addresses and no
4872 DirPort notice more quickly when their IP address changes, fixes a few
4873 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
4875 o New directory authorities:
4876 - Take lefkada out of the list of v3 directory authorities, since
4877 it has been down for months.
4878 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
4882 - Detect address changes more quickly on non-directory mirror
4883 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
4885 o Minor features (security):
4886 - Reject requests for reverse-dns lookup of names that are in
4887 a private address space. Patch from lodger.
4888 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
4891 o Minor bugfixes (crashes):
4892 - Avoid a rare assert that can trigger when Tor doesn't have much
4893 directory information yet and it tries to fetch a v2 hidden
4894 service descriptor. Fixes bug 651, reported by nwf.
4895 - Initialize log mutex before initializing dmalloc. Otherwise,
4896 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
4897 - Use recursive pthread mutexes in order to avoid deadlock when
4898 logging debug-level messages to a controller. Bug spotted by nwf,
4899 bugfix on 0.2.0.16-alpha.
4901 o Minor bugfixes (resource management):
4902 - Keep address policies from leaking memory: start their refcount
4903 at 1, not 2. Bugfix on 0.2.0.16-alpha.
4904 - Free authority certificates on exit, so they don't look like memory
4905 leaks. Bugfix on 0.2.0.19-alpha.
4906 - Free static hashtables for policy maps and for TLS connections on
4907 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
4908 - Avoid allocating extra space when computing consensuses on 64-bit
4909 platforms. Bug spotted by aakova.
4911 o Minor bugfixes (misc):
4912 - Do not read the configuration file when we've only been told to
4913 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
4914 based on patch from Sebastian Hahn.
4915 - Exit relays that are used as a client can now reach themselves
4916 using the .exit notation, rather than just launching an infinite
4917 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
4918 - When attempting to open a logfile fails, tell us why.
4919 - Fix a dumb bug that was preventing us from knowing that we should
4920 preemptively build circuits to handle expected directory requests.
4921 Fixes bug 660. Bugfix on 0.1.2.x.
4922 - Warn less verbosely about clock skew from netinfo cells from
4923 untrusted sources. Fixes bug 663.
4924 - Make controller stream events for DNS requests more consistent,
4925 by adding "new stream" events for DNS requests, and removing
4926 spurious "stream closed" events" for cached reverse resolves.
4927 Patch from mwenge. Fixes bug 646.
4928 - Correctly notify one-hop connections when a circuit build has
4929 failed. Possible fix for bug 669. Found by lodger.
4932 Changes in version 0.2.0.23-rc - 2008-03-24
4933 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
4934 makes bootstrapping faster if the first directory mirror you contact
4935 is down. The bundles also include the new Vidalia 0.1.2 release.
4938 - When a tunneled directory request is made to a directory server
4939 that's down, notice after 30 seconds rather than 120 seconds. Also,
4940 fail any begindir streams that are pending on it, so they can
4941 retry elsewhere. This was causing multi-minute delays on bootstrap.
4944 Changes in version 0.2.0.22-rc - 2008-03-18
4945 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
4946 enables encrypted directory connections by default for non-relays, fixes
4947 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
4948 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
4951 - Enable encrypted directory connections by default for non-relays,
4952 so censor tools that block Tor directory connections based on their
4953 plaintext patterns will no longer work. This means Tor works in
4954 certain censored countries by default again.
4957 - Make sure servers always request certificates from clients during
4958 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
4959 - Do not enter a CPU-eating loop when a connection is closed in
4960 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
4961 diagnosed by lodger; bugfix on 0.2.0.20-rc.
4962 - Fix assertion failure that could occur when a blocked circuit
4963 became unblocked, and it had pending client DNS requests. Bugfix
4964 on 0.2.0.1-alpha. Fixes bug 632.
4966 o Minor bugfixes (on 0.1.2.x):
4967 - Generate "STATUS_SERVER" events rather than misspelled
4968 "STATUS_SEVER" events. Caught by mwenge.
4969 - When counting the number of bytes written on a TLS connection,
4970 look at the BIO actually used for writing to the network, not
4971 at the BIO used (sometimes) to buffer data for the network.
4972 Looking at different BIOs could result in write counts on the
4973 order of ULONG_MAX. Fixes bug 614.
4974 - On Windows, correctly detect errors when listing the contents of
4975 a directory. Fix from lodger.
4977 o Minor bugfixes (on 0.2.0.x):
4978 - Downgrade "sslv3 alert handshake failure" message to INFO.
4979 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
4980 left BandwidthRate and BandwidthBurst at the default, we would be
4981 silently limited by those defaults. Now raise them to match the
4982 RelayBandwidth* values.
4983 - Fix the SVK version detection logic to work correctly on a branch.
4984 - Make --enable-openbsd-malloc work correctly on Linux with alpha
4985 CPUs. Fixes bug 625.
4986 - Logging functions now check that the passed severity is sane.
4987 - Use proper log levels in the testsuite call of
4988 get_interface_address6().
4989 - When using a nonstandard malloc, do not use the platform values for
4990 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
4991 - Make the openbsd malloc code use 8k pages on alpha CPUs and
4993 - Detect mismatched page sizes when using --enable-openbsd-malloc.
4994 - Avoid double-marked-for-close warning when certain kinds of invalid
4995 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
4996 for bug 617. Bugfix on 0.2.0.1-alpha.
4997 - Make sure that the "NULL-means-reject *:*" convention is followed by
4998 all the policy manipulation functions, avoiding some possible crash
4999 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
5000 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
5001 actually works, and doesn't warn about every single reverse lookup.
5002 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
5005 - Only log guard node status when guard node status has changed.
5006 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
5007 make "INFO" 75% less verbose.
5010 Changes in version 0.2.0.21-rc - 2008-03-02
5011 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
5012 makes Tor work well with Vidalia again, fixes a rare assert bug,
5013 and fixes a pair of more minor bugs. The bundles also include Vidalia
5014 0.1.0 and Torbutton 1.1.16.
5017 - The control port should declare that it requires password auth
5018 when HashedControlSessionPassword is set too. Patch from Matt Edman;
5019 bugfix on 0.2.0.20-rc. Fixes bug 615.
5020 - Downgrade assert in connection_buckets_decrement() to a log message.
5021 This may help us solve bug 614, and in any case will make its
5022 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
5023 - We were sometimes miscounting the number of bytes read from the
5024 network, causing our rate limiting to not be followed exactly.
5025 Bugfix on 0.2.0.16-alpha. Reported by lodger.
5028 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
5029 OpenSSL versions should have been working fine. Diagnosis and patch
5030 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
5031 Bugfix on 0.2.0.20-rc.
5034 Changes in version 0.2.0.20-rc - 2008-02-24
5035 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
5036 makes more progress towards normalizing Tor's TLS handshake, makes
5037 hidden services work better again, helps relays bootstrap if they don't
5038 know their IP address, adds optional support for linking in openbsd's
5039 allocator or tcmalloc, allows really fast relays to scale past 15000
5040 sockets, and fixes a bunch of minor bugs reported by Veracode.
5043 - Enable the revised TLS handshake based on the one designed by
5044 Steven Murdoch in proposal 124, as revised in proposal 130. It
5045 includes version negotiation for OR connections as described in
5046 proposal 105. The new handshake is meant to be harder for censors
5047 to fingerprint, and it adds the ability to detect certain kinds of
5048 man-in-the-middle traffic analysis attacks. The version negotiation
5049 feature will allow us to improve Tor's link protocol more safely
5051 - Choose which bridge to use proportional to its advertised bandwidth,
5052 rather than uniformly at random. This should speed up Tor for
5053 bridge users. Also do this for people who set StrictEntryNodes.
5054 - When a TrackHostExits-chosen exit fails too many times in a row,
5055 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
5058 - Resolved problems with (re-)fetching hidden service descriptors.
5059 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
5061 - If we only ever used Tor for hidden service lookups or posts, we
5062 would stop building circuits and start refusing connections after
5063 24 hours, since we falsely believed that Tor was dormant. Reported
5064 by nwf; bugfix on 0.1.2.x.
5065 - Servers that don't know their own IP address should go to the
5066 authorities for their first directory fetch, even if their DirPort
5067 is off or if they don't know they're reachable yet. This will help
5068 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
5069 - When counting the number of open sockets, count not only the number
5070 of sockets we have received from the socket() call, but also
5071 the number we've gotten from accept() and socketpair(). This bug
5072 made us fail to count all sockets that we were using for incoming
5073 connections. Bugfix on 0.2.0.x.
5074 - Fix code used to find strings within buffers, when those strings
5075 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
5076 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
5077 - Add a new __HashedControlSessionPassword option for controllers
5078 to use for one-off session password hashes that shouldn't get
5079 saved to disk by SAVECONF --- Vidalia users were accumulating a
5080 pile of HashedControlPassword lines in their torrc files, one for
5081 each time they had restarted Tor and then clicked Save. Make Tor
5082 automatically convert "HashedControlPassword" to this new option but
5083 only when it's given on the command line. Partial fix for bug 586.
5085 o Minor features (performance):
5086 - Tune parameters for cell pool allocation to minimize amount of
5088 - Add OpenBSD malloc code from phk as an optional malloc
5089 replacement on Linux: some glibc libraries do very poorly
5090 with Tor's memory allocation patterns. Pass
5091 --enable-openbsd-malloc to get the replacement malloc code.
5092 - Add a --with-tcmalloc option to the configure script to link
5093 against tcmalloc (if present). Does not yet search for
5094 non-system include paths.
5095 - Stop imposing an arbitrary maximum on the number of file descriptors
5096 used for busy servers. Bug reported by Olaf Selke; patch from
5099 o Minor features (other):
5100 - When SafeLogging is disabled, log addresses along with all TLS
5102 - When building with --enable-gcc-warnings, check for whether Apple's
5103 warning "-Wshorten-64-to-32" is available.
5104 - Add a --passphrase-fd argument to the tor-gencert command for
5107 o Minor bugfixes (memory leaks and code problems):
5108 - We were leaking a file descriptor if Tor started with a zero-length
5109 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
5110 - Detect size overflow in zlib code. Reported by Justin Ferguson and
5112 - We were comparing the raw BridgePassword entry with a base64'ed
5113 version of it, when handling a "/tor/networkstatus-bridges"
5114 directory request. Now compare correctly. Noticed by Veracode.
5115 - Recover from bad tracked-since value in MTBF-history file.
5117 - Alter the code that tries to recover from unhandled write
5118 errors, to not try to flush onto a socket that's given us
5119 unhandled errors. Bugfix on 0.1.2.x.
5120 - Make Unix controlsockets work correctly on OpenBSD. Patch from
5121 tup. Bugfix on 0.2.0.3-alpha.
5123 o Minor bugfixes (other):
5124 - If we have an extra-info document for our server, always make
5125 it available on the control port, even if we haven't gotten
5126 a copy of it from an authority yet. Patch from mwenge.
5127 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
5128 - Directory mirrors no longer include a guess at the client's IP
5129 address if the connection appears to be coming from the same /24
5130 network; it was producing too many wrong guesses.
5131 - Make the new hidden service code respect the SafeLogging setting.
5132 Bugfix on 0.2.0.x. Patch from Karsten.
5133 - When starting as an authority, do not overwrite all certificates
5134 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
5135 - If we're trying to flush the last bytes on a connection (for
5136 example, when answering a directory request), reset the
5137 time-to-give-up timeout every time we manage to write something
5138 on the socket. Bugfix on 0.1.2.x.
5139 - Change the behavior of "getinfo status/good-server-descriptor"
5140 so it doesn't return failure when any authority disappears.
5141 - Even though the man page said that "TrackHostExits ." should
5142 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
5143 - Report TLS "zero return" case as a "clean close" and "IO error"
5144 as a "close". Stop calling closes "unexpected closes": existing
5145 Tors don't use SSL_close(), so having a connection close without
5146 the TLS shutdown handshake is hardly unexpected.
5147 - Send NAMESERVER_STATUS messages for a single failed nameserver
5150 o Code simplifications and refactoring:
5151 - Remove the tor_strpartition function: its logic was confused,
5152 and it was only used for one thing that could be implemented far
5156 Changes in version 0.2.0.19-alpha - 2008-02-09
5157 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
5158 handshake, makes path selection for relays more secure and IP address
5159 guessing more robust, and generally fixes a lot of bugs in preparation
5160 for calling the 0.2.0 branch stable.
5163 - Do not include recognizeable strings in the commonname part of
5164 Tor's x509 certificates.
5167 - If we're a relay, avoid picking ourselves as an introduction point,
5168 a rendezvous point, or as the final hop for internal circuits. Bug
5169 reported by taranis and lodger. Bugfix on 0.1.2.x.
5170 - Patch from "Andrew S. Lists" to catch when we contact a directory
5171 mirror at IP address X and he says we look like we're coming from
5172 IP address X. Bugfix on 0.1.2.x.
5174 o Minor features (security):
5175 - Be more paranoid about overwriting sensitive memory on free(),
5176 as a defensive programming tactic to ensure forward secrecy.
5178 o Minor features (directory authority):
5179 - Actually validate the options passed to AuthDirReject,
5180 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
5181 - Reject router descriptors with out-of-range bandwidthcapacity or
5182 bandwidthburst values.
5184 o Minor features (controller):
5185 - Reject controller commands over 1MB in length. This keeps rogue
5186 processes from running us out of memory.
5188 o Minor features (misc):
5189 - Give more descriptive well-formedness errors for out-of-range
5190 hidden service descriptor/protocol versions.
5191 - Make memory debugging information describe more about history
5192 of cell allocation, so we can help reduce our memory use.
5194 o Deprecated features (controller):
5195 - The status/version/num-versioning and status/version/num-concurring
5196 GETINFO options are no longer useful in the v3 directory protocol:
5197 treat them as deprecated, and warn when they're used.
5200 - When our consensus networkstatus has been expired for a while, stop
5201 being willing to build circuits using it. Fixes bug 401. Bugfix
5203 - Directory caches now fetch certificates from all authorities
5204 listed in a networkstatus consensus, even when they do not
5205 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
5206 - When connecting to a bridge without specifying its key, insert
5207 the connection into the identity-to-connection map as soon as
5208 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
5209 - Detect versions of OS X where malloc_good_size() is present in the
5210 library but never actually declared. Resolves bug 587. Bugfix
5212 - Stop incorrectly truncating zlib responses to directory authority
5213 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
5214 - Stop recommending that every server operator send mail to tor-ops.
5215 Resolves bug 597. Bugfix on 0.1.2.x.
5216 - Don't trigger an assert if we start a directory authority with a
5217 private IP address (like 127.0.0.1).
5218 - Avoid possible failures when generating a directory with routers
5219 with over-long versions strings, or too many flags set. Bugfix
5221 - If an attempt to launch a DNS resolve request over the control
5222 port fails because we have overrun the limit on the number of
5223 connections, tell the controller that the request has failed.
5224 - Avoid using too little bandwidth when our clock skips a few
5225 seconds. Bugfix on 0.1.2.x.
5226 - Fix shell error when warning about missing packages in configure
5227 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
5228 - Do not become confused when receiving a spurious VERSIONS-like
5229 cell from a confused v1 client. Bugfix on 0.2.0.x.
5230 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
5231 introduction points for a hidden service have failed. Patch from
5232 Karsten Loesing. Bugfix on 0.2.0.x.
5234 o Code simplifications and refactoring:
5235 - Remove some needless generality from cpuworker code, for improved
5237 - Stop overloading the circuit_t.onionskin field for both "onionskin
5238 from a CREATE cell that we are waiting for a cpuworker to be
5239 assigned" and "onionskin from an EXTEND cell that we are going to
5240 send to an OR as soon as we are connected". Might help with bug 600.
5241 - Add an in-place version of aes_crypt() so that we can avoid doing a
5242 needless memcpy() call on each cell payload.
5245 Changes in version 0.2.0.18-alpha - 2008-01-25
5246 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
5247 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
5248 that can warn or reject connections to ports generally associated with
5249 vulnerable-plaintext protocols.
5251 o New directory authorities:
5252 - Set up dannenberg (run by CCC) as the sixth v3 directory
5256 - Fix a major memory leak when attempting to use the v2 TLS
5257 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
5258 - We accidentally enabled the under-development v2 TLS handshake
5259 code, which was causing log entries like "TLS error while
5260 renegotiating handshake". Disable it again. Resolves bug 590.
5261 - We were computing the wrong Content-Length: header for directory
5262 responses that need to be compressed on the fly, causing clients
5263 asking for those items to always fail. Bugfix on 0.2.0.x; partially
5267 - Avoid going directly to the directory authorities even if you're a
5268 relay, if you haven't found yourself reachable yet or if you've
5269 decided not to advertise your dirport yet. Addresses bug 556.
5270 - If we've gone 12 hours since our last bandwidth check, and we
5271 estimate we have less than 50KB bandwidth capacity but we could
5272 handle more, do another bandwidth test.
5273 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
5274 Tor can warn and/or refuse connections to ports commonly used with
5275 vulnerable-plaintext protocols. Currently we warn on ports 23,
5276 109, 110, and 143, but we don't reject any.
5279 - When we setconf ClientOnly to 1, close any current OR and Dir
5280 listeners. Reported by mwenge.
5281 - When we get a consensus that's been signed by more people than
5282 we expect, don't log about it; it's not a big deal. Reported
5286 - Don't answer "/tor/networkstatus-bridges" directory requests if
5287 the request isn't encrypted.
5288 - Make "ClientOnly 1" config option disable directory ports too.
5289 - Patches from Karsten Loesing to make v2 hidden services more
5290 robust: work even when there aren't enough HSDir relays available;
5291 retry when a v2 rend desc fetch fails; but don't retry if we
5292 already have a usable v0 rend desc.
5295 Changes in version 0.2.0.17-alpha - 2008-01-17
5296 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
5299 - Make the tor-gencert man page get included correctly in the tarball.
5302 Changes in version 0.2.0.16-alpha - 2008-01-17
5303 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
5304 Loesing, and generally cleans up a lot of features and minor bugs.
5306 o New directory authorities:
5307 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
5310 o Major performance improvements:
5311 - Switch our old ring buffer implementation for one more like that
5312 used by free Unix kernels. The wasted space in a buffer with 1mb
5313 of data will now be more like 8k than 1mb. The new implementation
5314 also avoids realloc();realloc(); patterns that can contribute to
5315 memory fragmentation.
5318 - Configuration files now accept C-style strings as values. This
5319 helps encode characters not allowed in the current configuration
5320 file format, such as newline or #. Addresses bug 557.
5321 - Although we fixed bug 539 (where servers would send HTTP status 503
5322 responses _and_ send a body too), there are still servers out
5323 there that haven't upgraded. Therefore, make clients parse such
5324 bodies when they receive them.
5325 - When we're not serving v2 directory information, there is no reason
5326 to actually keep any around. Remove the obsolete files and directory
5327 on startup if they are very old and we aren't going to serve them.
5329 o Minor performance improvements:
5330 - Reference-count and share copies of address policy entries; only 5%
5331 of them were actually distinct.
5332 - Never walk through the list of logs if we know that no log is
5333 interested in a given message.
5336 - When an authority has not signed a consensus, do not try to
5337 download a nonexistent "certificate with key 00000000". Bugfix
5338 on 0.2.0.x. Fixes bug 569.
5339 - Fix a rare assert error when we're closing one of our threads:
5340 use a mutex to protect the list of logs, so we never write to the
5341 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
5342 bug 575, which is kind of the revenge of bug 222.
5343 - Patch from Karsten Loesing to complain less at both the client
5344 and the relay when a relay used to have the HSDir flag but doesn't
5345 anymore, and we try to upload a hidden service descriptor.
5346 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
5348 - Do not try to download missing certificates until we have tried
5349 to check our fallback consensus. Fixes bug 583.
5350 - Make bridges round reported GeoIP stats info up to the nearest
5351 estimate, not down. Now we can distinguish between "0 people from
5352 this country" and "1 person from this country".
5353 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
5354 - Avoid possible segfault if key generation fails in
5355 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
5356 - Avoid segfault in the case where a badly behaved v2 versioning
5357 directory sends a signed networkstatus with missing client-versions.
5359 - Avoid segfaults on certain complex invocations of
5360 router_get_by_hexdigest(). Bugfix on 0.1.2.
5361 - Correct bad index on array access in parse_http_time(). Bugfix
5363 - Fix possible bug in vote generation when server versions are present
5364 but client versions are not.
5365 - Fix rare bug on REDIRECTSTREAM control command when called with no
5366 port set: it could erroneously report an error when none had
5368 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
5369 compressing large objects and find ourselves with more than 4k
5370 left over. Bugfix on 0.2.0.
5371 - Fix a small memory leak when setting up a hidden service.
5372 - Fix a few memory leaks that could in theory happen under bizarre
5374 - Fix an assert if we post a general-purpose descriptor via the
5375 control port but that descriptor isn't mentioned in our current
5376 network consensus. Bug reported by Jon McLachlan; bugfix on
5379 o Minor features (controller):
5380 - Get NS events working again. Patch from tup.
5381 - The GETCONF command now escapes and quotes configuration values
5382 that don't otherwise fit into the torrc file.
5383 - The SETCONF command now handles quoted values correctly.
5385 o Minor features (directory authorities):
5386 - New configuration options to override default maximum number of
5387 servers allowed on a single IP address. This is important for
5388 running a test network on a single host.
5389 - Actually implement the -s option to tor-gencert.
5390 - Add a manual page for tor-gencert.
5392 o Minor features (bridges):
5393 - Bridge authorities no longer serve bridge descriptors over
5394 unencrypted connections.
5396 o Minor features (other):
5397 - Add hidden services and DNSPorts to the list of things that make
5398 Tor accept that it has running ports. Change starting Tor with no
5399 ports from a fatal error to a warning; we might change it back if
5400 this turns out to confuse anybody. Fixes bug 579.
5403 Changes in version 0.1.2.19 - 2008-01-17
5404 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
5405 exit policy a little bit more conservative so it's safer to run an
5406 exit relay on a home system, and fixes a variety of smaller issues.
5409 - Exit policies now reject connections that are addressed to a
5410 relay's public (external) IP address too, unless
5411 ExitPolicyRejectPrivate is turned off. We do this because too
5412 many relays are running nearby to services that trust them based
5416 - When the clock jumps forward a lot, do not allow the bandwidth
5417 buckets to become negative. Fixes bug 544.
5418 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
5419 on every successful resolve. Reported by Mike Perry.
5420 - Purge old entries from the "rephist" database and the hidden
5421 service descriptor database even when DirPort is zero.
5422 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
5423 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
5424 crashing or mis-answering these requests.
5425 - When we decide to send a 503 response to a request for servers, do
5426 not then also send the server descriptors: this defeats the whole
5427 purpose. Fixes bug 539.
5430 - Changing the ExitPolicyRejectPrivate setting should cause us to
5431 rebuild our server descriptor.
5432 - Fix handling of hex nicknames when answering controller requests for
5433 networkstatus by name, or when deciding whether to warn about
5434 unknown routers in a config option. (Patch from mwenge.)
5435 - Fix a couple of hard-to-trigger autoconf problems that could result
5436 in really weird results on platforms whose sys/types.h files define
5437 nonstandard integer types.
5438 - Don't try to create the datadir when running --verify-config or
5439 --hash-password. Resolves bug 540.
5440 - If we were having problems getting a particular descriptor from the
5441 directory caches, and then we learned about a new descriptor for
5442 that router, we weren't resetting our failure count. Reported
5444 - Although we fixed bug 539 (where servers would send HTTP status 503
5445 responses _and_ send a body too), there are still servers out there
5446 that haven't upgraded. Therefore, make clients parse such bodies
5447 when they receive them.
5448 - Run correctly on systems where rlim_t is larger than unsigned long.
5449 This includes some 64-bit systems.
5450 - Run correctly on platforms (like some versions of OS X 10.5) where
5451 the real limit for number of open files is OPEN_FILES, not rlim_max
5452 from getrlimit(RLIMIT_NOFILES).
5453 - Avoid a spurious free on base64 failure.
5454 - Avoid segfaults on certain complex invocations of
5455 router_get_by_hexdigest().
5456 - Fix rare bug on REDIRECTSTREAM control command when called with no
5457 port set: it could erroneously report an error when none had
5461 Changes in version 0.2.0.15-alpha - 2007-12-25
5462 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
5463 features added in 0.2.0.13-alpha.
5466 - Fix several remotely triggerable asserts based on DirPort requests
5467 for a v2 or v3 networkstatus object before we were prepared. This
5468 was particularly bad for 0.2.0.13 and later bridge relays, who
5469 would never have a v2 networkstatus and would thus always crash
5470 when used. Bugfixes on 0.2.0.x.
5471 - Estimate the v3 networkstatus size more accurately, rather than
5472 estimating it at zero bytes and giving it artificially high priority
5473 compared to other directory requests. Bugfix on 0.2.0.x.
5476 - Fix configure.in logic for cross-compilation.
5477 - When we load a bridge descriptor from the cache, and it was
5478 previously unreachable, mark it as retriable so we won't just
5479 ignore it. Also, try fetching a new copy immediately. Bugfixes
5481 - The bridge GeoIP stats were counting other relays, for example
5482 self-reachability and authority-reachability tests.
5485 - Support compilation to target iPhone; patch from cjacker huang.
5486 To build for iPhone, pass the --enable-iphone option to configure.
5489 Changes in version 0.2.0.14-alpha - 2007-12-23
5491 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
5492 without a datadirectory from a previous Tor install. Reported
5494 - Fix a crash when we fetch a descriptor that turns out to be
5495 unexpected (it used to be in our networkstatus when we started
5496 fetching it, but it isn't in our current networkstatus), and we
5497 aren't using bridges. Bugfix on 0.2.0.x.
5498 - Fix a crash when accessing hidden services: it would work the first
5499 time you use a given introduction point for your service, but
5500 on subsequent requests we'd be using garbage memory. Fixed by
5501 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
5502 - Fix a crash when we load a bridge descriptor from disk but we don't
5503 currently have a Bridge line for it in our torrc. Bugfix on
5507 - If bridge authorities set BridgePassword, they will serve a
5508 snapshot of known bridge routerstatuses from their DirPort to
5509 anybody who knows that password. Unset by default.
5512 - Make the unit tests build again.
5513 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
5514 - Make PublishServerDescriptor default to 1, so the default doesn't
5515 have to change as we invent new directory protocol versions.
5516 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
5517 be included unless sys/time.h is already included. Fixes
5518 bug 553. Bugfix on 0.2.0.x.
5519 - If we receive a general-purpose descriptor and then receive an
5520 identical bridge-purpose descriptor soon after, don't discard
5521 the next one as a duplicate.
5524 - If BridgeRelay is set to 1, then the default for
5525 PublishServerDescriptor is now "bridge" rather than "v2,v3".
5526 - If the user sets RelayBandwidthRate but doesn't set
5527 RelayBandwidthBurst, then make them equal rather than erroring out.
5530 Changes in version 0.2.0.13-alpha - 2007-12-21
5531 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
5532 Goodell, fixes many more bugs, and adds a lot of infrastructure for
5535 o New directory authorities:
5536 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
5540 - Only update guard status (usable / not usable) once we have
5541 enough directory information. This was causing us to always pick
5542 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
5543 causing us to discard all our guards on startup if we hadn't been
5544 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
5545 - Purge old entries from the "rephist" database and the hidden
5546 service descriptor databases even when DirPort is zero. Bugfix
5548 - We were ignoring our RelayBandwidthRate for the first 30 seconds
5549 after opening a circuit -- even a relayed circuit. Bugfix on
5551 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
5552 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
5553 crashing or mis-answering these types of requests.
5554 - Relays were publishing their server descriptor to v1 and v2
5555 directory authorities, but they didn't try publishing to v3-only
5556 authorities. Fix this; and also stop publishing to v1 authorities.
5558 - When we were reading router descriptors from cache, we were ignoring
5559 the annotations -- so for example we were reading in bridge-purpose
5560 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
5561 - When we decided to send a 503 response to a request for servers, we
5562 were then also sending the server descriptors: this defeats the
5563 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
5566 - Bridge relays now behave like clients with respect to time
5567 intervals for downloading new consensus documents -- otherwise they
5568 stand out. Bridge users now wait until the end of the interval,
5569 so their bridge relay will be sure to have a new consensus document.
5570 - Three new config options (AlternateDirAuthority,
5571 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
5572 user selectively replace the default directory authorities by type,
5573 rather than the all-or-nothing replacement that DirServer offers.
5574 - Tor can now be configured to read a GeoIP file from disk in one
5575 of two formats. This can be used by controllers to map IP addresses
5576 to countries. Eventually, it may support exit-by-country.
5577 - When possible, bridge relays remember which countries users
5578 are coming from, and report aggregate information in their
5579 extra-info documents, so that the bridge authorities can learn
5580 where Tor is blocked.
5581 - Bridge directory authorities now do reachability testing on the
5582 bridges they know. They provide router status summaries to the
5583 controller via "getinfo ns/purpose/bridge", and also dump summaries
5584 to a file periodically.
5585 - Stop fetching directory info so aggressively if your DirPort is
5586 on but your ORPort is off; stop fetching v2 dir info entirely.
5587 You can override these choices with the new FetchDirInfoEarly
5591 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
5592 consensus documents when there are too many relays at a single
5593 IP address. Now clear it in v2 network status documents too, and
5594 also clear it in routerinfo_t when the relay is no longer listed
5595 in the relevant networkstatus document.
5596 - Don't crash if we get an unexpected value for the
5597 PublishServerDescriptor config option. Reported by Matt Edman;
5598 bugfix on 0.2.0.9-alpha.
5599 - Our new v2 hidden service descriptor format allows descriptors
5600 that have no introduction points. But Tor crashed when we tried
5601 to build a descriptor with no intro points (and it would have
5602 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
5604 - Fix building with dmalloc 5.5.2 with glibc.
5605 - Reject uploaded descriptors and extrainfo documents if they're
5606 huge. Otherwise we'll cache them all over the network and it'll
5607 clog everything up. Reported by Aljosha Judmayer.
5608 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
5609 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
5610 - When the DANGEROUS_VERSION controller status event told us we're
5611 running an obsolete version, it used the string "OLD" to describe
5612 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
5613 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
5614 - If we can't expand our list of entry guards (e.g. because we're
5615 using bridges or we have StrictEntryNodes set), don't mark relays
5616 down when they fail a directory request. Otherwise we're too quick
5617 to mark all our entry points down. Bugfix on 0.1.2.x.
5618 - Fix handling of hex nicknames when answering controller requests for
5619 networkstatus by name, or when deciding whether to warn about unknown
5620 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
5621 - Fix a couple of hard-to-trigger autoconf problems that could result
5622 in really weird results on platforms whose sys/types.h files define
5623 nonstandard integer types. Bugfix on 0.1.2.x.
5624 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
5625 - Don't crash on name lookup when we have no current consensus. Fixes
5626 bug 538; bugfix on 0.2.0.x.
5627 - Only Tors that want to mirror the v2 directory info should
5628 create the "cached-status" directory in their datadir. (All Tors
5629 used to create it.) Bugfix on 0.2.0.9-alpha.
5630 - Directory authorities should only automatically download Extra Info
5631 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
5634 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
5635 consumers. (We already do this on HUP.)
5636 - Authorities and caches fetch the v2 networkstatus documents
5637 less often, now that v3 is encouraged.
5638 - Add a new config option BridgeRelay that specifies you want to
5639 be a bridge relay. Right now the only difference is that it makes
5640 you answer begin_dir requests, and it makes you cache dir info,
5641 even if your DirPort isn't on.
5642 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
5643 ask about source, timestamp of arrival, purpose, etc. We need
5644 something like this to help Vidalia not do GeoIP lookups on bridge
5646 - Allow multiple HashedControlPassword config lines, to support
5647 multiple controller passwords.
5648 - Authorities now decide whether they're authoritative for a given
5649 router based on the router's purpose.
5650 - New config options AuthDirBadDir and AuthDirListBadDirs for
5651 authorities to mark certain relays as "bad directories" in the
5652 networkstatus documents. Also supports the "!baddir" directive in
5653 the approved-routers file.
5656 Changes in version 0.2.0.12-alpha - 2007-11-16
5657 This twelfth development snapshot fixes some more build problems as
5658 well as a few minor bugs.
5661 - Make it build on OpenBSD again. Patch from tup.
5662 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
5663 package-building for Red Hat, OS X, etc.
5665 o Minor bugfixes (on 0.1.2.x):
5666 - Changing the ExitPolicyRejectPrivate setting should cause us to
5667 rebuild our server descriptor.
5669 o Minor bugfixes (on 0.2.0.x):
5670 - When we're lacking a consensus, don't try to perform rendezvous
5671 operations. Reported by Karsten Loesing.
5672 - Fix a small memory leak whenever we decide against using a
5673 newly picked entry guard. Reported by Mike Perry.
5674 - When authorities detected more than two relays running on the same
5675 IP address, they were clearing all the status flags but forgetting
5676 to clear the "hsdir" flag. So clients were being told that a
5677 given relay was the right choice for a v2 hsdir lookup, yet they
5678 never had its descriptor because it was marked as 'not running'
5680 - If we're trying to fetch a bridge descriptor and there's no way
5681 the bridge authority could help us (for example, we don't know
5682 a digest, or there is no bridge authority), don't be so eager to
5683 fall back to asking the bridge authority.
5684 - If we're using bridges or have strictentrynodes set, and our
5685 chosen exit is in the same family as all our bridges/entry guards,
5686 then be flexible about families.
5689 - When we negotiate a v2 link-layer connection (not yet implemented),
5690 accept RELAY_EARLY cells and turn them into RELAY cells if we've
5691 negotiated a v1 connection for their next step. Initial code for
5695 Changes in version 0.2.0.11-alpha - 2007-11-12
5696 This eleventh development snapshot fixes some build problems with
5697 the previous snapshot. It also includes a more secure-by-default exit
5698 policy for relays, fixes an enormous memory leak for exit relays, and
5699 fixes another bug where servers were falling out of the directory list.
5702 - Exit policies now reject connections that are addressed to a
5703 relay's public (external) IP address too, unless
5704 ExitPolicyRejectPrivate is turned off. We do this because too
5705 many relays are running nearby to services that trust them based
5706 on network address. Bugfix on 0.1.2.x.
5709 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
5710 on every successful resolve. Reported by Mike Perry; bugfix
5712 - On authorities, never downgrade to old router descriptors simply
5713 because they're listed in the consensus. This created a catch-22
5714 where we wouldn't list a new descriptor because there was an
5715 old one in the consensus, and we couldn't get the new one in the
5716 consensus because we wouldn't list it. Possible fix for bug 548.
5717 Also, this might cause bug 543 to appear on authorities; if so,
5718 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
5720 o Packaging fixes on 0.2.0.10-alpha:
5721 - We were including instructions about what to do with the
5722 src/config/fallback-consensus file, but we weren't actually
5723 including it in the tarball. Disable all of that for now.
5726 - Allow people to say PreferTunnelledDirConns rather than
5727 PreferTunneledDirConns, for those alternate-spellers out there.
5730 - Don't reevaluate all the information from our consensus document
5731 just because we've downloaded a v2 networkstatus that we intend
5732 to cache. Fixes bug 545; bugfix on 0.2.0.x.
5735 Changes in version 0.2.0.10-alpha - 2007-11-10
5736 This tenth development snapshot adds a third v3 directory authority
5737 run by Mike Perry, adds most of Karsten Loesing's new hidden service
5738 descriptor format, fixes a bad crash bug and new bridge bugs introduced
5739 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
5740 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
5741 addresses many more minor issues.
5743 o New directory authorities:
5744 - Set up ides (run by Mike Perry) as the third v3 directory authority.
5747 - Allow tunnelled directory connections to ask for an encrypted
5748 "begin_dir" connection or an anonymized "uses a full Tor circuit"
5749 connection independently. Now we can make anonymized begin_dir
5750 connections for (e.g.) more secure hidden service posting and
5752 - More progress on proposal 114: code from Karsten Loesing to
5753 implement new hidden service descriptor format.
5754 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
5755 accommodate the growing number of servers that use the default
5756 and are reaching it.
5757 - Directory authorities use a new formula for selecting which nodes
5758 to advertise as Guards: they must be in the top 7/8 in terms of
5759 how long we have known about them, and above the median of those
5760 nodes in terms of weighted fractional uptime.
5761 - Make "not enough dir info yet" warnings describe *why* Tor feels
5762 it doesn't have enough directory info yet.
5765 - Stop servers from crashing if they set a Family option (or
5766 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
5768 - Make bridge users work again -- the move to v3 directories in
5769 0.2.0.9-alpha had introduced a number of bugs that made bridges
5770 no longer work for clients.
5771 - When the clock jumps forward a lot, do not allow the bandwidth
5772 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
5774 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
5775 - When the consensus lists a router descriptor that we previously were
5776 mirroring, but that we considered non-canonical, reload the
5777 descriptor as canonical. This fixes bug 543 where Tor servers
5778 would start complaining after a few days that they don't have
5779 enough directory information to build a circuit.
5780 - Consider replacing the current consensus when certificates arrive
5781 that make the pending consensus valid. Previously, we were only
5782 considering replacement when the new certs _didn't_ help.
5783 - Fix an assert error on startup if we didn't already have the
5784 consensus and certs cached in our datadirectory: we were caching
5785 the consensus in consensus_waiting_for_certs but then free'ing it
5787 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
5788 Request) if we need more v3 certs but we've already got pending
5789 requests for all of them.
5790 - Correctly back off from failing certificate downloads. Fixes
5792 - Authorities don't vote on the Running flag if they have been running
5793 for less than 30 minutes themselves. Fixes bug 547, where a newly
5794 started authority would vote that everyone was down.
5797 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
5798 it, it had no AES, and it hasn't seen any security patches since
5802 - Clients now hold circuitless TLS connections open for 1.5 times
5803 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
5804 rebuild a new circuit over them within that timeframe. Previously,
5805 they held them open only for KeepalivePeriod (5 minutes).
5806 - Use "If-Modified-Since" to avoid retrieving consensus
5807 networkstatuses that we already have.
5808 - When we have no consensus, check FallbackNetworkstatusFile (defaults
5809 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
5810 we start knowing some directory caches.
5811 - When we receive a consensus from the future, warn about skew.
5812 - Improve skew reporting: try to give the user a better log message
5813 about how skewed they are, and how much this matters.
5814 - When we have a certificate for an authority, believe that
5815 certificate's claims about the authority's IP address.
5816 - New --quiet command-line option to suppress the default console log.
5817 Good in combination with --hash-password.
5818 - Authorities send back an X-Descriptor-Not-New header in response to
5819 an accepted-but-discarded descriptor upload. Partially implements
5821 - Make the log message for "tls error. breaking." more useful.
5822 - Better log messages about certificate downloads, to attempt to
5823 track down the second incarnation of bug 546.
5825 o Minor features (bridges):
5826 - If bridge users set UpdateBridgesFromAuthority, but the digest
5827 they ask for is a 404 from the bridge authority, they now fall
5828 back to trying the bridge directly.
5829 - Bridges now use begin_dir to publish their server descriptor to
5830 the bridge authority, even when they haven't set TunnelDirConns.
5832 o Minor features (controller):
5833 - When reporting clock skew, and we know that the clock is _at least
5834 as skewed_ as some value, but we don't know the actual value,
5835 report the value as a "minimum skew."
5838 - Update linux-tor-prio.sh script to allow QoS based on the uid of
5839 the Tor process. Patch from Marco Bonetti with tweaks from Mike
5843 - Refuse to start if both ORPort and UseBridges are set. Bugfix
5844 on 0.2.0.x, suggested by Matt Edman.
5845 - Don't stop fetching descriptors when FetchUselessDescriptors is
5846 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
5847 reported by tup and ioerror.
5848 - Better log message on vote from unknown authority.
5849 - Don't log "Launching 0 request for 0 router" message.
5851 o Minor bugfixes (memory leaks):
5852 - Stop leaking memory every time we parse a v3 certificate. Bugfix
5854 - Stop leaking memory every time we load a v3 certificate. Bugfix
5855 on 0.2.0.1-alpha. Fixes bug 536.
5856 - Stop leaking a cached networkstatus on exit. Bugfix on
5858 - Stop leaking voter information every time we free a consensus.
5859 Bugfix on 0.2.0.3-alpha.
5860 - Stop leaking signed data every time we check a voter signature.
5861 Bugfix on 0.2.0.3-alpha.
5862 - Stop leaking a signature every time we fail to parse a consensus or
5863 a vote. Bugfix on 0.2.0.3-alpha.
5864 - Stop leaking v2_download_status_map on shutdown. Bugfix on
5866 - Stop leaking conn->nickname every time we make a connection to a
5867 Tor relay without knowing its expected identity digest (e.g. when
5868 using bridges). Bugfix on 0.2.0.3-alpha.
5870 - Minor bugfixes (portability):
5871 - Run correctly on platforms where rlim_t is larger than unsigned
5872 long, and/or where the real limit for number of open files is
5873 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
5874 particular, these may be needed for OS X 10.5.
5877 Changes in version 0.1.2.18 - 2007-10-28
5878 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
5879 hidden service introduction that were causing huge delays, and a big
5880 bug that was causing some servers to disappear from the network status
5881 lists for a few hours each day.
5883 o Major bugfixes (crashes):
5884 - If a connection is shut down abruptly because of something that
5885 happened inside connection_flushed_some(), do not call
5886 connection_finished_flushing(). Should fix bug 451:
5887 "connection_stop_writing: Assertion conn->write_event failed"
5888 Bugfix on 0.1.2.7-alpha.
5889 - Fix possible segfaults in functions called from
5890 rend_process_relay_cell().
5892 o Major bugfixes (hidden services):
5893 - Hidden services were choosing introduction points uniquely by
5894 hexdigest, but when constructing the hidden service descriptor
5895 they merely wrote the (potentially ambiguous) nickname.
5896 - Clients now use the v2 intro format for hidden service
5897 connections: they specify their chosen rendezvous point by identity
5898 digest rather than by (potentially ambiguous) nickname. These
5899 changes could speed up hidden service connections dramatically.
5901 o Major bugfixes (other):
5902 - Stop publishing a new server descriptor just because we get a
5903 HUP signal. This led (in a roundabout way) to some servers getting
5904 dropped from the networkstatus lists for a few hours each day.
5905 - When looking for a circuit to cannibalize, consider family as well
5906 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
5907 circuit cannibalization).
5908 - When a router wasn't listed in a new networkstatus, we were leaving
5909 the flags for that router alone -- meaning it remained Named,
5910 Running, etc -- even though absence from the networkstatus means
5911 that it shouldn't be considered to exist at all anymore. Now we
5912 clear all the flags for routers that fall out of the networkstatus
5913 consensus. Fixes bug 529.
5916 - Don't try to access (or alter) the state file when running
5917 --list-fingerprint or --verify-config or --hash-password. Resolves
5919 - When generating information telling us how to extend to a given
5920 router, do not try to include the nickname if it is
5921 absent. Resolves bug 467.
5922 - Fix a user-triggerable segfault in expand_filename(). (There isn't
5923 a way to trigger this remotely.)
5924 - When sending a status event to the controller telling it that an
5925 OR address is reachable, set the port correctly. (Previously we
5926 were reporting the dir port.)
5927 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
5928 command. Bugfix on 0.1.2.17.
5929 - When loading bandwidth history, do not believe any information in
5930 the future. Fixes bug 434.
5931 - When loading entry guard information, do not believe any information
5933 - When we have our clock set far in the future and generate an
5934 onion key, then re-set our clock to be correct, we should not stop
5935 the onion key from getting rotated.
5936 - On some platforms, accept() can return a broken address. Detect
5937 this more quietly, and deal accordingly. Fixes bug 483.
5938 - It's not actually an error to find a non-pending entry in the DNS
5939 cache when canceling a pending resolve. Don't log unless stuff
5940 is fishy. Resolves bug 463.
5941 - Don't reset trusted dir server list when we set a configuration
5942 option. Patch from Robert Hogan.
5943 - Don't try to create the datadir when running --verify-config or
5944 --hash-password. Resolves bug 540.
5947 Changes in version 0.2.0.9-alpha - 2007-10-24
5948 This ninth development snapshot switches clients to the new v3 directory
5949 system; allows servers to be listed in the network status even when they
5950 have the same nickname as a registered server; and fixes many other
5951 bugs including a big one that was causing some servers to disappear
5952 from the network status lists for a few hours each day.
5954 o Major features (directory system):
5955 - Clients now download v3 consensus networkstatus documents instead
5956 of v2 networkstatus documents. Clients and caches now base their
5957 opinions about routers on these consensus documents. Clients only
5958 download router descriptors listed in the consensus.
5959 - Authorities now list servers who have the same nickname as
5960 a different named server, but list them with a new flag,
5961 "Unnamed". Now we can list servers that happen to pick the same
5962 nickname as a server that registered two years ago and then
5963 disappeared. Partially implements proposal 122.
5964 - If the consensus lists a router as "Unnamed", the name is assigned
5965 to a different router: do not identify the router by that name.
5966 Partially implements proposal 122.
5967 - Authorities can now come to a consensus on which method to use to
5968 compute the consensus. This gives us forward compatibility.
5971 - Stop publishing a new server descriptor just because we HUP or
5972 when we find our DirPort to be reachable but won't actually publish
5973 it. New descriptors without any real changes are dropped by the
5974 authorities, and can screw up our "publish every 18 hours" schedule.
5976 - When a router wasn't listed in a new networkstatus, we were leaving
5977 the flags for that router alone -- meaning it remained Named,
5978 Running, etc -- even though absence from the networkstatus means
5979 that it shouldn't be considered to exist at all anymore. Now we
5980 clear all the flags for routers that fall out of the networkstatus
5981 consensus. Fixes bug 529; bugfix on 0.1.2.x.
5982 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
5983 extrainfo documents and then discard them immediately for not
5984 matching the latest router. Bugfix on 0.2.0.1-alpha.
5986 o Minor features (v3 directory protocol):
5987 - Allow tor-gencert to generate a new certificate without replacing
5989 - Allow certificates to include an address.
5990 - When we change our directory-cache settings, reschedule all voting
5991 and download operations.
5992 - Reattempt certificate downloads immediately on failure, as long as
5993 we haven't failed a threshold number of times yet.
5994 - Delay retrying consensus downloads while we're downloading
5995 certificates to verify the one we just got. Also, count getting a
5996 consensus that we already have (or one that isn't valid) as a failure,
5997 and count failing to get the certificates after 20 minutes as a
5999 - Build circuits and download descriptors even if our consensus is a
6000 little expired. (This feature will go away once authorities are
6003 o Minor features (router descriptor cache):
6004 - If we find a cached-routers file that's been sitting around for more
6005 than 28 days unmodified, then most likely it's a leftover from
6006 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
6008 - When we (as a cache) download a descriptor because it was listed
6009 in a consensus, remember when the consensus was supposed to expire,
6010 and don't expire the descriptor until then.
6012 o Minor features (performance):
6013 - Call routerlist_remove_old_routers() much less often. This should
6014 speed startup, especially on directory caches.
6015 - Don't try to launch new descriptor downloads quite so often when we
6016 already have enough directory information to build circuits.
6017 - Base64 decoding was actually showing up on our profile when parsing
6018 the initial descriptor file; switch to an in-process all-at-once
6019 implementation that's about 3.5x times faster than calling out to
6022 o Minor features (compilation):
6023 - Detect non-ASCII platforms (if any still exist) and refuse to
6024 build there: some of our code assumes that 'A' is 65 and so on.
6026 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
6027 - Make the "next period" votes into "current period" votes immediately
6028 after publishing the consensus; avoid a heisenbug that made them
6029 stick around indefinitely.
6030 - When we discard a vote as a duplicate, do not report this as
6032 - Treat missing v3 keys or certificates as an error when running as a
6033 v3 directory authority.
6034 - When we're configured to be a v3 authority, but we're only listed
6035 as a non-v3 authority in our DirServer line for ourself, correct
6037 - If an authority doesn't have a qualified hostname, just put
6038 its address in the vote. This fixes the problem where we referred to
6039 "moria on moria:9031."
6040 - Distinguish between detached signatures for the wrong period, and
6041 detached signatures for a divergent vote.
6042 - Fix a small memory leak when computing a consensus.
6043 - When there's no concensus, we were forming a vote every 30
6044 minutes, but writing the "valid-after" line in our vote based
6045 on our configured V3AuthVotingInterval: so unless the intervals
6046 matched up, we immediately rejected our own vote because it didn't
6047 start at the voting interval that caused us to construct a vote.
6049 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
6050 - Delete unverified-consensus when the real consensus is set.
6051 - Consider retrying a consensus networkstatus fetch immediately
6052 after one fails: don't wait 60 seconds to notice.
6053 - When fetching a consensus as a cache, wait until a newer consensus
6054 should exist before trying to replace the current one.
6055 - Use a more forgiving schedule for retrying failed consensus
6056 downloads than for other types.
6058 o Minor bugfixes (other directory issues):
6059 - Correct the implementation of "download votes by digest." Bugfix on
6061 - Authorities no longer send back "400 you're unreachable please fix
6062 it" errors to Tor servers that aren't online all the time. We're
6063 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
6065 o Minor bugfixes (controller):
6066 - Don't reset trusted dir server list when we set a configuration
6067 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
6068 - Respond to INT and TERM SIGNAL commands before we execute the
6069 signal, in case the signal shuts us down. We had a patch in
6070 0.1.2.1-alpha that tried to do this by queueing the response on
6071 the connection's buffer before shutting down, but that really
6072 isn't the same thing at all. Bug located by Matt Edman.
6074 o Minor bugfixes (misc):
6075 - Correctly check for bad options to the "PublishServerDescriptor"
6076 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
6077 - Stop leaking memory on failing case of base32_decode, and make
6078 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
6079 - Don't try to download extrainfo documents when we're trying to
6080 fetch enough directory info to build a circuit: having enough
6081 info should get priority. Bugfix on 0.2.0.x.
6082 - Don't complain that "your server has not managed to confirm that its
6083 ports are reachable" if we haven't been able to build any circuits
6084 yet. Bug found by spending four hours without a v3 consensus. Bugfix
6086 - Detect the reason for failing to mmap a descriptor file we just
6087 wrote, and give a more useful log message. Fixes bug 533. Bugfix
6090 o Code simplifications and refactoring:
6091 - Remove support for the old bw_accounting file: we've been storing
6092 bandwidth accounting information in the state file since
6093 0.1.2.5-alpha. This may result in bandwidth accounting errors
6094 if you try to upgrade from 0.1.1.x or earlier, or if you try to
6095 downgrade to 0.1.1.x or earlier.
6096 - New convenience code to locate a file within the DataDirectory.
6097 - Move non-authority functionality out of dirvote.c.
6098 - Refactor the arguments for router_pick_{directory_|trusteddir}server
6099 so that they all take the same named flags.
6102 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
6103 Unix users an easy way to script their Tor process (e.g. by
6104 adjusting bandwidth based on the time of the day).
6107 Changes in version 0.2.0.8-alpha - 2007-10-12
6108 This eighth development snapshot fixes a crash bug that's been bothering
6109 us since February 2007, lets bridge authorities store a list of bridge
6110 descriptors they've seen, gets v3 directory voting closer to working,
6111 starts caching v3 directory consensus documents on directory mirrors,
6112 and fixes a variety of smaller issues including some minor memory leaks.
6114 o Major features (router descriptor cache):
6115 - Store routers in a file called cached-descriptors instead of in
6116 cached-routers. Initialize cached-descriptors from cached-routers
6117 if the old format is around. The new format allows us to store
6118 annotations along with descriptors.
6119 - Use annotations to record the time we received each descriptor, its
6120 source, and its purpose.
6121 - Disable the SETROUTERPURPOSE controller command: it is now
6123 - Controllers should now specify cache=no or cache=yes when using
6124 the +POSTDESCRIPTOR command.
6125 - Bridge authorities now write bridge descriptors to disk, meaning
6126 we can export them to other programs and begin distributing them
6129 o Major features (directory authorities):
6130 - When a v3 authority is missing votes or signatures, it now tries
6132 - Directory authorities track weighted fractional uptime as well as
6133 weighted mean-time-between failures. WFU is suitable for deciding
6134 whether a node is "usually up", while MTBF is suitable for deciding
6135 whether a node is "likely to stay up." We need both, because
6136 "usually up" is a good requirement for guards, while "likely to
6137 stay up" is a good requirement for long-lived connections.
6139 o Major features (v3 directory system):
6140 - Caches now download v3 network status documents as needed,
6141 and download the descriptors listed in them.
6142 - All hosts now attempt to download and keep fresh v3 authority
6143 certificates, and re-attempt after failures.
6144 - More internal-consistency checks for vote parsing.
6146 o Major bugfixes (crashes):
6147 - If a connection is shut down abruptly because of something that
6148 happened inside connection_flushed_some(), do not call
6149 connection_finished_flushing(). Should fix bug 451. Bugfix on
6152 o Major bugfixes (performance):
6153 - Fix really bad O(n^2) performance when parsing a long list of
6154 routers: Instead of searching the entire list for an "extra-info "
6155 string which usually wasn't there, once for every routerinfo
6156 we read, just scan lines forward until we find one we like.
6158 - When we add data to a write buffer in response to the data on that
6159 write buffer getting low because of a flush, do not consider the
6160 newly added data as a candidate for immediate flushing, but rather
6161 make it wait until the next round of writing. Otherwise, we flush
6162 and refill recursively, and a single greedy TLS connection can
6163 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
6165 o Minor features (v3 authority system):
6166 - Add more ways for tools to download the votes that lead to the
6168 - Send a 503 when low on bandwidth and a vote, consensus, or
6169 certificate is requested.
6170 - If-modified-since is now implemented properly for all kinds of
6171 certificate requests.
6173 o Minor bugfixes (network statuses):
6174 - Tweak the implementation of proposal 109 slightly: allow at most
6175 two Tor servers on the same IP address, except if it's the location
6176 of a directory authority, in which case allow five. Bugfix on
6179 o Minor bugfixes (controller):
6180 - When sending a status event to the controller telling it that an
6181 OR address is reachable, set the port correctly. (Previously we
6182 were reporting the dir port.) Bugfix on 0.1.2.x.
6184 o Minor bugfixes (v3 directory system):
6185 - Fix logic to look up a cert by its signing key digest. Bugfix on
6187 - Only change the reply to a vote to "OK" if it's not already
6188 set. This gets rid of annoying "400 OK" log messages, which may
6189 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
6190 - When we get a valid consensus, recompute the voting schedule.
6191 - Base the valid-after time of a vote on the consensus voting
6192 schedule, not on our preferred schedule.
6193 - Make the return values and messages from signature uploads and
6194 downloads more sensible.
6195 - Fix a memory leak when serving votes and consensus documents, and
6196 another when serving certificates.
6198 o Minor bugfixes (performance):
6199 - Use a slightly simpler string hashing algorithm (copying Python's
6200 instead of Java's) and optimize our digest hashing algorithm to take
6201 advantage of 64-bit platforms and to remove some possibly-costly
6203 - Fix a minor memory leak whenever we parse guards from our state
6204 file. Bugfix on 0.2.0.7-alpha.
6205 - Fix a minor memory leak whenever we write out a file. Bugfix on
6207 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
6208 command. Bugfix on 0.2.0.5-alpha.
6210 o Minor bugfixes (portability):
6211 - On some platforms, accept() can return a broken address. Detect
6212 this more quietly, and deal accordingly. Fixes bug 483.
6213 - Stop calling tor_strlower() on uninitialized memory in some cases.
6214 Bugfix in 0.2.0.7-alpha.
6216 o Minor bugfixes (usability):
6217 - Treat some 403 responses from directory servers as INFO rather than
6218 WARN-severity events.
6219 - It's not actually an error to find a non-pending entry in the DNS
6220 cache when canceling a pending resolve. Don't log unless stuff is
6221 fishy. Resolves bug 463.
6223 o Minor bugfixes (anonymity):
6224 - Never report that we've used more bandwidth than we're willing to
6225 relay: it leaks how much non-relay traffic we're using. Resolves
6227 - When looking for a circuit to cannibalize, consider family as well
6228 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
6229 circuit cannibalization).
6231 o Code simplifications and refactoring:
6232 - Make a bunch of functions static. Remove some dead code.
6233 - Pull out about a third of the really big routerlist.c; put it in a
6234 new module, networkstatus.c.
6235 - Merge the extra fields in local_routerstatus_t back into
6236 routerstatus_t: we used to need one routerstatus_t for each
6237 authority's opinion, plus a local_routerstatus_t for the locally
6238 computed consensus opinion. To save space, we put the locally
6239 modified fields into local_routerstatus_t, and only the common
6240 stuff into routerstatus_t. But once v3 directories are in use,
6241 clients and caches will no longer need to hold authority opinions;
6242 thus, the rationale for keeping the types separate is now gone.
6243 - Make the code used to reschedule and reattempt downloads more
6245 - Turn all 'Are we a directory server/mirror?' logic into a call to
6247 - Remove the code to generate the oldest (v1) directory format.
6248 The code has been disabled since 0.2.0.5-alpha.
6251 Changes in version 0.2.0.7-alpha - 2007-09-21
6252 This seventh development snapshot makes bridges work again, makes bridge
6253 authorities work for the first time, fixes two huge performance flaws
6254 in hidden services, and fixes a variety of minor issues.
6256 o New directory authorities:
6257 - Set up moria1 and tor26 as the first v3 directory authorities. See
6258 doc/spec/dir-spec.txt for details on the new directory design.
6260 o Major bugfixes (crashes):
6261 - Fix possible segfaults in functions called from
6262 rend_process_relay_cell(). Bugfix on 0.1.2.x.
6264 o Major bugfixes (bridges):
6265 - Fix a bug that made servers send a "404 Not found" in response to
6266 attempts to fetch their server descriptor. This caused Tor servers
6267 to take many minutes to establish reachability for their DirPort,
6268 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
6269 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
6270 users configure that and specify a bridge with an identity
6271 fingerprint, now they will lookup the bridge descriptor at the
6272 default bridge authority via a one-hop tunnel, but once circuits
6273 are established they will switch to a three-hop tunnel for later
6274 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
6276 o Major bugfixes (hidden services):
6277 - Hidden services were choosing introduction points uniquely by
6278 hexdigest, but when constructing the hidden service descriptor
6279 they merely wrote the (potentially ambiguous) nickname.
6280 - Clients now use the v2 intro format for hidden service
6281 connections: they specify their chosen rendezvous point by identity
6282 digest rather than by (potentially ambiguous) nickname. Both
6283 are bugfixes on 0.1.2.x, and they could speed up hidden service
6284 connections dramatically. Thanks to Karsten Loesing.
6286 o Minor features (security):
6287 - As a client, do not believe any server that tells us that an
6288 address maps to an internal address space.
6289 - Make it possible to enable HashedControlPassword and
6290 CookieAuthentication at the same time.
6292 o Minor features (guard nodes):
6293 - Tag every guard node in our state file with the version that
6294 we believe added it, or with our own version if we add it. This way,
6295 if a user temporarily runs an old version of Tor and then switches
6296 back to a new one, she doesn't automatically lose her guards.
6298 o Minor features (speed):
6299 - When implementing AES counter mode, update only the portions of the
6300 counter buffer that need to change, and don't keep separate
6301 network-order and host-order counters when they are the same (i.e.,
6302 on big-endian hosts.)
6304 o Minor features (controller):
6305 - Accept LF instead of CRLF on controller, since some software has a
6306 hard time generating real Internet newlines.
6307 - Add GETINFO values for the server status events
6308 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
6312 - Routers no longer include bandwidth-history lines in their
6313 descriptors; this information is already available in extra-info
6314 documents, and including it in router descriptors took up 60%
6315 (!) of compressed router descriptor downloads. Completes
6316 implementation of proposal 104.
6317 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
6318 and TorControl.py, as they use the old v0 controller protocol,
6319 and are obsoleted by TorFlow anyway.
6320 - Drop support for v1 rendezvous descriptors, since we never used
6321 them anyway, and the code has probably rotted by now. Based on
6322 patch from Karsten Loesing.
6323 - On OSX, stop warning the user that kqueue support in libevent is
6324 "experimental", since it seems to have worked fine for ages.
6327 - When generating information telling us how to extend to a given
6328 router, do not try to include the nickname if it is absent. Fixes
6329 bug 467. Bugfix on 0.2.0.3-alpha.
6330 - Fix a user-triggerable (but not remotely-triggerable) segfault
6331 in expand_filename(). Bugfix on 0.1.2.x.
6332 - Fix a memory leak when freeing incomplete requests from DNSPort.
6333 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
6334 - Don't try to access (or alter) the state file when running
6335 --list-fingerprint or --verify-config or --hash-password. (Resolves
6336 bug 499.) Bugfix on 0.1.2.x.
6337 - Servers used to decline to publish their DirPort if their
6338 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
6339 were below a threshold. Now they only look at BandwidthRate and
6340 RelayBandwidthRate. Bugfix on 0.1.2.x.
6341 - Remove an optimization in the AES counter-mode code that assumed
6342 that the counter never exceeded 2^68. When the counter can be set
6343 arbitrarily as an IV (as it is by Karsten's new hidden services
6344 code), this assumption no longer holds. Bugfix on 0.1.2.x.
6345 - Resume listing "AUTHORITY" flag for authorities in network status.
6346 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
6348 o Code simplifications and refactoring:
6349 - Revamp file-writing logic so we don't need to have the entire
6350 contents of a file in memory at once before we write to disk. Tor,
6352 - Turn "descriptor store" into a full-fledged type.
6353 - Move all NT services code into a separate source file.
6354 - Unify all code that computes medians, percentile elements, etc.
6355 - Get rid of a needless malloc when parsing address policies.
6358 Changes in version 0.1.2.17 - 2007-08-30
6359 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
6360 X bundles. Vidalia 0.0.14 makes authentication required for the
6361 ControlPort in the default configuration, which addresses important
6362 security risks. Everybody who uses Vidalia (or another controller)
6365 In addition, this Tor update fixes major load balancing problems with
6366 path selection, which should speed things up a lot once many people
6369 o Major bugfixes (security):
6370 - We removed support for the old (v0) control protocol. It has been
6371 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
6372 become more of a headache than it's worth.
6374 o Major bugfixes (load balancing):
6375 - When choosing nodes for non-guard positions, weight guards
6376 proportionally less, since they already have enough load. Patch
6378 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6379 will allow fast Tor servers to get more attention.
6380 - When we're upgrading from an old Tor version, forget our current
6381 guards and pick new ones according to the new weightings. These
6382 three load balancing patches could raise effective network capacity
6383 by a factor of four. Thanks to Mike Perry for measurements.
6385 o Major bugfixes (stream expiration):
6386 - Expire not-yet-successful application streams in all cases if
6387 they've been around longer than SocksTimeout. Right now there are
6388 some cases where the stream will live forever, demanding a new
6389 circuit every 15 seconds. Fixes bug 454; reported by lodger.
6391 o Minor features (controller):
6392 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6393 is valid before any authentication has been received. It tells
6394 a controller what kind of authentication is expected, and what
6395 protocol is spoken. Implements proposal 119.
6397 o Minor bugfixes (performance):
6398 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
6399 greatly speeding up loading cached-routers from disk on startup.
6400 - Disable sentinel-based debugging for buffer code: we squashed all
6401 the bugs that this was supposed to detect a long time ago, and now
6402 its only effect is to change our buffer sizes from nice powers of
6403 two (which platform mallocs tend to like) to values slightly over
6404 powers of two (which make some platform mallocs sad).
6406 o Minor bugfixes (misc):
6407 - If exit bandwidth ever exceeds one third of total bandwidth, then
6408 use the correct formula to weight exit nodes when choosing paths.
6409 Based on patch from Mike Perry.
6410 - Choose perfectly fairly among routers when choosing by bandwidth and
6411 weighting by fraction of bandwidth provided by exits. Previously, we
6412 would choose with only approximate fairness, and correct ourselves
6413 if we ran off the end of the list.
6414 - If we require CookieAuthentication but we fail to write the
6415 cookie file, we would warn but not exit, and end up in a state
6416 where no controller could authenticate. Now we exit.
6417 - If we require CookieAuthentication, stop generating a new cookie
6418 every time we change any piece of our config.
6419 - Refuse to start with certain directory authority keys, and
6420 encourage people using them to stop.
6421 - Terminate multi-line control events properly. Original patch
6423 - Fix a minor memory leak when we fail to find enough suitable
6424 servers to choose a circuit.
6425 - Stop leaking part of the descriptor when we run into a particularly
6426 unparseable piece of it.
6429 Changes in version 0.2.0.6-alpha - 2007-08-26
6430 This sixth development snapshot features a new Vidalia version in the
6431 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
6432 the ControlPort in the default configuration, which addresses important
6435 In addition, this snapshot fixes major load balancing problems
6436 with path selection, which should speed things up a lot once many
6437 people have upgraded. The directory authorities also use a new
6438 mean-time-between-failure approach to tracking which servers are stable,
6439 rather than just looking at the most recent uptime.
6441 o New directory authorities:
6442 - Set up Tonga as the default bridge directory authority.
6445 - Directory authorities now track servers by weighted
6446 mean-times-between-failures. When we have 4 or more days of data,
6447 use measured MTBF rather than declared uptime to decide whether
6448 to call a router Stable. Implements proposal 108.
6450 o Major bugfixes (load balancing):
6451 - When choosing nodes for non-guard positions, weight guards
6452 proportionally less, since they already have enough load. Patch
6454 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6455 will allow fast Tor servers to get more attention.
6456 - When we're upgrading from an old Tor version, forget our current
6457 guards and pick new ones according to the new weightings. These
6458 three load balancing patches could raise effective network capacity
6459 by a factor of four. Thanks to Mike Perry for measurements.
6461 o Major bugfixes (descriptor parsing):
6462 - Handle unexpected whitespace better in malformed descriptors. Bug
6463 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
6466 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
6467 GETINFO for Torstat to use until it can switch to using extrainfos.
6468 - Optionally (if built with -DEXPORTMALLINFO) export the output
6469 of mallinfo via http, as tor/mallinfo.txt. Only accessible
6473 - Do not intermix bridge routers with controller-added
6474 routers. (Bugfix on 0.2.0.x)
6475 - Do not fail with an assert when accept() returns an unexpected
6476 address family. Addresses but does not wholly fix bug 483. (Bugfix
6478 - Let directory authorities startup even when they can't generate
6479 a descriptor immediately, e.g. because they don't know their
6481 - Stop putting the authentication cookie in a file called "0"
6482 in your working directory if you don't specify anything for the
6483 new CookieAuthFile option. Reported by Matt Edman.
6484 - Make it possible to read the PROTOCOLINFO response in a way that
6485 conforms to our control-spec. Reported by Matt Edman.
6486 - Fix a minor memory leak when we fail to find enough suitable
6487 servers to choose a circuit. Bugfix on 0.1.2.x.
6488 - Stop leaking part of the descriptor when we run into a particularly
6489 unparseable piece of it. Bugfix on 0.1.2.x.
6490 - Unmap the extrainfo cache file on exit.
6493 Changes in version 0.2.0.5-alpha - 2007-08-19
6494 This fifth development snapshot fixes compilation on Windows again;
6495 fixes an obnoxious client-side bug that slowed things down and put
6496 extra load on the network; gets us closer to using the v3 directory
6497 voting scheme; makes it easier for Tor controllers to use cookie-based
6498 authentication; and fixes a variety of other bugs.
6501 - Version 1 directories are no longer generated in full. Instead,
6502 authorities generate and serve "stub" v1 directories that list
6503 no servers. This will stop Tor versions 0.1.0.x and earlier from
6504 working, but (for security reasons) nobody should be running those
6507 o Major bugfixes (compilation, 0.2.0.x):
6508 - Try to fix Win32 compilation again: improve checking for IPv6 types.
6509 - Try to fix MSVC compilation: build correctly on platforms that do
6510 not define s6_addr16 or s6_addr32.
6511 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
6514 o Major bugfixes (stream expiration):
6515 - Expire not-yet-successful application streams in all cases if
6516 they've been around longer than SocksTimeout. Right now there are
6517 some cases where the stream will live forever, demanding a new
6518 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
6521 o Minor features (directory servers):
6522 - When somebody requests a list of statuses or servers, and we have
6523 none of those, return a 404 rather than an empty 200.
6525 o Minor features (directory voting):
6526 - Store v3 consensus status consensuses on disk, and reload them
6529 o Minor features (security):
6530 - Warn about unsafe ControlPort configurations.
6531 - Refuse to start with certain directory authority keys, and
6532 encourage people using them to stop.
6534 o Minor features (controller):
6535 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6536 is valid before any authentication has been received. It tells
6537 a controller what kind of authentication is expected, and what
6538 protocol is spoken. Implements proposal 119.
6539 - New config option CookieAuthFile to choose a new location for the
6540 cookie authentication file, and config option
6541 CookieAuthFileGroupReadable to make it group-readable.
6543 o Minor features (unit testing):
6544 - Add command-line arguments to unit-test executable so that we can
6545 invoke any chosen test from the command line rather than having
6546 to run the whole test suite at once; and so that we can turn on
6547 logging for the unit tests.
6549 o Minor bugfixes (on 0.1.2.x):
6550 - If we require CookieAuthentication but we fail to write the
6551 cookie file, we would warn but not exit, and end up in a state
6552 where no controller could authenticate. Now we exit.
6553 - If we require CookieAuthentication, stop generating a new cookie
6554 every time we change any piece of our config.
6555 - When loading bandwidth history, do not believe any information in
6556 the future. Fixes bug 434.
6557 - When loading entry guard information, do not believe any information
6559 - When we have our clock set far in the future and generate an
6560 onion key, then re-set our clock to be correct, we should not stop
6561 the onion key from getting rotated.
6562 - Clean up torrc sample config file.
6563 - Do not automatically run configure from autogen.sh. This
6564 non-standard behavior tended to annoy people who have built other
6567 o Minor bugfixes (on 0.2.0.x):
6568 - Fix a bug with AutomapHostsOnResolve that would always cause
6569 the second request to fail. Bug reported by Kate. Bugfix on
6571 - Fix a bug in ADDRMAP controller replies that would sometimes
6572 try to print a NULL. Patch from tup.
6573 - Read v3 directory authority keys from the right location.
6574 - Numerous bugfixes to directory voting code.
6577 Changes in version 0.1.2.16 - 2007-08-01
6578 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
6579 remote attacker in certain situations to rewrite the user's torrc
6580 configuration file. This can completely compromise anonymity of users
6581 in most configurations, including those running the Vidalia bundles,
6582 TorK, etc. Or worse.
6584 o Major security fixes:
6585 - Close immediately after missing authentication on control port;
6586 do not allow multiple authentication attempts.
6589 Changes in version 0.2.0.4-alpha - 2007-08-01
6590 This fourth development snapshot fixes a critical security vulnerability
6591 for most users, specifically those running Vidalia, TorK, etc. Everybody
6592 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
6594 o Major security fixes:
6595 - Close immediately after missing authentication on control port;
6596 do not allow multiple authentication attempts.
6598 o Major bugfixes (compilation):
6599 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
6602 o Minor features (performance):
6603 - Be even more aggressive about releasing RAM from small
6604 empty buffers. Thanks to our free-list code, this shouldn't be too
6605 performance-intensive.
6606 - Disable sentinel-based debugging for buffer code: we squashed all
6607 the bugs that this was supposed to detect a long time ago, and
6608 now its only effect is to change our buffer sizes from nice
6609 powers of two (which platform mallocs tend to like) to values
6610 slightly over powers of two (which make some platform mallocs sad).
6611 - Log malloc statistics from mallinfo() on platforms where it
6615 Changes in version 0.2.0.3-alpha - 2007-07-29
6616 This third development snapshot introduces new experimental
6617 blocking-resistance features and a preliminary version of the v3
6618 directory voting design, and includes many other smaller features
6622 - The first pieces of our "bridge" design for blocking-resistance
6623 are implemented. People can run bridge directory authorities;
6624 people can run bridges; and people can configure their Tor clients
6625 with a set of bridges to use as the first hop into the Tor network.
6626 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
6628 - Create listener connections before we setuid to the configured
6629 User and Group. Now non-Windows users can choose port values
6630 under 1024, start Tor as root, and have Tor bind those ports
6631 before it changes to another UID. (Windows users could already
6633 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
6634 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
6635 on "vserver" accounts. (Patch from coderman.)
6636 - Be even more aggressive about separating local traffic from relayed
6637 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
6639 o Major features (experimental):
6640 - First cut of code for "v3 dir voting": directory authorities will
6641 vote on a common network status document rather than each publishing
6642 their own opinion. This code needs more testing and more corner-case
6643 handling before it's ready for use.
6646 - Directory authorities now call routers Fast if their bandwidth is
6647 at least 100KB/s, and consider their bandwidth adequate to be a
6648 Guard if it is at least 250KB/s, no matter the medians. This fix
6649 complements proposal 107. [Bugfix on 0.1.2.x]
6650 - Directory authorities now never mark more than 3 servers per IP as
6651 Valid and Running. (Implements proposal 109, by Kevin Bauer and
6653 - Minor change to organizationName and commonName generation
6654 procedures in TLS certificates during Tor handshakes, to invalidate
6655 some earlier censorware approaches. This is not a long-term
6656 solution, but applying it will give us a bit of time to look into
6657 the epidemiology of countermeasures as they spread.
6659 o Major bugfixes (directory):
6660 - Rewrite directory tokenization code to never run off the end of
6661 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
6663 o Minor features (controller):
6664 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
6665 match requests to applications. (Patch from Robert Hogan.)
6666 - Report address and port correctly on connections to DNSPort. (Patch
6668 - Add a RESOLVE command to launch hostname lookups. (Original patch
6670 - Add GETINFO status/enough-dir-info to let controllers tell whether
6671 Tor has downloaded sufficient directory information. (Patch
6673 - You can now use the ControlSocket option to tell Tor to listen for
6674 controller connections on Unix domain sockets on systems that
6675 support them. (Patch from Peter Palfrader.)
6676 - STREAM NEW events are generated for DNSPort requests and for
6677 tunneled directory connections. (Patch from Robert Hogan.)
6678 - New "GETINFO address-mappings/*" command to get address mappings
6679 with expiry information. "addr-mappings/*" is now deprecated.
6682 o Minor features (misc):
6683 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
6685 - The tor-gencert tool for v3 directory authorities now creates all
6686 files as readable to the file creator only, and write-protects
6687 the authority identity key.
6688 - When dumping memory usage, list bytes used in buffer memory
6690 - When running with dmalloc, dump more stats on hup and on exit.
6691 - Directory authorities now fail quickly and (relatively) harmlessly
6692 if they generate a network status document that is somehow
6695 o Traffic load balancing improvements:
6696 - If exit bandwidth ever exceeds one third of total bandwidth, then
6697 use the correct formula to weight exit nodes when choosing paths.
6698 (Based on patch from Mike Perry.)
6699 - Choose perfectly fairly among routers when choosing by bandwidth and
6700 weighting by fraction of bandwidth provided by exits. Previously, we
6701 would choose with only approximate fairness, and correct ourselves
6702 if we ran off the end of the list. [Bugfix on 0.1.2.x]
6704 o Performance improvements:
6705 - Be more aggressive with freeing buffer RAM or putting it on the
6707 - Use Critical Sections rather than Mutexes for synchronizing threads
6708 on win32; Mutexes are heavier-weight, and designed for synchronizing
6711 o Deprecated and removed features:
6712 - RedirectExits is now deprecated.
6713 - Stop allowing address masks that do not correspond to bit prefixes.
6714 We have warned about these for a really long time; now it's time
6715 to reject them. (Patch from croup.)
6717 o Minor bugfixes (directory):
6718 - Fix another crash bug related to extra-info caching. (Bug found by
6719 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
6720 - Directories no longer return a "304 not modified" when they don't
6721 have the networkstatus the client asked for. Also fix a memory
6722 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
6723 - We had accidentally labelled 0.1.2.x directory servers as not
6724 suitable for begin_dir requests, and had labelled no directory
6725 servers as suitable for uploading extra-info documents. [Bugfix
6728 o Minor bugfixes (dns):
6729 - Fix a crash when DNSPort is set more than once. (Patch from Robert
6730 Hogan.) [Bugfix on 0.2.0.2-alpha]
6731 - Add DNSPort connections to the global connection list, so that we
6732 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
6734 - Fix a dangling reference that could lead to a crash when DNSPort is
6735 changed or closed (Patch from Robert Hogan.) [Bugfix on
6738 o Minor bugfixes (controller):
6739 - Provide DNS expiry times in GMT, not in local time. For backward
6740 compatibility, ADDRMAP events only provide GMT expiry in an extended
6741 field. "GETINFO address-mappings" always does the right thing.
6742 - Use CRLF line endings properly in NS events.
6743 - Terminate multi-line control events properly. (Original patch
6744 from tup.) [Bugfix on 0.1.2.x-alpha]
6745 - Do not include spaces in SOURCE_ADDR fields in STREAM
6746 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
6749 Changes in version 0.1.2.15 - 2007-07-17
6750 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
6751 problems, fixes compilation on BSD, and fixes a variety of other
6752 bugs. Everybody should upgrade.
6754 o Major bugfixes (compilation):
6755 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
6757 o Major bugfixes (crashes):
6758 - Try even harder not to dereference the first character after
6759 an mmap(). Reported by lodger.
6760 - Fix a crash bug in directory authorities when we re-number the
6761 routerlist while inserting a new router.
6762 - When the cached-routers file is an even multiple of the page size,
6763 don't run off the end and crash. (Fixes bug 455; based on idea
6765 - Fix eventdns.c behavior on Solaris: It is critical to include
6766 orconfig.h _before_ sys/types.h, so that we can get the expected
6767 definition of _FILE_OFFSET_BITS.
6769 o Major bugfixes (security):
6770 - Fix a possible buffer overrun when using BSD natd support. Bug
6772 - When sending destroy cells from a circuit's origin, don't include
6773 the reason for tearing down the circuit. The spec says we didn't,
6774 and now we actually don't. Reported by lodger.
6775 - Keep streamids from different exits on a circuit separate. This
6776 bug may have allowed other routers on a given circuit to inject
6777 cells into streams. Reported by lodger; fixes bug 446.
6778 - If there's a never-before-connected-to guard node in our list,
6779 never choose any guards past it. This way we don't expand our
6780 guard list unless we need to.
6782 o Minor bugfixes (guard nodes):
6783 - Weight guard selection by bandwidth, so that low-bandwidth nodes
6784 don't get overused as guards.
6786 o Minor bugfixes (directory):
6787 - Correctly count the number of authorities that recommend each
6788 version. Previously, we were under-counting by 1.
6789 - Fix a potential crash bug when we load many server descriptors at
6790 once and some of them make others of them obsolete. Fixes bug 458.
6792 o Minor bugfixes (hidden services):
6793 - Stop tearing down the whole circuit when the user asks for a
6794 connection to a port that the hidden service didn't configure.
6797 o Minor bugfixes (misc):
6798 - On Windows, we were preventing other processes from reading
6799 cached-routers while Tor was running. Reported by janbar.
6800 - Fix a possible (but very unlikely) bug in picking routers by
6801 bandwidth. Add a log message to confirm that it is in fact
6802 unlikely. Patch from lodger.
6803 - Backport a couple of memory leak fixes.
6804 - Backport miscellaneous cosmetic bugfixes.
6807 Changes in version 0.2.0.2-alpha - 2007-06-02
6808 o Major bugfixes on 0.2.0.1-alpha:
6809 - Fix an assertion failure related to servers without extra-info digests.
6810 Resolves bugs 441 and 442.
6812 o Minor features (directory):
6813 - Support "If-Modified-Since" when answering HTTP requests for
6814 directories, running-routers documents, and network-status documents.
6815 (There's no need to support it for router descriptors, since those
6816 are downloaded by descriptor digest.)
6818 o Minor build issues:
6819 - Clear up some MIPSPro compiler warnings.
6820 - When building from a tarball on a machine that happens to have SVK
6821 installed, report the micro-revision as whatever version existed
6822 in the tarball, not as "x".
6825 Changes in version 0.2.0.1-alpha - 2007-06-01
6826 This early development snapshot provides new features for people running
6827 Tor as both a client and a server (check out the new RelayBandwidth
6828 config options); lets Tor run as a DNS proxy; and generally moves us
6829 forward on a lot of fronts.
6831 o Major features, server usability:
6832 - New config options RelayBandwidthRate and RelayBandwidthBurst:
6833 a separate set of token buckets for relayed traffic. Right now
6834 relayed traffic is defined as answers to directory requests, and
6835 OR connections that don't have any local circuits on them.
6837 o Major features, client usability:
6838 - A client-side DNS proxy feature to replace the need for
6839 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
6840 for DNS requests on port 9999, use the Tor network to resolve them
6841 anonymously, and send the reply back like a regular DNS server.
6842 The code still only implements a subset of DNS.
6843 - Make PreferTunneledDirConns and TunnelDirConns work even when
6844 we have no cached directory info. This means Tor clients can now
6845 do all of their connections protected by TLS.
6847 o Major features, performance and efficiency:
6848 - Directory authorities accept and serve "extra info" documents for
6849 routers. These documents contain fields from router descriptors
6850 that aren't usually needed, and that use a lot of excess
6851 bandwidth. Once these fields are removed from router descriptors,
6852 the bandwidth savings should be about 60%. [Partially implements
6854 - Servers upload extra-info documents to any authority that accepts
6855 them. Authorities (and caches that have been configured to download
6856 extra-info documents) download them as needed. [Partially implements
6858 - Change the way that Tor buffers data that it is waiting to write.
6859 Instead of queueing data cells in an enormous ring buffer for each
6860 client->OR or OR->OR connection, we now queue cells on a separate
6861 queue for each circuit. This lets us use less slack memory, and
6862 will eventually let us be smarter about prioritizing different kinds
6864 - Use memory pools to allocate cells with better speed and memory
6865 efficiency, especially on platforms where malloc() is inefficient.
6866 - Stop reading on edge connections when their corresponding circuit
6867 buffers are full; start again as the circuits empty out.
6869 o Major features, other:
6870 - Add an HSAuthorityRecordStats option that hidden service authorities
6871 can use to track statistics of overall hidden service usage without
6872 logging information that would be very useful to an attacker.
6873 - Start work implementing multi-level keys for directory authorities:
6874 Add a standalone tool to generate key certificates. (Proposal 103.)
6877 - Directory authorities now call routers Stable if they have an
6878 uptime of at least 30 days, even if that's not the median uptime
6879 in the network. Implements proposal 107, suggested by Kevin Bauer
6882 o Minor fixes (resource management):
6883 - Count the number of open sockets separately from the number
6884 of active connection_t objects. This will let us avoid underusing
6885 our allocated connection limit.
6886 - We no longer use socket pairs to link an edge connection to an
6887 anonymous directory connection or a DirPort test connection.
6888 Instead, we track the link internally and transfer the data
6889 in-process. This saves two sockets per "linked" connection (at the
6890 client and at the server), and avoids the nasty Windows socketpair()
6892 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
6893 for every single inactive connection_t. Free items from the
6894 4k/16k-buffer free lists when they haven't been used for a while.
6896 o Minor features (build):
6897 - Make autoconf search for libevent, openssl, and zlib consistently.
6898 - Update deprecated macros in configure.in.
6899 - When warning about missing headers, tell the user to let us
6900 know if the compile succeeds anyway, so we can downgrade the
6902 - Include the current subversion revision as part of the version
6903 string: either fetch it directly if we're in an SVN checkout, do
6904 some magic to guess it if we're in an SVK checkout, or use
6905 the last-detected version if we're building from a .tar.gz.
6906 Use this version consistently in log messages.
6908 o Minor features (logging):
6909 - Always prepend "Bug: " to any log message about a bug.
6910 - Put a platform string (e.g. "Linux i686") in the startup log
6911 message, so when people paste just their logs, we know if it's
6912 OpenBSD or Windows or what.
6913 - When logging memory usage, break down memory used in buffers by
6916 o Minor features (directory system):
6917 - New config option V2AuthoritativeDirectory that all directory
6918 authorities should set. This will let future authorities choose
6919 not to serve V2 directory information.
6920 - Directory authorities allow multiple router descriptors and/or extra
6921 info documents to be uploaded in a single go. This will make
6922 implementing proposal 104 simpler.
6924 o Minor features (controller):
6925 - Add a new config option __DisablePredictedCircuits designed for
6926 use by the controller, when we don't want Tor to build any circuits
6928 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
6929 so we can exit from the middle of the circuit.
6930 - Implement "getinfo status/circuit-established".
6931 - Implement "getinfo status/version/..." so a controller can tell
6932 whether the current version is recommended, and whether any versions
6933 are good, and how many authorities agree. (Patch from shibz.)
6935 o Minor features (hidden services):
6936 - Allow multiple HiddenServicePort directives with the same virtual
6937 port; when they occur, the user is sent round-robin to one
6938 of the target ports chosen at random. Partially fixes bug 393 by
6939 adding limited ad-hoc round-robining.
6941 o Minor features (other):
6943 - Add a new AutomapHostsOnResolve option: when it is enabled, any
6944 resolve request for hosts matching a given pattern causes Tor to
6945 generate an internal virtual address mapping for that host. This
6946 allows DNSPort to work sensibly with hidden service users. By
6947 default, .exit and .onion addresses are remapped; the list of
6948 patterns can be reconfigured with AutomapHostsSuffixes.
6949 - Add an "-F" option to tor-resolve to force a resolve for a .onion
6950 address. Thanks to the AutomapHostsOnResolve option, this is no
6951 longer a completely silly thing to do.
6952 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
6953 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
6954 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
6955 minus 1 byte: the actual maximum declared bandwidth.
6958 - Removed support for the old binary "version 0" controller protocol.
6959 This has been deprecated since 0.1.1, and warnings have been issued
6960 since 0.1.2. When we encounter a v0 control message, we now send
6961 back an error and close the connection.
6962 - Remove the old "dns worker" server DNS code: it hasn't been default
6963 since 0.1.2.2-alpha, and all the servers seem to be using the new
6966 o Minor bugfixes (portability):
6967 - Even though Windows is equally happy with / and \ as path separators,
6968 try to use \ consistently on Windows and / consistently on Unix: it
6969 makes the log messages nicer.
6970 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
6971 - Read resolv.conf files correctly on platforms where read() returns
6972 partial results on small file reads.
6974 o Minor bugfixes (directory):
6975 - Correctly enforce that elements of directory objects do not appear
6976 more often than they are allowed to appear.
6977 - When we are reporting the DirServer line we just parsed, we were
6978 logging the second stanza of the key fingerprint, not the first.
6980 o Minor bugfixes (logging):
6981 - When we hit an EOF on a log (probably because we're shutting down),
6982 don't try to remove the log from the list: just mark it as
6983 unusable. (Bulletproofs against bug 222.)
6985 o Minor bugfixes (other):
6986 - In the exitlist script, only consider the most recently published
6987 server descriptor for each server. Also, when the user requests
6988 a list of servers that _reject_ connections to a given address,
6989 explicitly exclude the IPs that also have servers that accept
6990 connections to that address. (Resolves bug 405.)
6991 - Stop allowing hibernating servers to be "stable" or "fast".
6992 - On Windows, we were preventing other processes from reading
6993 cached-routers while Tor was running. (Reported by janbar)
6994 - Make the NodeFamilies config option work. (Reported by
6995 lodger -- it has never actually worked, even though we added it
6997 - Check return values from pthread_mutex functions.
6998 - Don't save non-general-purpose router descriptors to the disk cache,
6999 because we have no way of remembering what their purpose was when
7001 - Add even more asserts to hunt down bug 417.
7002 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
7003 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
7004 Add a log message to confirm that it is in fact unlikely.
7006 o Minor bugfixes (controller):
7007 - Make 'getinfo fingerprint' return a 551 error if we're not a
7008 server, so we match what the control spec claims we do. Reported
7010 - Fix a typo in an error message when extendcircuit fails that
7011 caused us to not follow the \r\n-based delimiter protocol. Reported
7014 o Code simplifications and refactoring:
7015 - Stop passing around circuit_t and crypt_path_t pointers that are
7016 implicit in other procedure arguments.
7017 - Drop the old code to choke directory connections when the
7018 corresponding OR connections got full: thanks to the cell queue
7019 feature, OR conns don't get full any more.
7020 - Make dns_resolve() handle attaching connections to circuits
7021 properly, so the caller doesn't have to.
7022 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
7023 - Keep the connection array as a dynamic smartlist_t, rather than as
7024 a fixed-sized array. This is important, as the number of connections
7025 is becoming increasingly decoupled from the number of sockets.
7028 Changes in version 0.1.2.14 - 2007-05-25
7029 Tor 0.1.2.14 changes the addresses of two directory authorities (this
7030 change especially affects those who serve or use hidden services),
7031 and fixes several other crash- and security-related bugs.
7033 o Directory authority changes:
7034 - Two directory authorities (moria1 and moria2) just moved to new
7035 IP addresses. This change will particularly affect those who serve
7036 or use hidden services.
7038 o Major bugfixes (crashes):
7039 - If a directory server runs out of space in the connection table
7040 as it's processing a begin_dir request, it will free the exit stream
7041 but leave it attached to the circuit, leading to unpredictable
7042 behavior. (Reported by seeess, fixes bug 425.)
7043 - Fix a bug in dirserv_remove_invalid() that would cause authorities
7044 to corrupt memory under some really unlikely scenarios.
7045 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
7046 - Avoid segfaults when reading from mmaped descriptor file. (Reported
7049 o Major bugfixes (security):
7050 - When choosing an entry guard for a circuit, avoid using guards
7051 that are in the same family as the chosen exit -- not just guards
7052 that are exactly the chosen exit. (Reported by lodger.)
7054 o Major bugfixes (resource management):
7055 - If a directory authority is down, skip it when deciding where to get
7056 networkstatus objects or descriptors. Otherwise we keep asking
7057 every 10 seconds forever. Fixes bug 384.
7058 - Count it as a failure if we fetch a valid network-status but we
7059 don't want to keep it. Otherwise we'll keep fetching it and keep
7060 not wanting to keep it. Fixes part of bug 422.
7061 - If all of our dirservers have given us bad or no networkstatuses
7062 lately, then stop hammering them once per minute even when we
7063 think they're failed. Fixes another part of bug 422.
7066 - Actually set the purpose correctly for descriptors inserted with
7068 - When we have k non-v2 authorities in our DirServer config,
7069 we ignored the last k authorities in the list when updating our
7071 - Correctly back-off from requesting router descriptors that we are
7072 having a hard time downloading.
7073 - Read resolv.conf files correctly on platforms where read() returns
7074 partial results on small file reads.
7075 - Don't rebuild the entire router store every time we get 32K of
7076 routers: rebuild it when the journal gets very large, or when
7077 the gaps in the store get very large.
7080 - When routers publish SVN revisions in their router descriptors,
7081 authorities now include those versions correctly in networkstatus
7083 - Warn when using a version of libevent before 1.3b to run a server on
7084 OSX or BSD: these versions interact badly with userspace threads.
7087 Changes in version 0.1.2.13 - 2007-04-24
7088 This release features some major anonymity fixes, such as safer path
7089 selection; better client performance; faster bootstrapping, better
7090 address detection, and better DNS support for servers; write limiting as
7091 well as read limiting to make servers easier to run; and a huge pile of
7092 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
7094 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
7095 of the Freenode IRC network, remembering his patience and vision for
7096 free speech on the Internet.
7099 - Fix a memory leak when we ask for "all" networkstatuses and we
7100 get one we don't recognize.
7101 - Add more asserts to hunt down bug 417.
7102 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
7105 Changes in version 0.1.2.12-rc - 2007-03-16
7107 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
7108 directory information requested inside Tor connections (i.e. via
7109 begin_dir cells). It only triggered when the same connection was
7110 serving other data at the same time. Reported by seeess.
7113 - When creating a circuit via the controller, send a 'launched'
7114 event when we're done, so we follow the spec better.
7117 Changes in version 0.1.2.11-rc - 2007-03-15
7118 o Minor bugfixes (controller), reported by daejees:
7119 - Correct the control spec to match how the code actually responds
7120 to 'getinfo addr-mappings/*'.
7121 - The control spec described a GUARDS event, but the code
7122 implemented a GUARD event. Standardize on GUARD, but let people
7126 Changes in version 0.1.2.10-rc - 2007-03-07
7127 o Major bugfixes (Windows):
7128 - Do not load the NT services library functions (which may not exist)
7129 just to detect if we're a service trying to shut down. Now we run
7130 on Win98 and friends again.
7132 o Minor bugfixes (other):
7133 - Clarify a couple of log messages.
7134 - Fix a misleading socks5 error number.
7137 Changes in version 0.1.2.9-rc - 2007-03-02
7138 o Major bugfixes (Windows):
7139 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
7140 of the usual GCC "%llu". This prevents a bug when saving 64-bit
7141 int configuration values: the high-order 32 bits would get
7142 truncated. In particular, we were being bitten by the default
7143 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
7144 and maybe also bug 397.)
7146 o Minor bugfixes (performance):
7147 - Use OpenSSL's AES implementation on platforms where it's faster.
7148 This could save us as much as 10% CPU usage.
7150 o Minor bugfixes (server):
7151 - Do not rotate onion key immediately after setting it for the first
7154 o Minor bugfixes (directory authorities):
7155 - Stop calling servers that have been hibernating for a long time
7156 "stable". Also, stop letting hibernating or obsolete servers affect
7157 uptime and bandwidth cutoffs.
7158 - Stop listing hibernating servers in the v1 directory.
7160 o Minor bugfixes (hidden services):
7161 - Upload hidden service descriptors slightly less often, to reduce
7162 load on authorities.
7164 o Minor bugfixes (other):
7165 - Fix an assert that could trigger if a controller quickly set then
7166 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
7167 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
7169 - Fix a potential race condition in the rpm installer. Found by
7171 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
7172 of 2 as indicating that the server is completely bad; it sometimes
7173 means that the server is just bad for the request in question. (may fix
7174 the last of bug 326.)
7175 - Disable encrypted directory connections when we don't have a server
7176 descriptor for the destination. We'll get this working again in
7180 Changes in version 0.1.2.8-beta - 2007-02-26
7181 o Major bugfixes (crashes):
7182 - Stop crashing when the controller asks us to resetconf more than
7183 one config option at once. (Vidalia 0.0.11 does this.)
7184 - Fix a crash that happened on Win98 when we're given command-line
7185 arguments: don't try to load NT service functions from advapi32.dll
7186 except when we need them. (Bug introduced in 0.1.2.7-alpha;
7188 - Fix a longstanding obscure crash bug that could occur when
7189 we run out of DNS worker processes. (Resolves bug 390.)
7191 o Major bugfixes (hidden services):
7192 - Correctly detect whether hidden service descriptor downloads are
7193 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
7195 o Major bugfixes (accounting):
7196 - When we start during an accounting interval before it's time to wake
7197 up, remember to wake up at the correct time. (May fix bug 342.)
7199 o Minor bugfixes (controller):
7200 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
7201 clear the corresponding on_circuit variable, and remember later
7202 that we don't need to send a redundant CLOSED event. (Resolves part
7204 - Report events where a resolve succeeded or where we got a socks
7205 protocol error correctly, rather than calling both of them
7207 - Change reported stream target addresses to IP consistently when
7208 we finally get the IP from an exit node.
7209 - Send log messages to the controller even if they happen to be very
7212 o Minor bugfixes (other):
7213 - Display correct results when reporting which versions are
7214 recommended, and how recommended they are. (Resolves bug 383.)
7215 - Improve our estimates for directory bandwidth to be less random:
7216 guess that an unrecognized directory will have the average bandwidth
7217 from all known directories, not that it will have the average
7218 bandwidth from those directories earlier than it on the list.
7219 - If we start a server with ClientOnly 1, then set ClientOnly to 0
7220 and hup, stop triggering an assert based on an empty onion_key.
7221 - On platforms with no working mmap() equivalent, don't warn the
7222 user when cached-routers doesn't exist.
7223 - Warn the user when mmap() [or its equivalent] fails for some reason
7224 other than file-not-found.
7225 - Don't warn the user when cached-routers.new doesn't exist: that's
7226 perfectly fine when starting up for the first time.
7227 - When EntryNodes are configured, rebuild the guard list to contain,
7228 in order: the EntryNodes that were guards before; the rest of the
7229 EntryNodes; the nodes that were guards before.
7230 - Mask out all signals in sub-threads; only the libevent signal
7231 handler should be processing them. This should prevent some crashes
7232 on some machines using pthreads. (Patch from coderman.)
7233 - Fix switched arguments on memset in the implementation of
7234 tor_munmap() for systems with no mmap() call.
7235 - When Tor receives a router descriptor that it asked for, but
7236 no longer wants (because it has received fresh networkstatuses
7237 in the meantime), do not warn the user. Cache the descriptor if
7238 we're a cache; drop it if we aren't.
7239 - Make earlier entry guards _really_ get retried when the network
7241 - On a malformed DNS reply, always give an error to the corresponding
7243 - Build with recent libevents on platforms that do not define the
7244 nonstandard types "u_int8_t" and friends.
7246 o Minor features (controller):
7247 - Warn the user when an application uses the obsolete binary v0
7248 control protocol. We're planning to remove support for it during
7249 the next development series, so it's good to give people some
7251 - Add STREAM_BW events to report per-entry-stream bandwidth
7252 use. (Patch from Robert Hogan.)
7253 - Rate-limit SIGNEWNYM signals in response to controllers that
7254 impolitely generate them for every single stream. (Patch from
7255 mwenge; closes bug 394.)
7256 - Make REMAP stream events have a SOURCE (cache or exit), and
7257 make them generated in every case where we get a successful
7258 connected or resolved cell.
7260 o Minor bugfixes (performance):
7261 - Call router_have_min_dir_info half as often. (This is showing up in
7262 some profiles, but not others.)
7263 - When using GCC, make log_debug never get called at all, and its
7264 arguments never get evaluated, when no debug logs are configured.
7265 (This is showing up in some profiles, but not others.)
7268 - Remove some never-implemented options. Mark PathlenCoinWeight as
7270 - Implement proposal 106: Stop requiring clients to have well-formed
7271 certificates; stop checking nicknames in certificates. (Clients
7272 have certificates so that they can look like Tor servers, but in
7273 the future we might want to allow them to look like regular TLS
7274 clients instead. Nicknames in certificates serve no purpose other
7275 than making our protocol easier to recognize on the wire.)
7276 - Revise messages on handshake failure again to be even more clear about
7277 which are incoming connections and which are outgoing.
7278 - Discard any v1 directory info that's over 1 month old (for
7279 directories) or over 1 week old (for running-routers lists).
7280 - Do not warn when individual nodes in the configuration's EntryNodes,
7281 ExitNodes, etc are down: warn only when all possible nodes
7282 are down. (Fixes bug 348.)
7283 - Always remove expired routers and networkstatus docs before checking
7284 whether we have enough information to build circuits. (Fixes
7286 - Put a lower-bound on MaxAdvertisedBandwidth.
7289 Changes in version 0.1.2.7-alpha - 2007-02-06
7290 o Major bugfixes (rate limiting):
7291 - Servers decline directory requests much more aggressively when
7292 they're low on bandwidth. Otherwise they end up queueing more and
7293 more directory responses, which can't be good for latency.
7294 - But never refuse directory requests from local addresses.
7295 - Fix a memory leak when sending a 503 response for a networkstatus
7297 - Be willing to read or write on local connections (e.g. controller
7298 connections) even when the global rate limiting buckets are empty.
7299 - If our system clock jumps back in time, don't publish a negative
7300 uptime in the descriptor. Also, don't let the global rate limiting
7301 buckets go absurdly negative.
7302 - Flush local controller connection buffers periodically as we're
7303 writing to them, so we avoid queueing 4+ megabytes of data before
7306 o Major bugfixes (NT services):
7307 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
7308 command-line flag so that admins can override the default by saying
7309 "tor --service install --user "SomeUser"". This will not affect
7310 existing installed services. Also, warn the user that the service
7311 will look for its configuration file in the service user's
7312 %appdata% directory. (We can't do the 'hardwire the user's appdata
7313 directory' trick any more, since we may not have read access to that
7316 o Major bugfixes (other):
7317 - Previously, we would cache up to 16 old networkstatus documents
7318 indefinitely, if they came from nontrusted authorities. Now we
7319 discard them if they are more than 10 days old.
7320 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
7322 - Detect and reject malformed DNS responses containing circular
7324 - If exits are rare enough that we're not marking exits as guards,
7325 ignore exit bandwidth when we're deciding the required bandwidth
7327 - When we're handling a directory connection tunneled over Tor,
7328 don't fill up internal memory buffers with all the data we want
7329 to tunnel; instead, only add it if the OR connection that will
7330 eventually receive it has some room for it. (This can lead to
7331 slowdowns in tunneled dir connections; a better solution will have
7334 o Minor bugfixes (dns):
7335 - Add some defensive programming to eventdns.c in an attempt to catch
7336 possible memory-stomping bugs.
7337 - Detect and reject DNS replies containing IPv4 or IPv6 records with
7338 an incorrect number of bytes. (Previously, we would ignore the
7340 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
7341 in the correct order, and doesn't crash.
7342 - Free memory held in recently-completed DNS lookup attempts on exit.
7343 This was not a memory leak, but may have been hiding memory leaks.
7344 - Handle TTL values correctly on reverse DNS lookups.
7345 - Treat failure to parse resolv.conf as an error.
7347 o Minor bugfixes (other):
7348 - Fix crash with "tor --list-fingerprint" (reported by seeess).
7349 - When computing clock skew from directory HTTP headers, consider what
7350 time it was when we finished asking for the directory, not what
7352 - Expire socks connections if they spend too long waiting for the
7353 handshake to finish. Previously we would let them sit around for
7354 days, if the connecting application didn't close them either.
7355 - And if the socks handshake hasn't started, don't send a
7356 "DNS resolve socks failed" handshake reply; just close it.
7357 - Stop using C functions that OpenBSD's linker doesn't like.
7358 - Don't launch requests for descriptors unless we have networkstatuses
7359 from at least half of the authorities. This delays the first
7360 download slightly under pathological circumstances, but can prevent
7361 us from downloading a bunch of descriptors we don't need.
7362 - Do not log IPs with TLS failures for incoming TLS
7363 connections. (Fixes bug 382.)
7364 - If the user asks to use invalid exit nodes, be willing to use
7366 - Stop using the reserved ac_cv namespace in our configure script.
7367 - Call stat() slightly less often; use fstat() when possible.
7368 - Refactor the way we handle pending circuits when an OR connection
7369 completes or fails, in an attempt to fix a rare crash bug.
7370 - Only rewrite a conn's address based on X-Forwarded-For: headers
7371 if it's a parseable public IP address; and stop adding extra quotes
7372 to the resulting address.
7375 - Weight directory requests by advertised bandwidth. Now we can
7376 let servers enable write limiting but still allow most clients to
7377 succeed at their directory requests. (We still ignore weights when
7378 choosing a directory authority; I hope this is a feature.)
7381 - Create a new file ReleaseNotes which was the old ChangeLog. The
7382 new ChangeLog file now includes the summaries for all development
7384 - Check for addresses with invalid characters at the exit as well
7385 as at the client, and warn less verbosely when they fail. You can
7386 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
7387 - Adapt a patch from goodell to let the contrib/exitlist script
7388 take arguments rather than require direct editing.
7389 - Inform the server operator when we decide not to advertise a
7390 DirPort due to AccountingMax enabled or a low BandwidthRate. It
7391 was confusing Zax, so now we're hopefully more helpful.
7392 - Bring us one step closer to being able to establish an encrypted
7393 directory tunnel without knowing a descriptor first. Still not
7394 ready yet. As part of the change, now assume we can use a
7395 create_fast cell if we don't know anything about a router.
7396 - Allow exit nodes to use nameservers running on ports other than 53.
7397 - Servers now cache reverse DNS replies.
7398 - Add an --ignore-missing-torrc command-line option so that we can
7399 get the "use sensible defaults if the configuration file doesn't
7400 exist" behavior even when specifying a torrc location on the command
7403 o Minor features (controller):
7404 - Track reasons for OR connection failure; make these reasons
7405 available via the controller interface. (Patch from Mike Perry.)
7406 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
7407 can learn when clients are sending malformed hostnames to Tor.
7408 - Clean up documentation for controller status events.
7409 - Add a REMAP status to stream events to note that a stream's
7410 address has changed because of a cached address or a MapAddress
7414 Changes in version 0.1.2.6-alpha - 2007-01-09
7416 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
7417 connection handles more than 4 gigs in either direction, we crash.
7418 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
7419 advertised exit node, somebody might try to exit from us when
7420 we're bootstrapping and before we've built our descriptor yet.
7421 Refuse the connection rather than crashing.
7424 - Warn if we (as a server) find that we've resolved an address that we
7425 weren't planning to resolve.
7426 - Warn that using select() on any libevent version before 1.1 will be
7427 unnecessarily slow (even for select()).
7428 - Flush ERR-level controller status events just like we currently
7429 flush ERR-level log events, so that a Tor shutdown doesn't prevent
7430 the controller from learning about current events.
7432 o Minor features (more controller status events):
7433 - Implement EXTERNAL_ADDRESS server status event so controllers can
7434 learn when our address changes.
7435 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
7436 can learn when directories reject our descriptor.
7437 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
7438 can learn when a client application is speaking a non-socks protocol
7440 - Implement DANGEROUS_SOCKS client status event so controllers
7441 can learn when a client application is leaking DNS addresses.
7442 - Implement BUG general status event so controllers can learn when
7443 Tor is unhappy about its internal invariants.
7444 - Implement CLOCK_SKEW general status event so controllers can learn
7445 when Tor thinks the system clock is set incorrectly.
7446 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
7447 server status events so controllers can learn when their descriptors
7448 are accepted by a directory.
7449 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
7450 server status events so controllers can learn about Tor's progress in
7451 deciding whether it's reachable from the outside.
7452 - Implement BAD_LIBEVENT general status event so controllers can learn
7453 when we have a version/method combination in libevent that needs to
7455 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
7456 and DNS_USELESS server status events so controllers can learn
7457 about changes to DNS server status.
7459 o Minor features (directory):
7460 - Authorities no longer recommend exits as guards if this would shift
7461 too much load to the exit nodes.
7464 Changes in version 0.1.2.5-alpha - 2007-01-06
7466 - Enable write limiting as well as read limiting. Now we sacrifice
7467 capacity if we're pushing out lots of directory traffic, rather
7468 than overrunning the user's intended bandwidth limits.
7469 - Include TLS overhead when counting bandwidth usage; previously, we
7470 would count only the bytes sent over TLS, but not the bytes used
7472 - Support running the Tor service with a torrc not in the same
7473 directory as tor.exe and default to using the torrc located in
7474 the %appdata%\Tor\ of the user who installed the service. Patch
7476 - Servers now check for the case when common DNS requests are going to
7477 wildcarded addresses (i.e. all getting the same answer), and change
7478 their exit policy to reject *:* if it's happening.
7479 - Implement BEGIN_DIR cells, so we can connect to the directory
7480 server via TLS to do encrypted directory requests rather than
7481 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
7482 config options if you like.
7484 o Minor features (config and docs):
7485 - Start using the state file to store bandwidth accounting data:
7486 the bw_accounting file is now obsolete. We'll keep generating it
7487 for a while for people who are still using 0.1.2.4-alpha.
7488 - Try to batch changes to the state file so that we do as few
7489 disk writes as possible while still storing important things in
7491 - The state file and the bw_accounting file get saved less often when
7492 the AvoidDiskWrites config option is set.
7493 - Make PIDFile work on Windows (untested).
7494 - Add internal descriptions for a bunch of configuration options:
7495 accessible via controller interface and in comments in saved
7497 - Reject *:563 (NNTPS) in the default exit policy. We already reject
7498 NNTP by default, so this seems like a sensible addition.
7499 - Clients now reject hostnames with invalid characters. This should
7500 avoid some inadvertent info leaks. Add an option
7501 AllowNonRFC953Hostnames to disable this behavior, in case somebody
7502 is running a private network with hosts called @, !, and #.
7503 - Add a maintainer script to tell us which options are missing
7504 documentation: "make check-docs".
7505 - Add a new address-spec.txt document to describe our special-case
7506 addresses: .exit, .onion, and .noconnnect.
7508 o Minor features (DNS):
7509 - Ongoing work on eventdns infrastructure: now it has dns server
7510 and ipv6 support. One day Tor will make use of it.
7511 - Add client-side caching for reverse DNS lookups.
7512 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
7513 - When we change nameservers or IP addresses, reset and re-launch
7514 our tests for DNS hijacking.
7516 o Minor features (directory):
7517 - Authorities now specify server versions in networkstatus. This adds
7518 about 2% to the size of compressed networkstatus docs, and allows
7519 clients to tell which servers support BEGIN_DIR and which don't.
7520 The implementation is forward-compatible with a proposed future
7521 protocol version scheme not tied to Tor versions.
7522 - DirServer configuration lines now have an orport= option so
7523 clients can open encrypted tunnels to the authorities without
7524 having downloaded their descriptors yet. Enabled for moria1,
7525 moria2, tor26, and lefkada now in the default configuration.
7526 - Directory servers are more willing to send a 503 "busy" if they
7527 are near their write limit, especially for v1 directory requests.
7528 Now they can use their limited bandwidth for actual Tor traffic.
7529 - Clients track responses with status 503 from dirservers. After a
7530 dirserver has given us a 503, we try not to use it until an hour has
7531 gone by, or until we have no dirservers that haven't given us a 503.
7532 - When we get a 503 from a directory, and we're not a server, we don't
7533 count the failure against the total number of failures allowed
7534 for the thing we're trying to download.
7535 - Report X-Your-Address-Is correctly from tunneled directory
7536 connections; don't report X-Your-Address-Is when it's an internal
7537 address; and never believe reported remote addresses when they're
7539 - Protect against an unlikely DoS attack on directory servers.
7540 - Add a BadDirectory flag to network status docs so that authorities
7541 can (eventually) tell clients about caches they believe to be
7544 o Minor features (controller):
7545 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
7546 - Reimplement GETINFO so that info/names stays in sync with the
7548 - Implement "GETINFO fingerprint".
7549 - Implement "SETEVENTS GUARD" so controllers can get updates on
7550 entry guard status as it changes.
7552 o Minor features (clean up obsolete pieces):
7553 - Remove some options that have been deprecated since at least
7554 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
7555 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
7557 - We no longer look for identity and onion keys in "identity.key" and
7558 "onion.key" -- these were replaced by secret_id_key and
7559 secret_onion_key in 0.0.8pre1.
7560 - We no longer require unrecognized directory entries to be
7563 o Major bugfixes (security):
7564 - Stop sending the HttpProxyAuthenticator string to directory
7565 servers when directory connections are tunnelled through Tor.
7566 - Clients no longer store bandwidth history in the state file.
7567 - Do not log introduction points for hidden services if SafeLogging
7569 - When generating bandwidth history, round down to the nearest
7570 1k. When storing accounting data, round up to the nearest 1k.
7571 - When we're running as a server, remember when we last rotated onion
7572 keys, so that we will rotate keys once they're a week old even if
7573 we never stay up for a week ourselves.
7575 o Major bugfixes (other):
7576 - Fix a longstanding bug in eventdns that prevented the count of
7577 timed-out resolves from ever being reset. This bug caused us to
7578 give up on a nameserver the third time it timed out, and try it
7579 10 seconds later... and to give up on it every time it timed out
7581 - Take out the '5 second' timeout from the connection retry
7582 schedule. Now the first connect attempt will wait a full 10
7583 seconds before switching to a new circuit. Perhaps this will help
7584 a lot. Based on observations from Mike Perry.
7585 - Fix a bug on the Windows implementation of tor_mmap_file() that
7586 would prevent the cached-routers file from ever loading. Reported
7590 - Fix an assert failure when a directory authority sets
7591 AuthDirRejectUnlisted and then receives a descriptor from an
7592 unlisted router. Reported by seeess.
7593 - Avoid a double-free when parsing malformed DirServer lines.
7594 - Fix a bug when a BSD-style PF socket is first used. Patch from
7596 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
7597 to resolve an address at a given exit node even when they ask for
7599 - Servers no longer ever list themselves in their "family" line,
7600 even if configured to do so. This makes it easier to configure
7601 family lists conveniently.
7602 - When running as a server, don't fall back to 127.0.0.1 when no
7603 nameservers are configured in /etc/resolv.conf; instead, make the
7604 user fix resolv.conf or specify nameservers explicitly. (Resolves
7606 - Stop accepting certain malformed ports in configured exit policies.
7607 - Don't re-write the fingerprint file every restart, unless it has
7609 - Stop warning when a single nameserver fails: only warn when _all_ of
7610 our nameservers have failed. Also, when we only have one nameserver,
7611 raise the threshold for deciding that the nameserver is dead.
7612 - Directory authorities now only decide that routers are reachable
7613 if their identity keys are as expected.
7614 - When the user uses bad syntax in the Log config line, stop
7615 suggesting other bad syntax as a replacement.
7616 - Correctly detect ipv6 DNS capability on OpenBSD.
7618 o Minor bugfixes (controller):
7619 - Report the circuit number correctly in STREAM CLOSED events. Bug
7620 reported by Mike Perry.
7621 - Do not report bizarre values for results of accounting GETINFOs
7622 when the last second's write or read exceeds the allotted bandwidth.
7623 - Report "unrecognized key" rather than an empty string when the
7624 controller tries to fetch a networkstatus that doesn't exist.
7627 Changes in version 0.1.1.26 - 2006-12-14
7628 o Security bugfixes:
7629 - Stop sending the HttpProxyAuthenticator string to directory
7630 servers when directory connections are tunnelled through Tor.
7631 - Clients no longer store bandwidth history in the state file.
7632 - Do not log introduction points for hidden services if SafeLogging
7636 - Fix an assert failure when a directory authority sets
7637 AuthDirRejectUnlisted and then receives a descriptor from an
7638 unlisted router (reported by seeess).
7641 Changes in version 0.1.2.4-alpha - 2006-12-03
7643 - Add support for using natd; this allows FreeBSDs earlier than
7644 5.1.2 to have ipfw send connections through Tor without using
7645 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
7648 - Make all connections to addresses of the form ".noconnect"
7649 immediately get closed. This lets application/controller combos
7650 successfully test whether they're talking to the same Tor by
7651 watching for STREAM events.
7652 - Make cross.sh cross-compilation script work even when autogen.sh
7653 hasn't been run. (Patch from Michael Mohr.)
7654 - Statistics dumped by -USR2 now include a breakdown of public key
7655 operations, for profiling.
7658 - Fix a major leak when directory authorities parse their
7659 approved-routers list, a minor memory leak when we fail to pick
7660 an exit node, and a few rare leaks on errors.
7661 - Handle TransPort connections even when the server sends data before
7662 the client sends data. Previously, the connection would just hang
7663 until the client sent data. (Patch from tup based on patch from
7665 - Avoid assert failure when our cached-routers file is empty on
7669 - Don't log spurious warnings when we see a circuit close reason we
7670 don't recognize; it's probably just from a newer version of Tor.
7671 - Have directory authorities allow larger amounts of drift in uptime
7672 without replacing the server descriptor: previously, a server that
7673 restarted every 30 minutes could have 48 "interesting" descriptors
7675 - Start linking to the Tor specification and Tor reference manual
7676 correctly in the Windows installer.
7677 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7678 Tor/Privoxy we also uninstall Vidalia.
7679 - Resume building on Irix64, and fix a lot of warnings from its
7681 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
7682 when we're running as a client.
7685 Changes in version 0.1.1.25 - 2006-11-04
7687 - When a client asks us to resolve (rather than connect to)
7688 an address, and we have a cached answer, give them the cached
7689 answer. Previously, we would give them no answer at all.
7690 - We were building exactly the wrong circuits when we predict
7691 hidden service requirements, meaning Tor would have to build all
7692 its circuits on demand.
7693 - If none of our live entry guards have a high uptime, but we
7694 require a guard with a high uptime, try adding a new guard before
7695 we give up on the requirement. This patch should make long-lived
7696 connections more stable on average.
7697 - When testing reachability of our DirPort, don't launch new
7698 tests when there's already one in progress -- unreachable
7699 servers were stacking up dozens of testing streams.
7701 o Security bugfixes:
7702 - When the user sends a NEWNYM signal, clear the client-side DNS
7703 cache too. Otherwise we continue to act on previous information.
7706 - Avoid a memory corruption bug when creating a hash table for
7708 - Avoid possibility of controller-triggered crash when misusing
7709 certain commands from a v0 controller on platforms that do not
7710 handle printf("%s",NULL) gracefully.
7711 - Avoid infinite loop on unexpected controller input.
7712 - Don't log spurious warnings when we see a circuit close reason we
7713 don't recognize; it's probably just from a newer version of Tor.
7714 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7715 Tor/Privoxy we also uninstall Vidalia.
7718 Changes in version 0.1.2.3-alpha - 2006-10-29
7720 - Prepare for servers to publish descriptors less often: never
7721 discard a descriptor simply for being too old until either it is
7722 recommended by no authorities, or until we get a better one for
7723 the same router. Make caches consider retaining old recommended
7724 routers for even longer.
7725 - If most authorities set a BadExit flag for a server, clients
7726 don't think of it as a general-purpose exit. Clients only consider
7727 authorities that advertise themselves as listing bad exits.
7728 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
7729 headers for content, so that we can work better in the presence of
7730 caching HTTP proxies.
7731 - Allow authorities to list nodes as bad exits by fingerprint or by
7734 o Minor features, controller:
7735 - Add a REASON field to CIRC events; for backward compatibility, this
7736 field is sent only to controllers that have enabled the extended
7737 event format. Also, add additional reason codes to explain why
7738 a given circuit has been destroyed or truncated. (Patches from
7740 - Add a REMOTE_REASON field to extended CIRC events to tell the
7741 controller about why a remote OR told us to close a circuit.
7742 - Stream events also now have REASON and REMOTE_REASON fields,
7743 working much like those for circuit events.
7744 - There's now a GETINFO ns/... field so that controllers can ask Tor
7745 about the current status of a router.
7746 - A new event type "NS" to inform a controller when our opinion of
7747 a router's status has changed.
7748 - Add a GETINFO events/names and GETINFO features/names so controllers
7749 can tell which events and features are supported.
7750 - A new CLEARDNSCACHE signal to allow controllers to clear the
7751 client-side DNS cache without expiring circuits.
7753 o Security bugfixes:
7754 - When the user sends a NEWNYM signal, clear the client-side DNS
7755 cache too. Otherwise we continue to act on previous information.
7758 - Avoid sending junk to controllers or segfaulting when a controller
7759 uses EVENT_NEW_DESC with verbose nicknames.
7760 - Stop triggering asserts if the controller tries to extend hidden
7761 service circuits (reported by mwenge).
7762 - Avoid infinite loop on unexpected controller input.
7763 - When the controller does a "GETINFO network-status", tell it
7764 about even those routers whose descriptors are very old, and use
7765 long nicknames where appropriate.
7766 - Change NT service functions to be loaded on demand. This lets us
7767 build with MinGW without breaking Tor for Windows 98 users.
7768 - Do DirPort reachability tests less often, since a single test
7769 chews through many circuits before giving up.
7770 - In the hidden service example in torrc.sample, stop recommending
7771 esoteric and discouraged hidden service options.
7772 - When stopping an NT service, wait up to 10 sec for it to actually
7773 stop. (Patch from Matt Edman; resolves bug 295.)
7774 - Fix handling of verbose nicknames with ORCONN controller events:
7775 make them show up exactly when requested, rather than exactly when
7777 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
7778 printing a duplicate "$" in the keys we send (reported by mwenge).
7779 - Correctly set maximum connection limit on Cygwin. (This time
7781 - Try to detect Windows correctly when cross-compiling.
7782 - Detect the size of the routers file correctly even if it is
7783 corrupted (on systems without mmap) or not page-aligned (on systems
7784 with mmap). This bug was harmless.
7785 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
7786 to open a stream fails; now we do in more cases. This should
7787 make clients able to find a good exit faster in some cases, since
7788 unhandleable requests will now get an error rather than timing out.
7789 - Resolve two memory leaks when rebuilding the on-disk router cache
7790 (reported by fookoowa).
7791 - Clean up minor code warnings suggested by the MIPSpro C compiler,
7792 and reported by some Centos users.
7793 - Controller signals now work on non-Unix platforms that don't define
7794 SIGUSR1 and SIGUSR2 the way we expect.
7795 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
7796 values before failing, and always enables eventdns.
7797 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
7798 Try to fix this in configure.in by checking for most functions
7799 before we check for libevent.
7802 Changes in version 0.1.2.2-alpha - 2006-10-07
7804 - Make our async eventdns library on-by-default for Tor servers,
7805 and plan to deprecate the separate dnsworker threads.
7806 - Add server-side support for "reverse" DNS lookups (using PTR
7807 records so clients can determine the canonical hostname for a given
7808 IPv4 address). Only supported by servers using eventdns; servers
7809 now announce in their descriptors whether they support eventdns.
7810 - Specify and implement client-side SOCKS5 interface for reverse DNS
7811 lookups (see doc/socks-extensions.txt).
7812 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
7813 connect to directory servers through Tor. Previously, clients needed
7814 to find Tor exits to make private connections to directory servers.
7815 - Avoid choosing Exit nodes for entry or middle hops when the
7816 total bandwidth available from non-Exit nodes is much higher than
7817 the total bandwidth available from Exit nodes.
7818 - Workaround for name servers (like Earthlink's) that hijack failing
7819 DNS requests and replace the no-such-server answer with a "helpful"
7820 redirect to an advertising-driven search portal. Also work around
7821 DNS hijackers who "helpfully" decline to hijack known-invalid
7822 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
7823 lets you turn it off.
7824 - Send out a burst of long-range padding cells once we've established
7825 that we're reachable. Spread them over 4 circuits, so hopefully
7826 a few will be fast. This exercises our bandwidth and bootstraps
7827 us into the directory more quickly.
7829 o New/improved config options:
7830 - Add new config option "ResolvConf" to let the server operator
7831 choose an alternate resolve.conf file when using eventdns.
7832 - Add an "EnforceDistinctSubnets" option to control our "exclude
7833 servers on the same /16" behavior. It's still on by default; this
7834 is mostly for people who want to operate private test networks with
7835 all the machines on the same subnet.
7836 - If one of our entry guards is on the ExcludeNodes list, or the
7837 directory authorities don't think it's a good guard, treat it as
7838 if it were unlisted: stop using it as a guard, and throw it off
7839 the guards list if it stays that way for a long time.
7840 - Allow directory authorities to be marked separately as authorities
7841 for the v1 directory protocol, the v2 directory protocol, and
7842 as hidden service directories, to make it easier to retire old
7843 authorities. V1 authorities should set "HSAuthoritativeDir 1"
7844 to continue being hidden service authorities too.
7845 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
7847 o Minor features, controller:
7848 - Fix CIRC controller events so that controllers can learn the
7849 identity digests of non-Named servers used in circuit paths.
7850 - Let controllers ask for more useful identifiers for servers. Instead
7851 of learning identity digests for un-Named servers and nicknames
7852 for Named servers, the new identifiers include digest, nickname,
7853 and indication of Named status. Off by default; see control-spec.txt
7854 for more information.
7855 - Add a "getinfo address" controller command so it can display Tor's
7856 best guess to the user.
7857 - New controller event to alert the controller when our server
7858 descriptor has changed.
7859 - Give more meaningful errors on controller authentication failure.
7861 o Minor features, other:
7862 - When asked to resolve a hostname, don't use non-exit servers unless
7863 requested to do so. This allows servers with broken DNS to be
7864 useful to the network.
7865 - Divide eventdns log messages into warn and info messages.
7866 - Reserve the nickname "Unnamed" for routers that can't pick
7867 a hostname: any router can call itself Unnamed; directory
7868 authorities will never allocate Unnamed to any particular router;
7869 clients won't believe that any router is the canonical Unnamed.
7870 - Only include function names in log messages for info/debug messages.
7871 For notice/warn/err, the content of the message should be clear on
7872 its own, and printing the function name only confuses users.
7873 - Avoid some false positives during reachability testing: don't try
7874 to test via a server that's on the same /24 as us.
7875 - If we fail to build a circuit to an intended enclave, and it's
7876 not mandatory that we use that enclave, stop wanting it.
7877 - When eventdns is enabled, allow multithreaded builds on NetBSD and
7878 OpenBSD. (We had previously disabled threads on these platforms
7879 because they didn't have working thread-safe resolver functions.)
7881 o Major bugfixes, anonymity/security:
7882 - If a client asked for a server by name, and there's a named server
7883 in our network-status but we don't have its descriptor yet, we
7884 could return an unnamed server instead.
7885 - Fix NetBSD bug that could allow someone to force uninitialized RAM
7886 to be sent to a server's DNS resolver. This only affects NetBSD
7887 and other platforms that do not bounds-check tolower().
7888 - Reject (most) attempts to use Tor circuits with length one. (If
7889 many people start using Tor as a one-hop proxy, exit nodes become
7890 a more attractive target for compromise.)
7891 - Just because your DirPort is open doesn't mean people should be
7892 able to remotely teach you about hidden service descriptors. Now
7893 only accept rendezvous posts if you've got HSAuthoritativeDir set.
7895 o Major bugfixes, other:
7896 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
7897 - When a client asks the server to resolve (not connect to)
7898 an address, and it has a cached answer, give them the cached answer.
7899 Previously, the server would give them no answer at all.
7900 - Allow really slow clients to not hang up five minutes into their
7901 directory downloads (suggested by Adam J. Richter).
7902 - We were building exactly the wrong circuits when we anticipated
7903 hidden service requirements, meaning Tor would have to build all
7904 its circuits on demand.
7905 - Avoid crashing when we mmap a router cache file of size 0.
7906 - When testing reachability of our DirPort, don't launch new
7907 tests when there's already one in progress -- unreachable
7908 servers were stacking up dozens of testing streams.
7910 o Minor bugfixes, correctness:
7911 - If we're a directory mirror and we ask for "all" network status
7912 documents, we would discard status documents from authorities
7914 - Avoid a memory corruption bug when creating a hash table for
7916 - Avoid controller-triggered crash when misusing certain commands
7917 from a v0 controller on platforms that do not handle
7918 printf("%s",NULL) gracefully.
7919 - Don't crash when a controller sends a third argument to an
7920 "extendcircuit" request.
7921 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7922 response; fix error code when "getinfo dir/status/" fails.
7923 - Avoid crash when telling controller stream-status and a stream
7925 - Patch from Adam Langley to fix assert() in eventdns.c.
7926 - Fix a debug log message in eventdns to say "X resolved to Y"
7927 instead of "X resolved to X".
7928 - Make eventdns give strings for DNS errors, not just error numbers.
7929 - Track unreachable entry guards correctly: don't conflate
7930 'unreachable by us right now' with 'listed as down by the directory
7931 authorities'. With the old code, if a guard was unreachable by
7932 us but listed as running, it would clog our guard list forever.
7933 - Behave correctly in case we ever have a network with more than
7934 2GB/s total advertised capacity.
7935 - Make TrackExitHosts case-insensitive, and fix the behavior of
7936 ".suffix" TrackExitHosts items to avoid matching in the middle of
7938 - Finally fix the openssl warnings from newer gccs that believe that
7939 ignoring a return value is okay, but casting a return value and
7940 then ignoring it is a sign of madness.
7941 - Prevent the contrib/exitlist script from printing the same
7942 result more than once.
7943 - Patch from Steve Hildrey: Generate network status correctly on
7944 non-versioning dirservers.
7945 - Don't listen to the X-Your-Address-Is hint if you did the lookup
7946 via Tor; otherwise you'll think you're the exit node's IP address.
7948 o Minor bugfixes, performance:
7949 - Two small performance improvements on parsing descriptors.
7950 - Major performance improvement on inserting descriptors: change
7951 algorithm from O(n^2) to O(n).
7952 - Make the common memory allocation path faster on machines where
7953 malloc(0) returns a pointer.
7954 - Start remembering X-Your-Address-Is directory hints even if you're
7955 a client, so you can become a server more smoothly.
7956 - Avoid duplicate entries on MyFamily line in server descriptor.
7958 o Packaging, features:
7959 - Remove architecture from OS X builds. The official builds are
7960 now universal binaries.
7961 - The Debian package now uses --verify-config when (re)starting,
7962 to distinguish configuration errors from other errors.
7963 - Update RPMs to require libevent 1.1b.
7965 o Packaging, bugfixes:
7966 - Patches so Tor builds with MinGW on Windows.
7967 - Patches so Tor might run on Cygwin again.
7968 - Resume building on non-gcc compilers and ancient gcc. Resume
7969 building with the -O0 compile flag. Resume building cleanly on
7971 - Run correctly on OS X platforms with case-sensitive filesystems.
7972 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
7973 - Add autoconf checks so Tor can build on Solaris x86 again.
7976 - Documented (and renamed) ServerDNSSearchDomains and
7977 ServerDNSResolvConfFile options.
7978 - Be clearer that the *ListenAddress directives can be repeated
7982 Changes in version 0.1.1.24 - 2006-09-29
7984 - Allow really slow clients to not hang up five minutes into their
7985 directory downloads (suggested by Adam J. Richter).
7986 - Fix major performance regression from 0.1.0.x: instead of checking
7987 whether we have enough directory information every time we want to
7988 do something, only check when the directory information has changed.
7989 This should improve client CPU usage by 25-50%.
7990 - Don't crash if, after a server has been running for a while,
7991 it can't resolve its hostname.
7994 - Allow Tor to start when RunAsDaemon is set but no logs are set.
7995 - Don't crash when the controller receives a third argument to an
7996 "extendcircuit" request.
7997 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7998 response; fix error code when "getinfo dir/status/" fails.
7999 - Fix configure.in to not produce broken configure files with
8000 more recent versions of autoconf. Thanks to Clint for his auto*
8002 - Fix security bug on NetBSD that could allow someone to force
8003 uninitialized RAM to be sent to a server's DNS resolver. This
8004 only affects NetBSD and other platforms that do not bounds-check
8006 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
8007 methods: these are known to be buggy.
8008 - If we're a directory mirror and we ask for "all" network status
8009 documents, we would discard status documents from authorities
8013 Changes in version 0.1.2.1-alpha - 2006-08-27
8015 - Add "eventdns" async dns library from Adam Langley, tweaked to
8016 build on OSX and Windows. Only enabled if you pass the
8017 --enable-eventdns argument to configure.
8018 - Allow servers with no hostname or IP address to learn their
8019 IP address by asking the directory authorities. This code only
8020 kicks in when you would normally have exited with a "no address"
8021 error. Nothing's authenticated, so use with care.
8022 - Rather than waiting a fixed amount of time between retrying
8023 application connections, we wait only 5 seconds for the first,
8024 10 seconds for the second, and 15 seconds for each retry after
8025 that. Hopefully this will improve the expected user experience.
8026 - Patch from Tup to add support for transparent AP connections:
8027 this basically bundles the functionality of trans-proxy-tor
8028 into the Tor mainline. Now hosts with compliant pf/netfilter
8029 implementations can redirect TCP connections straight to Tor
8030 without diverting through SOCKS. Needs docs.
8031 - Busy directory servers save lots of memory by spooling server
8032 descriptors, v1 directories, and v2 networkstatus docs to buffers
8033 as needed rather than en masse. Also mmap the cached-routers
8034 files, so we don't need to keep the whole thing in memory too.
8035 - Automatically avoid picking more than one node from the same
8036 /16 network when constructing a circuit.
8037 - Revise and clean up the torrc.sample that we ship with; add
8038 a section for BandwidthRate and BandwidthBurst.
8041 - Split circuit_t into origin_circuit_t and or_circuit_t, and
8042 split connection_t into edge, or, dir, control, and base structs.
8043 These will save quite a bit of memory on busy servers, and they'll
8044 also help us track down bugs in the code and bugs in the spec.
8045 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
8046 or later. Log when we are doing this, so we can diagnose it when
8047 it fails. (Also, recommend libevent 1.1b for kqueue and
8048 win32 methods; deprecate libevent 1.0b harder; make libevent
8049 recommendation system saner.)
8050 - Start being able to build universal binaries on OS X (thanks
8052 - Export the default exit policy via the control port, so controllers
8053 don't need to guess what it is / will be later.
8054 - Add a man page entry for ProtocolWarnings.
8055 - Add TestVia config option to the man page.
8056 - Remove even more protocol-related warnings from Tor server logs,
8057 such as bad TLS handshakes and malformed begin cells.
8058 - Stop fetching descriptors if you're not a dir mirror and you
8059 haven't tried to establish any circuits lately. [This currently
8060 causes some dangerous behavior, because when you start up again
8061 you'll use your ancient server descriptors.]
8062 - New DirPort behavior: if you have your dirport set, you download
8063 descriptors aggressively like a directory mirror, whether or not
8065 - Get rid of the router_retry_connections notion. Now routers
8066 no longer try to rebuild long-term connections to directory
8067 authorities, and directory authorities no longer try to rebuild
8068 long-term connections to all servers. We still don't hang up
8069 connections in these two cases though -- we need to look at it
8070 more carefully to avoid flapping, and we likely need to wait til
8071 0.1.1.x is obsolete.
8072 - Drop compatibility with obsolete Tors that permit create cells
8073 to have the wrong circ_id_type.
8074 - Re-enable per-connection rate limiting. Get rid of the "OP
8075 bandwidth" concept. Lay groundwork for "bandwidth classes" --
8076 separate global buckets that apply depending on what sort of conn
8078 - Start publishing one minute or so after we find our ORPort
8079 to be reachable. This will help reduce the number of descriptors
8080 we have for ourselves floating around, since it's quite likely
8081 other things (e.g. DirPort) will change during that minute too.
8082 - Fork the v1 directory protocol into its own spec document,
8083 and mark dir-spec.txt as the currently correct (v2) spec.
8086 - When we find our DirPort to be reachable, publish a new descriptor
8087 so we'll tell the world (reported by pnx).
8088 - Publish a new descriptor after we hup/reload. This is important
8089 if our config has changed such that we'll want to start advertising
8090 our DirPort now, etc.
8091 - Allow Tor to start when RunAsDaemon is set but no logs are set.
8092 - When we have a state file we cannot parse, tell the user and
8093 move it aside. Now we avoid situations where the user starts
8094 Tor in 1904, Tor writes a state file with that timestamp in it,
8095 the user fixes her clock, and Tor refuses to start.
8096 - Fix configure.in to not produce broken configure files with
8097 more recent versions of autoconf. Thanks to Clint for his auto*
8099 - "tor --verify-config" now exits with -1(255) or 0 depending on
8100 whether the config options are bad or good.
8101 - Resolve bug 321 when using dnsworkers: append a period to every
8102 address we resolve at the exit node, so that we do not accidentally
8103 pick up local addresses, and so that failing searches are retried
8104 in the resolver search domains. (This is already solved for
8105 eventdns.) (This breaks Blossom servers for now.)
8106 - If we are using an exit enclave and we can't connect, e.g. because
8107 its webserver is misconfigured to not listen on localhost, then
8108 back off and try connecting from somewhere else before we fail.
8111 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
8112 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
8113 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
8114 when the IP address is mapped through MapAddress to a hostname.
8115 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
8116 useless IPv6 DNS resolves.
8117 - Patch suggested by Karsten Loesing: respond to SIGNAL command
8118 before we execute the signal, in case the signal shuts us down.
8119 - Clean up AllowInvalidNodes man page entry.
8120 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
8121 - Add more asserts to track down an assert error on a windows Tor
8122 server with connection_add being called with socket == -1.
8123 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
8124 - Fix misleading log messages: an entry guard that is "unlisted",
8125 as well as not known to be "down" (because we've never heard
8126 of it), is not therefore "up".
8127 - Remove code to special-case "-cvs" ending, since it has not
8128 actually mattered since 0.0.9.
8129 - Make our socks5 handling more robust to broken socks clients:
8130 throw out everything waiting on the buffer in between socks
8131 handshake phases, since they can't possibly (so the theory
8132 goes) have predicted what we plan to respond to them.
8135 Changes in version 0.1.1.23 - 2006-07-30
8137 - Fast Tor servers, especially exit nodes, were triggering asserts
8138 due to a bug in handling the list of pending DNS resolves. Some
8139 bugs still remain here; we're hunting them.
8140 - Entry guards could crash clients by sending unexpected input.
8141 - More fixes on reachability testing: if you find yourself reachable,
8142 then don't ever make any client requests (so you stop predicting
8143 circuits), then hup or have your clock jump, then later your IP
8144 changes, you won't think circuits are working, so you won't try to
8145 test reachability, so you won't publish.
8148 - Avoid a crash if the controller does a resetconf firewallports
8149 and then a setconf fascistfirewall=1.
8150 - Avoid an integer underflow when the dir authority decides whether
8151 a router is stable: we might wrongly label it stable, and compute
8152 a slightly wrong median stability, when a descriptor is published
8154 - Fix a place where we might trigger an assert if we can't build our
8155 own server descriptor yet.
8158 Changes in version 0.1.1.22 - 2006-07-05
8160 - Fix a big bug that was causing servers to not find themselves
8161 reachable if they changed IP addresses. Since only 0.1.1.22+
8162 servers can do reachability testing correctly, now we automatically
8163 make sure to test via one of these.
8164 - Fix to allow clients and mirrors to learn directory info from
8165 descriptor downloads that get cut off partway through.
8166 - Directory authorities had a bug in deciding if a newly published
8167 descriptor was novel enough to make everybody want a copy -- a few
8168 servers seem to be publishing new descriptors many times a minute.
8170 - Fix a rare bug that was causing some servers to complain about
8171 "closing wedged cpuworkers" and skip some circuit create requests.
8172 - Make the Exit flag in directory status documents actually work.
8175 Changes in version 0.1.1.21 - 2006-06-10
8176 o Crash and assert fixes from 0.1.1.20:
8177 - Fix a rare crash on Tor servers that have enabled hibernation.
8178 - Fix a seg fault on startup for Tor networks that use only one
8179 directory authority.
8180 - Fix an assert from a race condition that occurs on Tor servers
8181 while exiting, where various threads are trying to log that they're
8182 exiting, and delete the logs, at the same time.
8183 - Make our unit tests pass again on certain obscure platforms.
8186 - Add support for building SUSE RPM packages.
8187 - Speed up initial bootstrapping for clients: if we are making our
8188 first ever connection to any entry guard, then don't mark it down
8190 - When only one Tor server in the network is labelled as a guard,
8191 and we've already picked him, we would cycle endlessly picking him
8192 again, being unhappy about it, etc. Now we specifically exclude
8193 current guards when picking a new guard.
8194 - Servers send create cells more reliably after the TLS connection
8195 is established: we were sometimes forgetting to send half of them
8196 when we had more than one pending.
8197 - If we get a create cell that asks us to extend somewhere, but the
8198 Tor server there doesn't match the expected digest, we now send
8199 a destroy cell back, rather than silently doing nothing.
8200 - Make options->RedirectExit work again.
8201 - Make cookie authentication for the controller work again.
8202 - Stop being picky about unusual characters in the arguments to
8203 mapaddress. It's none of our business.
8204 - Add a new config option "TestVia" that lets you specify preferred
8205 middle hops to use for test circuits. Perhaps this will let me
8206 debug the reachability problems better.
8208 o Log / documentation fixes:
8209 - If we're a server and some peer has a broken TLS certificate, don't
8210 log about it unless ProtocolWarnings is set, i.e., we want to hear
8211 about protocol violations by others.
8212 - Fix spelling of VirtualAddrNetwork in man page.
8213 - Add a better explanation at the top of the autogenerated torrc file
8214 about what happened to our old torrc.
8217 Changes in version 0.1.1.20 - 2006-05-23
8219 - Downgrade a log severity where servers complain that they're
8221 - Avoid a compile warning on FreeBSD.
8222 - Remove string size limit on NEWDESC messages; solve bug 291.
8223 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
8224 more thoroughly when we're running on windows.
8227 Changes in version 0.1.1.19-rc - 2006-05-03
8229 - Regenerate our local descriptor if it's dirty and we try to use
8230 it locally (e.g. if it changes during reachability detection).
8231 - If we setconf our ORPort to 0, we continued to listen on the
8232 old ORPort and receive connections.
8233 - Avoid a second warning about machine/limits.h on Debian
8235 - Be willing to add our own routerinfo into the routerlist.
8236 Now authorities will include themselves in their directories
8237 and network-statuses.
8238 - Stop trying to upload rendezvous descriptors to every
8239 directory authority: only try the v1 authorities.
8240 - Servers no longer complain when they think they're not
8241 registered with the directory authorities. There were too many
8243 - Backport dist-rpm changes so rpms can be built without errors.
8246 - Implement an option, VirtualAddrMask, to set which addresses
8247 get handed out in response to mapaddress requests. This works
8248 around a bug in tsocks where 127.0.0.0/8 is never socksified.
8251 Changes in version 0.1.1.18-rc - 2006-04-10
8253 - Work harder to download live network-statuses from all the
8254 directory authorities we know about. Improve the threshold
8255 decision logic so we're more robust to edge cases.
8256 - When fetching rendezvous descriptors, we were willing to ask
8257 v2 authorities too, which would always return 404.
8260 - Stop listing down or invalid nodes in the v1 directory. This will
8261 reduce its bulk by about 1/3, and reduce load on directory
8263 - When deciding whether a router is Fast or Guard-worthy, consider
8264 his advertised BandwidthRate and not just the BandwidthCapacity.
8265 - No longer ship INSTALL and README files -- they are useless now.
8266 - Force rpmbuild to behave and honor target_cpu.
8267 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
8268 - Start to include translated versions of the tor-doc-*.html
8269 files, along with the screenshots. Still needs more work.
8270 - Start sending back 512 and 451 errors if mapaddress fails,
8271 rather than not sending anything back at all.
8272 - When we fail to bind or listen on an incoming or outgoing
8273 socket, we should close it before failing. otherwise we just
8274 leak it. (thanks to weasel for finding.)
8275 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
8276 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
8277 - Make NoPublish (even though deprecated) work again.
8278 - Fix a minor security flaw where a versioning auth dirserver
8279 could list a recommended version many times in a row to make
8280 clients more convinced that it's recommended.
8281 - Fix crash bug if there are two unregistered servers running
8282 with the same nickname, one of them is down, and you ask for
8283 them by nickname in your EntryNodes or ExitNodes. Also, try
8284 to pick the one that's running rather than an arbitrary one.
8285 - Fix an infinite loop we could hit if we go offline for too long.
8286 - Complain when we hit WSAENOBUFS on recv() or write() too.
8287 Perhaps this will help us hunt the bug.
8288 - If you're not a versioning dirserver, don't put the string
8289 "client-versions \nserver-versions \n" in your network-status.
8290 - Lower the minimum required number of file descriptors to 1000,
8291 so we can have some overhead for Valgrind on Linux, where the
8292 default ulimit -n is 1024.
8295 - Add tor.dizum.com as the fifth authoritative directory server.
8296 - Add a new config option FetchUselessDescriptors, off by default,
8297 for when you plan to run "exitlist" on your client and you want
8298 to know about even the non-running descriptors.
8301 Changes in version 0.1.1.17-rc - 2006-03-28
8303 - Clients and servers since 0.1.1.10-alpha have been expiring
8304 connections whenever they are idle for 5 minutes and they *do*
8305 have circuits on them. Oops. With this new version, clients will
8306 discard their previous entry guard choices and avoid choosing
8307 entry guards running these flawed versions.
8308 - Fix memory leak when uncompressing concatenated zlib streams. This
8309 was causing substantial leaks over time on Tor servers.
8310 - The v1 directory was including servers as much as 48 hours old,
8311 because that's how the new routerlist->routers works. Now only
8312 include them if they're 20 hours old or less.
8315 - Resume building on irix64, netbsd 2.0, etc.
8316 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
8318 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
8319 and it is confusing some users.
8320 - Mirrors stop caching the v1 directory so often.
8321 - Make the max number of old descriptors that a cache will hold
8322 rise with the number of directory authorities, so we can scale.
8323 - Change our win32 uname() hack to be more forgiving about what
8324 win32 versions it thinks it's found.
8327 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
8329 - When the controller's *setconf commands fail, collect an error
8330 message in a string and hand it back to the controller.
8331 - Make the v2 dir's "Fast" flag based on relative capacity, just
8332 like "Stable" is based on median uptime. Name everything in the
8333 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
8334 - Log server fingerprint on startup, so new server operators don't
8335 have to go hunting around their filesystem for it.
8336 - Return a robots.txt on our dirport to discourage google indexing.
8337 - Let the controller ask for GETINFO dir/status/foo so it can ask
8338 directly rather than connecting to the dir port. Only works when
8339 dirport is set for now.
8341 o New config options rather than constants in the code:
8342 - SocksTimeout: How long do we let a socks connection wait
8343 unattached before we fail it?
8344 - CircuitBuildTimeout: Cull non-open circuits that were born
8345 at least this many seconds ago.
8346 - CircuitIdleTimeout: Cull open clean circuits that were born
8347 at least this many seconds ago.
8350 Changes in version 0.1.1.16-rc - 2006-03-18
8351 o Bugfixes on 0.1.1.15-rc:
8352 - Fix assert when the controller asks to attachstream a connect-wait
8353 or resolve-wait stream.
8354 - Now do address rewriting when the controller asks us to attach
8355 to a particular circuit too. This will let Blossom specify
8356 "moria2.exit" without having to learn what moria2's IP address is.
8357 - Make the "tor --verify-config" command-line work again, so people
8358 can automatically check if their torrc will parse.
8359 - Authoritative dirservers no longer require an open connection from
8360 a server to consider him "reachable". We need this change because
8361 when we add new auth dirservers, old servers won't know not to
8363 - Let Tor build on Sun CC again.
8364 - Fix an off-by-one buffer size in dirserv.c that magically never
8365 hit our three authorities but broke sjmurdoch's own tor network.
8366 - If we as a directory mirror don't know of any v1 directory
8367 authorities, then don't try to cache any v1 directories.
8368 - Stop warning about unknown servers in our family when they are
8369 given as hex digests.
8370 - Stop complaining as quickly to the server operator that he
8371 hasn't registered his nickname/key binding.
8372 - Various cleanups so we can add new V2 Auth Dirservers.
8373 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
8374 reflect the updated flags in our v2 dir protocol.
8375 - Resume allowing non-printable characters for exit streams (both
8376 for connecting and for resolving). Now we tolerate applications
8377 that don't follow the RFCs. But continue to block malformed names
8380 o Bugfixes on 0.1.0.x:
8381 - Fix assert bug in close_logs(): when we close and delete logs,
8382 remove them all from the global "logfiles" list.
8383 - Fix minor integer overflow in calculating when we expect to use up
8384 our bandwidth allocation before hibernating.
8385 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
8386 there are multiple SSLs installed with different versions.
8387 - When we try to be a server and Address is not explicitly set and
8388 our hostname resolves to a private IP address, try to use an
8389 interface address if it has a public address. Now Windows machines
8390 that think of themselves as localhost can work by default.
8393 - Let the controller ask for GETINFO dir/server/foo so it can ask
8394 directly rather than connecting to the dir port.
8395 - Let the controller tell us about certain router descriptors
8396 that it doesn't want Tor to use in circuits. Implement
8397 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
8398 - New config option SafeSocks to reject all application connections
8399 using unsafe socks protocols. Defaults to off.
8402 Changes in version 0.1.1.15-rc - 2006-03-11
8403 o Bugfixes and cleanups:
8404 - When we're printing strings from the network, don't try to print
8405 non-printable characters. This protects us against shell escape
8406 sequence exploits, and also against attacks to fool humans into
8407 misreading their logs.
8408 - Fix a bug where Tor would fail to establish any connections if you
8409 left it off for 24 hours and then started it: we were happy with
8410 the obsolete network statuses, but they all referred to router
8411 descriptors that were too old to fetch, so we ended up with no
8412 valid router descriptors.
8413 - Fix a seg fault in the controller's "getinfo orconn-status"
8414 command while listing status on incoming handshaking connections.
8415 Introduce a status name "NEW" for these connections.
8416 - If we get a linelist or linelist_s config option from the torrc
8417 (e.g. ExitPolicy) and it has no value, warn and skip rather than
8418 silently resetting it to its default.
8419 - Don't abandon entry guards until they've been down or gone for
8421 - Cleaner and quieter log messages.
8424 - New controller signal NEWNYM that makes new application requests
8426 - Add a new circuit purpose 'controller' to let the controller ask
8427 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
8428 controller command to let you specify the purpose if you're
8429 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
8430 command to let you change a circuit's purpose after it's been
8432 - Accept "private:*" in routerdesc exit policies; not generated yet
8433 because older Tors do not understand it.
8434 - Add BSD-style contributed startup script "rc.subr" from Peter
8438 Changes in version 0.1.1.14-alpha - 2006-02-20
8439 o Bugfixes on 0.1.1.x:
8440 - Don't die if we ask for a stdout or stderr log (even implicitly)
8441 and we're set to RunAsDaemon -- just warn.
8442 - We still had a few bugs in the OR connection rotation code that
8443 caused directory servers to slowly aggregate connections to other
8444 fast Tor servers. This time for sure!
8445 - Make log entries on Win32 include the name of the function again.
8446 - We were treating a pair of exit policies if they were equal even
8447 if one said accept and the other said reject -- causing us to
8448 not always publish a new descriptor since we thought nothing
8450 - Retry pending server downloads as well as pending networkstatus
8451 downloads when we unexpectedly get a socks request.
8452 - We were ignoring the IS_FAST flag in the directory status,
8453 meaning we were willing to pick trivial-bandwidth nodes for "fast"
8455 - If the controller's SAVECONF command fails (e.g. due to file
8456 permissions), let the controller know that it failed.
8459 - If we're trying to be a Tor server and running Windows 95/98/ME
8460 as a server, explain that we'll likely crash.
8461 - When we're a server, a client asks for an old-style directory,
8462 and our write bucket is empty, don't give it to him. This way
8463 small servers can continue to serve the directory *sometimes*,
8464 without getting overloaded.
8465 - Compress exit policies even more -- look for duplicate lines
8467 - Clients now honor the "guard" flag in the router status when
8468 picking entry guards, rather than looking at is_fast or is_stable.
8469 - Retain unrecognized lines in $DATADIR/state file, so that we can
8470 be forward-compatible.
8471 - Generate 18.0.0.0/8 address policy format in descs when we can;
8472 warn when the mask is not reducible to a bit-prefix.
8473 - Let the user set ControlListenAddress in the torrc. This can be
8474 dangerous, but there are some cases (like a secured LAN) where it
8476 - Split ReachableAddresses into ReachableDirAddresses and
8477 ReachableORAddresses, so we can restrict Dir conns to port 80
8478 and OR conns to port 443.
8479 - Now we can target arch and OS in rpm builds (contributed by
8480 Phobos). Also make the resulting dist-rpm filename match the
8482 - New config options to help controllers: FetchServerDescriptors
8483 and FetchHidServDescriptors for whether to fetch server
8484 info and hidserv info or let the controller do it, and
8485 PublishServerDescriptor and PublishHidServDescriptors.
8486 - Also let the controller set the __AllDirActionsPrivate config
8487 option if you want all directory fetches/publishes to happen via
8488 Tor (it assumes your controller bootstraps your circuits).
8491 Changes in version 0.1.0.17 - 2006-02-17
8492 o Crash bugfixes on 0.1.0.x:
8493 - When servers with a non-zero DirPort came out of hibernation,
8494 sometimes they would trigger an assert.
8496 o Other important bugfixes:
8497 - On platforms that don't have getrlimit (like Windows), we were
8498 artificially constraining ourselves to a max of 1024
8499 connections. Now just assume that we can handle as many as 15000
8500 connections. Hopefully this won't cause other problems.
8502 o Backported features:
8503 - When we're a server, a client asks for an old-style directory,
8504 and our write bucket is empty, don't give it to him. This way
8505 small servers can continue to serve the directory *sometimes*,
8506 without getting overloaded.
8507 - Whenever you get a 503 in response to a directory fetch, try
8508 once more. This will become important once servers start sending
8509 503's whenever they feel busy.
8510 - Fetch a new directory every 120 minutes, not every 40 minutes.
8511 Now that we have hundreds of thousands of users running the old
8512 directory algorithm, it's starting to hurt a lot.
8513 - Bump up the period for forcing a hidden service descriptor upload
8514 from 20 minutes to 1 hour.
8517 Changes in version 0.1.1.13-alpha - 2006-02-09
8518 o Crashes in 0.1.1.x:
8519 - When you tried to setconf ORPort via the controller, Tor would
8520 crash. So people using TorCP to become a server were sad.
8521 - Solve (I hope) the stack-smashing bug that we were seeing on fast
8522 servers. The problem appears to be something do with OpenSSL's
8523 random number generation, or how we call it, or something. Let me
8524 know if the crashes continue.
8525 - Turn crypto hardware acceleration off by default, until we find
8526 somebody smart who can test it for us. (It appears to produce
8527 seg faults in at least some cases.)
8528 - Fix a rare assert error when we've tried all intro points for
8529 a hidden service and we try fetching the service descriptor again:
8530 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
8533 - Fix a major load balance bug: we were round-robining in 16 KB
8534 chunks, and servers with bandwidthrate of 20 KB, while downloading
8535 a 600 KB directory, would starve their other connections. Now we
8536 try to be a bit more fair.
8537 - Dir authorities and mirrors were never expiring the newest
8538 descriptor for each server, causing memory and directory bloat.
8539 - Fix memory-bloating and connection-bloating bug on servers: We
8540 were never closing any connection that had ever had a circuit on
8541 it, because we were checking conn->n_circuits == 0, yet we had a
8542 bug that let it go negative.
8543 - Make Tor work using squid as your http proxy again -- squid
8544 returns an error if you ask for a URL that's too long, and it uses
8545 a really generic error message. Plus, many people are behind a
8546 transparent squid so they don't even realize it.
8547 - On platforms that don't have getrlimit (like Windows), we were
8548 artificially constraining ourselves to a max of 1024
8549 connections. Now just assume that we can handle as many as 15000
8550 connections. Hopefully this won't cause other problems.
8551 - Add a new config option ExitPolicyRejectPrivate which defaults to
8552 1. This means all exit policies will begin with rejecting private
8553 addresses, unless the server operator explicitly turns it off.
8556 - Clients no longer download descriptors for non-running
8558 - Before we add new directory authorities, we should make it
8559 clear that only v1 authorities should receive/publish hidden
8560 service descriptors.
8563 - As soon as we've fetched some more directory info, immediately
8564 try to download more server descriptors. This way we don't have
8565 a 10 second pause during initial bootstrapping.
8566 - Remove even more loud log messages that the server operator can't
8568 - When we're running an obsolete or un-recommended version, make
8569 the log message more clear about what the problem is and what
8570 versions *are* still recommended.
8571 - Provide a more useful warn message when our onion queue gets full:
8572 the CPU is too slow or the exit policy is too liberal.
8573 - Don't warn when we receive a 503 from a dirserver/cache -- this
8574 will pave the way for them being able to refuse if they're busy.
8575 - When we fail to bind a listener, try to provide a more useful
8576 log message: e.g., "Is Tor already running?"
8577 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
8578 Goldberg can prove things about our handshake protocol more
8580 - MaxConn has been obsolete for a while now. Document the ConnLimit
8581 config option, which is a *minimum* number of file descriptors
8582 that must be available else Tor refuses to start.
8583 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
8584 if you log to syslog and want something other than LOG_DAEMON.
8585 - Make dirservers generate a separate "guard" flag to mean,
8586 "would make a good entry guard". Make clients parse it and vote
8587 on it. Not used by clients yet.
8588 - Implement --with-libevent-dir option to ./configure. Also, improve
8589 search techniques to find libevent, and use those for openssl too.
8590 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
8591 - Only start testing reachability once we've established a
8592 circuit. This will make startup on dirservers less noisy.
8593 - Don't try to upload hidden service descriptors until we have
8594 established a circuit.
8595 - Fix the controller's "attachstream 0" command to treat conn like
8596 it just connected, doing address remapping, handling .exit and
8597 .onion idioms, and so on. Now we're more uniform in making sure
8598 that the controller hears about new and closing connections.
8601 Changes in version 0.1.1.12-alpha - 2006-01-11
8602 o Bugfixes on 0.1.1.x:
8603 - The fix to close duplicate server connections was closing all
8604 Tor client connections if they didn't establish a circuit
8605 quickly enough. Oops.
8606 - Fix minor memory issue (double-free) that happened on exit.
8608 o Bugfixes on 0.1.0.x:
8609 - Tor didn't warn when it failed to open a log file.
8612 Changes in version 0.1.1.11-alpha - 2006-01-10
8613 o Crashes in 0.1.1.x:
8614 - Include all the assert/crash fixes from 0.1.0.16.
8615 - If you start Tor and then quit very quickly, there were some
8616 races that tried to free things that weren't allocated yet.
8617 - Fix a rare memory stomp if you're running hidden services.
8618 - Fix segfault when specifying DirServer in config without nickname.
8619 - Fix a seg fault when you finish connecting to a server but at
8620 that moment you dump his server descriptor.
8621 - Extendcircuit and Attachstream controller commands would
8622 assert/crash if you don't give them enough arguments.
8623 - Fix an assert error when we're out of space in the connection_list
8624 and we try to post a hidden service descriptor (reported by weasel).
8625 - If you specify a relative torrc path and you set RunAsDaemon in
8626 your torrc, then it chdir()'s to the new directory. If you HUP,
8627 it tries to load the new torrc location, fails, and exits.
8628 The fix: no longer allow a relative path to torrc using -f.
8631 - Implement "entry guards": automatically choose a handful of entry
8632 nodes and stick with them for all circuits. Only pick new guards
8633 when the ones you have are unsuitable, and if the old guards
8634 become suitable again, switch back. This will increase security
8635 dramatically against certain end-point attacks. The EntryNodes
8636 config option now provides some hints about which entry guards you
8637 want to use most; and StrictEntryNodes means to only use those.
8638 - New directory logic: download by descriptor digest, not by
8639 fingerprint. Caches try to download all listed digests from
8640 authorities; clients try to download "best" digests from caches.
8641 This avoids partitioning and isolating attacks better.
8642 - Make the "stable" router flag in network-status be the median of
8643 the uptimes of running valid servers, and make clients pay
8644 attention to the network-status flags. Thus the cutoff adapts
8645 to the stability of the network as a whole, making IRC, IM, etc
8646 connections more reliable.
8649 - Tor servers with dynamic IP addresses were needing to wait 18
8650 hours before they could start doing reachability testing using
8651 the new IP address and ports. This is because they were using
8652 the internal descriptor to learn what to test, yet they were only
8653 rebuilding the descriptor once they decided they were reachable.
8654 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
8655 to download certain server descriptors, throw them away, and then
8656 fetch them again after 30 minutes. Now mirrors throw away these
8657 server descriptors so clients can't get them.
8658 - We were leaving duplicate connections to other ORs open for a week,
8659 rather than closing them once we detect a duplicate. This only
8660 really affected authdirservers, but it affected them a lot.
8661 - Spread the authdirservers' reachability testing over the entire
8662 testing interval, so we don't try to do 500 TLS's at once every
8666 - If the network is down, and we try to connect to a conn because
8667 we have a circuit in mind, and we timeout (30 seconds) because the
8668 network never answers, we were expiring the circuit, but we weren't
8669 obsoleting the connection or telling the entry_guards functions.
8670 - Some Tor servers process billions of cells per day. These statistics
8671 need to be uint64_t's.
8672 - Check for integer overflows in more places, when adding elements
8673 to smartlists. This could possibly prevent a buffer overflow
8674 on malicious huge inputs. I don't see any, but I haven't looked
8676 - ReachableAddresses kept growing new "reject *:*" lines on every
8678 - When you "setconf log" via the controller, it should remove all
8679 logs. We were automatically adding back in a "log notice stdout".
8680 - Newly bootstrapped Tor networks couldn't establish hidden service
8681 circuits until they had nodes with high uptime. Be more tolerant.
8682 - We were marking servers down when they could not answer every piece
8683 of the directory request we sent them. This was far too harsh.
8684 - Fix the torify (tsocks) config file to not use Tor for localhost
8686 - Directory authorities now go to the proper authority when asking for
8687 a networkstatus, even when they want a compressed one.
8688 - Fix a harmless bug that was causing Tor servers to log
8689 "Got an end because of misc error, but we're not an AP. Closing."
8690 - Authorities were treating their own descriptor changes as cosmetic,
8691 meaning the descriptor available in the network-status and the
8692 descriptor that clients downloaded were different.
8693 - The OS X installer was adding a symlink for tor_resolve but
8694 the binary was called tor-resolve (reported by Thomas Hardly).
8695 - Workaround a problem with some http proxies where they refuse GET
8696 requests that specify "Content-Length: 0" (reported by Adrian).
8697 - Fix wrong log message when you add a "HiddenServiceNodes" config
8698 line without any HiddenServiceDir line (reported by Chris Thomas).
8701 - Write the TorVersion into the state file so we have a prayer of
8702 keeping forward and backward compatibility.
8703 - Revive the FascistFirewall config option rather than eliminating it:
8704 now it's a synonym for ReachableAddresses *:80,*:443.
8705 - Clients choose directory servers from the network status lists,
8706 not from their internal list of router descriptors. Now they can
8707 go to caches directly rather than needing to go to authorities
8709 - Directory authorities ignore router descriptors that have only
8710 cosmetic differences: do this for 0.1.0.x servers now too.
8711 - Add a new flag to network-status indicating whether the server
8712 can answer v2 directory requests too.
8713 - Authdirs now stop whining so loudly about bad descriptors that
8714 they fetch from other dirservers. So when there's a log complaint,
8715 it's for sure from a freshly uploaded descriptor.
8716 - Reduce memory requirements in our structs by changing the order
8718 - There used to be two ways to specify your listening ports in a
8719 server descriptor: on the "router" line and with a separate "ports"
8720 line. Remove support for the "ports" line.
8721 - New config option "AuthDirRejectUnlisted" for auth dirservers as
8722 a panic button: if we get flooded with unusable servers we can
8723 revert to only listing servers in the approved-routers file.
8724 - Auth dir servers can now mark a fingerprint as "!reject" or
8725 "!invalid" in the approved-routers file (as its nickname), to
8726 refuse descriptors outright or include them but marked as invalid.
8727 - Servers store bandwidth history across restarts/crashes.
8728 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
8729 get a better idea of why their circuits failed. Not used yet.
8730 - Directory mirrors now cache up to 16 unrecognized network-status
8731 docs. Now we can add new authdirservers and they'll be cached too.
8732 - When picking a random directory, prefer non-authorities if any
8734 - New controller option "getinfo desc/all-recent" to fetch the
8735 latest server descriptor for every router that Tor knows about.
8738 Changes in version 0.1.0.16 - 2006-01-02
8739 o Crash bugfixes on 0.1.0.x:
8740 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8741 corrupting the heap, losing FDs, or crashing when we need to resize
8742 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8743 - It turns out sparc64 platforms crash on unaligned memory access
8744 too -- so detect and avoid this.
8745 - Handle truncated compressed data correctly (by detecting it and
8747 - Fix possible-but-unlikely free(NULL) in control.c.
8748 - When we were closing connections, there was a rare case that
8749 stomped on memory, triggering seg faults and asserts.
8750 - Avoid potential infinite recursion when building a descriptor. (We
8751 don't know that it ever happened, but better to fix it anyway.)
8752 - We were neglecting to unlink marked circuits from soon-to-close OR
8753 connections, which caused some rare scribbling on freed memory.
8754 - Fix a memory stomping race bug when closing the joining point of two
8755 rendezvous circuits.
8756 - Fix an assert in time parsing found by Steven Murdoch.
8758 o Other bugfixes on 0.1.0.x:
8759 - When we're doing reachability testing, provide more useful log
8760 messages so the operator knows what to expect.
8761 - Do not check whether DirPort is reachable when we are suppressing
8762 advertising it because of hibernation.
8763 - When building with -static or on Solaris, we sometimes needed -ldl.
8764 - When we're deciding whether a stream has enough circuits around
8765 that can handle it, count the freshly dirty ones and not the ones
8766 that are so dirty they won't be able to handle it.
8767 - When we're expiring old circuits, we had a logic error that caused
8768 us to close new rendezvous circuits rather than old ones.
8769 - Give a more helpful log message when you try to change ORPort via
8770 the controller: you should upgrade Tor if you want that to work.
8771 - We were failing to parse Tor versions that start with "Tor ".
8772 - Tolerate faulty streams better: when a stream fails for reason
8773 exitpolicy, stop assuming that the router is lying about his exit
8774 policy. When a stream fails for reason misc, allow it to retry just
8775 as if it was resolvefailed. When a stream has failed three times,
8776 reset its failure count so we can try again and get all three tries.
8779 Changes in version 0.1.1.10-alpha - 2005-12-11
8780 o Correctness bugfixes on 0.1.0.x:
8781 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8782 corrupting the heap, losing FDs, or crashing when we need to resize
8783 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8784 - Stop doing the complex voodoo overkill checking for insecure
8785 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
8786 - When we were closing connections, there was a rare case that
8787 stomped on memory, triggering seg faults and asserts.
8788 - We were neglecting to unlink marked circuits from soon-to-close OR
8789 connections, which caused some rare scribbling on freed memory.
8790 - When we're deciding whether a stream has enough circuits around
8791 that can handle it, count the freshly dirty ones and not the ones
8792 that are so dirty they won't be able to handle it.
8793 - Recover better from TCP connections to Tor servers that are
8794 broken but don't tell you (it happens!); and rotate TLS
8795 connections once a week.
8796 - When we're expiring old circuits, we had a logic error that caused
8797 us to close new rendezvous circuits rather than old ones.
8798 - Fix a scary-looking but apparently harmless bug where circuits
8799 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
8800 servers, and never switch to state CIRCUIT_STATE_OPEN.
8801 - When building with -static or on Solaris, we sometimes needed to
8803 - Give a useful message when people run Tor as the wrong user,
8804 rather than telling them to start chowning random directories.
8805 - We were failing to inform the controller about new .onion streams.
8807 o Security bugfixes on 0.1.0.x:
8808 - Refuse server descriptors if the fingerprint line doesn't match
8809 the included identity key. Tor doesn't care, but other apps (and
8810 humans) might actually be trusting the fingerprint line.
8811 - We used to kill the circuit when we receive a relay command we
8812 don't recognize. Now we just drop it.
8813 - Start obeying our firewall options more rigorously:
8814 . If we can't get to a dirserver directly, try going via Tor.
8815 . Don't ever try to connect (as a client) to a place our
8816 firewall options forbid.
8817 . If we specify a proxy and also firewall options, obey the
8818 firewall options even when we're using the proxy: some proxies
8819 can only proxy to certain destinations.
8820 - Fix a bug found by Lasse Overlier: when we were making internal
8821 circuits (intended to be cannibalized later for rendezvous and
8822 introduction circuits), we were picking them so that they had
8823 useful exit nodes. There was no need for this, and it actually
8824 aids some statistical attacks.
8825 - Start treating internal circuits and exit circuits separately.
8826 It's important to keep them separate because internal circuits
8827 have their last hops picked like middle hops, rather than like
8828 exit hops. So exiting on them will break the user's expectations.
8830 o Bugfixes on 0.1.1.x:
8831 - Take out the mis-feature where we tried to detect IP address
8832 flapping for people with DynDNS, and chose not to upload a new
8833 server descriptor sometimes.
8834 - Try to be compatible with OpenSSL 0.9.6 again.
8835 - Log fix: when the controller is logging about .onion addresses,
8836 sometimes it didn't include the ".onion" part of the address.
8837 - Don't try to modify options->DirServers internally -- if the
8838 user didn't specify any, just add the default ones directly to
8839 the trusted dirserver list. This fixes a bug where people running
8840 controllers would use SETCONF on some totally unrelated config
8841 option, and Tor would start yelling at them about changing their
8843 - Let the controller's redirectstream command specify a port, in
8844 case the controller wants to change that too.
8845 - When we requested a pile of server descriptors, we sometimes
8846 accidentally launched a duplicate request for the first one.
8847 - Bugfix for trackhostexits: write down the fingerprint of the
8848 chosen exit, not its nickname, because the chosen exit might not
8850 - When parsing foo.exit, if foo is unknown, and we are leaving
8851 circuits unattached, set the chosen_exit field and leave the
8852 address empty. This matters because controllers got confused
8854 - Directory authorities no longer try to download server
8855 descriptors that they know they will reject.
8857 o Features and updates:
8858 - Replace balanced trees with hash tables: this should make stuff
8859 significantly faster.
8860 - Resume using the AES counter-mode implementation that we ship,
8861 rather than OpenSSL's. Ours is significantly faster.
8862 - Many other CPU and memory improvements.
8863 - Add a new config option FastFirstHopPK (on by default) so clients
8864 do a trivial crypto handshake for their first hop, since TLS has
8865 already taken care of confidentiality and authentication.
8866 - Add a new config option TestSocks so people can see if their
8867 applications are using socks4, socks4a, socks5-with-ip, or
8868 socks5-with-hostname. This way they don't have to keep mucking
8869 with tcpdump and wondering if something got cached somewhere.
8870 - Warn when listening on a public address for socks. I suspect a
8871 lot of people are setting themselves up as open socks proxies,
8872 and they have no idea that jerks on the Internet are using them,
8873 since they simply proxy the traffic into the Tor network.
8874 - Add "private:*" as an alias in configuration for policies. Now
8875 you can simplify your exit policy rather than needing to list
8876 every single internal or nonroutable network space.
8877 - Add a new controller event type that allows controllers to get
8878 all server descriptors that were uploaded to a router in its role
8879 as authoritative dirserver.
8880 - Start shipping socks-extensions.txt, tor-doc-unix.html,
8881 tor-doc-server.html, and stylesheet.css in the tarball.
8882 - Stop shipping tor-doc.html in the tarball.
8885 Changes in version 0.1.1.9-alpha - 2005-11-15
8886 o Usability improvements:
8887 - Start calling it FooListenAddress rather than FooBindAddress,
8888 since few of our users know what it means to bind an address
8890 - Reduce clutter in server logs. We're going to try to make
8891 them actually usable now. New config option ProtocolWarnings that
8892 lets you hear about how _other Tors_ are breaking the protocol. Off
8894 - Divide log messages into logging domains. Once we put some sort
8895 of interface on this, it will let people looking at more verbose
8896 log levels specify the topics they want to hear more about.
8897 - Make directory servers return better http 404 error messages
8898 instead of a generic "Servers unavailable".
8899 - Check for even more Windows version flags when writing the platform
8900 string in server descriptors, and note any we don't recognize.
8901 - Clean up more of the OpenSSL memory when exiting, so we can detect
8902 memory leaks better.
8903 - Make directory authorities be non-versioning, non-naming by
8904 default. Now we can add new directory servers without requiring
8905 their operators to pay close attention.
8906 - When logging via syslog, include the pid whenever we provide
8907 a log entry. Suggested by Todd Fries.
8909 o Performance improvements:
8910 - Directory servers now silently throw away new descriptors that
8911 haven't changed much if the timestamps are similar. We do this to
8912 tolerate older Tor servers that upload a new descriptor every 15
8913 minutes. (It seemed like a good idea at the time.)
8914 - Inline bottleneck smartlist functions; use fast versions by default.
8915 - Add a "Map from digest to void*" abstraction digestmap_t so we
8916 can do less hex encoding/decoding. Use it in router_get_by_digest()
8917 to resolve a performance bottleneck.
8918 - Allow tor_gzip_uncompress to extract as much as possible from
8919 truncated compressed data. Try to extract as many
8920 descriptors as possible from truncated http responses (when
8921 DIR_PURPOSE_FETCH_ROUTERDESC).
8922 - Make circ->onionskin a pointer, not a static array. moria2 was using
8923 125000 circuit_t's after it had been up for a few weeks, which
8924 translates to 20+ megs of wasted space.
8925 - The private half of our EDH handshake keys are now chosen out
8926 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
8928 o Security improvements:
8929 - Start making directory caches retain old routerinfos, so soon
8930 clients can start asking by digest of descriptor rather than by
8931 fingerprint of server.
8932 - Add half our entropy from RAND_poll in OpenSSL. This knows how
8933 to use egd (if present), openbsd weirdness (if present), vms/os2
8934 weirdness (if we ever port there), and more in the future.
8936 o Bugfixes on 0.1.0.x:
8937 - Do round-robin writes of at most 16 kB per write. This might be
8938 more fair on loaded Tor servers, and it might resolve our Windows
8939 crash bug. It might also slow things down.
8940 - Our TLS handshakes were generating a single public/private
8941 keypair for the TLS context, rather than making a new one for
8942 each new connections. Oops. (But we were still rotating them
8943 periodically, so it's not so bad.)
8944 - When we were cannibalizing a circuit with a particular exit
8945 node in mind, we weren't checking to see if that exit node was
8946 already present earlier in the circuit. Oops.
8947 - When a Tor server's IP changes (e.g. from a dyndns address),
8948 upload a new descriptor so clients will learn too.
8949 - Really busy servers were keeping enough circuits open on stable
8950 connections that they were wrapping around the circuit_id
8951 space. (It's only two bytes.) This exposed a bug where we would
8952 feel free to reuse a circuit_id even if it still exists but has
8953 been marked for close. Try to fix this bug. Some bug remains.
8954 - If we would close a stream early (e.g. it asks for a .exit that
8955 we know would refuse it) but the LeaveStreamsUnattached config
8956 option is set by the controller, then don't close it.
8958 o Bugfixes on 0.1.1.8-alpha:
8959 - Fix a big pile of memory leaks, some of them serious.
8960 - Do not try to download a routerdesc if we would immediately reject
8962 - Resume inserting a newline between all router descriptors when
8963 generating (old style) signed directories, since our spec says
8965 - When providing content-type application/octet-stream for
8966 server descriptors using .z, we were leaving out the
8967 content-encoding header. Oops. (Everything tolerated this just
8968 fine, but that doesn't mean we need to be part of the problem.)
8969 - Fix a potential seg fault in getconf and getinfo using version 1
8970 of the controller protocol.
8971 - Avoid crash: do not check whether DirPort is reachable when we
8972 are suppressing it because of hibernation.
8973 - Make --hash-password not crash on exit.
8976 Changes in version 0.1.1.8-alpha - 2005-10-07
8977 o New features (major):
8978 - Clients don't download or use the directory anymore. Now they
8979 download and use network-statuses from the trusted dirservers,
8980 and fetch individual server descriptors as needed from mirrors.
8981 See dir-spec.txt for all the gory details.
8982 - Be more conservative about whether to advertise our DirPort.
8983 The main change is to not advertise if we're running at capacity
8984 and either a) we could hibernate or b) our capacity is low and
8985 we're using a default DirPort.
8986 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
8988 o New features (minor):
8989 - Try to be smart about when to retry network-status and
8990 server-descriptor fetches. Still needs some tuning.
8991 - Stop parsing, storing, or using running-routers output (but
8992 mirrors still cache and serve it).
8993 - Consider a threshold of versioning dirservers (dirservers who have
8994 an opinion about which Tor versions are still recommended) before
8995 deciding whether to warn the user that he's obsolete.
8996 - Dirservers can now reject/invalidate by key and IP, with the
8997 config options "AuthDirInvalid" and "AuthDirReject". This is
8998 useful since currently we automatically list servers as running
8999 and usable even if we know they're jerks.
9000 - Provide dire warnings to any users who set DirServer; move it out
9001 of torrc.sample and into torrc.complete.
9002 - Add MyFamily to torrc.sample in the server section.
9003 - Add nicknames to the DirServer line, so we can refer to them
9004 without requiring all our users to memorize their IP addresses.
9005 - When we get an EOF or a timeout on a directory connection, note
9006 how many bytes of serverdesc we are dropping. This will help
9007 us determine whether it is smart to parse incomplete serverdesc
9009 - Add a new function to "change pseudonyms" -- that is, to stop
9010 using any currently-dirty circuits for new streams, so we don't
9011 link new actions to old actions. Currently it's only called on
9012 HUP (or SIGNAL RELOAD).
9013 - On sighup, if UseHelperNodes changed to 1, use new circuits.
9014 - Start using RAND_bytes rather than RAND_pseudo_bytes from
9015 OpenSSL. Also, reseed our entropy every hour, not just at
9016 startup. And entropy in 512-bit chunks, not 160-bit chunks.
9018 o Fixes on 0.1.1.7-alpha:
9019 - Nobody ever implemented EVENT_ADDRMAP for control protocol
9020 version 0, so don't let version 0 controllers ask for it.
9021 - If you requested something with too many newlines via the
9022 v1 controller protocol, you could crash tor.
9023 - Fix a number of memory leaks, including some pretty serious ones.
9024 - Re-enable DirPort testing again, so Tor servers will be willing
9025 to advertise their DirPort if it's reachable.
9026 - On TLS handshake, only check the other router's nickname against
9027 its expected nickname if is_named is set.
9029 o Fixes forward-ported from 0.1.0.15:
9030 - Don't crash when we don't have any spare file descriptors and we
9031 try to spawn a dns or cpu worker.
9032 - Make the numbers in read-history and write-history into uint64s,
9033 so they don't overflow and publish negatives in the descriptor.
9036 - For the OS X package's modified privoxy config file, comment
9037 out the "logfile" line so we don't log everything passed
9039 - We were whining about using socks4 or socks5-with-local-lookup
9040 even when it's an IP in the "virtual" range we designed exactly
9042 - We were leaking some memory every time the client changes IPs.
9043 - Never call free() on tor_malloc()d memory. This will help us
9044 use dmalloc to detect memory leaks.
9045 - Check for named servers when looking them up by nickname;
9046 warn when we'recalling a non-named server by its nickname;
9047 don't warn twice about the same name.
9048 - Try to list MyFamily elements by key, not by nickname, and warn
9049 if we've not heard of the server.
9050 - Make windows platform detection (uname equivalent) smarter.
9051 - It turns out sparc64 doesn't like unaligned access either.
9054 Changes in version 0.1.0.15 - 2005-09-23
9055 o Bugfixes on 0.1.0.x:
9056 - Reject ports 465 and 587 (spam targets) in default exit policy.
9057 - Don't crash when we don't have any spare file descriptors and we
9058 try to spawn a dns or cpu worker.
9059 - Get rid of IgnoreVersion undocumented config option, and make us
9060 only warn, never exit, when we're running an obsolete version.
9061 - Don't try to print a null string when your server finds itself to
9062 be unreachable and the Address config option is empty.
9063 - Make the numbers in read-history and write-history into uint64s,
9064 so they don't overflow and publish negatives in the descriptor.
9065 - Fix a minor memory leak in smartlist_string_remove().
9066 - We were only allowing ourselves to upload a server descriptor at
9067 most every 20 minutes, even if it changed earlier than that.
9068 - Clean up log entries that pointed to old URLs.
9071 Changes in version 0.1.1.7-alpha - 2005-09-14
9072 o Fixes on 0.1.1.6-alpha:
9073 - Exit servers were crashing when people asked them to make a
9074 connection to an address not in their exit policy.
9075 - Looking up a non-existent stream for a v1 control connection would
9077 - Fix a seg fault if we ask a dirserver for a descriptor by
9078 fingerprint but he doesn't know about him.
9079 - SETCONF was appending items to linelists, not clearing them.
9080 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
9081 out and refuse the setconf if it would fail.
9082 - Downgrade the dirserver log messages when whining about
9086 - Add Peter Palfrader's check-tor script to tor/contrib/
9087 It lets you easily check whether a given server (referenced by
9088 nickname) is reachable by you.
9089 - Numerous changes to move towards client-side v2 directories. Not
9093 - If the user gave tor an odd number of command-line arguments,
9094 we were silently ignoring the last one. Now we complain and fail.
9095 [This wins the oldest-bug prize -- this bug has been present since
9096 November 2002, as released in Tor 0.0.0.]
9097 - Do not use unaligned memory access on alpha, mips, or mipsel.
9098 It *works*, but is very slow, so we treat them as if it doesn't.
9099 - Retry directory requests if we fail to get an answer we like
9100 from a given dirserver (we were retrying before, but only if
9101 we fail to connect).
9102 - When writing the RecommendedVersions line, sort them first.
9103 - When the client asked for a rendezvous port that the hidden
9104 service didn't want to provide, we were sending an IP address
9105 back along with the end cell. Fortunately, it was zero. But stop
9107 - Correct "your server is reachable" log entries to indicate that
9108 it was self-testing that told us so.
9111 Changes in version 0.1.1.6-alpha - 2005-09-09
9112 o Fixes on 0.1.1.5-alpha:
9113 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
9114 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
9115 - Fix bug with tor_memmem finding a match at the end of the string.
9116 - Make unit tests run without segfaulting.
9117 - Resolve some solaris x86 compile warnings.
9118 - Handle duplicate lines in approved-routers files without warning.
9119 - Fix bug where as soon as a server refused any requests due to his
9120 exit policy (e.g. when we ask for localhost and he tells us that's
9121 127.0.0.1 and he won't do it), we decided he wasn't obeying his
9122 exit policy using him for any exits.
9123 - Only do openssl hardware accelerator stuff if openssl version is
9126 o New controller features/fixes:
9127 - Add a "RESETCONF" command so you can set config options like
9128 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
9129 a config option in the torrc with no value, then it clears it
9130 entirely (rather than setting it to its default).
9131 - Add a "GETINFO config-file" to tell us where torrc is.
9132 - Avoid sending blank lines when GETINFO replies should be empty.
9133 - Add a QUIT command for the controller (for using it manually).
9134 - Fix a bug in SAVECONF that was adding default dirservers and
9135 other redundant entries to the torrc file.
9137 o Start on the new directory design:
9138 - Generate, publish, cache, serve new network-status format.
9139 - Publish individual descriptors (by fingerprint, by "all", and by
9141 - Publish client and server recommended versions separately.
9142 - Allow tor_gzip_uncompress() to handle multiple concatenated
9143 compressed strings. Serve compressed groups of router
9144 descriptors. The compression logic here could be more
9146 - Distinguish v1 authorities (all currently trusted directories)
9147 from v2 authorities (all trusted directories).
9148 - Change DirServers config line to note which dirs are v1 authorities.
9149 - Add configuration option "V1AuthoritativeDirectory 1" which
9150 moria1, moria2, and tor26 should set.
9151 - Remove option when getting directory cache to see whether they
9152 support running-routers; they all do now. Replace it with one
9153 to see whether caches support v2 stuff.
9156 - Dirservers now do their own external reachability testing of each
9157 Tor server, and only list them as running if they've been found to
9158 be reachable. We also send back warnings to the server's logs if
9159 it uploads a descriptor that we already believe is unreachable.
9160 - Implement exit enclaves: if we know an IP address for the
9161 destination, and there's a running Tor server at that address
9162 which allows exit to the destination, then extend the circuit to
9163 that exit first. This provides end-to-end encryption and end-to-end
9164 authentication. Also, if the user wants a .exit address or enclave,
9165 use 4 hops rather than 3, and cannibalize a general circ for it
9167 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
9168 controller. Also, rotate dns and cpu workers if the controller
9169 changes options that will affect them; and initialize the dns
9170 worker cache tree whether or not we start out as a server.
9171 - Only upload a new server descriptor when options change, 18
9172 hours have passed, uptime is reset, or bandwidth changes a lot.
9173 - Check [X-]Forwarded-For headers in HTTP requests when generating
9174 log messages. This lets people run dirservers (and caches) behind
9175 Apache but still know which IP addresses are causing warnings.
9177 o Config option changes:
9178 - Replace (Fascist)Firewall* config options with a new
9179 ReachableAddresses option that understands address policies.
9180 For example, "ReachableAddresses *:80,*:443"
9181 - Get rid of IgnoreVersion undocumented config option, and make us
9182 only warn, never exit, when we're running an obsolete version.
9183 - Make MonthlyAccountingStart config option truly obsolete now.
9186 - Reject ports 465 and 587 in the default exit policy, since
9187 people have started using them for spam too.
9188 - It turns out we couldn't bootstrap a network since we added
9189 reachability detection in 0.1.0.1-rc. Good thing the Tor network
9190 has never gone down. Add an AssumeReachable config option to let
9191 servers and dirservers bootstrap. When we're trying to build a
9192 high-uptime or high-bandwidth circuit but there aren't enough
9193 suitable servers, try being less picky rather than simply failing.
9194 - Our logic to decide if the OR we connected to was the right guy
9195 was brittle and maybe open to a mitm for unverified routers.
9196 - We weren't cannibalizing circuits correctly for
9197 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
9198 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
9199 build those from scratch. This should make hidden services faster.
9200 - Predict required circuits better, with an eye toward making hidden
9201 services faster on the service end.
9202 - Retry streams if the exit node sends back a 'misc' failure. This
9203 should result in fewer random failures. Also, after failing
9204 from resolve failed or misc, reset the num failures, so we give
9205 it a fair shake next time we try.
9206 - Clean up the rendezvous warn log msgs, and downgrade some to info.
9207 - Reduce severity on logs about dns worker spawning and culling.
9208 - When we're shutting down and we do something like try to post a
9209 server descriptor or rendezvous descriptor, don't complain that
9210 we seem to be unreachable. Of course we are, we're shutting down.
9211 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
9212 We don't use them yet, but maybe one day our DNS resolver will be
9213 able to discover them.
9214 - Make ContactInfo mandatory for authoritative directory servers.
9215 - Require server descriptors to list IPv4 addresses -- hostnames
9216 are no longer allowed. This also fixes some potential security
9217 problems with people providing hostnames as their address and then
9218 preferentially resolving them to partition users.
9219 - Change log line for unreachability to explicitly suggest /etc/hosts
9220 as the culprit. Also make it clearer what IP address and ports we're
9221 testing for reachability.
9222 - Put quotes around user-supplied strings when logging so users are
9223 more likely to realize if they add bad characters (like quotes)
9225 - Let auth dir servers start without specifying an Address config
9227 - Make unit tests (and other invocations that aren't the real Tor)
9228 run without launching listeners, creating subdirectories, and so on.
9231 Changes in version 0.1.1.5-alpha - 2005-08-08
9232 o Bugfixes included in 0.1.0.14.
9234 o Bugfixes on 0.1.0.x:
9235 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
9236 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
9237 it would silently using ignore the 6668.
9240 Changes in version 0.1.0.14 - 2005-08-08
9241 o Bugfixes on 0.1.0.x:
9242 - Fix the other half of the bug with crypto handshakes
9244 - Fix an assert trigger if you send a 'signal term' via the
9245 controller when it's listening for 'event info' messages.
9248 Changes in version 0.1.1.4-alpha - 2005-08-04
9249 o Bugfixes included in 0.1.0.13.
9252 - Improve tor_gettimeofday() granularity on windows.
9253 - Make clients regenerate their keys when their IP address changes.
9254 - Implement some more GETINFO goodness: expose helper nodes, config
9255 options, getinfo keys.
9258 Changes in version 0.1.0.13 - 2005-08-04
9259 o Bugfixes on 0.1.0.x:
9260 - Fix a critical bug in the security of our crypto handshakes.
9261 - Fix a size_t underflow in smartlist_join_strings2() that made
9262 it do bad things when you hand it an empty smartlist.
9263 - Fix Windows installer to ship Tor license (thanks to Aphex for
9264 pointing out this oversight) and put a link to the doc directory
9266 - Explicitly set no-unaligned-access for sparc: it turns out the
9267 new gcc's let you compile broken code, but that doesn't make it
9271 Changes in version 0.1.1.3-alpha - 2005-07-23
9272 o Bugfixes on 0.1.1.2-alpha:
9273 - Fix a bug in handling the controller's "post descriptor"
9275 - Fix several bugs in handling the controller's "extend circuit"
9277 - Fix a bug in handling the controller's "stream status" event.
9278 - Fix an assert failure if we have a controller listening for
9279 circuit events and we go offline.
9280 - Re-allow hidden service descriptors to publish 0 intro points.
9281 - Fix a crash when generating your hidden service descriptor if
9282 you don't have enough intro points already.
9284 o New features on 0.1.1.2-alpha:
9285 - New controller function "getinfo accounting", to ask how
9286 many bytes we've used in this time period.
9287 - Experimental support for helper nodes: a lot of the risk from
9288 a small static adversary comes because users pick new random
9289 nodes every time they rebuild a circuit. Now users will try to
9290 stick to the same small set of entry nodes if they can. Not
9291 enabled by default yet.
9293 o Bugfixes on 0.1.0.12:
9294 - If you're an auth dir server, always publish your dirport,
9295 even if you haven't yet found yourself to be reachable.
9296 - Fix a size_t underflow in smartlist_join_strings2() that made
9297 it do bad things when you hand it an empty smartlist.
9300 Changes in version 0.1.0.12 - 2005-07-18
9301 o New directory servers:
9302 - tor26 has changed IP address.
9304 o Bugfixes on 0.1.0.x:
9305 - Fix a possible double-free in tor_gzip_uncompress().
9306 - When --disable-threads is set, do not search for or link against
9308 - Don't trigger an assert if an authoritative directory server
9309 claims its dirport is 0.
9310 - Fix bug with removing Tor as an NT service: some people were
9311 getting "The service did not return an error." Thanks to Matt
9315 Changes in version 0.1.1.2-alpha - 2005-07-15
9316 o New directory servers:
9317 - tor26 has changed IP address.
9319 o Bugfixes on 0.1.0.x, crashes/leaks:
9320 - Port the servers-not-obeying-their-exit-policies fix from
9322 - Fix an fd leak in start_daemon().
9323 - On Windows, you can't always reopen a port right after you've
9324 closed it. So change retry_listeners() to only close and re-open
9325 ports that have changed.
9326 - Fix a possible double-free in tor_gzip_uncompress().
9328 o Bugfixes on 0.1.0.x, usability:
9329 - When tor_socketpair() fails in Windows, give a reasonable
9330 Windows-style errno back.
9331 - Let people type "tor --install" as well as "tor -install" when
9333 want to make it an NT service.
9334 - NT service patch from Matt Edman to improve error messages.
9335 - When the controller asks for a config option with an abbreviated
9336 name, give the full name in our response.
9337 - Correct the man page entry on TrackHostExitsExpire.
9338 - Looks like we were never delivering deflated (i.e. compressed)
9339 running-routers lists, even when asked. Oops.
9340 - When --disable-threads is set, do not search for or link against
9343 o Bugfixes on 0.1.1.x:
9344 - Fix a seg fault with autodetecting which controller version is
9348 - New hidden service descriptor format: put a version in it, and
9349 let people specify introduction/rendezvous points that aren't
9350 in "the directory" (which is subjective anyway).
9351 - Allow the DEBUG controller event to work again. Mark certain log
9352 entries as "don't tell this to controllers", so we avoid cycles.
9355 Changes in version 0.1.0.11 - 2005-06-30
9356 o Bugfixes on 0.1.0.x:
9357 - Fix major security bug: servers were disregarding their
9358 exit policies if clients behaved unexpectedly.
9359 - Make OS X init script check for missing argument, so we don't
9360 confuse users who invoke it incorrectly.
9361 - Fix a seg fault in "tor --hash-password foo".
9362 - The MAPADDRESS control command was broken.
9365 Changes in version 0.1.1.1-alpha - 2005-06-29
9367 - Make OS X init script check for missing argument, so we don't
9368 confuse users who invoke it incorrectly.
9369 - Fix a seg fault in "tor --hash-password foo".
9370 - Fix a possible way to DoS dirservers.
9371 - When we complain that your exit policy implicitly allows local or
9372 private address spaces, name them explicitly so operators can
9374 - Make the log message less scary when all the dirservers are
9375 temporarily unreachable.
9376 - We were printing the number of idle dns workers incorrectly when
9380 - Revised controller protocol (version 1) that uses ascii rather
9381 than binary. Add supporting libraries in python and java so you
9382 can use the controller from your applications without caring how
9384 - Spiffy new support for crypto hardware accelerators. Can somebody
9388 Changes in version 0.0.9.10 - 2005-06-16
9389 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
9390 - Refuse relay cells that claim to have a length larger than the
9391 maximum allowed. This prevents a potential attack that could read
9392 arbitrary memory (e.g. keys) from an exit server's process
9396 Changes in version 0.1.0.10 - 2005-06-14
9397 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
9398 libevent before 1.1a.
9401 Changes in version 0.1.0.9-rc - 2005-06-09
9403 - Reset buf->highwater every time buf_shrink() is called, not just on
9404 a successful shrink. This was causing significant memory bloat.
9405 - Fix buffer overflow when checking hashed passwords.
9406 - Security fix: if seeding the RNG on Win32 fails, quit.
9407 - Allow seeding the RNG on Win32 even when you're not running as
9409 - Disable threading on Solaris too. Something is wonky with it,
9410 cpuworkers, and reentrant libs.
9411 - Reenable the part of the code that tries to flush as soon as an
9412 OR outbuf has a full TLS record available. Perhaps this will make
9413 OR outbufs not grow as huge except in rare cases, thus saving lots
9414 of CPU time plus memory.
9415 - Reject malformed .onion addresses rather then passing them on as
9416 normal web requests.
9417 - Adapt patch from Adam Langley: fix possible memory leak in
9418 tor_lookup_hostname().
9419 - Initialize libevent later in the startup process, so the logs are
9420 already established by the time we start logging libevent warns.
9421 - Use correct errno on win32 if libevent fails.
9422 - Check and warn about known-bad/slow libevent versions.
9423 - Pay more attention to the ClientOnly config option.
9424 - Have torctl.in/tor.sh.in check for location of su binary (needed
9426 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
9427 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
9428 HttpProxyAuthenticator
9429 - Stop warning about sigpipes in the logs. We're going to
9430 pretend that getting these occassionally is normal and fine.
9431 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
9433 installer screens; and don't put stuff into StartupItems unless
9434 the user asks you to.
9435 - Require servers that use the default dirservers to have public IP
9436 addresses. We have too many servers that are configured with private
9437 IPs and their admins never notice the log entries complaining that
9438 their descriptors are being rejected.
9439 - Add OSX uninstall instructions. An actual uninstall script will
9443 Changes in version 0.1.0.8-rc - 2005-05-23
9445 - It turns out that kqueue on OS X 10.3.9 was causing kernel
9446 panics. Disable kqueue on all OS X Tors.
9447 - Fix RPM: remove duplicate line accidentally added to the rpm
9449 - Disable threads on openbsd too, since its gethostaddr is not
9451 - Tolerate libevent 0.8 since it still works, even though it's
9453 - Enable building on Red Hat 9.0 again.
9454 - Allow the middle hop of the testing circuit to be running any
9455 version, now that most of them have the bugfix to let them connect
9456 to unknown servers. This will allow reachability testing to work
9457 even when 0.0.9.7-0.0.9.9 become obsolete.
9458 - Handle relay cells with rh.length too large. This prevents
9459 a potential attack that could read arbitrary memory (maybe even
9460 keys) from the exit server's process.
9461 - We screwed up the dirport reachability testing when we don't yet
9462 have a cached version of the directory. Hopefully now fixed.
9463 - Clean up router_load_single_router() (used by the controller),
9464 so it doesn't seg fault on error.
9465 - Fix a minor memory leak when somebody establishes an introduction
9466 point at your Tor server.
9467 - If a socks connection ends because read fails, don't warn that
9468 you're not sending a socks reply back.
9471 - Add HttpProxyAuthenticator config option too, that works like
9472 the HttpsProxyAuthenticator config option.
9473 - Encode hashed controller passwords in hex instead of base64,
9474 to make it easier to write controllers.
9477 Changes in version 0.1.0.7-rc - 2005-05-17
9479 - Fix a bug in the OS X package installer that prevented it from
9480 installing on Tiger.
9481 - Fix a script bug in the OS X package installer that made it
9482 complain during installation.
9483 - Find libevent even if it's hiding in /usr/local/ and your
9484 CFLAGS and LDFLAGS don't tell you to look there.
9485 - Be able to link with libevent as a shared library (the default
9486 after 1.0d), even if it's hiding in /usr/local/lib and even
9487 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
9488 assuming you're running gcc. Otherwise fail and give a useful
9490 - Fix a bug in the RPM packager: set home directory for _tor to
9491 something more reasonable when first installing.
9492 - Free a minor amount of memory that is still reachable on exit.
9495 Changes in version 0.1.0.6-rc - 2005-05-14
9497 - Implement --disable-threads configure option. Disable threads on
9498 netbsd by default, because it appears to have no reentrant resolver
9500 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
9501 release (1.1) detects and disables kqueue if it's broken.
9502 - Append default exit policy before checking for implicit internal
9503 addresses. Now we don't log a bunch of complaints on startup
9504 when using the default exit policy.
9505 - Some people were putting "Address " in their torrc, and they had
9506 a buggy resolver that resolved " " to 0.0.0.0. Oops.
9507 - If DataDir is ~/.tor, and that expands to /.tor, then default to
9508 LOCALSTATEDIR/tor instead.
9509 - Fix fragmented-message bug in TorControl.py.
9510 - Resolve a minor bug which would prevent unreachable dirports
9511 from getting suppressed in the published descriptor.
9512 - When the controller gave us a new descriptor, we weren't resolving
9513 it immediately, so Tor would think its address was 0.0.0.0 until
9514 we fetched a new directory.
9515 - Fix an uppercase/lowercase case error in suppressing a bogus
9516 libevent warning on some Linuxes.
9519 - Begin scrubbing sensitive strings from logs by default. Turn off
9520 the config option SafeLogging if you need to do debugging.
9521 - Switch to a new buffer management algorithm, which tries to avoid
9522 reallocing and copying quite as much. In first tests it looks like
9523 it uses *more* memory on average, but less cpu.
9524 - First cut at support for "create-fast" cells. Clients can use
9525 these when extending to their first hop, since the TLS already
9526 provides forward secrecy and authentication. Not enabled on
9528 - When dirservers refuse a router descriptor, we now log its
9529 contactinfo, platform, and the poster's IP address.
9530 - Call tor_free_all instead of connections_free_all after forking, to
9531 save memory on systems that need to fork.
9532 - Whine at you if you're a server and you don't set your contactinfo.
9533 - Implement --verify-config command-line option to check if your torrc
9534 is valid without actually launching Tor.
9535 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
9536 rather than just rejecting it.
9539 Changes in version 0.1.0.5-rc - 2005-04-27
9541 - Stop trying to print a null pointer if an OR conn fails because
9542 we didn't like its cert.
9544 - Switch our internal buffers implementation to use a ring buffer,
9545 to hopefully improve performance for fast servers a lot.
9546 - Add HttpsProxyAuthenticator support (basic auth only), based
9547 on patch from Adam Langley.
9548 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
9549 the fast servers that have been joining lately.
9550 - Give hidden service accesses extra time on the first attempt,
9551 since 60 seconds is often only barely enough. This might improve
9553 - Improve performance for dirservers: stop re-parsing the whole
9554 directory every time you regenerate it.
9555 - Add more debugging info to help us find the weird dns freebsd
9556 pthreads bug; cleaner debug messages to help track future issues.
9559 Changes in version 0.0.9.9 - 2005-04-23
9560 o Bugfixes on 0.0.9.x:
9561 - If unofficial Tor clients connect and send weird TLS certs, our
9562 Tor server triggers an assert. This release contains a minimal
9563 backport from the broader fix that we put into 0.1.0.4-rc.
9566 Changes in version 0.1.0.4-rc - 2005-04-23
9568 - If unofficial Tor clients connect and send weird TLS certs, our
9569 Tor server triggers an assert. Stop asserting, and start handling
9570 TLS errors better in other situations too.
9571 - When the controller asks us to tell it about all the debug-level
9572 logs, it turns out we were generating debug-level logs while
9573 telling it about them, which turns into a bad loop. Now keep
9574 track of whether you're sending a debug log to the controller,
9575 and don't log when you are.
9576 - Fix the "postdescriptor" feature of the controller interface: on
9577 non-complete success, only say "done" once.
9579 - Clients are now willing to load balance over up to 2mB, not 1mB,
9580 of advertised bandwidth capacity.
9581 - Add a NoPublish config option, so you can be a server (e.g. for
9582 testing running Tor servers in other Tor networks) without
9583 publishing your descriptor to the primary dirservers.
9586 Changes in version 0.1.0.3-rc - 2005-04-08
9587 o Improvements on 0.1.0.2-rc:
9588 - Client now retries when streams end early for 'hibernating' or
9589 'resource limit' reasons, rather than failing them.
9590 - More automated handling for dirserver operators:
9591 - Automatically approve nodes running 0.1.0.2-rc or later,
9592 now that the the reachability detection stuff is working.
9593 - Now we allow two unverified servers with the same nickname
9594 but different keys. But if a nickname is verified, only that
9595 nickname+key are allowed.
9596 - If you're an authdirserver connecting to an address:port,
9597 and it's not the OR you were expecting, forget about that
9598 descriptor. If he *was* the one you were expecting, then forget
9599 about all other descriptors for that address:port.
9600 - Allow servers to publish descriptors from 12 hours in the future.
9601 Corollary: only whine about clock skew from the dirserver if
9602 he's a trusted dirserver (since now even verified servers could
9603 have quite wrong clocks).
9604 - Adjust maximum skew and age for rendezvous descriptors: let skew
9605 be 48 hours rather than 90 minutes.
9606 - Efficiency improvements:
9607 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
9608 it much faster to look up a circuit for each relay cell.
9609 - Remove most calls to assert_all_pending_dns_resolves_ok(),
9610 since they're eating our cpu on exit nodes.
9611 - Stop wasting time doing a case insensitive comparison for every
9612 dns name every time we do any lookup. Canonicalize the names to
9613 lowercase and be done with it.
9614 - Start sending 'truncated' cells back rather than destroy cells,
9615 if the circuit closes in front of you. This means we won't have
9616 to abandon partially built circuits.
9617 - Only warn once per nickname from add_nickname_list_to_smartlist
9618 per failure, so an entrynode or exitnode choice that's down won't
9620 - Put a note in the torrc about abuse potential with the default
9622 - Revise control spec and implementation to allow all log messages to
9623 be sent to controller with their severities intact (suggested by
9624 Matt Edman). Update TorControl to handle new log event types.
9625 - Provide better explanation messages when controller's POSTDESCRIPTOR
9627 - Stop putting nodename in the Platform string in server descriptors.
9628 It doesn't actually help, and it is confusing/upsetting some people.
9630 o Bugfixes on 0.1.0.2-rc:
9631 - We were printing the host mask wrong in exit policies in server
9632 descriptors. This isn't a critical bug though, since we were still
9633 obeying the exit policy internally.
9634 - Fix Tor when compiled with libevent but without pthreads: move
9635 connection_unregister() from _connection_free() to
9637 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
9638 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
9639 when we look through the connection array, we'll find any of the
9640 cpu/dnsworkers. This is no good.
9642 o Bugfixes on 0.0.9.8:
9643 - Fix possible bug on threading platforms (e.g. win32) which was
9644 leaking a file descriptor whenever a cpuworker or dnsworker died.
9645 - When using preferred entry or exit nodes, ignore whether the
9646 circuit wants uptime or capacity. They asked for the nodes, they
9648 - chdir() to your datadirectory at the *end* of the daemonize process,
9649 not the beginning. This was a problem because the first time you
9650 run tor, if your datadir isn't there, and you have runasdaemon set
9651 to 1, it will try to chdir to it before it tries to create it. Oops.
9652 - Handle changed router status correctly when dirserver reloads
9653 fingerprint file. We used to be dropping all unverified descriptors
9654 right then. The bug was hidden because we would immediately
9655 fetch a directory from another dirserver, which would include the
9656 descriptors we just dropped.
9657 - When we're connecting to an OR and he's got a different nickname/key
9658 than we were expecting, only complain loudly if we're an OP or a
9659 dirserver. Complaining loudly to the OR admins just confuses them.
9660 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
9661 artificially capped at 500kB.
9664 Changes in version 0.0.9.8 - 2005-04-07
9665 o Bugfixes on 0.0.9.x:
9666 - We have a bug that I haven't found yet. Sometimes, very rarely,
9667 cpuworkers get stuck in the 'busy' state, even though the cpuworker
9668 thinks of itself as idle. This meant that no new circuits ever got
9669 established. Here's a workaround to kill any cpuworker that's been
9670 busy for more than 100 seconds.
9673 Changes in version 0.1.0.2-rc - 2005-04-01
9674 o Bugfixes on 0.1.0.1-rc:
9675 - Fixes on reachability detection:
9676 - Don't check for reachability while hibernating.
9677 - If ORPort is reachable but DirPort isn't, still publish the
9678 descriptor, but zero out DirPort until it's found reachable.
9679 - When building testing circs for ORPort testing, use only
9680 high-bandwidth nodes, so fewer circuits fail.
9681 - Complain about unreachable ORPort separately from unreachable
9682 DirPort, so the user knows what's going on.
9683 - Make sure we only conclude ORPort reachability if we didn't
9684 initiate the conn. Otherwise we could falsely conclude that
9685 we're reachable just because we connected to the guy earlier
9686 and he used that same pipe to extend to us.
9687 - Authdirservers shouldn't do ORPort reachability detection,
9688 since they're in clique mode, so it will be rare to find a
9689 server not already connected to them.
9690 - When building testing circuits, always pick middle hops running
9691 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
9692 bug. (This is a kludge; it will go away when 0.0.9.x becomes
9694 - When we decide we're reachable, actually publish our descriptor
9696 - Fix bug in redirectstream in the controller.
9697 - Fix the state descriptor strings so logs don't claim edge streams
9698 are in a different state than they actually are.
9699 - Use recent libevent features when possible (this only really affects
9700 win32 and osx right now, because the new libevent with these
9701 features hasn't been released yet). Add code to suppress spurious
9703 - Prevent possible segfault in connection_close_unattached_ap().
9704 - Fix newlines on torrc in win32.
9705 - Improve error msgs when tor-resolve fails.
9707 o Improvements on 0.0.9.x:
9708 - New experimental script tor/contrib/ExerciseServer.py (needs more
9709 work) that uses the controller interface to build circuits and
9710 fetch pages over them. This will help us bootstrap servers that
9711 have lots of capacity but haven't noticed it yet.
9712 - New experimental script tor/contrib/PathDemo.py (needs more work)
9713 that uses the controller interface to let you choose whole paths
9715 "<hostname>.<path,separated by dots>.<length of path>.path"
9716 - When we've connected to an OR and handshaked but didn't like
9717 the result, we were closing the conn without sending destroy
9718 cells back for pending circuits. Now send those destroys.
9721 Changes in version 0.0.9.7 - 2005-04-01
9722 o Bugfixes on 0.0.9.x:
9723 - Fix another race crash bug (thanks to Glenn Fink for reporting).
9724 - Compare identity to identity, not to nickname, when extending to
9725 a router not already in the directory. This was preventing us from
9726 extending to unknown routers. Oops.
9727 - Make sure to create OS X Tor user in <500 range, so we aren't
9728 creating actual system users.
9729 - Note where connection-that-hasn't-sent-end was marked, and fix
9730 a few really loud instances of this harmless bug (it's fixed more
9734 Changes in version 0.1.0.1-rc - 2005-03-28
9736 - Add reachability testing. Your Tor server will automatically try
9737 to see if its ORPort and DirPort are reachable from the outside,
9738 and it won't upload its descriptor until it decides they are.
9739 - Handle unavailable hidden services better. Handle slow or busy
9740 hidden services better.
9741 - Add support for CONNECTing through https proxies, with "HttpsProxy"
9743 - New exit policy: accept most low-numbered ports, rather than
9744 rejecting most low-numbered ports.
9745 - More Tor controller support (still experimental). See
9746 http://tor.eff.org/doc/control-spec.txt for all the new features,
9747 including signals to emulate unix signals from any platform;
9748 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
9749 closestream; closecircuit; etc.
9750 - Make nt services work and start on startup on win32 (based on
9751 patch by Matt Edman).
9752 - Add a new AddressMap config directive to rewrite incoming socks
9753 addresses. This lets you, for example, declare an implicit
9754 required exit node for certain sites.
9755 - Add a new TrackHostExits config directive to trigger addressmaps
9756 for certain incoming socks addresses -- for sites that break when
9757 your exit keeps changing (based on patch by Mike Perry).
9758 - Redo the client-side dns cache so it's just an addressmap too.
9759 - Notice when our IP changes, and reset stats/uptime/reachability.
9760 - When an application is using socks5, give him the whole variety of
9761 potential socks5 responses (connect refused, host unreachable, etc),
9762 rather than just "success" or "failure".
9763 - A more sane version numbering system. See
9764 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
9765 - New contributed script "exitlist": a simple python script to
9766 parse directories and find Tor nodes that exit to listed
9768 - New contributed script "privoxy-tor-toggle" to toggle whether
9769 Privoxy uses Tor. Seems to be configured for Debian by default.
9770 - Report HTTP reasons to client when getting a response from directory
9771 servers -- so you can actually know what went wrong.
9772 - New config option MaxAdvertisedBandwidth which lets you advertise
9773 a low bandwidthrate (to not attract as many circuits) while still
9774 allowing a higher bandwidthrate in reality.
9776 o Robustness/stability fixes:
9777 - Make Tor use Niels Provos's libevent instead of its current
9778 poll-but-sometimes-select mess. This will let us use faster async
9779 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
9781 - pthread support now too. This was forced because when we forked,
9782 we ended up wasting a lot of duplicate ram over time. Also switch
9783 to foo_r versions of some library calls to allow reentry and
9785 - Better handling for heterogeneous / unreliable nodes:
9786 - Annotate circuits w/ whether they aim to contain high uptime nodes
9787 and/or high capacity nodes. When building circuits, choose
9789 - This means that every single node in an intro rend circuit,
9790 not just the last one, will have a minimum uptime.
9791 - New config option LongLivedPorts to indicate application streams
9792 that will want high uptime circuits.
9793 - Servers reset uptime when a dir fetch entirely fails. This
9794 hopefully reflects stability of the server's network connectivity.
9795 - If somebody starts his tor server in Jan 2004 and then fixes his
9796 clock, don't make his published uptime be a year.
9797 - Reset published uptime when you wake up from hibernation.
9798 - Introduce a notion of 'internal' circs, which are chosen without
9799 regard to the exit policy of the last hop. Intro and rendezvous
9800 circs must be internal circs, to avoid leaking information. Resolve
9801 and connect streams can use internal circs if they want.
9802 - New circuit pooling algorithm: make sure to have enough circs around
9803 to satisfy any predicted ports, and also make sure to have 2 internal
9804 circs around if we've required internal circs lately (and with high
9805 uptime if we've seen that lately too).
9806 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
9807 which describes how often we retry making new circuits if current
9808 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
9809 how long we're willing to make use of an already-dirty circuit.
9810 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
9811 circ as necessary, if there are any completed ones lying around
9812 when we try to launch one.
9813 - Make hidden services try to establish a rendezvous for 30 seconds,
9814 rather than for n (where n=3) attempts to build a circuit.
9815 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
9816 "ShutdownWaitLength".
9817 - Try to be more zealous about calling connection_edge_end when
9818 things go bad with edge conns in connection.c.
9819 - Revise tor-spec to add more/better stream end reasons.
9820 - Revise all calls to connection_edge_end to avoid sending "misc",
9821 and to take errno into account where possible.
9824 - Fix a race condition that can trigger an assert, when we have a
9825 pending create cell and an OR connection fails right then.
9826 - Fix several double-mark-for-close bugs, e.g. where we were finding
9827 a conn for a cell even if that conn is already marked for close.
9828 - Make sequence of log messages when starting on win32 with no config
9829 file more reasonable.
9830 - When choosing an exit node for a new non-internal circ, don't take
9831 into account whether it'll be useful for any pending x.onion
9832 addresses -- it won't.
9833 - Turn addr_policy_compare from a tristate to a quadstate; this should
9834 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
9835 for google.com" problem.
9836 - Make "platform" string in descriptor more accurate for Win32 servers,
9837 so it's not just "unknown platform".
9838 - Fix an edge case in parsing config options (thanks weasel).
9839 If they say "--" on the commandline, it's not an option.
9840 - Reject odd-looking addresses at the client (e.g. addresses that
9841 contain a colon), rather than having the server drop them because
9843 - tor-resolve requests were ignoring .exit if there was a working circuit
9844 they could use instead.
9845 - REUSEADDR on normal platforms means you can rebind to the port
9846 right after somebody else has let it go. But REUSEADDR on win32
9847 means to let you bind to the port _even when somebody else
9848 already has it bound_! So, don't do that on Win32.
9849 - Change version parsing logic: a version is "obsolete" if it is not
9850 recommended and (1) there is a newer recommended version in the
9851 same series, or (2) there are no recommended versions in the same
9852 series, but there are some recommended versions in a newer series.
9853 A version is "new" if it is newer than any recommended version in
9855 - Stop most cases of hanging up on a socks connection without sending
9859 - Require BandwidthRate to be at least 20kB/s for servers.
9860 - When a dirserver causes you to give a warn, mention which dirserver
9862 - New config option DirAllowPrivateAddresses for authdirservers.
9863 Now by default they refuse router descriptors that have non-IP or
9864 private-IP addresses.
9865 - Stop publishing socksport in the directory, since it's not
9866 actually meant to be public. For compatibility, publish a 0 there
9868 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
9869 smart" value, that is low for servers and high for clients.
9870 - If our clock jumps forward by 100 seconds or more, assume something
9871 has gone wrong with our network and abandon all not-yet-used circs.
9872 - Warn when exit policy implicitly allows local addresses.
9873 - If we get an incredibly skewed timestamp from a dirserver mirror
9874 that isn't a verified OR, don't warn -- it's probably him that's
9876 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
9877 cookies to disk and doesn't log each web request to disk. (Thanks
9878 to Brett Carrington for pointing this out.)
9879 - When a client asks us for a dir mirror and we don't have one,
9880 launch an attempt to get a fresh one.
9881 - If we're hibernating and we get a SIGINT, exit immediately.
9882 - Add --with-dmalloc ./configure option, to track memory leaks.
9883 - And try to free all memory on closing, so we can detect what
9885 - Cache local dns resolves correctly even when they're .exit
9887 - Give a better warning when some other server advertises an
9888 ORPort that is actually an apache running ssl.
9889 - Add "opt hibernating 1" to server descriptor to make it clearer
9890 whether the server is hibernating.
9893 Changes in version 0.0.9.6 - 2005-03-24
9894 o Bugfixes on 0.0.9.x (crashes and asserts):
9895 - Add new end stream reasons to maintainance branch. Fix bug where
9896 reason (8) could trigger an assert. Prevent bug from recurring.
9897 - Apparently win32 stat wants paths to not end with a slash.
9898 - Fix assert triggers in assert_cpath_layer_ok(), where we were
9899 blowing away the circuit that conn->cpath_layer points to, then
9900 checking to see if the circ is well-formed. Backport check to make
9901 sure we dont use the cpath on a closed connection.
9902 - Prevent circuit_resume_edge_reading_helper() from trying to package
9903 inbufs for marked-for-close streams.
9904 - Don't crash on hup if your options->address has become unresolvable.
9905 - Some systems (like OS X) sometimes accept() a connection and tell
9906 you the remote host is 0.0.0.0:0. If this happens, due to some
9907 other mis-features, we get confused; so refuse the conn for now.
9909 o Bugfixes on 0.0.9.x (other):
9910 - Fix harmless but scary "Unrecognized content encoding" warn message.
9911 - Add new stream error reason: TORPROTOCOL reason means "you are not
9912 speaking a version of Tor I understand; say bye-bye to your stream."
9913 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
9914 into the future, now that we are more tolerant of skew. This
9915 resolves a bug where a Tor server would refuse to cache a directory
9916 because all the directories it gets are too far in the future;
9917 yet the Tor server never logs any complaints about clock skew.
9918 - Mac packaging magic: make man pages useable, and do not overwrite
9919 existing torrc files.
9920 - Make OS X log happily to /var/log/tor/tor.log
9923 Changes in version 0.0.9.5 - 2005-02-22
9924 o Bugfixes on 0.0.9.x:
9925 - Fix an assert race at exit nodes when resolve requests fail.
9926 - Stop picking unverified dir mirrors--it only leads to misery.
9927 - Patch from Matt Edman to make NT services work better. Service
9928 support is still not compiled into the executable by default.
9929 - Patch from Dmitri Bely so the Tor service runs better under
9930 the win32 SYSTEM account.
9931 - Make tor-resolve actually work (?) on Win32.
9932 - Fix a sign bug when getrlimit claims to have 4+ billion
9933 file descriptors available.
9934 - Stop refusing to start when bandwidthburst == bandwidthrate.
9935 - When create cells have been on the onion queue more than five
9936 seconds, just send back a destroy and take them off the list.
9939 Changes in version 0.0.9.4 - 2005-02-03
9940 o Bugfixes on 0.0.9:
9941 - Fix an assert bug that took down most of our servers: when
9942 a server claims to have 1 GB of bandwidthburst, don't
9944 - Don't crash as badly if we have spawned the max allowed number
9945 of dnsworkers, or we're out of file descriptors.
9946 - Block more file-sharing ports in the default exit policy.
9947 - MaxConn is now automatically set to the hard limit of max
9948 file descriptors we're allowed (ulimit -n), minus a few for
9950 - Give a clearer message when servers need to raise their
9951 ulimit -n when they start running out of file descriptors.
9952 - SGI Compatibility patches from Jan Schaumann.
9953 - Tolerate a corrupt cached directory better.
9954 - When a dirserver hasn't approved your server, list which one.
9955 - Go into soft hibernation after 95% of the bandwidth is used,
9956 not 99%. This is especially important for daily hibernators who
9957 have a small accounting max. Hopefully it will result in fewer
9958 cut connections when the hard hibernation starts.
9959 - Load-balance better when using servers that claim more than
9960 800kB/s of capacity.
9961 - Make NT services work (experimental, only used if compiled in).
9964 Changes in version 0.0.9.3 - 2005-01-21
9965 o Bugfixes on 0.0.9:
9966 - Backport the cpu use fixes from main branch, so busy servers won't
9967 need as much processor time.
9968 - Work better when we go offline and then come back, or when we
9969 run Tor at boot before the network is up. We do this by
9970 optimistically trying to fetch a new directory whenever an
9971 application request comes in and we think we're offline -- the
9972 human is hopefully a good measure of when the network is back.
9973 - Backport some minimal hidserv bugfixes: keep rend circuits open as
9974 long as you keep using them; actually publish hidserv descriptors
9975 shortly after they change, rather than waiting 20-40 minutes.
9976 - Enable Mac startup script by default.
9977 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
9978 - When you update AllowUnverifiedNodes or FirewallPorts via the
9979 controller's setconf feature, we were always appending, never
9981 - When you update HiddenServiceDir via setconf, it was screwing up
9982 the order of reading the lines, making it fail.
9983 - Do not rewrite a cached directory back to the cache; otherwise we
9984 will think it is recent and not fetch a newer one on startup.
9985 - Workaround for webservers that lie about Content-Encoding: Tor
9986 now tries to autodetect compressed directories and compression
9987 itself. This lets us Proxypass dir fetches through apache.
9990 Changes in version 0.0.9.2 - 2005-01-04
9991 o Bugfixes on 0.0.9 (crashes and asserts):
9992 - Fix an assert on startup when the disk is full and you're logging
9994 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
9995 style address, then we'd crash.
9996 - Fix an assert trigger when the running-routers string we get from
9997 a dirserver is broken.
9998 - Make worker threads start and run on win32. Now win32 servers
10000 - Bandaid (not actually fix, but now it doesn't crash) an assert
10001 where the dns worker dies mysteriously and the main Tor process
10002 doesn't remember anything about the address it was resolving.
10004 o Bugfixes on 0.0.9 (Win32):
10005 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
10006 name out of the warning/assert messages.
10007 - Fix a superficial "unhandled error on read" bug on win32.
10008 - The win32 installer no longer requires a click-through for our
10009 license, since our Free Software license grants rights but does not
10011 - Win32: When connecting to a dirserver fails, try another one
10012 immediately. (This was already working for non-win32 Tors.)
10013 - Stop trying to parse $HOME on win32 when hunting for default
10015 - Make tor-resolve.c work on win32 by calling network_init().
10017 o Bugfixes on 0.0.9 (other):
10018 - Make 0.0.9.x build on Solaris again.
10019 - Due to a fencepost error, we were blowing away the \n when reporting
10020 confvalue items in the controller. So asking for multiple config
10021 values at once couldn't work.
10022 - When listing circuits that are pending on an opening OR connection,
10023 if we're an OR we were listing circuits that *end* at us as
10024 being pending on every listener, dns/cpu worker, etc. Stop that.
10025 - Dirservers were failing to create 'running-routers' or 'directory'
10026 strings if we had more than some threshold of routers. Fix them so
10027 they can handle any number of routers.
10028 - Fix a superficial "Duplicate mark for close" bug.
10029 - Stop checking for clock skew for OR connections, even for servers.
10030 - Fix a fencepost error that was chopping off the last letter of any
10031 nickname that is the maximum allowed nickname length.
10032 - Update URLs in log messages so they point to the new website.
10033 - Fix a potential problem in mangling server private keys while
10034 writing to disk (not triggered yet, as far as we know).
10035 - Include the licenses for other free software we include in Tor,
10036 now that we're shipping binary distributions more regularly.
10039 Changes in version 0.0.9.1 - 2004-12-15
10040 o Bugfixes on 0.0.9:
10041 - Make hibernation actually work.
10042 - Make HashedControlPassword config option work.
10043 - When we're reporting event circuit status to a controller,
10044 don't use the stream status code.
10047 Changes in version 0.0.9 - 2004-12-12
10049 - Clean up manpage and torrc.sample file.
10050 - Clean up severities and text of log warnings.
10052 - Make servers trigger an assert when they enter hibernation.
10055 Changes in version 0.0.9rc7 - 2004-12-08
10056 o Bugfixes on 0.0.9rc:
10057 - Fix a stack-trashing crash when an exit node begins hibernating.
10058 - Avoid looking at unallocated memory while considering which
10059 ports we need to build circuits to cover.
10060 - Stop a sigpipe: when an 'end' cell races with eof from the app,
10061 we shouldn't hold-open-until-flush if the eof arrived first.
10062 - Fix a bug with init_cookie_authentication() in the controller.
10063 - When recommending new-format log lines, if the upper bound is
10064 LOG_ERR, leave it implicit.
10066 o Bugfixes on 0.0.8.1:
10067 - Fix a whole slew of memory leaks.
10068 - Fix isspace() and friends so they still make Solaris happy
10069 but also so they don't trigger asserts on win32.
10070 - Fix parse_iso_time on platforms without strptime (eg win32).
10071 - win32: tolerate extra "readable" events better.
10072 - win32: when being multithreaded, leave parent fdarray open.
10073 - Make unit tests work on win32.
10076 Changes in version 0.0.9rc6 - 2004-12-06
10077 o Bugfixes on 0.0.9pre:
10078 - Clean up some more integer underflow opportunities (not exploitable
10080 - While hibernating, hup should not regrow our listeners.
10081 - Send an end to the streams we close when we hibernate, rather
10082 than just chopping them off.
10083 - React to eof immediately on non-open edge connections.
10085 o Bugfixes on 0.0.8.1:
10086 - Calculate timeout for waiting for a connected cell from the time
10087 we sent the begin cell, not from the time the stream started. If
10088 it took a long time to establish the circuit, we would time out
10089 right after sending the begin cell.
10090 - Fix router_compare_addr_to_addr_policy: it was not treating a port
10091 of * as always matching, so we were picking reject *:* nodes as
10092 exit nodes too. Oops.
10095 - New circuit building strategy: keep a list of ports that we've
10096 used in the past 6 hours, and always try to have 2 circuits open
10097 or on the way that will handle each such port. Seed us with port
10098 80 so web users won't complain that Tor is "slow to start up".
10099 - Make kill -USR1 dump more useful stats about circuits.
10100 - When warning about retrying or giving up, print the address, so
10101 the user knows which one it's talking about.
10102 - If you haven't used a clean circuit in an hour, throw it away,
10103 just to be on the safe side. (This means after 6 hours a totally
10104 unused Tor client will have no circuits open.)
10107 Changes in version 0.0.9rc5 - 2004-12-01
10108 o Bugfixes on 0.0.8.1:
10109 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
10110 - Let resolve conns retry/expire also, rather than sticking around
10112 - If we are using select, make sure we stay within FD_SETSIZE.
10114 o Bugfixes on 0.0.9pre:
10115 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
10116 but doesn't seem to be currently; thanks to Ilja van Sprundel for
10118 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
10119 instead. Impose minima and maxima for all *Period options; impose
10120 even tighter maxima for fetching if we are a caching dirserver.
10121 Clip rather than rejecting.
10122 - Fetch cached running-routers from servers that serve it (that is,
10123 authdirservers and servers running 0.0.9rc5-cvs or later.)
10126 - Accept *:706 (silc) in default exit policy.
10127 - Implement new versioning format for post 0.1.
10128 - Support "foo.nickname.exit" addresses, to let Alice request the
10129 address "foo" as viewed by exit node "nickname". Based on a patch
10131 - Make tor --version --version dump the cvs Id of every file.
10134 Changes in version 0.0.9rc4 - 2004-11-28
10135 o Bugfixes on 0.0.8.1:
10136 - Make windows sockets actually non-blocking (oops), and handle
10137 win32 socket errors better.
10139 o Bugfixes on 0.0.9rc1:
10140 - Actually catch the -USR2 signal.
10143 Changes in version 0.0.9rc3 - 2004-11-25
10144 o Bugfixes on 0.0.8.1:
10145 - Flush the log file descriptor after we print "Tor opening log file",
10146 so we don't see those messages days later.
10148 o Bugfixes on 0.0.9rc1:
10149 - Make tor-resolve work again.
10150 - Avoid infinite loop in tor-resolve if tor hangs up on it.
10151 - Fix an assert trigger for clients/servers handling resolves.
10154 Changes in version 0.0.9rc2 - 2004-11-24
10155 o Bugfixes on 0.0.9rc1:
10156 - I broke socks5 support while fixing the eof bug.
10157 - Allow unitless bandwidths and intervals; they default to bytes
10159 - New servers don't start out hibernating; they are active until
10160 they run out of bytes, so they have a better estimate of how
10161 long it takes, and so their operators can know they're working.
10164 Changes in version 0.0.9rc1 - 2004-11-23
10165 o Bugfixes on 0.0.8.1:
10166 - Finally fix a bug that's been plaguing us for a year:
10167 With high load, circuit package window was reaching 0. Whenever
10168 we got a circuit-level sendme, we were reading a lot on each
10169 socket, but only writing out a bit. So we would eventually reach
10170 eof. This would be noticed and acted on even when there were still
10171 bytes sitting in the inbuf.
10172 - When poll() is interrupted, we shouldn't believe the revents values.
10174 o Bugfixes on 0.0.9pre6:
10175 - Fix hibernate bug that caused pre6 to be broken.
10176 - Don't keep rephist info for routers that haven't had activity for
10177 24 hours. (This matters now that clients have keys, since we track
10179 - Never call close_temp_logs while validating log options.
10180 - Fix backslash-escaping on tor.sh.in and torctl.in.
10183 - Implement weekly/monthly/daily accounting: now you specify your
10184 hibernation properties by
10185 AccountingMax N bytes|KB|MB|GB|TB
10186 AccountingStart day|week|month [day] HH:MM
10187 Defaults to "month 1 0:00".
10188 - Let bandwidth and interval config options be specified as 5 bytes,
10189 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
10190 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
10191 get back to normal.)
10192 - If your requested entry or exit node has advertised bandwidth 0,
10194 - Be more greedy about filling up relay cells -- we try reading again
10195 once we've processed the stuff we read, in case enough has arrived
10196 to fill the last cell completely.
10197 - Apply NT service patch from Osamu Fujino. Still needs more work.
10200 Changes in version 0.0.9pre6 - 2004-11-15
10201 o Bugfixes on 0.0.8.1:
10202 - Fix assert failure on malformed socks4a requests.
10203 - Use identity comparison, not nickname comparison, to choose which
10204 half of circuit-ID-space each side gets to use. This is needed
10205 because sometimes we think of a router as a nickname, and sometimes
10206 as a hex ID, and we can't predict what the other side will do.
10207 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
10208 write() call will fail and we handle it there.
10209 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
10210 and smartlist_len, which are two major profiling offenders.
10212 o Bugfixes on 0.0.9pre5:
10213 - Fix a bug in read_all that was corrupting config files on windows.
10214 - When we're raising the max number of open file descriptors to
10215 'unlimited', don't log that we just raised it to '-1'.
10216 - Include event code with events, as required by control-spec.txt.
10217 - Don't give a fingerprint when clients do --list-fingerprint:
10218 it's misleading, because it will never be the same again.
10219 - Stop using strlcpy in tor_strndup, since it was slowing us
10221 - Remove warn on startup about missing cached-directory file.
10222 - Make kill -USR1 work again.
10223 - Hibernate if we start tor during the "wait for wakeup-time" phase
10224 of an accounting interval. Log our hibernation plans better.
10225 - Authoritative dirservers now also cache their directory, so they
10226 have it on start-up.
10229 - Fetch running-routers; cache running-routers; compress
10230 running-routers; serve compressed running-routers.z
10231 - Add NSI installer script contributed by J Doe.
10232 - Commit VC6 and VC7 workspace/project files.
10233 - Commit a tor.spec for making RPM files, with help from jbash.
10234 - Add contrib/torctl.in contributed by Glenn Fink.
10235 - Implement the control-spec's SAVECONF command, to write your
10236 configuration to torrc.
10237 - Get cookie authentication for the controller closer to working.
10238 - Include control-spec.txt in the tarball.
10239 - When set_conf changes our server descriptor, upload a new copy.
10240 But don't upload it too often if there are frequent changes.
10241 - Document authentication config in man page, and document signals
10243 - Clean up confusing parts of man page and torrc.sample.
10244 - Make expand_filename handle ~ and ~username.
10245 - Use autoconf to enable largefile support where necessary. Use
10246 ftello where available, since ftell can fail at 2GB.
10247 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
10248 log more informatively.
10249 - Give a slightly more useful output for "tor -h".
10250 - Refuse application socks connections to port 0.
10251 - Check clock skew for verified servers, but allow unverified
10252 servers and clients to have any clock skew.
10253 - Break DirFetchPostPeriod into:
10254 - DirFetchPeriod for fetching full directory,
10255 - StatusFetchPeriod for fetching running-routers,
10256 - DirPostPeriod for posting server descriptor,
10257 - RendPostPeriod for posting hidden service descriptors.
10258 - Make sure the hidden service descriptors are at a random offset
10259 from each other, to hinder linkability.
10262 Changes in version 0.0.9pre5 - 2004-11-09
10263 o Bugfixes on 0.0.9pre4:
10264 - Fix a seg fault in unit tests (doesn't affect main program).
10265 - Fix an assert bug where a hidden service provider would fail if
10266 the first hop of his rendezvous circuit was down.
10267 - Hidden service operators now correctly handle version 1 style
10268 INTRODUCE1 cells (nobody generates them still, so not a critical
10270 - If do_hup fails, actually notice.
10271 - Handle more errnos from accept() without closing the listener.
10272 Some OpenBSD machines were closing their listeners because
10273 they ran out of file descriptors.
10274 - Send resolve cells to exit routers that are running a new
10275 enough version of the resolve code to work right.
10276 - Better handling of winsock includes on non-MSV win32 compilers.
10277 - Some people had wrapped their tor client/server in a script
10278 that would restart it whenever it died. This did not play well
10279 with our "shut down if your version is obsolete" code. Now people
10280 don't fetch a new directory if their local cached version is
10282 - Make our autogen.sh work on ksh as well as bash.
10285 - Hibernation: New config option "AccountingMaxKB" lets you
10286 set how many KBytes per month you want to allow your server to
10287 consume. Rather than spreading those bytes out evenly over the
10288 month, we instead hibernate for some of the month and pop up
10289 at a deterministic time, work until the bytes are consumed, then
10290 hibernate again. Config option "MonthlyAccountingStart" lets you
10291 specify which day of the month your billing cycle starts on.
10292 - Control interface: a separate program can now talk to your
10293 client/server over a socket, and get/set config options, receive
10294 notifications of circuits and streams starting/finishing/dying,
10295 bandwidth used, etc. The next step is to get some GUIs working.
10296 Let us know if you want to help out. See doc/control-spec.txt .
10297 - Ship a contrib/tor-control.py as an example script to interact
10298 with the control port.
10299 - "tor --hash-password zzyxz" will output a salted password for
10300 use in authenticating to the control interface.
10301 - New log format in config:
10302 "Log minsev[-maxsev] stdout|stderr|syslog" or
10303 "Log minsev[-maxsev] file /var/foo"
10306 - DirPolicy config option, to let people reject incoming addresses
10307 from their dirserver.
10308 - "tor --list-fingerprint" will list your identity key fingerprint
10310 - Add "pass" target for RedirectExit, to make it easier to break
10311 out of a sequence of RedirectExit rules.
10312 - Clients now generate a TLS cert too, in preparation for having
10313 them act more like real nodes.
10314 - Ship src/win32/ in the tarball, so people can use it to build.
10315 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
10317 - New "router-status" line in directory, to better bind each verified
10318 nickname to its identity key.
10319 - Deprecate unofficial config option abbreviations, and abbreviations
10320 not on the command line.
10321 - Add a pure-C tor-resolve implementation.
10322 - Use getrlimit and friends to ensure we can reach MaxConn (currently
10323 1024) file descriptors.
10325 o Code security improvements, inspired by Ilja:
10326 - Replace sprintf with snprintf. (I think they were all safe, but
10328 - Replace strcpy/strncpy with strlcpy in more places.
10329 - Avoid strcat; use snprintf or strlcat instead.
10330 - snprintf wrapper with consistent (though not C99) overflow behavior.
10333 Changes in version 0.0.9pre4 - 2004-10-17
10334 o Bugfixes on 0.0.9pre3:
10335 - If the server doesn't specify an exit policy, use the real default
10336 exit policy, not reject *:*.
10337 - Ignore fascistfirewall when uploading/downloading hidden service
10338 descriptors, since we go through Tor for those; and when using
10339 an HttpProxy, since we assume it can reach them all.
10340 - When looking for an authoritative dirserver, use only the ones
10341 configured at boot. Don't bother looking in the directory.
10342 - The rest of the fix for get_default_conf_file() on older win32.
10343 - Make 'Routerfile' config option obsolete.
10346 - New 'MyFamily nick1,...' config option for a server to
10347 specify other servers that shouldn't be used in the same circuit
10348 with it. Only believed if nick1 also specifies us.
10349 - New 'NodeFamily nick1,nick2,...' config option for a client to
10350 specify nodes that it doesn't want to use in the same circuit.
10351 - New 'Redirectexit pattern address:port' config option for a
10352 server to redirect exit connections, e.g. to a local squid.
10355 Changes in version 0.0.9pre3 - 2004-10-13
10356 o Bugfixes on 0.0.8.1:
10357 - Better torrc example lines for dirbindaddress and orbindaddress.
10358 - Improved bounds checking on parsed ints (e.g. config options and
10359 the ones we find in directories.)
10360 - Better handling of size_t vs int, so we're more robust on 64
10362 - Fix the rest of the bug where a newly started OR would appear
10363 as unverified even after we've added his fingerprint and hupped
10365 - Fix a bug from 0.0.7: when read() failed on a stream, we would
10366 close it without sending back an end. So 'connection refused'
10367 would simply be ignored and the user would get no response.
10369 o Bugfixes on 0.0.9pre2:
10370 - Serving the cached-on-disk directory to people is bad. We now
10371 provide no directory until we've fetched a fresh one.
10372 - Workaround for bug on windows where cached-directories get crlf
10374 - Make get_default_conf_file() work on older windows too.
10375 - If we write a *:* exit policy line in the descriptor, don't write
10376 any more exit policy lines.
10379 - Use only 0.0.9pre1 and later servers for resolve cells.
10380 - Make the dirservers file obsolete.
10381 - Include a dir-signing-key token in directories to tell the
10382 parsing entity which key is being used to sign.
10383 - Remove the built-in bulky default dirservers string.
10384 - New config option "Dirserver %s:%d [fingerprint]", which can be
10385 repeated as many times as needed. If no dirservers specified,
10386 default to moria1,moria2,tor26.
10387 - Make moria2 advertise a dirport of 80, so people behind firewalls
10388 will be able to get a directory.
10389 - Http proxy support
10390 - Dirservers translate requests for http://%s:%d/x to /x
10391 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
10392 be routed through this host.
10393 - Clients ask for /tor/x rather than /x for new enough dirservers.
10394 This way we can one day coexist peacefully with apache.
10395 - Clients specify a "Host: %s%d" http header, to be compatible
10396 with more proxies, and so running squid on an exit node can work.
10399 Changes in version 0.0.8.1 - 2004-10-13
10401 - Fix a seg fault that can be triggered remotely for Tor
10402 clients/servers with an open dirport.
10403 - Fix a rare assert trigger, where routerinfos for entries in
10404 our cpath would expire while we're building the path.
10405 - Fix a bug in OutboundBindAddress so it (hopefully) works.
10406 - Fix a rare seg fault for people running hidden services on
10407 intermittent connections.
10408 - Fix a bug in parsing opt keywords with objects.
10409 - Fix a stale pointer assert bug when a stream detaches and
10411 - Fix a string format vulnerability (probably not exploitable)
10412 in reporting stats locally.
10413 - Fix an assert trigger: sometimes launching circuits can fail
10414 immediately, e.g. because too many circuits have failed recently.
10415 - Fix a compile warning on 64 bit platforms.
10418 Changes in version 0.0.9pre2 - 2004-10-03
10420 - Make fetching a cached directory work for 64-bit platforms too.
10421 - Make zlib.h a required header, not an optional header.
10424 Changes in version 0.0.9pre1 - 2004-10-01
10426 - Stop using separate defaults for no-config-file and
10427 empty-config-file. Now you have to explicitly turn off SocksPort,
10428 if you don't want it open.
10429 - Fix a bug in OutboundBindAddress so it (hopefully) works.
10430 - Improve man page to mention more of the 0.0.8 features.
10431 - Fix a rare seg fault for people running hidden services on
10432 intermittent connections.
10433 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
10435 - Fix more dns related bugs: send back resolve_failed and end cells
10436 more reliably when the resolve fails, rather than closing the
10437 circuit and then trying to send the cell. Also attach dummy resolve
10438 connections to a circuit *before* calling dns_resolve(), to fix
10439 a bug where cached answers would never be sent in RESOLVED cells.
10440 - When we run out of disk space, or other log writing error, don't
10441 crash. Just stop logging to that log and continue.
10442 - We were starting to daemonize before we opened our logs, so if
10443 there were any problems opening logs, we would complain to stderr,
10444 which wouldn't work, and then mysteriously exit.
10445 - Fix a rare bug where sometimes a verified OR would connect to us
10446 before he'd uploaded his descriptor, which would cause us to
10447 assign conn->nickname as though he's unverified. Now we look through
10448 the fingerprint list to see if he's there.
10449 - Fix a rare assert trigger, where routerinfos for entries in
10450 our cpath would expire while we're building the path.
10453 - Clients can ask dirservers for /dir.z to get a compressed version
10454 of the directory. Only works for servers running 0.0.9, of course.
10455 - Make clients cache directories and use them to seed their router
10456 lists at startup. This means clients have a datadir again.
10457 - Configuration infrastructure support for warning on obsolete
10459 - Respond to content-encoding headers by trying to uncompress as
10461 - Reply with a deflated directory when a client asks for "dir.z".
10462 We could use allow-encodings instead, but allow-encodings isn't
10463 specified in HTTP 1.0.
10464 - Raise the max dns workers from 50 to 100.
10465 - Discourage people from setting their dirfetchpostperiod more often
10466 than once per minute.
10467 - Protect dirservers from overzealous descriptor uploading -- wait
10468 10 seconds after directory gets dirty, before regenerating.
10471 Changes in version 0.0.8 - 2004-08-25
10472 o Port it to SunOS 5.9 / Athena
10475 Changes in version 0.0.8rc2 - 2004-08-20
10476 o Make it compile on cygwin again.
10477 o When picking unverified routers, skip those with low uptime and/or
10478 low bandwidth, depending on what properties you care about.
10481 Changes in version 0.0.8rc1 - 2004-08-18
10482 o Changes from 0.0.7.3:
10484 - Fix assert triggers: if the other side returns an address 0.0.0.0,
10485 don't put it into the client dns cache.
10486 - If a begin failed due to exit policy, but we believe the IP address
10487 should have been allowed, switch that router to exitpolicy reject *:*
10488 until we get our next directory.
10490 - Clients choose nodes proportional to advertised bandwidth.
10491 - Avoid using nodes with low uptime as introduction points.
10492 - Handle servers with dynamic IP addresses: don't replace
10493 options->Address with the resolved one at startup, and
10494 detect our address right before we make a routerinfo each time.
10495 - 'FascistFirewall' option to pick dirservers and ORs on specific
10496 ports; plus 'FirewallPorts' config option to tell FascistFirewall
10497 which ports are open. (Defaults to 80,443)
10498 - Be more aggressive about trying to make circuits when the network
10499 has changed (e.g. when you unsuspend your laptop).
10500 - Check for time skew on http headers; report date in response to
10502 - If the entrynode config line has only one node, don't pick it as
10504 - Add strict{entry|exit}nodes config options. If set to 1, then
10505 we refuse to build circuits that don't include the specified entry
10507 - OutboundBindAddress config option, to bind to a specific
10508 IP address for outgoing connect()s.
10509 - End truncated log entries (e.g. directories) with "[truncated]".
10511 o Patches to 0.0.8preX:
10513 - Patches to compile and run on win32 again (maybe)?
10514 - Fix crash when looking for ~/.torrc with no $HOME set.
10515 - Fix a race bug in the unit tests.
10516 - Handle verified/unverified name collisions better when new
10517 routerinfo's arrive in a directory.
10518 - Sometimes routers were getting entered into the stats before
10519 we'd assigned their identity_digest. Oops.
10520 - Only pick and establish intro points after we've gotten a
10523 - AllowUnverifiedNodes config option to let circuits choose no-name
10524 routers in entry,middle,exit,introduction,rendezvous positions.
10525 Allow middle and rendezvous positions by default.
10526 - Add a man page for tor-resolve.
10529 Changes in version 0.0.7.3 - 2004-08-12
10530 o Stop dnsworkers from triggering an assert failure when you
10531 ask them to resolve the host "".
10534 Changes in version 0.0.8pre3 - 2004-08-09
10535 o Changes from 0.0.7.2:
10536 - Allow multiple ORs with same nickname in routerlist -- now when
10537 people give us one identity key for a nickname, then later
10538 another, we don't constantly complain until the first expires.
10539 - Remember used bandwidth (both in and out), and publish 15-minute
10540 snapshots for the past day into our descriptor.
10541 - You can now fetch $DIRURL/running-routers to get just the
10542 running-routers line, not the whole descriptor list. (But
10543 clients don't use this yet.)
10544 - When people mistakenly use Tor as an http proxy, point them
10545 at the tor-doc.html rather than the INSTALL.
10546 - Remove our mostly unused -- and broken -- hex_encode()
10547 function. Use base16_encode() instead. (Thanks to Timo Lindfors
10548 for pointing out this bug.)
10549 - Rotate onion keys every 12 hours, not every 2 hours, so we have
10550 fewer problems with people using the wrong key.
10551 - Change the default exit policy to reject the default edonkey,
10552 kazaa, gnutella ports.
10553 - Add replace_file() to util.[ch] to handle win32's rename().
10555 o Changes from 0.0.8preX:
10556 - Fix two bugs in saving onion keys to disk when rotating, so
10557 hopefully we'll get fewer people using old onion keys.
10558 - Fix an assert error that was making SocksPolicy not work.
10559 - Be willing to expire routers that have an open dirport -- it's
10560 just the authoritative dirservers we want to not forget.
10561 - Reject tor-resolve requests for .onion addresses early, so we
10562 don't build a whole rendezvous circuit and then fail.
10563 - When you're warning a server that he's unverified, don't cry
10564 wolf unpredictably.
10565 - Fix a race condition: don't try to extend onto a connection
10566 that's still handshaking.
10567 - For servers in clique mode, require the conn to be open before
10568 you'll choose it for your path.
10569 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
10570 end relay cell, etc.
10571 - Measure bandwidth capacity over the last 24 hours, not just 12
10572 - Bugfix: authoritative dirservers were making and signing a new
10573 directory for each client, rather than reusing the cached one.
10576 Changes in version 0.0.8pre2 - 2004-08-04
10577 o Changes from 0.0.7.2:
10579 - Check directory signature _before_ you decide whether you're
10580 you're running an obsolete version and should exit.
10581 - Check directory signature _before_ you parse the running-routers
10582 list to decide who's running or verified.
10583 - Bugfixes and features:
10584 - Check return value of fclose while writing to disk, so we don't
10585 end up with broken files when servers run out of disk space.
10586 - Log a warning if the user uses an unsafe socks variant, so people
10587 are more likely to learn about privoxy or socat.
10588 - Dirservers now include RFC1123-style dates in the HTTP headers,
10589 which one day we will use to better detect clock skew.
10591 o Changes from 0.0.8pre1:
10592 - Make it compile without warnings again on win32.
10593 - Log a warning if you're running an unverified server, to let you
10594 know you might want to get it verified.
10595 - Only pick a default nickname if you plan to be a server.
10598 Changes in version 0.0.8pre1 - 2004-07-23
10600 - Made our unit tests compile again on OpenBSD 3.5, and tor
10601 itself compile again on OpenBSD on a sparc64.
10602 - We were neglecting milliseconds when logging on win32, so
10603 everything appeared to happen at the beginning of each second.
10605 o Protocol changes:
10606 - 'Extend' relay cell payloads now include the digest of the
10607 intended next hop's identity key. Now we can verify that we're
10608 extending to the right router, and also extend to routers we
10609 hadn't heard of before.
10612 - Tor nodes can now act as relays (with an advertised ORPort)
10613 without being manually verified by the dirserver operators.
10614 - Uploaded descriptors of unverified routers are now accepted
10615 by the dirservers, and included in the directory.
10616 - Verified routers are listed by nickname in the running-routers
10617 list; unverified routers are listed as "$<fingerprint>".
10618 - We now use hash-of-identity-key in most places rather than
10619 nickname or addr:port, for improved security/flexibility.
10620 - To avoid Sybil attacks, paths still use only verified servers.
10621 But now we have a chance to play around with hybrid approaches.
10622 - Nodes track bandwidth usage to estimate capacity (not used yet).
10623 - ClientOnly option for nodes that never want to become servers.
10624 - Directory caching.
10625 - "AuthoritativeDir 1" option for the official dirservers.
10626 - Now other nodes (clients and servers) will cache the latest
10627 directory they've pulled down.
10628 - They can enable their DirPort to serve it to others.
10629 - Clients will pull down a directory from any node with an open
10630 DirPort, and check the signature/timestamp correctly.
10631 - Authoritative dirservers now fetch directories from other
10632 authdirservers, to stay better synced.
10633 - Running-routers list tells who's down also, along with noting
10634 if they're verified (listed by nickname) or unverified (listed
10636 - Allow dirservers to serve running-router list separately.
10637 This isn't used yet.
10638 - ORs connect-on-demand to other ORs
10639 - If you get an extend cell to an OR you're not connected to,
10640 connect, handshake, and forward the create cell.
10641 - The authoritative dirservers stay connected to everybody,
10642 and everybody stays connected to 0.0.7 servers, but otherwise
10643 clients/servers expire unused connections after 5 minutes.
10644 - When servers get a sigint, they delay 30 seconds (refusing new
10645 connections) then exit. A second sigint causes immediate exit.
10646 - File and name management:
10647 - Look for .torrc if no CONFDIR "torrc" is found.
10648 - If no datadir is defined, then choose, make, and secure ~/.tor
10650 - If torrc not found, exitpolicy reject *:*.
10651 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
10652 - If no nickname is defined, derive default from hostname.
10653 - Rename secret key files, e.g. identity.key -> secret_id_key,
10654 to discourage people from mailing their identity key to tor-ops.
10655 - Refuse to build a circuit before the directory has arrived --
10656 it won't work anyway, since you won't know the right onion keys
10658 - Try other dirservers immediately if the one you try is down. This
10659 should tolerate down dirservers better now.
10660 - Parse tor version numbers so we can do an is-newer-than check
10661 rather than an is-in-the-list check.
10662 - New socks command 'resolve', to let us shim gethostbyname()
10664 - A 'tor_resolve' script to access the socks resolve functionality.
10665 - A new socks-extensions.txt doc file to describe our
10666 interpretation and extensions to the socks protocols.
10667 - Add a ContactInfo option, which gets published in descriptor.
10668 - Publish OR uptime in descriptor (and thus in directory) too.
10669 - Write tor version at the top of each log file
10670 - New docs in the tarball:
10672 - Document that you should proxy your SSL traffic too.
10675 Changes in version 0.0.7.2 - 2004-07-07
10676 o A better fix for the 0.0.0.0 problem, that will hopefully
10677 eliminate the remaining related assertion failures.
10680 Changes in version 0.0.7.1 - 2004-07-04
10681 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
10682 since internally we use 0.0.0.0 to signify "not yet resolved".
10685 Changes in version 0.0.7 - 2004-06-07
10686 o Updated the man page to reflect the new features.
10689 Changes in version 0.0.7rc2 - 2004-06-06
10690 o Changes from 0.0.7rc1:
10691 - Make it build on Win32 again.
10692 o Changes from 0.0.6.2:
10693 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
10697 Changes in version 0.0.7rc1 - 2004-06-02
10699 - On sighup, we were adding another log without removing the first
10700 one. So log messages would get duplicated n times for n sighups.
10701 - Several cases of using a connection after we'd freed it. The
10702 problem was that connections that are pending resolve are in both
10703 the pending_resolve tree, and also the circuit's resolving_streams
10704 list. When you want to remove one, you must remove it from both.
10705 - Fix a double-mark-for-close where an end cell arrived for a
10706 resolving stream, and then the resolve failed.
10707 - Check directory signatures based on name of signer, not on whom
10708 we got the directory from. This will let us cache directories more
10711 - Crank up some of our constants to handle more users.
10714 Changes in version 0.0.7pre1 - 2004-06-02
10715 o Fixes for crashes and other obnoxious bugs:
10716 - Fix an epipe bug: sometimes when directory connections failed
10717 to connect, we would give them a chance to flush before closing
10719 - When we detached from a circuit because of resolvefailed, we
10720 would immediately try the same circuit twice more, and then
10721 give up on the resolve thinking we'd tried three different
10723 - Limit the number of intro circuits we'll attempt to build for a
10724 hidden service per 15-minute period.
10725 - Check recommended-software string *early*, before actually parsing
10726 the directory. Thus we can detect an obsolete version and exit,
10727 even if the new directory format doesn't parse.
10728 o Fixes for security bugs:
10729 - Remember which nodes are dirservers when you startup, and if a
10730 random OR enables his dirport, don't automatically assume he's
10731 a trusted dirserver.
10733 - Directory connections were asking the wrong poll socket to
10734 start writing, and not asking themselves to start writing.
10735 - When we detached from a circuit because we sent a begin but
10736 didn't get a connected, we would use it again the first time;
10737 but after that we would correctly switch to a different one.
10738 - Stop warning when the first onion decrypt attempt fails; they
10739 will sometimes legitimately fail now that we rotate keys.
10740 - Override unaligned-access-ok check when $host_cpu is ia64 or
10741 arm. Apparently they allow it but the kernel whines.
10742 - Dirservers try to reconnect periodically too, in case connections
10744 - Fix some memory leaks in directory servers.
10745 - Allow backslash in Win32 filenames.
10746 - Made Tor build complain-free on FreeBSD, hopefully without
10747 breaking other BSD builds. We'll see.
10749 - Doxygen markup on all functions and global variables.
10750 - Make directory functions update routerlist, not replace it. So
10751 now directory disagreements are not so critical a problem.
10752 - Remove the upper limit on number of descriptors in a dirserver's
10753 directory (not that we were anywhere close).
10754 - Allow multiple logfiles at different severity ranges.
10755 - Allow *BindAddress to specify ":port" rather than setting *Port
10756 separately. Allow multiple instances of each BindAddress config
10757 option, so you can bind to multiple interfaces if you want.
10758 - Allow multiple exit policy lines, which are processed in order.
10759 Now we don't need that huge line with all the commas in it.
10760 - Enable accept/reject policies on SOCKS connections, so you can bind
10761 to 0.0.0.0 but still control who can use your OP.
10764 Changes in version 0.0.6.2 - 2004-05-16
10765 o Our integrity-checking digest was checking only the most recent cell,
10766 not the previous cells like we'd thought.
10767 Thanks to Stefan Mark for finding the flaw!
10770 Changes in version 0.0.6.1 - 2004-05-06
10771 o Fix two bugs in our AES counter-mode implementation (this affected
10772 onion-level stream encryption, but not TLS-level). It turns
10773 out we were doing something much more akin to a 16-character
10774 polyalphabetic cipher. Oops.
10775 Thanks to Stefan Mark for finding the flaw!
10776 o Retire moria3 as a directory server, and add tor26 as a directory
10780 Changes in version 0.0.6 - 2004-05-02
10781 [version bump only]
10784 Changes in version 0.0.6rc4 - 2004-05-01
10785 o Update the built-in dirservers list to use the new directory format
10786 o Fix a rare seg fault: if a node offering a hidden service attempts
10787 to build a circuit to Alice's rendezvous point and fails before it
10788 reaches the last hop, it retries with a different circuit, but
10790 o Handle windows socket errors correctly.
10793 Changes in version 0.0.6rc3 - 2004-04-28
10794 o Don't expire non-general excess circuits (if we had enough
10795 circuits open, we were expiring rendezvous circuits -- even
10796 when they had a stream attached. oops.)
10797 o Fetch randomness from /dev/urandom better (not via fopen/fread)
10798 o Better debugging for tls errors
10799 o Some versions of openssl have an SSL_pending function that erroneously
10800 returns bytes when there is a non-application record pending.
10801 o Set Content-Type on the directory and hidserv descriptor.
10802 o Remove IVs from cipher code, since AES-ctr has none.
10803 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
10804 o We were using an array of length zero in a few places.
10805 o win32's gethostbyname can't resolve an IP to an IP.
10806 o win32's close can't close a socket.
10809 Changes in version 0.0.6rc2 - 2004-04-26
10810 o Fix a bug where we were closing tls connections intermittently.
10811 It turns out openssl keeps its errors around -- so if an error
10812 happens, and you don't ask about it, and then another openssl
10813 operation happens and succeeds, and you ask if there was an error,
10814 it tells you about the first error. Fun fun.
10815 o Fix a bug that's been lurking since 27 may 03 (!)
10816 When passing back a destroy cell, we would use the wrong circ id.
10817 'Mostly harmless', but still worth fixing.
10818 o Since we don't support truncateds much, don't bother sending them;
10819 just close the circ.
10820 o check for <machine/limits.h> so we build on NetBSD again (I hope).
10821 o don't crash if a conn that sent a begin has suddenly lost its circuit
10822 (this was quite rare).
10825 Changes in version 0.0.6rc1 - 2004-04-25
10826 o We now rotate link (tls context) keys and onion keys.
10827 o CREATE cells now include oaep padding, so you can tell
10828 if you decrypted them correctly.
10829 o Add bandwidthburst to server descriptor.
10830 o Directories now say which dirserver signed them.
10831 o Use a tor_assert macro that logs failed assertions too.
10834 Changes in version 0.0.6pre5 - 2004-04-18
10835 o changes from 0.0.6pre4:
10836 - make tor build on broken freebsd 5.2 installs
10837 - fix a failed assert when you try an intro point, get a nack, and try
10838 a second one and it works.
10839 - when alice uses a port that the hidden service doesn't accept,
10840 it now sends back an end cell (denied by exit policy). otherwise
10841 alice would just have to wait to time out.
10842 - fix another rare bug: when we had tried all the intro
10843 points for a hidden service, we fetched the descriptor
10844 again, but we left our introcirc thinking it had already
10845 sent an intro, so it kept waiting for a response...
10846 - bugfix: when you sleep your hidden-service laptop, as soon
10847 as it wakes up it tries to upload a service descriptor, but
10848 socketpair fails for some reason (localhost not up yet?).
10849 now we simply give up on that upload, and we'll try again later.
10850 i'd still like to find the bug though.
10851 - if an intro circ waiting for an ack dies before getting one, then
10853 - we were reusing stale service descriptors and refetching usable
10857 Changes in version 0.0.6pre4 - 2004-04-14
10858 o changes from 0.0.6pre3:
10859 - when bob fails to connect to the rendezvous point, and his
10860 circ didn't fail because of the rendezvous point itself, then
10861 he retries a couple of times
10862 - we expire introduction and rendezvous circs more thoroughly
10863 (sometimes they were hanging around forever)
10864 - we expire unattached rendezvous streams that have been around
10865 too long (they were sticking around forever).
10866 - fix a measly fencepost error that was crashing everybody with
10870 Changes in version 0.0.6pre3 - 2004-04-14
10871 o changes from 0.0.6pre2:
10872 - make hup work again
10873 - fix some memory leaks for dirservers
10874 - allow more skew in rendezvous descriptor timestamps, to help
10875 handle people like blanu who don't know what time it is
10876 - normal circs are 3 hops, but some rend/intro circs are 4, if
10877 the initiator doesn't get to choose the last hop
10878 - send acks for introductions, so alice can know whether to try
10880 - bob publishes intro points more correctly
10881 o changes from 0.0.5:
10882 - fix an assert trigger that's been plaguing us since the days
10883 of 0.0.2prexx (thanks weasel!)
10884 - retry stream correctly when we fail to connect because of
10885 exit-policy-reject (should try another) or can't-resolve-address
10886 (also should try another, because dns on random internet servers
10888 - when we hup a dirserver and we've *removed* a server from the
10889 approved-routers list, now we remove that server from the
10890 in-memory directories too
10893 Changes in version 0.0.6pre2 - 2004-04-08
10894 o We fixed our base32 implementation. Now it works on all architectures.
10897 Changes in version 0.0.6pre1 - 2004-04-08
10899 - Hidden services and rendezvous points are implemented. Go to
10900 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
10901 hidden services. (This only works via a socks4a proxy such as
10902 Privoxy, and currently it's quite slow.)
10905 Changes in version 0.0.5 - 2004-03-30
10906 [version bump only]
10909 Changes in version 0.0.5rc3 - 2004-03-29
10910 o Install torrc as torrc.sample -- we no longer clobber your
10912 o Re-enable recommendedversion checking (we broke it in rc2, oops)
10913 o Add in a 'notice' log level for things the operator should hear
10914 but that aren't warnings
10917 Changes in version 0.0.5rc2 - 2004-03-29
10918 o Hold socks connection open until reply is flushed (if possible)
10919 o Make exit nodes resolve IPs to IPs immediately, rather than asking
10920 the dns farm to do it.
10921 o Fix c99 aliasing warnings in rephist.c
10922 o Don't include server descriptors that are older than 24 hours in the
10924 o Give socks 'reject' replies their whole 15s to attempt to flush,
10925 rather than seeing the 60s timeout and assuming the flush had failed.
10926 o Clean automake droppings from the cvs repository
10929 Changes in version 0.0.5rc1 - 2004-03-28
10930 o Fix mangled-state bug in directory fetching (was causing sigpipes).
10931 o Only build circuits after we've fetched the directory: clients were
10932 using only the directory servers before they'd fetched a directory.
10933 This also means longer startup time; so it goes.
10934 o Fix an assert trigger where an OP would fail to handshake, and we'd
10935 expect it to have a nickname.
10936 o Work around a tsocks bug: do a socks reject when AP connection dies
10937 early, else tsocks goes into an infinite loop.
10940 Changes in version 0.0.4 - 2004-03-26
10941 o When connecting to a dirserver or OR and the network is down,
10945 Changes in version 0.0.3 - 2004-03-26
10946 o Warn and fail if server chose a nickname with illegal characters
10947 o Port to Solaris and Sparc:
10948 - include missing header fcntl.h
10949 - have autoconf find -lsocket -lnsl automatically
10950 - deal with hardware word alignment
10951 - make uname() work (solaris has a different return convention)
10952 - switch from using signal() to sigaction()
10953 o Preliminary work on reputation system:
10954 - Keep statistics on success/fail of connect attempts; they're published
10955 by kill -USR1 currently.
10956 - Add a RunTesting option to try to learn link state by creating test
10957 circuits, even when SocksPort is off.
10958 - Remove unused open circuits when there are too many.
10961 Changes in version 0.0.2 - 2004-03-19
10962 - Include strlcpy and strlcat for safer string ops
10963 - define INADDR_NONE so we compile (but still not run) on solaris
10966 Changes in version 0.0.2pre27 - 2004-03-14
10968 - Allow internal tor networks (we were rejecting internal IPs,
10969 now we allow them if they're set explicitly).
10970 - And fix a few endian issues.
10973 Changes in version 0.0.2pre26 - 2004-03-14
10975 - If a stream times out after 15s without a connected cell, don't
10976 try that circuit again: try a new one.
10977 - Retry streams at most 4 times. Then give up.
10978 - When a dirserver gets a descriptor from an unknown router, it
10979 logs its fingerprint (so the dirserver operator can choose to
10980 accept it even without mail from the server operator).
10981 - Inform unapproved servers when we reject their descriptors.
10982 - Make tor build on Windows again. It works as a client, who knows
10984 - Clearer instructions in the torrc for how to set up a server.
10985 - Be more efficient about reading fd's when our global token bucket
10986 (used for rate limiting) becomes empty.
10988 - Stop asserting that computers always go forward in time. It's
10990 - When we sent a cell (e.g. destroy) and then marked an OR connection
10991 expired, we might close it before finishing a flush if the other
10992 side isn't reading right then.
10993 - Don't allow dirservers to start if they haven't defined
10994 RecommendedVersions
10995 - We were caching transient dns failures. Oops.
10996 - Prevent servers from publishing an internal IP as their address.
10997 - Address a strcat vulnerability in circuit.c
11000 Changes in version 0.0.2pre25 - 2004-03-04
11002 - Put the OR's IP in its router descriptor, not its fqdn. That way
11003 we'll stop being stalled by gethostbyname for nodes with flaky dns,
11006 - If the user typed in an address that didn't resolve, the server
11010 Changes in version 0.0.2pre24 - 2004-03-03
11012 - Fix an assertion failure in dns.c, where we were trying to dequeue
11013 a pending dns resolve even if it wasn't pending
11014 - Fix a spurious socks5 warning about still trying to write after the
11015 connection is finished.
11016 - Hold certain marked_for_close connections open until they're finished
11017 flushing, rather than losing bytes by closing them too early.
11018 - Correctly report the reason for ending a stream
11019 - Remove some duplicate calls to connection_mark_for_close
11020 - Put switch_id and start_daemon earlier in the boot sequence, so it
11021 will actually try to chdir() to options.DataDirectory
11022 - Make 'make test' exit(1) if a test fails; fix some unit tests
11023 - Make tor fail when you use a config option it doesn't know about,
11024 rather than warn and continue.
11025 - Make --version work
11026 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
11029 Changes in version 0.0.2pre23 - 2004-02-29
11031 - Print a statement when the first circ is finished, so the user
11032 knows it's working.
11033 - If a relay cell is unrecognized at the end of the circuit,
11034 send back a destroy. (So attacks to mutate cells are more
11036 - New config option 'excludenodes' to avoid certain nodes for circuits.
11037 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
11038 so you can collect coredumps there.
11040 - Fix a bug in tls flushing where sometimes data got wedged and
11041 didn't flush until more data got sent. Hopefully this bug was
11042 a big factor in the random delays we were seeing.
11043 - Make 'connected' cells include the resolved IP, so the client
11044 dns cache actually gets populated.
11045 - Disallow changing from ORPort=0 to ORPort>0 on hup.
11046 - When we time-out on a stream and detach from the circuit, send an
11047 end cell down it first.
11048 - Only warn about an unknown router (in exitnodes, entrynodes,
11049 excludenodes) after we've fetched a directory.
11052 Changes in version 0.0.2pre22 - 2004-02-26
11054 - Servers publish less revealing uname information in descriptors.
11055 - More memory tracking and assertions, to crash more usefully when
11057 - If the default torrc isn't there, just use some default defaults.
11058 Plus provide an internal dirservers file if they don't have one.
11059 - When the user tries to use Tor as an http proxy, give them an http
11060 501 failure explaining that we're a socks proxy.
11061 - Dump a new router.desc on hup, to help confused people who change
11062 their exit policies and then wonder why router.desc doesn't reflect
11064 - Clean up the generic tor.sh init script that we ship with.
11066 - If the exit stream is pending on the resolve, and a destroy arrives,
11067 then the stream wasn't getting removed from the pending list. I
11068 think this was the one causing recent server crashes.
11069 - Use a more robust poll on OSX 10.3, since their poll is flaky.
11070 - When it couldn't resolve any dirservers, it was useless from then on.
11071 Now it reloads the RouterFile (or default dirservers) if it has no
11073 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
11074 many users don't even *have* a /usr/local/sbin/.
11077 Changes in version 0.0.2pre21 - 2004-02-18
11079 - There's a ChangeLog file that actually reflects the changelog.
11080 - There's a 'torify' wrapper script, with an accompanying
11081 tor-tsocks.conf, that simplifies the process of using tsocks for
11082 tor. It even has a man page.
11083 - The tor binary gets installed to sbin rather than bin now.
11084 - Retry streams where the connected cell hasn't arrived in 15 seconds
11085 - Clean up exit policy handling -- get the default out of the torrc,
11086 so we can update it without forcing each server operator to fix
11088 - Allow imaps and pop3s in default exit policy
11090 - Prevent picking middleman nodes as the last node in the circuit
11093 Changes in version 0.0.2pre20 - 2004-01-30
11095 - We now have a deb package, and it's in debian unstable. Go to
11096 it, apt-getters. :)
11097 - I've split the TotalBandwidth option into BandwidthRate (how many
11098 bytes per second you want to allow, long-term) and
11099 BandwidthBurst (how many bytes you will allow at once before the cap
11100 kicks in). This better token bucket approach lets you, say, set
11101 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
11102 performance while not exceeding your monthly bandwidth quota.
11103 - Push out a tls record's worth of data once you've got it, rather
11104 than waiting until you've read everything waiting to be read. This
11105 may improve performance by pipelining better. We'll see.
11106 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
11107 from failed circuits (if they haven't been connected yet) and attach
11109 - Expire old streams that haven't managed to connect. Some day we'll
11110 have them reattach to new circuits instead.
11113 - Fix several memory leaks that were causing servers to become bloated
11115 - Fix a few very rare assert triggers. A few more remain.
11116 - Setuid to User _before_ complaining about running as root.
11119 Changes in version 0.0.2pre19 - 2004-01-07
11121 - Fix deadlock condition in dns farm. We were telling a child to die by
11122 closing the parent's file descriptor to him. But newer children were
11123 inheriting the open file descriptor from the parent, and since they
11124 weren't closing it, the socket never closed, so the child never read
11125 eof, so he never knew to exit. Similarly, dns workers were holding
11126 open other sockets, leading to all sorts of chaos.
11127 - New cleaner daemon() code for forking and backgrounding.
11128 - If you log to a file, it now prints an entry at the top of the
11129 logfile so you know it's working.
11130 - The onionskin challenge length was 30 bytes longer than necessary.
11131 - Started to patch up the spec so it's not quite so out of date.
11134 Changes in version 0.0.2pre18 - 2004-01-02
11136 - Fix endian issues with the 'integrity' field in the relay header.
11137 - Fix a potential bug where connections in state
11138 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
11141 Changes in version 0.0.2pre17 - 2003-12-30
11143 - Made --debuglogfile (or any second log file, actually) work.
11144 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
11145 adversary could force us into an infinite loop.
11148 - Each onionskin handshake now includes a hash of the computed key,
11149 to prove the server's identity and help perfect forward secrecy.
11150 - Changed cell size from 256 to 512 bytes (working toward compatibility
11152 - Changed cell length to 2 bytes, and moved it to the relay header.
11153 - Implemented end-to-end integrity checking for the payloads of
11155 - Separated streamid from 'recognized' (otherwise circuits will get
11156 messed up when we try to have streams exit from the middle). We
11157 use the integrity-checking to confirm that a cell is addressed to
11159 - Randomize the initial circid and streamid values, so an adversary who
11160 breaks into a node can't learn how many circuits or streams have
11164 Changes in version 0.0.2pre16 - 2003-12-14
11166 - Fixed a bug that made HUP trigger an assert
11167 - Fixed a bug where a circuit that immediately failed wasn't being
11168 counted as a failed circuit in counting retries.
11171 - Now we close the circuit when we get a truncated cell: otherwise we're
11172 open to an anonymity attack where a bad node in the path truncates
11173 the circuit and then we open streams at him.
11174 - Add port ranges to exit policies
11175 - Add a conservative default exit policy
11176 - Warn if you're running tor as root
11177 - on HUP, retry OR connections and close/rebind listeners
11178 - options.EntryNodes: try these nodes first when picking the first node
11179 - options.ExitNodes: if your best choices happen to include any of
11180 your preferred exit nodes, you choose among just those preferred
11182 - options.ExcludedNodes: nodes that are never picked in path building
11185 Changes in version 0.0.2pre15 - 2003-12-03
11186 o Robustness and bugfixes:
11187 - Sometimes clients would cache incorrect DNS resolves, which would
11188 really screw things up.
11189 - An OP that goes offline would slowly leak all its sockets and stop
11191 - A wide variety of bugfixes in exit node selection, exit policy
11192 handling, and processing pending streams when a new circuit is
11194 - Pick nodes for a path only from those the directory says are up
11195 - Choose randomly from all running dirservers, not always the first one
11196 - Increase allowed http header size for directory fetch.
11197 - Stop writing to stderr (if we're daemonized it will be closed).
11198 - Enable -g always, so cores will be more useful to me.
11199 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
11202 - Wrote a man page. It lists commonly used options.
11205 - Change default loglevel to warn.
11206 - Make PidFile default to null rather than littering in your CWD.
11207 - OnionRouter config option is now obsolete. Instead it just checks
11209 - Moved to a single unified torrc file for both clients and servers.
11212 Changes in version 0.0.2pre14 - 2003-11-29
11213 o Robustness and bugfixes:
11214 - Force the admin to make the DataDirectory himself
11215 - to get ownership/permissions right
11216 - so clients no longer make a DataDirectory and then never use it
11217 - fix bug where a client who was offline for 45 minutes would never
11218 pull down a directory again
11219 - fix (or at least hide really well) the dns assert bug that was
11220 causing server crashes
11221 - warnings and improved robustness wrt clockskew for certs
11222 - use the native daemon(3) to daemonize, when available
11223 - exit if bind() fails
11224 - exit if neither socksport nor orport is defined
11225 - include our own tor_timegm (Win32 doesn't have its own)
11226 - bugfix for win32 with lots of connections
11227 - fix minor bias in PRNG
11228 - make dirserver more robust to corrupt cached directory
11231 - Wrote the design document (woo)
11233 o Circuit building and exit policies:
11234 - Circuits no longer try to use nodes that the directory has told them
11236 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
11237 bitcounts (18.0.0.0/8).
11238 - Make AP connections standby for a circuit if no suitable circuit
11239 exists, rather than failing
11240 - Circuits choose exit node based on addr/port, exit policies, and
11241 which AP connections are standing by
11242 - Bump min pathlen from 2 to 3
11243 - Relay end cells have a payload to describe why the stream ended.
11244 - If the stream failed because of exit policy, try again with a new
11246 - Clients have a dns cache to remember resolved addresses.
11247 - Notice more quickly when we have no working circuits
11250 - APPort is now called SocksPort
11251 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
11253 - RecommendedVersions is now a config variable rather than
11254 hardcoded (for dirservers)
11255 - Reloads config on HUP
11256 - Usage info on -h or --help
11257 - If you set User and Group config vars, it'll setu/gid to them.
11260 Changes in version 0.0.2pre13 - 2003-10-19
11261 o General stability:
11262 - SSL_write no longer fails when it returns WANTWRITE and the number
11263 of bytes in the buf has changed by the next SSL_write call.
11264 - Fix segfault fetching directory when network is down
11265 - Fix a variety of minor memory leaks
11266 - Dirservers reload the fingerprints file on HUP, so I don't have
11267 to take down the network when I approve a new router
11268 - Default server config file has explicit Address line to specify fqdn
11271 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
11272 - Make listener connections not ever alloc bufs
11274 o Autoconf improvements:
11275 - don't clobber an external CFLAGS in ./configure
11276 - Make install now works
11277 - create var/lib/tor on make install
11278 - autocreate a tor.sh initscript to help distribs
11279 - autocreate the torrc and sample-server-torrc with correct paths
11281 o Log files and Daemonizing now work:
11282 - If --DebugLogFile is specified, log to it at -l debug
11283 - If --LogFile is specified, use it instead of commandline
11284 - If --RunAsDaemon is set, tor forks and backgrounds on startup