Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XLFxd-00038S-B8 for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 18:22:45 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.53 as permitted sender) client-ip=209.85.216.53; envelope-from=will.yager@gmail.com; helo=mail-qa0-f53.google.com; Received: from mail-qa0-f53.google.com ([209.85.216.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XLFxT-0006ZF-73 for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 18:22:45 +0000 Received: by mail-qa0-f53.google.com with SMTP id v10so10687979qac.40 for ; Sat, 23 Aug 2014 11:22:27 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.33.230 with SMTP id j93mr18424838qgj.64.1408818147724; Sat, 23 Aug 2014 11:22:27 -0700 (PDT) Received: by 10.140.51.37 with HTTP; Sat, 23 Aug 2014 11:22:27 -0700 (PDT) In-Reply-To: <20140823175038.GU22640@nl.grid.coop> References: <53F3DFF7.9070709@jrn.me.uk> <1569765.oHsHtFYAhh@1337h4x0r> <53F8C656.6010200@riseup.net> <20140823175038.GU22640@nl.grid.coop> Date: Sat, 23 Aug 2014 13:22:27 -0500 Message-ID: From: William Yager Cc: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a113a75ce3f93400501500973 X-Spam-Score: 0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (will.yager[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1XLFxT-0006ZF-73 Subject: Re: [Bitcoin-development] Proposal: Encrypt bitcoin messages X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2014 18:22:45 -0000 --001a113a75ce3f93400501500973 Content-Type: text/plain; charset=UTF-8 On Sat, Aug 23, 2014 at 12:50 PM, Troy Benjegerdes wrote: > they can hire a hacker who will > find a misplaced (} in your crypto code, and all the work you did to > encrypt wire protocols becomes silently worthless. > Not to mention encrypting basically non-sensitive inter-node traffic is almost completely worthless in providing anonymity anyway... Seriously, I have not heard a strong justification for this proposal yet. I have heard some people talking about Tor-ifying communications, but that is a completely different issue and should not be confused with just "encrypting bitcoin messages". --001a113a75ce3f93400501500973 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sat, Aug 23, 2014 at 12:50 PM, Troy Benjegerdes <hozer@h= ozed.org> wrote:
=C2=A0they can hire a hacker who will
find a misplaced (} in your crypto code, and all the work you did to
encrypt wire protocols becomes silently worthless.
Not to mention encrypting basically non-sensitive inter-node tr= affic is almost completely worthless in providing anonymity anyway...=C2=A0=

Seriously, I have not heard a strong justification for = this proposal yet. I have heard some people talking about Tor-ifying commun= ications, but that is a completely different issue and should not be confus= ed with just "encrypting bitcoin messages".
--001a113a75ce3f93400501500973--