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
88
89
90
91
92
93
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <vmartchenko@gmail.com>) id 1QWBRi-0001MC-Bg
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 18:01:06 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.47 as permitted sender)
client-ip=209.85.216.47; envelope-from=vmartchenko@gmail.com;
helo=mail-qw0-f47.google.com;
Received: from mail-qw0-f47.google.com ([209.85.216.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QWBRh-00041D-Ih
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 18:01:06 +0000
Received: by qwh5 with SMTP id 5so3057648qwh.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 13 Jun 2011 11:01:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.200.6 with SMTP id eu6mr602097qab.220.1307988060000; Mon,
13 Jun 2011 11:01:00 -0700 (PDT)
Sender: vmartchenko@gmail.com
Received: by 10.229.96.21 with HTTP; Mon, 13 Jun 2011 11:00:59 -0700 (PDT)
In-Reply-To: <BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com>
References: <BANLkTin_qs4bDabnu+b3K1hTzLzr4JKHsg@mail.gmail.com>
<BANLkTimDGr-yX9zgS3qWPZALprWCsFieXg@mail.gmail.com>
<BANLkTi=oYjydw7sT=sqSN3sHMhM+pq=c6w@mail.gmail.com>
<BANLkTikNd6rqssQ1bHGhPURc7tiXLkBGwQ@mail.gmail.com>
<BANLkTi=X4vZn_Oe6iYirp9++jwfXHJaqwg@mail.gmail.com>
<BANLkTikbQpU8+NMT_-f2mVNe-cGLY-ZeuQ@mail.gmail.com>
<BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com>
Date: Mon, 13 Jun 2011 19:00:59 +0100
X-Google-Sender-Auth: V5qFZAN-y3XetQUVnVOcG0CV48s
Message-ID: <BANLkTi=XUxZOXP-U8swyfBuu7ntjo6VyUg@mail.gmail.com>
From: Vladimir Marchenko <vladimir@marchenko.co.uk>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
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 FREEMAIL_FROM Sender email is freemail (vmartchenko[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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
0.0 RFC_ABUSE_POST Both abuse and postmaster missing on sender domain
0.0 T_TO_NO_BRKTS_FREEMAIL T_TO_NO_BRKTS_FREEMAIL
-0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QWBRh-00041D-Ih
Subject: Re: [Bitcoin-development] Bootstrapping via BitTorrent trackers
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: Mon, 13 Jun 2011 18:01:06 -0000
Jeff is absolutely correct, stating that DNS bootstrapping can
potentially be very robust.
Consider, for example, that seeds can be hosted by services like
zerigo, who provide decent management API's, as well as by thousands
of small VPS operated by people all over the world. Moreover, if
namecoin lives up to it's promises than some seeds can be hosted using
it's tlds, and as such we would get around centralised ICANN/registrar
weakness.
The most practical way I see how to improve DNS bootstrapping is
publishing build instructions for a simple DNS server build and a
script which feeds it with node data. Something simple like djbdns plus
a perl script, or similar zerigo API script, would do. Than anyone can
host it. All left to do than is to hardcode a bunch of such DNS seeds
into the client.
Hardcoding seeds is not good enough? Get a convention that anyone
owning a bitcoin.* domain should point seed.bitcoin.* to a decent DNS
seed. Than clients simply scan 100-200 tld's to find working
seed.bitcoin.*
I am not quite sure, though, is if this would enable some attacks by
poisoned seeds.
Vladimir.
|
