public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: gb <kiwigb@yahoo.com>
To: Pieter Wuille <pieter.wuille@gmail.com>,
	Bitcoin Core Discussion
	<bitcoin-core-dev@lists.linuxfoundation.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [bitcoin-core-dev] Bitcoin Core update notice
Date: Sat, 22 Sep 2018 10:39:46 +1200	[thread overview]
Message-ID: <1537569586.4405.2.camel@yahoo.com> (raw)
In-Reply-To: <CAPg+sBhdO_7m46UphVay3vJUM+Va9=3Kq5aa4VQN4cobY-krmw@mail.gmail.com>

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




  reply	other threads:[~2018-09-21 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  0:06 [bitcoin-dev] Bitcoin Core update notice Pieter Wuille
2018-09-21 22:39 ` gb [this message]
2018-09-22  4:56   ` [bitcoin-dev] [bitcoin-core-dev] " Andrew Chow
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=1537569586.4405.2.camel@yahoo.com \
    --to=kiwigb@yahoo.com \
    --cc=bitcoin-core-dev@lists.linuxfoundation.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pieter.wuille@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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