1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1V4AV1-0000mm-Jt
for bitcoin-development@lists.sourceforge.net;
Tue, 30 Jul 2013 14:02:03 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.177 as permitted sender)
client-ip=209.85.212.177; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f177.google.com;
Received: from mail-wi0-f177.google.com ([209.85.212.177])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V4AV0-0001p5-PE
for bitcoin-development@lists.sourceforge.net;
Tue, 30 Jul 2013 14:02:03 +0000
Received: by mail-wi0-f177.google.com with SMTP id hq12so3694118wib.4
for <bitcoin-development@lists.sourceforge.net>;
Tue, 30 Jul 2013 07:01:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:x-gm-message-state;
bh=IDQp+h8nJvGiisqd1x4pzGwkI7lCHCuTevaM6WF7060=;
b=IoZX33sh4LTyRvJqKgdirj/B8SWeIobwkUgxD2XiFCccqa7VWcUnasyUZgnmWhAyEZ
Np6mX7bszuLpIBU2y0sVBc3Pc6yB4BdqlqH8GHCxtqDHAceQ2NWaCcxeHF9xfsaDd1jV
TofMQx1lf6WUzGzRrx5cmJzQBOwicx9m7hi+nv674DDvZ5FypVjGq25hfaOoRbMjgLo4
kHb2Snd5MCJFK+1rlICLytFkxA4PgE0feEdLxfy73M1MY11o35iJ2J8JRZPLwatyVWZo
jycGD9JcTvgvRahIhHvJcn4WXzrLaQeY+NnU1vZn94POjhz085vZ3ieDULp9TxbB5gyF
+Wkg==
MIME-Version: 1.0
X-Received: by 10.180.75.144 with SMTP id c16mr525525wiw.1.1375192916547; Tue,
30 Jul 2013 07:01:56 -0700 (PDT)
Received: by 10.194.242.36 with HTTP; Tue, 30 Jul 2013 07:01:56 -0700 (PDT)
In-Reply-To: <CANEZrP3rqTW_DEZ75B9tg6kNPtfX4ENBJupaJD1axSLsxMdCwQ@mail.gmail.com>
References: <FB36762E8B574F7AAB7D25618841CF01@grabhive.com>
<CANEZrP3rqTW_DEZ75B9tg6kNPtfX4ENBJupaJD1axSLsxMdCwQ@mail.gmail.com>
Date: Tue, 30 Jul 2013 10:01:56 -0400
Message-ID: <CAJHLa0PcxdCwHRN8ZrpOyD_NWPfBod4SJNooxpMXQUqHg102uQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQls4A33lk/E6/n0Js/tWahnFE2U20w/IvdOOt9uREdSSz4L2EXKxoBeIsHuzC3Bsu2DR1Kw
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 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: 1V4AV0-0001p5-PE
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Tor and Bitcoin
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 14:02:03 -0000
On Tue, Jul 30, 2013 at 8:41 AM, Mike Hearn <mike@plan99.net> wrote:
> * Talk the Tor protocol directly and have the app explicitly pick its own
> diverse set of exit nodes, one per p2p connection. This is likely to be
> complicated. Last time I looked Tor doesn't provide any kind of library or
> API.
This has been discussed on IRC, and would be interesting to explore.
For several applications, linking directly with a Tor library is far
superior to the fragility of requiring a properly configured external
process. Lacking such a Tor library right now, one must be written
<hint hint>
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
