From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XJmQV-0003E2-G7 for bitcoin-development@lists.sourceforge.net; Tue, 19 Aug 2014 16:38:27 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.172 as permitted sender) client-ip=209.85.223.172; envelope-from=gmaxwell@gmail.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 1XJmQU-00078y-K5 for bitcoin-development@lists.sourceforge.net; Tue, 19 Aug 2014 16:38:27 +0000 Received: by mail-ie0-f172.google.com with SMTP id lx4so1427796iec.17 for ; Tue, 19 Aug 2014 09:38:21 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.253.193 with SMTP id ac1mr6826595igd.49.1408466301187; Tue, 19 Aug 2014 09:38:21 -0700 (PDT) Received: by 10.107.14.67 with HTTP; Tue, 19 Aug 2014 09:38:21 -0700 (PDT) In-Reply-To: <53F37635.5070807@riseup.net> References: <0C0EF7F9-DBBA-4872-897D-63CFA3853726@ricmoo.com> <33D4B2E3-DBF0-444E-B76A-765C4C17E964@ricmoo.com> <53F37635.5070807@riseup.net> Date: Tue, 19 Aug 2014 09:38:21 -0700 Message-ID: From: Gregory Maxwell To: Justus Ranvier 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -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: 1XJmQU-00078y-K5 Cc: Bitcoin Development 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: Tue, 19 Aug 2014 16:38:27 -0000 On Tue, Aug 19, 2014 at 9:07 AM, Justus Ranvier wrote: > If that's not acceptable, even using TLS with self-signed certificates > would be an improvement. TLS is a huge complex attack surface, any use of it requires an additional dependency with a large amount of difficult to audit code. TLS is trivially DOS attacked and every major/widely used TLS implementation has had multiple memory disclosure or remote execution vulnerabilities even in just the last several years. We've dodged several emergency scale vulnerabilities by not having TLS.