Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXdJG-0006Td-06 for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 21:11:58 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.45 as permitted sender) client-ip=209.85.213.45; envelope-from=gavinandresen@gmail.com; helo=mail-yh0-f45.google.com; Received: from mail-yh0-f45.google.com ([209.85.213.45]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXdJE-0007ui-0O for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 21:11:57 +0000 Received: by mail-yh0-f45.google.com with SMTP id a41so1500277yho.32 for ; Tue, 08 Apr 2014 14:11:50 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.84.227 with SMTP id s63mr8940362yhe.26.1396991510530; Tue, 08 Apr 2014 14:11:50 -0700 (PDT) Received: by 10.170.133.195 with HTTP; Tue, 8 Apr 2014 14:11:50 -0700 (PDT) Date: Tue, 8 Apr 2014 17:11:50 -0400 Message-ID: From: Gavin Andresen To: Bitcoin Dev Content-Type: multipart/alternative; boundary=20cf3011dd85bd505404f68e6e45 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WXdJE-0007ui-0O Subject: [Bitcoin-development] 0.9.1 released X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2014 21:11:58 -0000 --20cf3011dd85bd505404f68e6e45 Content-Type: text/plain; charset=ISO-8859-1 Bitcoin Core version 0.9.1 is now available from: https://bitcoin.org/bin/0.9.1/ This is a security update. It is recommended to upgrade to this release as soon as possible. It is especially important to upgrade if you currently have version 0.9.0 installed and are using the graphical interface OR you are using bitcoind from any pre-0.9.1 version, and have enabled SSL for RPC and have configured allowip to allow rpc connections from potentially hostile hosts. Please report bugs using the issue tracker at github: https://github.com/bitcoin/bitcoin/issues How to Upgrade -------------- If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux). If you are upgrading from version 0.7.2 or earlier, the first time you run 0.9.1 your blockchain files will be re-indexed, which will take anywhere from 30 minutes to several hours, depending on the speed of your machine. 0.9.1 Release notes ======================= No code changes were made between 0.9.0 and 0.9.1. Only the dependencies were changed. - Upgrade OpenSSL to 1.0.1g. This release fixes the following vulnerabilities which can affect the Bitcoin Core software: - CVE-2014-0160 ("heartbleed") A missing bounds check in the handling of the TLS heartbeat extension can be used to reveal up to 64k of memory to a connected client or server. - CVE-2014-0076 The Montgomery ladder implementation in OpenSSL does not ensure that certain swap operations have a constant-time behavior, which makes it easier for local users to obtain ECDSA nonces via a FLUSH+RELOAD cache side-channel attack. - Add statically built executables to Linux build Credits -------- Credits go to the OpenSSL team for fixing the vulnerabilities quickly. --20cf3011dd85bd505404f68e6e45 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Bitcoin Core version 0.9.1 is now available from:


This is a security up= date. It is recommended to upgrade to this release
as soon as possible.

It is especially importa= nt to upgrade if you currently have version
0.9.0 installed and a= re using the graphical interface OR you are using
bitcoind from a= ny pre-0.9.1 version, and have enabled SSL for RPC and
have configured allowip to allow rpc connections from potentially
hostile hosts.

Please report bugs using the = issue tracker at github:


How to Upgrade
--------------

<= /div>
If you are running an older version, shut it down. Wait until it = has completely
shut down (which might take a few minutes for olde= r versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on = Mac) or
bitcoind/bitcoin-qt (on Linux).

= If you are upgrading from version 0.7.2 or earlier, the first time you run<= /div>
0.9.1 your blockchain files will be re-indexed, which will take anywhe= re from=A0
30 minutes to several hours, depending on the speed of= your machine.

0.9.1 Release notes
=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

No code changes were made between 0.9.0 and 0.9.1. Only= the dependencies were changed.

- Upgrade OpenSSL = to 1.0.1g. This release fixes the following vulnerabilities which can
=A0 affect the Bitcoin Core software:

=A0 - C= VE-2014-0160 ("heartbleed")
=A0 =A0 A missing bounds ch= eck in the handling of the TLS heartbeat extension can
=A0 =A0 be= used to reveal up to 64k of memory to a connected client or server.

=A0 - CVE-2014-0076
=A0 =A0 The Montgomery la= dder implementation in OpenSSL does not ensure that
=A0 =A0 certa= in swap operations have a constant-time behavior, which makes it
= =A0 =A0 easier for local users to obtain ECDSA nonces via a FLUSH+RELOAD ca= che
=A0 =A0 side-channel attack.

- Add statically= built executables to Linux build

Credits
--------

Credits go to the OpenSSL team for fixi= ng the vulnerabilities quickly.

--20cf3011dd85bd505404f68e6e45--