From: "Slurms MacKenzie" <slurms@gmx•us>
To: dscotese@litmocracy•com
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis
Date: Sat, 25 Jul 2015 13:19:43 +0200 [thread overview]
Message-ID: <trinity-eb8ed324-143d-48a4-9b11-ac782d96c65b-1437823183453@3capp-mailcom-bs03> (raw)
In-Reply-To: <CAGLBAhdggPPnxLgp+xQPWGtK1KA_QZt7eug2votak4in2DrwJA@mail.gmail.com>
The answer to that is a less illegal than probing other peoples web servers. Up until recently the reverse name lookup for that IP address was markets.blockchain.info, which I resolve when I log incoming connections in an attempt to filter out some abusive clients coming from university connections.
Other people have noticed these abusive clients too. There’s mentions of other connections running the same version of BitcoinJ coming from sources that appear to be blockchain.info which display similar behavior. A user in #bitcoin-dev was complaining about this client hammering closed ports with connections when they are kicked off.
http://bitcoinstats.com/irc/bitcoin-dev/logs/2015/02/09#l1423513396.0
> Sent: Saturday, July 25, 2015 at 4:23 AM
> From: "Dave Scotese via bitcoin-dev" <bitcoin-dev@lists•linuxfoundation.org>
> To: bitcoin-dev@lists•linuxfoundation.org
> Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis
> When I looked up that IP address, the Whois info names "OVH" and "Octave Klaba" (who founded OVH, according to Wikipedia) as the owner. "blockchain.info[http://blockchain.info]" appears in the HTML header as retrieved by the "Anti-Hacker Alliance" (http://anti-hacker-alliance.com/index.php?details=37.187.136.15[http://anti-hacker-alliance.com/index.php?details=37.187.136.15]). Blockchain.info itself returns IP addresses managed by CloudFlare whenever I try it.
next prev parent reply other threads:[~2015-07-25 11:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 2:23 Dave Scotese
2015-07-25 11:19 ` Slurms MacKenzie [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-24 2:57 Dave Scotese
2015-07-24 3:37 ` Slurms MacKenzie
2015-07-24 11:38 ` Mike Hearn
2015-07-24 14:09 ` Adam Back
2015-07-24 15:22 ` Simon Liu
2015-07-24 17:40 ` Peter Todd
2015-07-24 20:28 ` Eric Lombrozo
2015-07-24 20:31 ` Eric Lombrozo
2015-07-24 15:08 ` Dave Scotese
2015-07-24 13:39 ` Thomas Zander
2015-07-24 17:43 ` Peter Todd
2015-07-24 20:23 ` Eric Lombrozo
2015-07-24 21:12 ` Slurms MacKenzie
2015-07-24 15:40 ` Milly Bitcoin
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=trinity-eb8ed324-143d-48a4-9b11-ac782d96c65b-1437823183453@3capp-mailcom-bs03 \
--to=slurms@gmx$(echo .)us \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dscotese@litmocracy$(echo .)com \
/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