Delivery-Date: Tue, 28 Oct 2014 13:18:47 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 3FCB51E0C33;
	Tue, 28 Oct 2014 13:18:46 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1248530EDF;
	Tue, 28 Oct 2014 17:18:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 410BF210E0
 for <tor-talk@lists.torproject.org>; Tue, 28 Oct 2014 17:18:37 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id KNiZ71vE3O83 for <tor-talk@lists.torproject.org>;
 Tue, 28 Oct 2014 17:18:37 +0000 (UTC)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com
 [IPv6:2a00:1450:4010:c03::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id B577C209E1
 for <tor-talk@lists.torproject.org>; Tue, 28 Oct 2014 17:18:33 +0000 (UTC)
Received: by mail-la0-f42.google.com with SMTP id gq15so1053449lab.29
 for <tor-talk@lists.torproject.org>; Tue, 28 Oct 2014 10:18:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=0664pp896CMC9egwVjXRZ3NRE90+ysx0m5EWo78E1rg=;
 b=cXUrOmrjLgGEl/Y6ulxQ/0zurnf/67oIolPGIsmyWfIAqJI0Y/K8fU9q/0qrpMbu+j
 1hVQ2SXGgtA01yrcWuOUOgpMitc9twyjxulR091wYZnH5yTEUKkyyc5VklmDq6iqPgBZ
 S2B8fnbtvKCMhr74w1pikjrTdrIyzUsHOnuPnNPLWjQTO1v4rUikCe9ErWMzp4Y4R4eM
 dCZeqVtJ2NDNQ4VXpKRrC3d4b7zf6mS17Ok/GcLG/5H8aIfS8PJ1LRZtyJhg31becI0e
 iFwsC595L1g0ClNja4c4QMihCrI5hlA57mEoNr7eYWLtyGgfmD/FL9vF/G+rctleOGvy
 RzzQ==
MIME-Version: 1.0
X-Received: by 10.152.18.166 with SMTP id x6mr5492868lad.18.1414516709526;
 Tue, 28 Oct 2014 10:18:29 -0700 (PDT)
Received: by 10.112.157.133 with HTTP; Tue, 28 Oct 2014 10:18:29 -0700 (PDT)
In-Reply-To: <544EA504.6070201@riseup.net>
References: <20141023191048.17a50660@meilong>
 <20141023232921.GF21428@torproject.org>
 <20141024103527.fd3ac8eff8862bf101b45d95@mega-nerd.com>
 <CAD2Ti2_QWc1Xq+uTvmurFLqjLVsSACMYYDzTAs7zk5SWyQE7Cw@mail.gmail.com>
 <544EA504.6070201@riseup.net>
Date: Tue, 28 Oct 2014 12:18:29 -0500
Message-ID: <CAHZ_AjvixZV+Kb=j6F2L=WYg881HbM4PzgcFDudW0D2GbQrJVA@mail.gmail.com>
From: eric gisse <jowr.pi@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk]
	=?utf-8?q?Bitcoin_over_Tor_isn=E2=80=99t_a_good_idea_?=
	=?utf-8?q?=28Alex_Biryukov_/_Ivan_Pustogarov_story=29?=
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

To that end, I setup a bitcoin node that listens on the v4/v6 internet as
well as tor.

The hidden service address is dsyadrvivtt34s26.onion

Could some folks please test this for me and make sure it works for others?
I can see it is quite happily running on v4/v6 (and getting traffic) but
its' less obvious that it is working over tor.

On Mon, Oct 27, 2014 at 3:03 PM, Thomas White <thomaswhite@riseup.net>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I didn't realise my nodes didn't allow the bitcoin port. I'll get
> right on it.
>
> Also, if anyone in the Tor community has spare capacity, you can also
> setup a full bitcoin node on the same server you use as an
> exit/relay/bridge and it doesn't take up a great deal of resources
> other than disk space (16Gb I think right now and growing slowly). On
> my series of exits there is also full bitcoin nodes accessible
> exclusively over hidden services and others which are accessible over
> regular clearnet.
>
> - -T
>
> On 27/10/2014 19:58, grarpamp wrote:
> > On Thu, Oct 23, 2014 at 7:35 PM, Erik de Castro Lopo
> > <mle+tools@mega-nerd.com> wrote:
> >
> > http://arxiv.org/pdf/1410.6079v1.pdf
> >
> >> Could this situation be improved if people ran limited exit nodes
> >> that only alloed the bitcoin p2p protocol to exit? I for one
> >> don't have enough
> >
> > There are about ten exit nodes that do only this today. [One of
> > which is run by Mike Hearn who has advocated building in censorship
> > capabilities to Tor, and blocking (historically) tainted coins
> > (such as you have now or might receive through otherwise
> > completely innocent transactions with you, or from your own
> > trans/mixing with others).]
> >
> > Then there is question if your client will select such 'only *coin'
> > nodes versus those with high bandwidth and open exit policies.
> >
> > There are also a fair number of hidden services in Tor/I2P/CJDNS
> > that act as bitcoin nodes.
> >
> > As related tangent, yes, the bitcoin protocol needs to be
> > encrypted on the wire, at least bitcoin node to bitcoin node with
> > TLS, obviously and urgently so, particularly if you wish to guard
> > your trans from wire listeners.
> >
> > You might be best to in fact run bitcoin always and entirely over
> > Tor, especially while transacting. But then also routinely compare
> > that received blockchain to one you receive via alternate/trusted
> > sources, such as clearnet or signed bittorrent checkpoints.
> >
>
> - --
> Fingerprint: 9DB0 082F 8FE2 E691 DA2A 6D03 4DAE 4226 9EB0 EB0B
> Fingerprint: FAA4 2253 AA4B 38D0 1BC4 085E F688 CEF6 F9BF D57F
> OTR IRC: DF63021D 27973EAA 02FA4DF6 9E52C9E0 8821E0EF
> OTR XMPP: 77DB65BC C417C4DD 19F9664D 83D6D3FB 6C3D3A0E
>
> Twitter: https://twitter.com/CthulhuSec
>
> Not familiar with PGP? Get started today:
> http://www.bitcoinnotbombs.com/beginners-guide-to-pgp/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
>
> iQIcBAEBAgAGBQJUTqUCAAoJEE2uQiaesOsL23QQAJG4XGhiMRCtAMhb6dbq9jHo
> OZ5CPysEkXwMSK6dTwpCm9GuMHloK3Dq+CzKa6dDeBmEVslWxbXtsx0by0pDjJbS
> I7tiIpjHrCJTrKgDbPQWJP3yZQ8W+fu3JYW+OxZxbrRXEvrX9vgD2pF3zVn2vb76
> n5LEtlmR8rMCC5JAq2tjFY7665xMkloYXay/VE7E2d9eZ5W1/4V1nHcm5cn7RTix
> PxDvD6FAJCNAH7F5rGoGHzC9V9mPAatBfV5S/3Ya49PRtM70tWWBJD/L3KrB71k0
> F7P5eNrfL7gOgFgAIJ1FWuJH7Ri9kCyntsLSgEZBSwYeHEACfFL2qGO1IEw1qRCj
> nxopXSMCNBQu8XP1568ha6KPyKLOTD0kVehE3tgVizabRMTwkuXqiUslbMCRthwy
> y7WmPAaVgEYnGhIhnRHnf/G0tbfsBcInIyCrBuqfJfLnVfx7IPMDP52JLIg71tyM
> RamPUNIv840HkpvTlYwTVIRwL5hFpeW327hxhcnkWFi0mUwb12Lr+N7BlB3aQGE9
> bVmqS4oq1qb6y0TTUlcEg42CDs9GpdVB3Amdcm9Y5scE6upDq+J9yO6322eh82Kq
> qlJK1mnVHMyf3ZGS0ItqGuu54SjiB4kzVt4FV2einjYu4gXT+WiMRCmx1Hzk2hgO
> t6iZ3nLBtWK19kpt4UVD
> =jdgx
> -----END PGP SIGNATURE-----
> --
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

