From: Andrew Chow <achow101-lists@achow101•com>
To: gb <kiwigb@yahoo•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Pieter Wuille <pieter.wuille@gmail•com>,
Bitcoin Core Discussion
<bitcoin-core-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [bitcoin-core-dev] Bitcoin Core update notice
Date: Sat, 22 Sep 2018 04:56:13 +0000 [thread overview]
Message-ID: <FbOWqeUN8UVSAnvIRst9G-AuQ2z0U9qh5OV6Y-q1vpjCBXQ95fyyAUyb3qclC3GtC8EZuEWeGdtB11D17VQK2Kx2plbwqsWpsNOq33pJefI=@achow101.com> (raw)
In-Reply-To: <1537569586.4405.2.camel@yahoo.com>
The backported versions have not been released yet. They are still going
through the gitian build process. 0.16.3 was the first one to be
released so that is the one that everyone is being recommended to
upgrade to. Regardless, you should upgrade to a patched version, whether
that is 0.14.3, 0.15.2, or 0.16.3. It is not misinformation that
everybody must upgrade.
On 09/21/2018 06:39 PM, gb via bitcoin-dev wrote:
> If the bugfix can be backported to earlier versions why is the
> hype/hysteria about "everybody" must immediately upgrade to 0.16.3
> currently being spread on the forums/reddit?
>
> https://bitcointalk.org/index.php?topic=5034070.0
> https://old.reddit.com/r/Bitcoin/comments/9hp90p/1775_nodes_out_of_9616_185_are_currently_on/
>
> I don't see any effort to correct this misinformation either.
>
> Regards.
>
> On Tue, 2018-09-18 at 17:06 -0700, Pieter Wuille via bitcoin-core-dev
> wrote:
>> Hello all,
>>
>> Bitcoin Core 0.16.3 was just released with a fix for
>> CVE-2018-17144:
>> https://bitcoincore.org/en/2018/09/18/release-0.16.3/
>>
>> We urge all network participants to upgrade to 0.16.3[*] as soon
>> as possible.
>>
>> [*] For those who build from source, the 0.14, 0.15, 0.16, 0.17,
>> and master branches on GitHub (https://github.com/bitcoin/bitcoin)
>> are fixed as well.
>>
>> --
>> Pieter
>> _______________________________________________
>> bitcoin-core-dev mailing list
>> bitcoin-core-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2018-09-22 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 0:06 [bitcoin-dev] " Pieter Wuille
2018-09-21 22:39 ` [bitcoin-dev] [bitcoin-core-dev] " gb
2018-09-22 4:56 ` Andrew Chow [this message]
2018-09-22 4:59 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='FbOWqeUN8UVSAnvIRst9G-AuQ2z0U9qh5OV6Y-q1vpjCBXQ95fyyAUyb3qclC3GtC8EZuEWeGdtB11D17VQK2Kx2plbwqsWpsNOq33pJefI=@achow101.com' \
--to=achow101-lists@achow101$(echo .)com \
--cc=bitcoin-core-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kiwigb@yahoo$(echo .)com \
--cc=pieter.wuille@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox