public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Roy Badami <roy@gnomon.org.uk>
To: Matt Corallo <bitcoin-list@bluematt.me>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Area of Focus
Date: Sat, 20 Dec 2014 10:08:17 +0000	[thread overview]
Message-ID: <20141220100816.GD7902@giles.gnomon.org.uk> (raw)
In-Reply-To: <54953A11.1060202@bluematt.me>

Why would we want to have anything to do with people who are hosting
malware?  Or do I misunderstand?

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.
> 
> Of course we really dont want to move off of DNS because it has this big
> built-in anonymity network where the DNS seed servers only get
> information about your ISP, not you, and its cached so you dont get as
> much information about how many users are making those requests.
> 
> A potential solution might be supporting some subdomain which has
> results XORed with some constant mask to tweak the real IP.
> 
> Additionally, it might be cool to stuff a TXT/AAAA/whatever record with
> a signature of the results provided by the DNSseed operator.
> 
> Matt
> 
> On 12/20/14 07:42, Will Bickford wrote:
> > Hi all, I'm looking to help with Bitcoin core development in my spare
> > time (a few hours per week).
> > 
> > A little bit about me:
> > * I use C++ and Qt daily
> > * I love to automate and enhance software systems
> > * I enjoy root causing and fixing issues
> > 
> > I saw Gavin say we needed help with testing in a Reddit AMA a while ago.
> > I'm curious where I can make the best impact. Any feedback would be
> > appreciated. Thanks!
> > 
> > Will Bickford
> > "In Google We Trust"
> > 
> > 
> > ------------------------------------------------------------------------------
> > 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
> > 
> 
> ------------------------------------------------------------------------------
> 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
> 



  reply	other threads:[~2014-12-20 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-20  7:42 [Bitcoin-development] Area of Focus Will Bickford
2014-12-20  8:57 ` Matt Corallo
2014-12-20 10:08   ` Roy Badami [this message]
2014-12-20 11:14     ` Jeremy Spilman
2014-12-20 21:20       ` Matt Corallo
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=20141220100816.GD7902@giles.gnomon.org.uk \
    --to=roy@gnomon.org.uk \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=bitcoin-list@bluematt.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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