From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Area of Focus
Date: Sat, 20 Dec 2014 21:20:53 +0000 [thread overview]
Message-ID: <5495E835.2080802@bluematt.me> (raw)
In-Reply-To: <op.xq5yue2cyldrnw@laptop-air>
Well, some ISPs, when they see an IP address serving malware, will
(apparently) simply replace DNS results for anything returning that IP
with a warning page.
One solutions is to just blindly block everything with HTTP(S), as
Christian has done, but this is a rather ugly solution, since many
perfectly good nodes will get caught in the crossfire. Hiding what
actual IPs we're returning in the results seems much cleaner, despite
being an ugly hack.
On 12/20/14 11:14, Jeremy Spilman wrote:
> 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 <roy@gnomon•org.uk> 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?
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2014-12-20 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 7:42 Will Bickford
2014-12-20 8:57 ` Matt Corallo
2014-12-20 10:08 ` Roy Badami
2014-12-20 11:14 ` Jeremy Spilman
2014-12-20 21:20 ` Matt Corallo [this message]
2014-12-20 21:30 ` Gregory Maxwell
2014-12-20 18:27 ` Christian Decker
2014-12-20 21:26 ` Jeff Garzik
2014-12-20 22:37 ` Will Bickford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5495E835.2080802@bluematt.me \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox