Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.174 as permitted sender)
	client-ip=209.85.216.174; envelope-from=etotheipi@gmail.com;
	helo=mail-qc0-f174.google.com; 
Message-ID: <54C26BFE.1080103@gmail.com>
Date: Fri, 23 Jan 2015 10:42:54 -0500
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAJna-HjwMRff_+7BvcR2YME9f2yUQPvfKOGZ1qq9d0nOGqORkg@mail.gmail.com>
	<78662993-6C67-4480-8062-55CC9FA63908@bitsofproof.com>
In-Reply-To: <78662993-6C67-4480-8062-55CC9FA63908@bitsofproof.com>
Content-Type: multipart/alternative;
	boundary="------------050708060006090709090707"
Subject: Re: [Bitcoin-development] SIGHASH_WITHINPUTVALUE
Precedence: list

This is a multi-part message in MIME format.
--------------050708060006090709090707
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Unfortunately, one major attack vector is someone isolating your node,
getting you to sign away your whole wallet to fee, and then selling it
to a mining pool to mine it before you can figure why your transactions
aren't making it to the network.  In such an attack, the relay rules
aren't relevant, and if the attacker can DoS you for 24 hours, it
doesn't take a ton of mining power to make the attack extremely likely
to succeed.


On 01/23/2015 10:31 AM, Tamas Blummer wrote:
> Not a fix, but would reduce the financial risk, if nodes were not
> relaying excessive fee transactions.
>
> Tamas Blummer
>
>


--------------050708060006090709090707
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Unfortunately, one major attack vector is someone isolating your
    node, getting you to sign away your whole wallet to fee, and then
    selling it to a mining pool to mine it before you can figure why
    your transactions aren't making it to the network.  In such an
    attack, the relay rules aren't relevant, and if the attacker can DoS
    you for 24 hours, it doesn't take a ton of mining power to make the
    attack extremely likely to succeed.<br>
    <br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 01/23/2015 10:31 AM, Tamas Blummer
      wrote:<br>
    </div>
    <blockquote
      cite="mid:78662993-6C67-4480-8062-55CC9FA63908@bitsofproof.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>Not a fix, but would reduce the financial risk, if nodes were
        not relaying excessive fee transactions.</div>
      <div><br>
      </div>
      <div apple-content-edited="true">
        <div style="color: rgb(0, 0, 0); font-family: Helvetica;
          font-size: 12px; font-style: normal; font-variant: normal;
          font-weight: normal; letter-spacing: normal; line-height:
          normal; orphans: auto; text-align: start; text-indent: 0px;
          text-transform: none; white-space: normal; widows: auto;
          word-spacing: 0px; -webkit-text-stroke-width: 0px;">Tamas
          Blummer</div>
        <div style="color: rgb(0, 0, 0); font-family: Helvetica;
          font-size: 12px; font-style: normal; font-variant: normal;
          font-weight: normal; letter-spacing: normal; line-height:
          normal; orphans: auto; text-align: start; text-indent: 0px;
          text-transform: none; white-space: normal; widows: auto;
          word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>
        </div>
      </div>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------050708060006090709090707--