diff options
| author | Emilian Ursu <emu@emuadmin.com> | 2017-04-07 09:46:47 +0300 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2017-04-07 06:53:35 +0000 |
| commit | 30659bcc568787f50734717f8ecaebb7f0151b01 (patch) | |
| tree | a9684a6d99b338c14c70c0e58f99a0eb91d7657f | |
| parent | 0a618113c3a097750d94d5ae036c278b75b32031 (diff) | |
| download | pi-bitcoindev-30659bcc568787f50734717f8ecaebb7f0151b01.tar.gz pi-bitcoindev-30659bcc568787f50734717f8ecaebb7f0151b01.zip | |
Re: [bitcoin-dev] BIP proposal: Inhibiting a covert attack on the Bitcoin POW function
| -rw-r--r-- | d1/01a6574c904108d414c5e4b0a709f1a2c3d98a | 93 |
1 files changed, 93 insertions, 0 deletions
diff --git a/d1/01a6574c904108d414c5e4b0a709f1a2c3d98a b/d1/01a6574c904108d414c5e4b0a709f1a2c3d98a new file mode 100644 index 000000000..6f90f3070 --- /dev/null +++ b/d1/01a6574c904108d414c5e4b0a709f1a2c3d98a @@ -0,0 +1,93 @@ +Return-Path: <emu@emuadmin.com> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 408534A4 + for <bitcoin-dev@lists.linuxfoundation.org>; + Fri, 7 Apr 2017 06:53:35 +0000 (UTC) +X-Greylist: delayed 00:06:40 by SQLgrey-1.7.6 +Received: from www01.emuadmin.com (www01.emuadmin.com [108.61.189.74]) + by smtp1.linuxfoundation.org (Postfix) with SMTP id DF1A8151 + for <bitcoin-dev@lists.linuxfoundation.org>; + Fri, 7 Apr 2017 06:53:30 +0000 (UTC) +Received: (qmail 3181 invoked by uid 1005); 7 Apr 2017 06:46:49 -0000 +X-Qmail-Scanner-Diagnostics: from localhost by www01.emuadmin.com + (envelope-from <emu@emuadmin.com>, + uid 64011) with qmail-scanner-2.11 + (mhr: 1.0. clamscan: 0.98.6/20208. + Clear:RC:1(127.0.0.1):. + Processed in 0.005707 secs); 07 Apr 2017 06:46:49 -0000 +Received: from localhost (127.0.0.1) + by www01.emuadmin.com with SMTP; 7 Apr 2017 06:46:49 -0000 +Date: Fri, 7 Apr 2017 09:46:47 +0300 (EEST) +From: Emilian Ursu <emu@emuadmin.com> +X-X-Sender: morbid@gw00.emuadmin.com +To: Daniele Pinna via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> +In-Reply-To: <CAEgR2PHPvhT8sPJAshp3UMRWLxc4fNb=Vdke0NQpB+i=SCDaDg@mail.gmail.com> +Message-ID: <alpine.BSF.2.20.1704070946250.1298@gw00.emuadmin.com> +References: <CAEgR2PHPvhT8sPJAshp3UMRWLxc4fNb=Vdke0NQpB+i=SCDaDg@mail.gmail.com> +User-Agent: Alpine 2.20 (BSF 67 2015-01-07) +MIME-Version: 1.0 +Content-Type: multipart/mixed; BOUNDARY="4266313884-920737043-1491547609=:1298" +X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD + autolearn=ham version=3.3.1 +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +X-Mailman-Approved-At: Fri, 07 Apr 2017 06:57:40 +0000 +Subject: Re: [bitcoin-dev] BIP proposal: Inhibiting a covert attack on the + Bitcoin POW function +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Fri, 07 Apr 2017 06:53:35 -0000 + + This message is in MIME format. The first part should be readable text, + while the remaining parts are likely unreadable without MIME-aware tools. + +--4266313884-920737043-1491547609=:1298 +Content-Type: text/plain; charset=UTF-8; format=flowed +Content-Transfer-Encoding: 8BIT + + + +The fact that this is possible should be enough for us to implement +meassures against it. + +On Fri, 7 Apr 2017, Daniele Pinna via bitcoin-dev wrote: + +> +> Can you please not forget to supply us more details on the claims made regarding the reverse engineering of the Asic chip? +> +> It is absolutely crucial that we get these independently verified ASAP. +> +> Daniele +> +> Message: 2 +> Date: Thu, 6 Apr 2017 21:38:31 +0000 +> From: Gregory Maxwell <greg@xiph.org> +> To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org> +> Subject: Re: [bitcoin-dev] BIP proposal: Inhibiting a covert attack on +> the Bitcoin POW function +> Message-ID: +> <CAAS2fgSTrMjKZVpL4wRidnzTCC9O3OEF=oCnROf1pggz2cDgJA@mail.gmail.com> +> Content-Type: text/plain; charset=UTF-8 +> On Wed, Apr 5, 2017 at 9:37 PM, Gregory Maxwell <greg@xiph.org> wrote: +> > each block MUST either contain a BIP-141 segwit commitment or a +> > correct WTXID commitment with ID 0xaa21a9ef. +> It was just pointed out to me that the proposed ID (which I just +> selected to be above the segwit one) collides with one chosen in +> another non-BIP proposal. This wasn't intentional, and I'll happily +> change the value when I update the document. +> +> +> +> +--4266313884-920737043-1491547609=:1298-- + |