summaryrefslogtreecommitdiff
path: root/9c/d284ba866d87dfbacaccdb81a36d863a5f995a
blob: 193b8f6ac8f15cfc43564542aa6d2ae94bf41742 (plain)
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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1WlIpL-0004go-3R
	for bitcoin-development@lists.sourceforge.net;
	Fri, 16 May 2014 14:09:35 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.41 as permitted sender)
	client-ip=209.85.219.41; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f41.google.com; 
Received: from mail-oa0-f41.google.com ([209.85.219.41])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WlIpJ-0003CW-S7
	for bitcoin-development@lists.sourceforge.net;
	Fri, 16 May 2014 14:09:35 +0000
Received: by mail-oa0-f41.google.com with SMTP id m1so3052469oag.14
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 16 May 2014 07:09:28 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.176.9 with SMTP id ce9mr17123933oec.55.1400249368251;
	Fri, 16 May 2014 07:09:28 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Fri, 16 May 2014 07:09:28 -0700 (PDT)
Received: by 10.76.71.162 with HTTP; Fri, 16 May 2014 07:09:28 -0700 (PDT)
In-Reply-To: <ll4kvl$3nu$1@ger.gmane.org>
References: <ll29m5$r6c$1@ger.gmane.org>
	<CAAS2fgQrbK4LxWaeCmnJQKi_vUPByBDXFmxGfRG_3j0ZUsVEZQ@mail.gmail.com>
	<ll4kvl$3nu$1@ger.gmane.org>
Date: Fri, 16 May 2014 16:09:28 +0200
X-Google-Sender-Auth: MaLD3btUffQBgQD9XhLP7FMQrFk
Message-ID: <CANEZrP0Eocd7CFXoW=meatRtcf-wVRQ=uE70exwO-aQJiYss_Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=089e0118226c31166b04f984f6dc
X-Spam-Score: -0.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 commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1WlIpJ-0003CW-S7
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
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: Fri, 16 May 2014 14:09:35 -0000

--089e0118226c31166b04f984f6dc
Content-Type: text/plain; charset=UTF-8

My android wallet is working OK. Yes it isn't great when seeds have
temporary availability problems but things are still working.

There's a couple of pull reqs outstanding to include hard coded seed peers
and getaddr sourced IPs. Once those are finished and merged in there'll be
more backup paths.
On 16 May 2014 11:16, "Andreas Schildbach" <andreas@schildbach.de> wrote:

> On 05/15/2014 07:48 PM, Gregory Maxwell wrote:
> > On Thu, May 15, 2014 at 4:50 AM, Andreas Schildbach
> > <andreas@schildbach.de> wrote:
> >> I'm bringing this issue up again. The current Bitcoin DNS seed
> >> infrastructure is unstable. I assume this is because of we're using a
> >> custom DNS implementation which is not 100% compatible. There have been
> >> bugs in the past, like a case sensitive match for the domain name.
> >
> > If software is using the DNS seeds in a way where one or two being
> > unavailable is problematic, then the software may be using them
> > poorly.
> >
> > Generally DNS seeds should only be used as fast connectivity hints,
> > primarily for initial connectivity. Relying on them exclusively
> > increases isolation vulnerabilities (e.g. because the dns seed
> > operators or any ISP or network attacker on the path between you and
> > the seeds can replace the results with ones that isolate you on a
> > bogus network).
>
> I just used "nslookup", after seeing the issues in bitcoinj.
>
> I agree that clients should be robust regarding DNS lookups (and
> bitcoinj isn't), but still I think the first step needs to be
> maintaining a quality infrastructure.
>
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--089e0118226c31166b04f984f6dc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">My android wallet is working OK. Yes it isn&#39;t great when=
 seeds have temporary availability problems but things are still working. <=
/p>
<p dir=3D"ltr">There&#39;s a couple of pull reqs outstanding to include har=
d coded seed peers and getaddr sourced IPs. Once those are finished and mer=
ged in there&#39;ll be more backup paths.</p>
<div class=3D"gmail_quote">On 16 May 2014 11:16, &quot;Andreas Schildbach&q=
uot; &lt;<a href=3D"mailto:andreas@schildbach.de">andreas@schildbach.de</a>=
&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 05/15/2014 07:48 PM, Gregory Maxwell wrote:<br>
&gt; On Thu, May 15, 2014 at 4:50 AM, Andreas Schildbach<br>
&gt; &lt;<a href=3D"mailto:andreas@schildbach.de">andreas@schildbach.de</a>=
&gt; wrote:<br>
&gt;&gt; I&#39;m bringing this issue up again. The current Bitcoin DNS seed=
<br>
&gt;&gt; infrastructure is unstable. I assume this is because of we&#39;re =
using a<br>
&gt;&gt; custom DNS implementation which is not 100% compatible. There have=
 been<br>
&gt;&gt; bugs in the past, like a case sensitive match for the domain name.=
<br>
&gt;<br>
&gt; If software is using the DNS seeds in a way where one or two being<br>
&gt; unavailable is problematic, then the software may be using them<br>
&gt; poorly.<br>
&gt;<br>
&gt; Generally DNS seeds should only be used as fast connectivity hints,<br=
>
&gt; primarily for initial connectivity. Relying on them exclusively<br>
&gt; increases isolation vulnerabilities (e.g. because the dns seed<br>
&gt; operators or any ISP or network attacker on the path between you and<b=
r>
&gt; the seeds can replace the results with ones that isolate you on a<br>
&gt; bogus network).<br>
<br>
I just used &quot;nslookup&quot;, after seeing the issues in bitcoinj.<br>
<br>
I agree that clients should be robust regarding DNS lookups (and<br>
bitcoinj isn&#39;t), but still I think the first step needs to be<br>
maintaining a quality infrastructure.<br>
<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
&quot;Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE=
<br>
Instantly run your Selenium tests across 300+ browser/OS combos.<br>
Get unparalleled scalability from the best Selenium testing platform availa=
ble<br>
Simple to use. Nothing to install. Get started now for free.&quot;<br>
<a href=3D"http://p.sf.net/sfu/SauceLabs" target=3D"_blank">http://p.sf.net=
/sfu/SauceLabs</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div>

--089e0118226c31166b04f984f6dc--