Tor Browser Bundle (2.2.35-5)
Update Firefox to 10.0
Update Qt to 4.7.4
Update OpenSSL to 1.0.0g
Update zlib to 1.2.6
Update HTTPS Everywhere to 1.2.2
Update NoScript to 2.2.8
New Firefox patches
Limit the number of fonts per document

Linux changes
Put documentation in remove-shared-lib-symlinks debug dumps (closes: #4984)

Windows changes
Make sure mozconfig always gets copied into the Firefox build directory
(closes: #4879)

Tor Browser Bundle (2.2.35-6); suite=windows

* Update Firefox to 10.0.1
* Update Vidalia to 0.2.17
* Update Libevent to 2.0.17-stable
* Update NoScript to 2.3

Changes in version 0.2.3.12-alpha - 2012-02-13
Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
to use bridges that run Tor 0.2.2.x, and resolves several big bugs
when Tor is configured to use a pluggable transport like obfsproxy.

o Major bugfixes:
- Fix builds when the path to sed, openssl, or sha1sum contains
spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
on 0.2.2.1-alpha.
- Set the SO_REUSEADDR socket option before we call bind() on outgoing
connections. This change should allow busy exit relays to stop
running out of available sockets as quickly. Fixes bug 4950;
bugfix on 0.2.2.26-beta.
- Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
would ask the bridge for microdescriptors, which are only supported
in 0.2.3.x, and then fail to bootstrap when it didn't get the
answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
- Avoid an assert when managed proxies like obfsproxy are configured,
and we receive HUP signals or configuration values too rapidly. This
situation happens most commonly when Vidalia tries to attach to
Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
bugfix on 0.2.3.6-alpha.
- Properly set up obfsproxy's environment when in managed mode. The
Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
and when you run your Tor as a daemon, there's no HOME. Fixes bugs
5076 and 5082; bugfix on 0.2.3.6-alpha.

o Minor features:
- Use the dead_strip option when building Tor on OS X. This reduces
binary size by almost 19% when linking openssl and libevent
statically, which we do for Tor Browser Bundle.
- Fix broken URLs in the sample torrc file, and tell readers about
the OutboundBindAddress, ExitPolicyRejectPrivate, and
PublishServerDescriptor options. Addresses bug 4652.
- Update to the February 7 2012 Maxmind GeoLite Country database.

o Minor bugfixes:
- Downgrade the "We're missing a certificate" message from notice
to info: people kept mistaking it for a real problem, whereas it
is seldom the problem even when we are failing to bootstrap. Fixes
bug 5067; bugfix on 0.2.0.10-alpha.
- Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
managed pluggable transport server proxy's environment.
Previously, we would put it there, even though Tor doesn't
implement an 'extended server port' yet, and even though Tor
almost certainly isn't listening at that address. For now, we set
it to an empty string to avoid crashing older obfsproxies. Bugfix
on 0.2.3.6-alpha.
- Log the heartbeat message every HeartbeatPeriod seconds, not every
HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
0.2.3.1-alpha. Bug reported by Scott Bennett.
- Calculate absolute paths correctly on Windows. Fixes bug 4973;
bugfix on 0.2.3.11-alpha.
- Update "ClientOnly" man page entry to explain that there isn't
really any point to messing with it. Resolves ticket 5005.
- Use the correct CVE number for CVE-2011-4576 in our comments and
log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
0.2.3.11-alpha.

o Code simplifications and refactoring:
- Use the _WIN32 macro throughout our code to detect Windows.
(Previously we had used the obsolete 'WIN32' and the idiosyncratic
'MS_WINDOWS'.)

the only difference between 0.2.16 and 0.2.17 is what translations are in. Since we changed our translations workflow, we needed to update the availability policy. Basically, every new translation that has more than 90% done gets enabled. If any of the enabled translations drop bellow the 75% done, we take them out.

Remember that if you find any bugs, you can report them at https://trac.torproject.org/.

Here's what changed since 0.2.15:

0.2.17 11-Feb-2012
Improve the translation policy: do not remove translations that
are not under 75% done. This re enables Polish and Catalan.

0.2.16 11-Feb-2012
Make the default data directory in windows be located in the Local
AppData instead of the Roaming one. Fixes bug 2319.
Do not launch Firefox with every CIRCUIT_ESTABLISHED signal, do it
only if Firefox isn't open yet. Fixes bug 2943.
Uses TAKEOWNERSHIP and __OwningControllerProcess to avoid leaving
tor running in background if Vidalia exits unexpectedly. Fixes bug
3463.
Attempt to remove port.conf file before using it to avoid a race
condition between tor and Vidalia. Fixes bug 4048.
Do not allow users to check the "My ISP blocks..." checkbox
without entering any bridges. Also updates the
documentation. Fixes bug 4290.
Check that the authentication-cookie file length is exactly 32
bytes long. Fixes bug 4304.
Explicitly disable ControlPort auto. Fixes bug 4379.
Make the non exit relay option backward compatible with Vidalia <
0.2.14 so that it doesn't confuse users. Fixes bug 4642.
Sets the preferred size for the GUI layout so it doesn't squeeze
widges when the size isn't big enough. Fixes bug 4656.
Removes the option to have only HTTPProxy since it does not work
any more as it used to do with older tor versions. Users should
use HTTP/HTTPSProxy instead. Fixes bug 4724.
Add a hidden configuration option called SkipVersionCheck so
systems like Tails can force Vidalia to skip checking tor's
version. Resolves ticket 4736.
When Tor has cached enough information it bootstraps faster than
what takes Vidalia connect to it, so Vidalia does not see the
event to update the progress bar. Now Vidalia explicitly asks for
bootstrap-phase when it connects to Tor, and updates the progress
to what is actually happening instead of hanging in
"Authenticating to Tor". Fixes bug 4827.
Fix size hints in the main window layout so that tilling window
managers display the window properly. Thanks to Mike Warren for
the fix. Fixes bug 4907.
Vidalia only validates IPv4 bridge lines. IPv6 bridges are now
available, and there will be pluggable transport bridge lines. So
the validation is now delegated to Tor through SETCONF.
Explicitly disable SocksPort auto by setting it to its default
(9050). Fixes bug 4598.
Sets __ReloadTorrcOnSIGHUP to 0 if SAVECONF failed, which means
the user can't write the torrc file. Fixes bug 4833.
Enable new translations that are >90% done. The new languages are:
Bulgarian, Czech, Hebrew, Greek, Indonesian, Korean,
Dutch. Resolves ticket 5051.
Remove translations that aren't ready enough: Japanese, Thai,
Albanian, Vietnamese, Chinese (Taiwan), Polish, Catalan and
Burmese.

There are new alpha Tor Browser Bundles and Vidalia Bundles available for testing!

These bundles include the latest Vidalia 0.3.1 alpha release and Tor 0.2.3.12-alpha. Right now they are technology previews.

Included applications
---------------------

Vidalia 0.3.1-alpha (with Qt 4.7.4)
Tor 0.2.3.12-alpha (with libevent-2.0.17-stable, zlib-1.2.6 and openssl-1.0.1-beta1)
Firefox 10.0.1
\_ Torbutton 1.4.5.1
|_ NoScript 2.3
|_ HTTPS-Everywhere 2.0development.4

Tor Browser Bundle (2.2.35-8); suite=windows

* Update Firefox to 11.0
* Update OpenSSL to 1.0.0h
* Update NoScript to 2.3.4
* Update HTTPS Everywhere to 2.0.1
* Always build to with warnings enabled (closes; #4470)
* Disable HTTPS Everywhere SSL Observatory screen (closes: #5300)
* Remove tor-resolve from the Windows bundle (closes: #5403)

Tor Browser Bundle (2.3.12-alpha-2); suite=windows

* Update Firefox to 11.0
* Update NoScript to 2.3.4
* Update HTTPS Everywhere to 3.0development.1
* Disable HTTPS Everywhere SSL Observatory screen (closes: #5300)
* Always build to with warnings enabled (closes: #4470)
* Remove tor-resolve from the Windows bundle (closes: #5403)

-- Erinn Clark <erinn@torproject.org> Mon Mar 19 01:14:43 BRT 2012

Tor Browser Bundle (2.2.35-9); suite=windows

* Update Firefox to 12.0
* Update OpenSSL to 1.0.1b
* Update Libevent to 2.0.18-stable
* Update Qt to 4.8.1
* Update Libpng to 1.5.10
* Update HTTPS Everywhere to 2.0.2
* Update NoScript to 2.3.9
* Rebrand Firefox to TorBrowser (closes: #2176)
* New Firefox patches
- Make Download Manager memory-only (closes: #4017)
- Add DuckDuckGo and Startpage to Omnibox (closes: #4902)

-- Erinn Clark <erinn@torproject.org> Fri Apr 27 12:43:33 BRT 2012

Changes in version 0.2.3.15-alpha - 2012-04-30
Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
the development branch build on Windows again.

o Minor bugfixes (on 0.2.2.x and earlier):
- Make sure that there are no unhandled pending TLS errors before
reading from a TLS stream. We had checks in 0.1.0.3-rc, but
lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
Bugfix on 0.1.0.5-rc; fixes bug 4528.
- Fix an assert that directory authorities could trigger on sighup
during some configuration state transitions. We now don't treat
it as a fatal error when the new descriptor we just generated in
init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
- After we pick a directory mirror, we would refuse to use it if
it's in our ExcludeExitNodes list, resulting in mysterious failures
to bootstrap for people who just wanted to avoid exiting from
certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
- When building with --enable-static-tor on OpenBSD, do not
erroneously attempt to link -lrt. Fixes bug 5103.

o Minor bugfixes (on 0.2.3.x):
- When Tor is built with kernel headers from a recent (last few
years) Linux kernel, do not fail to run on older (pre-2.6.28
Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
- Fix cross-compilation isssues with mingw. Bugfixes on 0.2.3.6-alpha
and 0.2.3.12-alpha.
- Fix compilation with miniupnpc version 1.6; patch from
Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
- Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
- Fix compilation on platforms without unistd.h, or where environ
is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.

o Minor features:
- Directory authorities are now a little more lenient at accepting
older router descriptors, or newer router descriptors that don't
make big changes. This should help ameliorate past and future
issues where routers think they have uploaded valid descriptors,
but the authorities don't think so. Fix for ticket 2479.
- Make the code that clients use to detect an address change be
IPv6-aware, so that it won't fill clients' logs with error
messages when trying to get the IPv4 address of an IPv6
connection. Implements ticket 5537.

o Removed features:
- Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
authorities needed to use it for a while to keep the network working
as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
that was six months ago. As of now, it should no longer be needed
or used.

Tor Browser Bundle (2.2.35-11); suite=windows

* Security release to stop TorBrowser from bypassing SOCKS proxy DNS
configuration
* New Firefox patches:
- Prevent WebSocket DNS leak (closes: #5741)
- Fix a race condition that could be used to link browsing sessions
together when using new identity from Tor Browser (closes: #5715)
* Remove extraneous BetterPrivacy settings from prefs.js (closes: #5722)

-- Erinn Clark <erinn@torproject.org> Thu May 3 08:00:00 BRT 2012

Tor Browser Bundle (2.2.35-12); suite=windows

 * Update OpenSSL to 1.0.1c
 * Update Libevent to 2.0.19-stable
 * Update zlib to 1.2.7
 * Update NoScript to 2.4.1

-- Erinn Clark <erinn@torproject.org>  Fri May 11 20:16:10 BRT 2012

Tor Browser Bundle (2.2.35-13); suite=windows

* Fix Firefox build to sanitize file paths (closes: #5922)

-- Erinn Clark <erinn@torproject.org> Tue May 22 23:28:37 BRT 2012

Changes in version 0.2.2.36 - 2012-05-24
Tor 0.2.2.36 updates the addresses for two of the eight directory
authorities, fixes some potential anonymity and security issues,
and fixes several crash bugs.

Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
known flaws, and nobody should be using them. You should upgrade. If
you're using a Linux or BSD and its packages are obsolete, stop using
those packages and upgrade anyway.

o Directory authority changes:
- Change IP address for maatuska (v3 directory authority).
- Change IP address for ides (v3 directory authority), and rename
it to turtles.

o Security fixes:
- When building or running with any version of OpenSSL earlier
than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
versions have a bug (CVE-2011-4576) in which their block cipher
padding includes uninitialized data, potentially leaking sensitive
information to any peer with whom they make a SSLv3 connection. Tor
does not use SSL v3 by default, but a hostile client or server
could force an SSLv3 connection in order to gain information that
they shouldn't have been able to get. The best solution here is to
upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
to make sure that the bug can't happen.
- Never use a bridge or a controller-supplied node as an exit, even
if its exit policy allows it. Found by wanoskarnet. Fixes bug
5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
and 0.2.0.3-alpha (for bridge-purpose descriptors).
- Only build circuits if we have a sufficient threshold of the total
descriptors that are marked in the consensus with the "Exit"
flag. This mitigates an attack proposed by wanoskarnet, in which
all of a client's bridges collude to restrict the exit nodes that
the client knows about. Fixes bug 5343.
- Provide controllers with a safer way to implement the cookie
authentication mechanism. With the old method, if another locally
running program could convince a controller that it was the Tor
process, then that program could trick the contoller into telling
it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
authentication method uses a challenge-response approach to prevent
this attack. Fixes bug 5185; implements proposal 193.

o Major bugfixes:
- Avoid logging uninitialized data when unable to decode a hidden
service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
- Avoid a client-side assertion failure when receiving an INTRODUCE2
cell on a general purpose circuit. Fixes bug 5644; bugfix on
0.2.1.6-alpha.
- Fix builds when the path to sed, openssl, or sha1sum contains
spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
on 0.2.2.1-alpha.
- Correct our replacements for the timeradd() and timersub() functions
on platforms that lack them (for example, Windows). The timersub()
function is used when expiring circuits, while timeradd() is
currently unused. Bug report and patch by Vektor. Fixes bug 4778;
bugfix on 0.2.2.24-alpha.
- Fix the SOCKET_OK test that we use to tell when socket
creation fails so that it works on Win64. Fixes part of bug 4533;
bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.

o Minor bugfixes:
- Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
Fixes bug 5346; bugfix on 0.0.8pre3.
- Make our number-parsing functions always treat too-large values
as an error, even when those values exceed the width of the
underlying type. Previously, if the caller provided these
functions with minima or maxima set to the extreme values of the
underlying integer type, these functions would return those
values on overflow rather than treating overflow as an error.
Fixes part of bug 5786; bugfix on 0.0.9.
- Older Linux kernels erroneously respond to strange nmap behavior
by having accept() return successfully with a zero-length
socket. When this happens, just close the connection. Previously,
we would try harder to learn the remote address: but there was
no such remote address to learn, and our method for trying to
learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
- Correct parsing of certain date types in parse_http_time().
Without this patch, If-Modified-Since would behave
incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
Esteban Manchado Velázques.
- Change the BridgePassword feature (part of the "bridge community"
design, which is not yet implemented) to use a time-independent
comparison. The old behavior might have allowed an adversary
to use timing to guess the BridgePassword value. Fixes bug 5543;
bugfix on 0.2.0.14-alpha.
- Detect and reject certain misformed escape sequences in
configuration values. Previously, these values would cause us
to crash if received in a torrc file or over an authenticated
control port. Bug found by Esteban Manchado Velázquez, and
independently by Robert Connolly from Matta Consulting who further
noted that it allows a post-authentication heap overflow. Patch
by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
bugfix on 0.2.0.16-alpha.
- Fix a compile warning when using the --enable-openbsd-malloc
configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
- During configure, detect when we're building with clang version
3.0 or lower and disable the -Wnormalized=id and -Woverride-init
CFLAGS. clang doesn't support them yet.
- When sending an HTTP/1.1 proxy request, include a Host header.
Fixes bug 5593; bugfix on 0.2.2.1-alpha.
- Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
- If we hit the error case where routerlist_insert() replaces an
existing (old) server descriptor, make sure to remove that
server descriptor from the old_routers list. Fix related to bug
1776. Bugfix on 0.2.2.18-alpha.

o Minor bugfixes (documentation and log messages):
- Fix a typo in a log message in rend_service_rendezvous_has_opened().
Fixes bug 4856; bugfix on Tor 0.0.6.
- Update "ClientOnly" man page entry to explain that there isn't
really any point to messing with it. Resolves ticket 5005.
- Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
directory authority option (introduced in Tor 0.2.2.34).
- Downgrade the "We're missing a certificate" message from notice
to info: people kept mistaking it for a real problem, whereas it
is seldom the problem even when we are failing to bootstrap. Fixes
bug 5067; bugfix on 0.2.0.10-alpha.
- Correctly spell "connect" in a log message on failure to create a
controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
- Clarify the behavior of MaxCircuitDirtiness with hidden service
circuits. Fixes issue 5259.

o Minor features:
- Directory authorities now reject versions of Tor older than
0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
inclusive. These versions accounted for only a small fraction of
the Tor network, and have numerous known security issues. Resolves
issue 4788.
- Update to the May 1 2012 Maxmind GeoLite Country database.

- Feature removal:
- When sending or relaying a RELAY_EARLY cell, we used to convert
it to a RELAY cell if the connection was using the v1 link
protocol. This was a workaround for older versions of Tor, which
didn't handle RELAY_EARLY cells properly. Now that all supported
versions can handle RELAY_EARLY cells, and now that we're enforcing
the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
remove this workaround. Addresses bug 4786.

Tor Browser Bundle (2.2.36-1); suite=windows

* Update Tor to 0.2.2.36
* Update NoScript to 2.3.4
* Update HTTPS Everywhere to 2.0.5

-- Erinn Clark <erinn@torproject.org> Mon May 28 15:50:09 BRT 2012

Changes in version 0.2.2.37 - 2012-06-06
Tor 0.2.2.37 introduces a workaround for a critical renegotiation
bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
currently).

o Major bugfixes:
- Work around a bug in OpenSSL that broke renegotiation with TLS
1.1 and TLS 1.2. Without this workaround, all attempts to speak
the v2 Tor connection protocol when both sides were using OpenSSL
1.0.1 would fail. Resolves ticket 6033.
- When waiting for a client to renegotiate, don't allow it to add
any bytes to the input buffer. This fixes a potential DoS issue.
Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
- Fix an edge case where if we fetch or publish a hidden service
descriptor, we might build a 4-hop circuit and then use that circuit
for exiting afterwards -- even if the new last hop doesn't obey our
ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.

o Minor bugfixes:
- Fix a build warning with Clang 3.1 related to our use of vasprintf.
Fixes bug 5969. Bugfix on 0.2.2.11-alpha.

o Minor features:
- Tell GCC and Clang to check for any errors in format strings passed
to the tor_v*(print|scan)f functions.

I'm glad to announce that Vidalia stable has new releases, 0.2.18 and 0.2.19.
They are not really big releases, but there are some fixes here to make it more comfortable for you while we get the alpha ready to be called stable.

Why two different releases? Well, errors occur and version numbers don't cost any money, so basically 0.2.18 was released, a couple of issues were found and then we made 0.2.19 fixing them.

You can find the source tarballs in here: https://www.torproject.org/dist/vidalia/

IMPORTANT NOTE: Vidalia releases have been in sync with Tor Browser Bundle releases. This won't necessarily happen anymore. It became hard to sync all the software that TBB contains, so Vidalia releases got delayed for more urgent Firefox issues and things like that. We therefor decided that Vidalia will be released when ready, and TBB will get it at some point.

So, if you don't want to build Vidalia from source, you need to be patient.

Here's what changed for 0.2.18 and 0.2.19:

0.2.18 14-May-2012
Use consensus bandwidth for routers when microdescriptors is
enabled. Fixes bug 3287.

Notify users that a warning status event has appeared by flashing
the Message Log button. Fixes bug 3957.
Fix a method that didn't return the specified type if another
control method was selected. Fixes bug 4065.
Resume listing relays in the Network Map panel even when Tor only
offers microdescriptors (new in Tor 0.2.3.x). Fixes ticket 4203.
Handle unrecognized Tor bootstrap phases. (Tor tells us a summary
description of each bootstrap phase as it occurs, so we can use
that string if needed.) Fixes bug 5109.
Displays Korean, Catalan and Greek in their native scripts. Fix
bug 5110.
Support adding comments in the same line as a config option inside
the torrc dialog. Fixes bug 5475.
Remove Polipo and Torbutton from Vidalia's build scripts. Resolves
ticket 5769.
Fix deadlock when the browser process failed to launch in OS X.
Add ProfileDirectory, DefaultProfileDirectory, PluginsDirectory,
DefaultPluginsDirectory for better Browser configuration. Also set
the Vidalia binary location as the starting point for relative
paths.
Enable Burmese, Croatian, Basque and Serbian translation.
Remove the "Find bridges" button in order to avoid compromising
users that need to hide behind tor at all times. Fixes bug 5371.
Add visual feedback from VClickLabel when in "pressed" state.
Resolves ticket 5766.

0.2.19 30-May-2012
Disable "Run Vidalia when my system starts" if the
BrowserExecutable config option is set. This will avoid issues with
TBB users starting Vidalia the wrong way.
Automigrate TorExecutable, Torrc and DataDirectory config options
to the new relative path handling.
Really get rid of the openssl dependency. The goal had been to
achieve that for 0.2.18, but not everything was actually removed.
For static builds on windows, correctly link with zlib and
ws32_2.lib.

Tor Browser Bundle (2.2.37-1); suite=windows

* Update Tor to 0.2.2.37
* Switch Firefox to 10.0.5esr, since we will be tracking the extended stable
releases for TBB stable versions
* Update Vidalia to 0.2.19
* Update Torbutton to 1.4.6
* Update NoScript to 2.4.4

-- Erinn Clark <erinn@torproject.org> Thu Jun 7 17:51:04 BRT 2012

Tor Browser Bundle (2.2.37-2); suite=windows

* Update Firefox to 10.0.6esr
* Update Vidalia to 0.2.20
* Update NoScript to 2.4.8
* Disable Firefox crashreporter
* Updated Firefox patches:
- Fix Firefox transparency problems with Aero theme on Windows (closes:
#4795)

-- Erinn Clark <erinn@torproject.org> Wed Jul 18 17:34:16 BST 2012

0.2.20 10-Jul-2012
o Append router status information if Tor is using microdescriptors.
o Display paths with their native separators. Resolves ticket 4337.
o Do not ignore the Show on Startup checkbox. Fixes bug 5351.
o Do not add relative root to DataDirectory if it is empty. Fixes
bug 6178.

Changes in version 0.2.3.19-rc - 2012-07-06
Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
series. It fixes the compile on Windows, reverts to a GeoIP database
that isn't as broken, and fixes a flow control bug that has been around
since the beginning of Tor.

o Major bugfixes:
- Fix a bug handling SENDME cells on nonexistent streams that could
result in bizarre window values. Report and patch contributed
pseudonymously. Fixes part of bug 6271. This bug was introduced
before the first Tor release, in svn commit r152.
- Revert to the May 1 2012 Maxmind GeoLite Country database. In the
June 2012 database, Maxmind marked many Tor relays as country "A1",
which will cause risky behavior for clients that set EntryNodes
or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
- Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.

o Minor bugfixes:
- Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
bugfix on 0.2.1.10-alpha.

Tor Browser Bundle (2.3.19-alpha-1)

Update Tor to 0.2.3.19-rc
Update Firefox to 14.0.1
Update libevent to 2.0.19-stable
Update OpenSSL to 1.0.1c
Update zlib to 1.2.7
Update Torbutton to 1.4.6
Update NoScript to 2.4.9
Update HTTPS Everywhere to 3.0development.5
Downgrade Vidalia to 0.2.20
Update libpng to 1.5.12

Tor Browser Bundle (2.3.20-alpha-1); suite=windows

* Update Tor to 0.2.3.20-rc
* Update NoScript to 2.5
* Change the urlbar search engine to Startpage (closes: #5925)
* Firefox patch updates:
- Fix the Tor Browser SIGFPE crash bug (closes: #6492)
- Add a redirect API for HTTPS-Everywhere (closes: #5477)
- Enable WebGL (as click-to-play only) (closes: #6370)

Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
series. It fixes a pair of code security bugs and a potential anonymity
issue, updates our RPM spec files, and cleans up other smaller issues.

o Security fixes:
- Avoid read-from-freed-memory and double-free bugs that could occur
when a DNS request fails while launching it. Fixes bug 6480;
bugfix on 0.2.0.1-alpha.
- Avoid an uninitialized memory read when reading a vote or consensus
document that has an unrecognized flavor name. This read could
lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
- Try to leak less information about what relays a client is
choosing to a side-channel attacker. Previously, a Tor client would
stop iterating through the list of available relays as soon as it
had chosen one, thus finishing a little earlier when it picked
a router earlier in the list. If an attacker can recover this
timing information (nontrivial but not proven to be impossible),
they could learn some coarse-grained information about which relays
a client was picking (middle nodes in particular are likelier to
be affected than exits). The timing attack might be mitigated by
other factors (see bug 6537 for some discussion), but it's best
not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.

o Minor features:
- Try to make the warning when giving an obsolete SOCKSListenAddress
a little more useful.
- Terminate active server managed proxies if Tor stops being a
relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
- Provide a better error message about possible OSX Asciidoc failure
reasons. Fixes bug 6436.
- Warn when Tor is configured to use accounting in a way that can
link a hidden service to some other hidden service or public
address. Resolves ticket 6490.

o Minor bugfixes:
- Check return value of fputs() when writing authority certificate
file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
- Ignore ServerTransportPlugin lines when Tor is not configured as
a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
- When disabling guards for having too high a proportion of failed
circuits, make sure to look at each guard. Fixes bug 6397; bugfix
on 0.2.3.17-beta.

o Packaging (RPM):
- Update our default RPM spec files to work with mock and rpmbuild
on RHEL/Fedora. They have an updated set of dependencies and
conflicts, a fix for an ancient typo when creating the "_tor"
user, and better instructions. Thanks to Ondrej Mikle for the
patch series. Fixes bug 6043.

o Testing:
- Make it possible to set the TestingTorNetwork configuration
option using AlternateDirAuthority and AlternateBridgeAuthority
as an alternative to setting DirServer. Addresses ticket 6377.

o Documentation:
- Clarify the documentation for the Alternate*Authority options.
Fixes bug 6387.
- Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.

o Code simplification and refactoring:
- Do not use SMARTLIST_FOREACH for any loop whose body exceeds
10 lines. Also, don't nest them. Doing so in the past has
led to hard-to-debug code. The new style is to use the
SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.

Changes in version 0.2.2.38 - 2012-08-12
Tor 0.2.2.38 fixes a rare race condition that can crash exit relays;
fixes a remotely triggerable crash bug; and fixes a timing attack that
could in theory leak path information.

o Security fixes:
- Avoid read-from-freed-memory and double-free bugs that could occur
when a DNS request fails while launching it. Fixes bug 6480;
bugfix on 0.2.0.1-alpha.
- Avoid an uninitialized memory read when reading a vote or consensus
document that has an unrecognized flavor name. This read could
lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
- Try to leak less information about what relays a client is
choosing to a side-channel attacker. Previously, a Tor client would
stop iterating through the list of available relays as soon as it
had chosen one, thus finishing a little earlier when it picked
a router earlier in the list. If an attacker can recover this
timing information (nontrivial but not proven to be impossible),
they could learn some coarse-grained information about which relays
a client was picking (middle nodes in particular are likelier to
be affected than exits). The timing attack might be mitigated by
other factors (see bug 6537 for some discussion), but it's best
not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.

Tor Browser Bundle (2.2.38-1); suite=windows

* Update Tor to 0.2.2.38
* Update NoScript to 2.5
* Update HTTPS Everywhere to 2.1

-- Erinn Clark <erinn@torproject.org> Mon Aug 13 22:58:55 BST 2012