From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XJuE6-0003Rz-Vp for bitcoin-development@lists.sourceforge.net; Wed, 20 Aug 2014 00:58:11 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.149.115 as permitted sender) client-ip=62.13.149.115; envelope-from=pete@petertodd.org; helo=outmail149115.authsmtp.co.uk; Received: from outmail149115.authsmtp.co.uk ([62.13.149.115]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XJuE0-0000Mn-Bo for bitcoin-development@lists.sourceforge.net; Wed, 20 Aug 2014 00:58:10 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s7K0vwts051823; Wed, 20 Aug 2014 01:57:58 +0100 (BST) Received: from android-61a40235731d80b6.lan (76-10-178-110.dsl.teksavvy.com [76.10.178.110]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s7K0vtiS068267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Aug 2014 01:57:56 +0100 (BST) User-Agent: K-9 Mail for Android In-Reply-To: <53F3F07D.20409@riseup.net> References: <0C0EF7F9-DBBA-4872-897D-63CFA3853726@ricmoo.com> <33D4B2E3-DBF0-444E-B76A-765C4C17E964@ricmoo.com> <53F37635.5070807@riseup.net> <53F38AC9.4000608@corganlabs.com> <53F3DFF7.9070709@jrn.me.uk> <3476b0a1-e08a-46bf-9ee4-ef56fcb02d72@email.android.com> <53F3F07D.20409@riseup.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Peter Todd Date: Tue, 19 Aug 2014 20:57:53 -0400 To: Justus Ranvier , Bitcoin Development Message-ID: <38a13fbd-09e7-460e-9715-6d585f48f815@email.android.com> X-Server-Quench: 06071015-2805-11e4-b396-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aAdMdAIUGUATAgsB AmIbW1VeVVp7XGU7 bAxPbAVDY01GQQRr UFdNRFdNFUsrBmcB QFpHMRl0fwdAfzB3 bUNjEHBdXEN7dUd4 X0xcFWgbZGY1bH1N U0leagNUcgZDfk5E bwQuUz1vNG8XDQg5 AwQ0PjZ0MThBJSBS WgQAK04nCX4RGSY7 XBkGT30CG0YfVj0v ZxYnNlUbHUBZN0gp KlIuVElw X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 76.10.178.110/465 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [62.13.149.115 listed in list.dnswl.org] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1XJuE0-0000Mn-Bo 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: Wed, 20 Aug 2014 00:58:11 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 19 August 2014 20:49:01 GMT-04:00, Justus Ranvier wrote: >On 08/20/2014 12:16 AM, Peter Todd wrote: >> The easiest way to do this would be to make the Debian/Ubuntu >> packages depend on Tor, and include a install-time script to setup >> the hidden service. I've verified with the Tor devs that they would >> welcome the additional load on the Tor network that Bitcoin would >> add. > >The easiest way for the people who operates nodes would be to compile >Tor into Bitcoin Core as a library so that it "just works" when turned >on. That library doesn't exist yet to my knowledge, and more importantly, would increase the attack surface of Bitcoin Core. (much like using OpenSSL for straight SSL support would) Also, my proposal of adding Tor support to the Debian packages can be implemented in a relatively short install time script; no code changes required. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQFQBAEBCAA6BQJT8/KRMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8 cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhauiB/9iEvsRYQGt9lFmrtbW SBjDt91/v7r3NcI/19aKDNGMaKl61rpzDr1zM3kIBdY3xzFoaYt+LA6O/tZVvaVC B9zPlZsh+0ZmbU+Ejxd816DvJVDv8aO6Nt+sLuVkkN/TsBa/WCBhvwJ7ixS65/dY WpFV7awzW+E08RETsV826scP+30lsnY5qcADoHWfuaW7HZQArpCsA+b+Amng8Vf6 mFb5GrxKlvG06w+esLSXMCISS3eMduvfzymfxBxGlgxRAqiYZRbWY3msdRRfWl3e lISrnqZoB3G529WVGOn4o5DrzDdSJFcb8k2A/Na2J+pIxAD4Cv9vwYM2KCffbeUB PH6x =Mw3I -----END PGP SIGNATURE-----