diff options
author | Jeff Garzik <jgarzik@bitpay.com> | 2014-08-08 14:21:18 -0400 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2014-08-08 18:21:45 +0000 |
commit | 8534f41063a5bffd788c4d5572d4ca314ffc3a63 (patch) | |
tree | ee3bc50cb7a362695ad58c5049600c9d8ba1d745 | |
parent | ae0f9877afd3a9216a2f6036fc54fa2bc6a68938 (diff) | |
download | pi-bitcoindev-8534f41063a5bffd788c4d5572d4ca314ffc3a63.tar.gz pi-bitcoindev-8534f41063a5bffd788c4d5572d4ca314ffc3a63.zip |
Re: [Bitcoin-development] Miners MiTM
-rw-r--r-- | 43/c0203343972a62a07cb4dda877db737c81c0d3 | 114 |
1 files changed, 114 insertions, 0 deletions
diff --git a/43/c0203343972a62a07cb4dda877db737c81c0d3 b/43/c0203343972a62a07cb4dda877db737c81c0d3 new file mode 100644 index 000000000..9b3ad85bc --- /dev/null +++ b/43/c0203343972a62a07cb4dda877db737c81c0d3 @@ -0,0 +1,114 @@ +Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <jgarzik@bitpay.com>) id 1XFonR-0001Ez-Kk + for bitcoin-development@lists.sourceforge.net; + Fri, 08 Aug 2014 18:21:45 +0000 +Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com + designates 209.85.223.172 as permitted sender) + client-ip=209.85.223.172; envelope-from=jgarzik@bitpay.com; + helo=mail-ie0-f172.google.com; +Received: from mail-ie0-f172.google.com ([209.85.223.172]) + by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1XFonQ-0006hl-Ar + for bitcoin-development@lists.sourceforge.net; + Fri, 08 Aug 2014 18:21:45 +0000 +Received: by mail-ie0-f172.google.com with SMTP id lx4so6919942iec.3 + for <bitcoin-development@lists.sourceforge.net>; + Fri, 08 Aug 2014 11:21:39 -0700 (PDT) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:mime-version:in-reply-to:references:from:date + :message-id:subject:to:cc:content-type; + bh=PUVR7duUDOXUje/L0al7PXsAAJfLpseaOrV+fbBdBnM=; + b=hXnp+yNutdGA6l5wXLXIw4VR1O6gUaKkite7TNZ2vVB04awLG0psmDgVUliKq0Eun6 + 7i9mmLx1ZizqcgwhErc/V/iUacnyRlVONCxIOKszl9xdtmho1wYI90rp6lYu6NPRxbE1 + SIUUgRVv84s68oQgPofGkvSi23lcWm6FlTqnz4pAzcZ2qrdU919w2qv7Q+sHyuGBboFc + FiOYc9Bqx55p9qiVp3toNyP8dXxDj+gEunfp6kOA2jGvP6W9Eeg6EsG0bvZsX5YjMrpf + ixhjCc7rFnC1zJNSDFPRVHl3nr4MzC44KXt/uWuP3mo0VYAH7Mp0OA4tlI0uGkEVzSLB + JMIg== +X-Gm-Message-State: ALoCoQky8suqDD7GADueBqczqr+pFth+PvWdOGoTKAvKvZsfK1nTaW5+zAXiBPXWCvuolF2PX2AI +X-Received: by 10.50.107.7 with SMTP id gy7mr7515442igb.15.1407522098984; Fri, + 08 Aug 2014 11:21:38 -0700 (PDT) +MIME-Version: 1.0 +Received: by 10.107.10.78 with HTTP; Fri, 8 Aug 2014 11:21:18 -0700 (PDT) +In-Reply-To: <CANEZrP00kRtNxtG9OVOmQLSTZ-MSHSuCe1PniM6v1pnhzz5Jog@mail.gmail.com> +References: <CAPS+U9-ze_-gcYh1WNVJ5h8AZ8owoQX=8OUgNcKnaxgvjxZATA@mail.gmail.com> + <201408072345.45363.luke@dashjr.org> + <CAJna-HjzMO68KSXYG++X-8vzQCLurkrAAhfrVo9-AbaoYdqZhw@mail.gmail.com> + <201408080101.16453.luke@dashjr.org> + <CANEZrP00kRtNxtG9OVOmQLSTZ-MSHSuCe1PniM6v1pnhzz5Jog@mail.gmail.com> +From: Jeff Garzik <jgarzik@bitpay.com> +Date: Fri, 8 Aug 2014 14:21:18 -0400 +Message-ID: <CAJHLa0NBJo+NFFFZEHNo81KPBwgx05tbuMwtSKMs=07+wCmQgA@mail.gmail.com> +To: Mike Hearn <mike@plan99.net> +Content-Type: text/plain; charset=UTF-8 +X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record + -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: 1XFonQ-0006hl-Ar +Cc: "bitcoin-development@lists.sourceforge.net" + <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Miners MiTM +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Fri, 08 Aug 2014 18:21:45 -0000 + +gmaxwell noted on IRC that enabling TLS could be functionally, if not +literally, a DoS on the pool servers. Hence the thought towards a +more lightweight method that simply prevents client payout redirection ++ server impersonation. + + +On Fri, Aug 8, 2014 at 5:53 AM, Mike Hearn <mike@plan99.net> wrote: +>> Certificate validation isn't needed unless the attacker can do a direct +>> MITM +>> at connection time, which is a lot harder to maintain than injecting a +>> client.reconnect. +> +> +> Surely the TCP connection will be reset once the route reconfiguration is +> completed, either by the MITM server or by the client TCP stack when it +> discovers the server doesn't know about the connection anymore? +> +> TLS without cert validation defeats the point, you can still be connected to +> a MITM at any point by anyone who can simply interrupt or corrupt the +> stream, forcing a reconnect. +> +> ------------------------------------------------------------------------------ +> Want fast and easy access to all the code in your enterprise? Index and +> search up to 200,000 lines of code with a free copy of Black Duck +> Code Sight - the same software that powers the world's largest code +> search on Ohloh, the Black Duck Open Hub! Try it now. +> http://p.sf.net/sfu/bds +> _______________________________________________ +> Bitcoin-development mailing list +> Bitcoin-development@lists.sourceforge.net +> https://lists.sourceforge.net/lists/listinfo/bitcoin-development +> + + + +-- +Jeff Garzik +Bitcoin core developer and open source evangelist +BitPay, Inc. https://bitpay.com/ + + |