From: Christian Decker <decker.christian@gmail.com>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.9.0 release candidate two
Date: Sun, 2 Mar 2014 22:11:01 +0100 [thread overview]
Message-ID: <CALxbBHWCzJo-G3Y+Lsd8g5Q-MdXg6Xk_1m0GZfz-v4oyAzETyQ@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJAKJHHK31wzjrAJVdb6Rw8WRVc6b4eEjWrj0GxXH=aCnQ@mail.gmail.com>
The domain bitcoin.org resolves to that IP address. Could it be some
update check together with a circular redirect? That could at least
explain the large number of connection attempts.
--
Christian Decker
On Sun, Mar 2, 2014 at 9:56 PM, Wladimir <laanwj@gmail.com> wrote:
>
> On Sun, Mar 2, 2014 at 7:34 PM, James Hartig <fastest963@gmail.com> wrote:
>>
>> Heads up... downloaded the linux tar.gz to my OVH box and got my server
>> terminated. Screenshot from the email:
>> http://cl.ly/image/3q0C2a3Y0T0V
>>
>> They claimed I was attacking 88.198.199.140 over port 443.
>
>
> Sounds very unlikely that bitcoind would connect to port 443, let alone
> 'attack' anything.
>
> Anything in debug.log regarding that IP?
>
> Wladimir
>
>
> ------------------------------------------------------------------------------
> Flow-based real-time traffic analytics software. Cisco certified tool.
> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> Customize your own dashboards, set traffic alerts and generate reports.
> Network behavioral analysis & security monitoring. All-in-one tool.
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
prev parent reply other threads:[~2014-03-02 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 13:54 [Bitcoin-development] 0.9.0 release candidate two Gavin Andresen
2014-03-02 18:34 ` James Hartig
2014-03-02 20:56 ` Wladimir
2014-03-02 20:59 ` James Hartig
2014-03-02 21:11 ` Christian Decker [this message]
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=CALxbBHWCzJo-G3Y+Lsd8g5Q-MdXg6Xk_1m0GZfz-v4oyAzETyQ@mail.gmail.com \
--to=decker.christian@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=laanwj@gmail.com \
/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