Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <wtogami@gmail.com>) id 1VvVVk-0003zT-Tb
	for bitcoin-development@lists.sourceforge.net;
	Tue, 24 Dec 2013 17:11:16 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.54 as permitted sender)
	client-ip=209.85.219.54; envelope-from=wtogami@gmail.com;
	helo=mail-oa0-f54.google.com; 
Received: from mail-oa0-f54.google.com ([209.85.219.54])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VvVVk-0006VH-6q
	for bitcoin-development@lists.sourceforge.net;
	Tue, 24 Dec 2013 17:11:16 +0000
Received: by mail-oa0-f54.google.com with SMTP id h16so7169623oag.13
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 24 Dec 2013 09:11:10 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.124.138 with SMTP id mi10mr2169460oeb.57.1387905070757;
	Tue, 24 Dec 2013 09:11:10 -0800 (PST)
Received: by 10.76.178.225 with HTTP; Tue, 24 Dec 2013 09:11:10 -0800 (PST)
In-Reply-To: <20131224140228.GA9838@savin>
References: <op.w8k9l8qayldrnw@laptop-air.hsd1.ca.comcast.net>
	<20131224140228.GA9838@savin>
Date: Tue, 24 Dec 2013 09:11:10 -0800
Message-ID: <CAEz79PqbDS=i54zNkOVwdUFaSYuGGcvwdyLGPxS1poE5hx+7LA@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=047d7b5d5fbab9832304ee4ad459
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(wtogami[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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
	0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
	See
	http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
	for more information. [URIs: petertodd.org]
X-Headers-End: 1VvVVk-0006VH-6q
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Peer Discovery and Overlay
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, 24 Dec 2013 17:11:17 -0000

--047d7b5d5fbab9832304ee4ad459
Content-Type: text/plain; charset=UTF-8

I was concerned about this issue so we sponsored BlueMatt to implement an
address database for bitcoinj.  In the future it won't be entirely reliant
on what DNS tells it.

Warren

On Tue, Dec 24, 2013 at 6:02 AM, Peter Todd <pete@petertodd.org> wrote:

> As for node addresses being a service, that's what the DNS seeds are!
> bitcoinj clients, for instance, depend very heavily on those seeds and
> can be easily compromised in a variety of ways by them.
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">I was concerned about this issu=
e so we sponsored BlueMatt to implement an address database for bitcoinj. =
=C2=A0In the future it won&#39;t be entirely reliant on what DNS tells it.<=
/div><div class=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">Warren<br><br><div class=3D"gmail_quot=
e">On Tue, Dec 24, 2013 at 6:02 AM, Peter Todd <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@petertodd.org</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(3=
4,34,34)">As for node addresses being a service, that&#39;s what the DNS se=
eds are!</span><br>
</div>
bitcoinj clients, for instance, depend very heavily on those seeds and<br>
can be easily compromised in a variety of ways by them.<br></blockquote></d=
iv></div></div>

--047d7b5d5fbab9832304ee4ad459--