Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work again on the latest OS X, and updates the location of a directory authority.

Major bugfixes (performance):
- We were selecting our guards uniformly at random, and then weighting which of our guards we'd use uniformly at random. This imbalance meant that Tor clients were severely limited on throughput (and probably latency too) by the first hop in their circuit. Now we select guards weighted by currently advertised bandwidth. We also automatically discard guards picked using the old algorithm. Fixes bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.

Major bugfixes:
- Make Tor work again on the latest OS X: when deciding whether to use strange flags to turn TLS renegotiation on, detect the OpenSSL version at run-time, not compile time. We need to do this because Apple doesn't update its dev-tools headers when it updates its libraries in a security patch.
- Fix a potential buffer overflow in lookup_last_hid_serv_request() that could happen on 32-bit platforms with 64-bit time_t. Also fix a memory leak when requesting a hidden service descriptor we've requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found by aakova.

Directory authority changes:
- Change IP address for dannenberg (v3 directory authority), and remove moria2 (obsolete v1, v2 directory authority and v0 hidden service directory authority) from the list.

Minor bugfixes:
- Refactor resolve_my_address() to not use gethostbyname() anymore. Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.

Minor features:
- Avoid a mad rush at the beginning of each month when each client rotates half of its guards. Instead we spread the rotation out throughout the month, but we still avoid leaving a precise timestamp in the state file about when we first picked the guard. Improves over the behavior introduced in 0.1.2.17.

1.3.8
- update Firefox to 3.5.11

1.3.9
- update Pidgin to 2.7.2

o Major bugfixes:
- Stop assigning the HSDir flag to relays that disable their
DirPort (and thus will refuse to answer directory requests). This
fix should dramatically improve the reachability of hidden services:
hidden services and hidden service clients pick six HSDir relays
to store and retrieve the hidden service descriptor, and currently
about half of the HSDir relays will refuse to work. Bugfix on
0.2.0.10-alpha; fixes part of bug 1693.
- The PerConnBWRate and Burst config options, along with the
bwconnrate and bwconnburst consensus params, initialized each conn's
token bucket values only when the connection is established. Now we
update them if the config options change, and update them every time
we get a new consensus. Otherwise we can encounter an ugly edge
case where we initialize an OR conn to client-level bandwidth,
but then later the relay joins the consensus and we leave it
throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
- Fix a regression that caused Tor to rebind its ports if it receives
SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.

o Major features:
- Lower the maximum weighted-fractional-uptime cutoff to 98%. This
should give us approximately 40-50% more Guard-flagged nodes,
improving the anonymity the Tor network can provide and also
decreasing the dropoff in throughput that relays experience when
they first get the Guard flag.
- Allow enabling or disabling the *Statistics config options while
Tor is running.

o Minor features:
- Update to the August 1 2010 Maxmind GeoLite Country database.
- Have the controller interface give a more useful message than
"Internal Error" in response to failed GETINFO requests.
- Warn when the same option is provided more than once in a torrc
file, on the command line, or in a single SETCONF statement, and
the option is one that only accepts a single line. Closes bug 1384.
- Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
Patch from mingw-san.
- Add support for the country code "{??}" in torrc options like
ExcludeNodes, to indicate all routers of unknown country. Closes
bug 1094.
- Relays report the number of bytes spent on answering directory
requests in extra-info descriptors similar to {read,write}-history.
Implements enhancement 1790.

o Minor bugfixes (on 0.2.1.x and earlier):
- Complain if PublishServerDescriptor is given multiple arguments that
include 0 or 1. This configuration will be rejected in the future.
Bugfix on 0.2.0.1-alpha; closes bug 1107.
- Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
Bugfix on 0.2.0.13-alpha; closes bug 928.
- Change "Application request when we're believed to be offline."
notice to "Application request when we haven't used client
functionality lately.", to clarify that it's not an error. Bugfix
on 0.0.9.3; fixes bug 1222.
- Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
would return "551 Internal error" rather than "552 Unrecognized key
ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
- Users can't configure a regular relay to be their bridge. It didn't
work because when Tor fetched the bridge descriptor, it found
that it already had it, and didn't realize that the purpose of the
descriptor had changed. Now we replace routers with a purpose other
than bridge with bridge descriptors when fetching them. Bugfix on
0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
refetch the descriptor with router purpose 'general', disabling
it as a bridge.
- Fix a rare bug in rend_fn unit tests: we would fail a test when
a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
on 0.2.0.10-alpha; fixes bug 1808.
- Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
stream ending reason for this case: END_STREAM_REASON_NOROUTE.
Servers can start sending this code when enough clients recognize
it. Also update the spec to reflect this new reason. Bugfix on
0.1.0.1-rc; fixes part of bug 1793.
- Delay geoip stats collection by bridges for 6 hours, not 2 hours,
when we switch from being a public relay to a bridge. Otherwise
there will still be clients that see the relay in their consensus,
and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
932 even more.
- Instead of giving an assertion failure on an internal mismatch
on estimated freelist size, just log a BUG warning and try later.
Mitigates but does not fix bug 1125.
- Fix an assertion failure that could occur in caches or bridge users
when using a very short voting interval on a testing network.
Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.

o Minor bugfixes (on 0.2.2.x):
- Alter directory authorities to always consider Exit-flagged nodes
as potential Guard nodes in their votes. The actual decision to
use Exits as Guards is done in the consensus bandwidth weights.
Fixes bug 1294; bugfix on 0.2.2.10-alpha.
- When the controller is reporting the purpose of circuits that
didn't finish building before the circuit build timeout, it was
printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
- Our libevent version parsing code couldn't handle versions like
1.4.14b-stable and incorrectly warned the user about using an
old and broken version of libevent. Treat 1.4.14b-stable like
1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
on 0.2.2.1-alpha.
- Don't use substitution references like $(VAR:MOD) when
$(asciidoc_files) is empty -- make(1) on NetBSD transforms
'$()' to 'x' rather than the empty string. This bites us in
doc/ when configured with --disable-asciidoc. Bugfix on
0.2.2.9-alpha; fixes bug 1773.
- Remove a spurious hidden service server-side log notice about
"Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
bug 1741.
- Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
fixes bug 1832.
- Correctly report written bytes on linked connections. Found while
implementing 1790. Bugfix on 0.2.2.4-alpha.
- Fix three memory leaks: one in circuit_build_times_parse_state(),
one in dirvote_add_signatures_to_pending_consensus(), and one every
time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.

o Code simplifications and refactoring:
- Take a first step towards making or.h smaller by splitting out
function definitions for all source files in src/or/. Leave
structures and defines in or.h for now.
- Remove a bunch of unused function declarations as well as a block of
#if 0'd code from the unit tests. Closes bug 1824.
- New unit tests for exit-port history statistics; refactored exit
statistics code to be more easily tested.
- Remove the old debian/ directory from the main Tor distribution.
The official Tor-for-debian git repository lives at the URL
https://git.torproject.org/debian/tor.git

1.3.10: Released 2010-09-28

update Vidalia to 0.2.10
update Firefox to 3.6.10
add new extensions:
Better Privacy 1.48.3
NoScript 2.0.3.2
HTTPS Everywhere 0.2.2

1.3.11: Release 2010-10-25
update Firefox to 3.6.11
update Pidgin to 2.7.4

Update Firefox to 3.6.12

Yet another OpenSSL security patch broke its compatibility with Tor:
Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
also took this opportunity to fix several crash bugs, integrate a new
directory authority, and update the bundled GeoIP database.

o Major bugfixes:
- Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
No longer set the tlsext_host_name extension on server SSL objects;
but continue to set it on client SSL objects. Our goal in setting
it was to imitate a browser, not a vhosting server. Fixes bug 2204;
bugfix on 0.2.1.1-alpha.
- Do not log messages to the controller while shrinking buffer
freelists. Doing so would sometimes make the controller connection
try to allocate a buffer chunk, which would mess up the internals
of the freelist and cause an assertion failure. Fixes bug 1125;
fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
- Learn our external IP address when we're a relay or bridge, even if
we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
where we introduced bridge relays that don't need to publish to
be useful. Fixes bug 2050.
- Do even more to reject (and not just ignore) annotations on
router descriptors received anywhere but from the cache. Previously
we would ignore such annotations at first, but cache them to disk
anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
- When you're using bridges and your network goes away and your
bridges get marked as down, recover when you attempt a new socks
connection (if the network is back), rather than waiting up to an
hour to try fetching new descriptors for your bridges. Bugfix on
0.2.0.3-alpha; fixes bug 1981.

o Major features:
- Move to the November 2010 Maxmind GeoLite country db (rather
than the June 2009 ip-to-country GeoIP db) for our statistics that
count how many users relays are seeing from each country. Now we'll
have more accurate data, especially for many African countries.

o New directory authorities:
- Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
authority.

o Minor bugfixes:
- Fix an assertion failure that could occur in directory caches or
bridge users when using a very short voting interval on a testing
network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
0.2.0.8-alpha.
- Enforce multiplicity rules when parsing annotations. Bugfix on
0.2.0.8-alpha. Found by piebeer.
- Allow handshaking OR connections to take a full KeepalivePeriod
seconds to handshake. Previously, we would close them after
IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
for analysis help.
- When building with --enable-gcc-warnings on OpenBSD, disable
warnings in system headers. This makes --enable-gcc-warnings
pass on OpenBSD 4.8.

o Minor features:
- Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
stream ending reason for this case: END_STREAM_REASON_NOROUTE.
Servers can start sending this code when enough clients recognize
it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
- Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
Patch from mingw-san.

o Removed files:
- Remove the old debian/ directory from the main Tor distribution.
The official Tor-for-debian git repository lives at the URL
https://git.torproject.org/debian/tor.git
- Stop shipping the old doc/website/ directory in the tarball. We
changed the website format in late 2010, and what we shipped in
0.2.1.26 really wasn't that useful anyway.

Windows Tor Browser Bundles
There were some controversial changes recently made to the Windows bundle, and for those I apologize. I have removed BetterPrivacy and NoScript from them pending further testing. The whole changelog:

1.3.13: Released 2010-11-25
update Tor to 0.2.1.27
update Pidgin to 2.7.5
update OpenSSL to 0.9.8p
fix Firefox extension install path so extensions show in the installed add-ons list
disable Firefox's ability to search the Windows registry path for system-wide
plugins and extensions (closes: #2118)
remove NoScript and BetterPrivacy from stable bundle until they receive more
testing

Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely exploitable bugs. We also took this opportunity to change the IP address for one of our directory authorities, and to update the geoip database we ship.

Major bugfixes:
- Fix a remotely exploitable bug that could be used to crash instances of Tor remotely by overflowing on the heap. Remote-code execution hasn't been confirmed, but can't be ruled out. Everyone should upgrade. Bugfix on the 0.1.1 series and later.

Directory authority changes:
- Change IP address and ports for gabelmoo (v3 directory authority).

Minor features:
- Update to the December 1 2010 Maxmind GeoLite Country database.

- update HTTPS-Everywhere to 0.9.9.development.2
- update Tor to 0.2.1.28

1 Changes in version 0.2.2.23-alpha - 2011-03-08
2 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3 they restart they don't lose their bandwidth capacity estimate. This
4 release also fixes a diverse set of user-facing bugs, ranging from
5 relays overrunning their rate limiting to clients falsely warning about
6 clock skew to bridge descriptor leaks by our bridge directory authority.
7
8 o Major bugfixes:
9 - Stop sending a CLOCK_SKEW controller status event whenever
10 we fetch directory information from a relay that has a wrong clock.
11 Instead, only inform the controller when it's a trusted authority
12 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
13 the rest of bug 1074.
14 - Fix an assert in parsing router descriptors containing IPv6
15 addresses. This one took down the directory authorities when
16 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
17 - Make the bridge directory authority refuse to answer directory
18 requests for "all" descriptors. It used to include bridge
19 descriptors in its answer, which was a major information leak.
20 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22 Tor would ignore their RelayBandwidthBurst setting,
23 potentially using more bandwidth than expected. Bugfix on
24 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
26 hidserv" in her torrc. The 'hidserv' argument never controlled
27 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
28
29 o Major features:
30 - Relays now save observed peak bandwidth throughput rates to their
31 state file (along with total usage, which was already saved)
32 so that they can determine their correct estimated bandwidth on
33 restart. Resolves bug 1863, where Tor relays would reset their
34 estimated bandwidth to 0 after restarting.
35 - Directory authorities now take changes in router IP address and
36 ORPort into account when determining router stability. Previously,
37 if a router changed its IP or ORPort, the authorities would not
38 treat it as having any downtime for the purposes of stability
39 calculation, whereas clients would experience downtime since the
40 change could take a while to propagate to them. Resolves issue 1035.
41 - Enable Address Space Layout Randomization (ASLR) and Data Execution
42 Prevention (DEP) by default on Windows to make it harder for
43 attackers to exploit vulnerabilities. Patch from John Brooks.
44
45 o Minor bugfixes (on 0.2.1.x and earlier):
46 - Fix a rare crash bug that could occur when a client was configured
47 with a large number of bridges. Fixes bug 2629; bugfix on
48 0.2.1.2-alpha. Bugfix by trac user "shitlei".
49 - Avoid a double mark-for-free warning when failing to attach a
50 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
51 bug 2279.
52 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
53 found by "cypherpunks". This bug was introduced before the first
54 Tor release, in svn commit r110.
55 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
56 don't mention them in the manpage. Fixes bug 2450; issue
57 spotted by keb and G-Lo.
58 - Fix a bug in bandwidth history state parsing that could have been
59 triggered if a future version of Tor ever changed the timing
60 granularity at which bandwidth history is measured. Bugfix on
61 Tor 0.1.1.11-alpha.
62 - When a relay decides that its DNS is too broken for it to serve
63 as an exit server, it advertised itself as a non-exit, but
64 continued to act as an exit. This could create accidental
65 partitioning opportunities for users. Instead, if a relay is
66 going to advertise reject *:* as its exit policy, it should
67 really act with exit policy "reject *:*". Fixes bug 2366.
68 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
69 - In the special case where you configure a public exit relay as your
70 bridge, Tor would be willing to use that exit relay as the last
71 hop in your circuit as well. Now we fail that circuit instead.
72 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
73 - Fix a bug with our locking implementation on Windows that couldn't
74 correctly detect when a file was already locked. Fixes bug 2504,
75 bugfix on 0.2.1.6-alpha.
76 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
77 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
78 "piebeer".
79 - Set target port in get_interface_address6() correctly. Bugfix
80 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
81 - Directory authorities are now more robust to hops back in time
82 when calculating router stability. Previously, if a run of uptime
83 or downtime appeared to be negative, the calculation could give
84 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
85 bug 1035.
86 - Fix an assert that got triggered when using the TestingTorNetwork
87 configuration option and then issuing a GETINFO config-text control
88 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
89
90 o Minor bugfixes (on 0.2.2.x):
91 - Clients should not weight BadExit nodes as Exits in their node
92 selection. Similarly, directory authorities should not count BadExit
93 bandwidth as Exit bandwidth when computing bandwidth-weights.
94 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
95 - Correctly clear our dir_read/dir_write history when there is an
96 error parsing any bw history value from the state file. Bugfix on
97 Tor 0.2.2.15-alpha.
98 - Resolve a bug in verifying signatures of directory objects
99 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
100 Fixes bug 2409. Found by "piebeer".
101 - Bridge authorities no longer crash on SIGHUP when they try to
102 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
103 on 0.2.2.22-alpha.
104
105 o Minor features:
106 - Log less aggressively about circuit timeout changes, and improve
107 some other circuit timeout messages. Resolves bug 2004.
108 - Log a little more clearly about the times at which we're no longer
109 accepting new connections. Resolves bug 2181.
110 - Reject attempts at the client side to open connections to private
111 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
112 a randomly chosen exit node. Attempts to do so are always
113 ill-defined, generally prevented by exit policies, and usually
114 in error. This will also help to detect loops in transparent
115 proxy configurations. You can disable this feature by setting
116 "ClientRejectInternalAddresses 0" in your torrc.
117 - Always treat failure to allocate an RSA key as an unrecoverable
118 allocation error.
119 - Update to the March 1 2011 Maxmind GeoLite Country database.
120
121 o Minor features (log subsystem):
122 - Add documentation for configuring logging at different severities in
123 different log domains. We've had this feature since 0.2.1.1-alpha,
124 but for some reason it never made it into the manpage. Fixes
125 bug 2215.
126 - Make it simpler to specify "All log domains except for A and B".
127 Previously you needed to say "[*,~A,~". Now you can just say
128 "[~A,~".
129 - Add a "LogMessageDomains 1" option to include the domains of log
130 messages along with the messages. Without this, there's no way
131 to use log domains without reading the source or doing a lot
132 of guessing.
133
134 o Packaging changes:
135 - Stop shipping the Tor specs files and development proposal documents
136 in the tarball. They are now in a separate git repository at
137 git://git.torproject.org/torspec.git