From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Y2IwO-0005Zr-3P for bitcoin-development@lists.sourceforge.net; Sat, 20 Dec 2014 12:15:24 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of taplink.co designates 50.117.27.232 as permitted sender) client-ip=50.117.27.232; envelope-from=jeremy@taplink.co; helo=mail.taplink.co; Received: from mail.taplink.co ([50.117.27.232]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.76) id 1Y2IwM-0003QB-B1 for bitcoin-development@lists.sourceforge.net; Sat, 20 Dec 2014 12:15:24 +0000 Received: from laptop-air (Unknown [192.168.168.160]) by mail.taplink.co with ESMTPSA (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256) ; Sat, 20 Dec 2014 03:14:44 -0800 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: bitcoin-development@lists.sourceforge.net References: <54953A11.1060202@bluematt.me> <20141220100816.GD7902@giles.gnomon.org.uk> Date: Sat, 20 Dec 2014 03:14:28 -0800 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Jeremy Spilman" Organization: TapLink Message-ID: In-Reply-To: <20141220100816.GD7902@giles.gnomon.org.uk> User-Agent: Opera Mail/1.0 (Win32) 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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay 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: 1Y2IwM-0003QB-B1 Subject: Re: [Bitcoin-development] Area of Focus X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2014 12:15:24 -0000 On Sat, Dec 20, 2014 at 08:57:53AM +0000, Matt Corallo wrote: >> There was recently some discussion around dnsseeds. Currently some >> dnsseeds are getting blocked by ISPs because the hosts they pick up >> (which run bitcoin core nodes) often run rather web servers alongside >> which serve malware or whatever else and thus end up on IP-based malware >> blacklists. On Sat, 20 Dec 2014 02:08:17 -0800, Roy Badami wrote: > Why would we want to have anything to do with people who are hosting > malware? Or do I misunderstand? It sounds like Matt is saying the nodes the dnsseed is pointing to as valid full nodes, that those IPs are hosting the malware. Since the dnsseed picks up any stable nodes it can find without auditing, it's perhaps not surprising some servers in the world are running a full node and a malware server together. I guess what confused me about this though, how are ISPs reading the dnsseed's node list, scanning *those* IPs for malware, and then ending up blocking the dnsseed? Seems like a pretty winding path to end up blocking a DNS server? Since when do ISPs null-route a DNS server for happening to resolve some domains to IPs which happen to also be hosting some malware? Null-route those endpoint IPs sure, but the DNS server too? I guess there was that incident of Microsoft taking over No-IP.com -- are dnsseeds being blocked ostensibly because they are acting as dyanamic DNS infrastructure for malware sites?