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
|
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 <c1.sf-bitcoin@niftybox.net>) id 1W3eb3-0001X6-My
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jan 2014 04:30:25 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of niftybox.net
designates 95.142.167.147 as permitted sender)
client-ip=95.142.167.147;
envelope-from=c1.sf-bitcoin@niftybox.net; helo=i3.hyper.to;
Received: from i3.hyper.to ([95.142.167.147])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1W3eb1-000653-HZ for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jan 2014 04:30:25 +0000
Received: from localhost (localhost [127.0.0.1])
by i3.hyper.to (Postfix) with ESMTP id C6494E017A;
Thu, 16 Jan 2014 05:30:17 +0100 (CET)
Received: from i3.hyper.to ([127.0.0.1])
by localhost (i3.hyper.to [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id Q7IHaCayTVwO; Thu, 16 Jan 2014 05:30:17 +0100 (CET)
Received: from [10.1.10.188] (50-1-105-185.dsl.dynamic.sonic.net
[50.1.105.185]) by i3.hyper.to (Postfix) with ESMTPSA id 18B4EE016C;
Thu, 16 Jan 2014 05:30:15 +0100 (CET)
Message-ID: <1389846611.19590.24.camel@mimiz>
From: Miron <c1.sf-bitcoin@niftybox.net>
To: Brooks Boyd <boydb@midnightdesign.ws>
Date: Wed, 15 Jan 2014 20:30:11 -0800
In-Reply-To: <CANg-TZAyr8LyRQ5e4DpQA8fXEbGq6kxv=peB9oYB+bU_xA98ww@mail.gmail.com>
References: <5747D5DF-879B-4A60-8BD6-18251E7D5F47@plan99.net>
<CANg-TZBCSvVeDTNKQSPV-Fw+uZ8np04WoE=o0J+8wULBHrsgKQ@mail.gmail.com>
<CANEZrP1iP6J5gczrQ-+Lzq4uohys7Rrfa0c5F0r-cqx3OJMDGg@mail.gmail.com>
<CANg-TZAyr8LyRQ5e4DpQA8fXEbGq6kxv=peB9oYB+bU_xA98ww@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.4-0ubuntu1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.5 (-)
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
X-Headers-End: 1W3eb1-000653-HZ
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Tor / SPV
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: Thu, 16 Jan 2014 04:30:25 -0000
On Wed, 2014-01-15 at 20:26 -0600, Brooks Boyd wrote:
> My goal here is not necessarily to hide P2P nodes - we still
> need lots of clearnet P2P nodes for the forseeable future no
> matter what. Rather we're just using hidden services as a way
> to get authentication and encryption. Actually the 6-hop
> hidden service circuits are overkill for this application, a
> 3-hop circuit would work just as well for most nodes that
> aren't Tor-exclusive.
>
>
>
...
> communication to Tor doesn't change that. I agree the six-hop circuits
> would be overkill for that; I wonder if the network slowdown you get
BTW, I believe that the number of hops can be reduced below 3 on both
sides (client/server). For Orchid, this will require a change to
CircuitPathChooser. For other Tor implementations, it might require
using the control port to custom-build a circuit.
|
