Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WKDfn-0001jV-Ew for bitcoin-development@lists.sourceforge.net; Sun, 02 Mar 2014 21:11:47 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.176 as permitted sender) client-ip=209.85.214.176; envelope-from=decker.christian@gmail.com; helo=mail-ob0-f176.google.com; Received: from mail-ob0-f176.google.com ([209.85.214.176]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WKDfm-000758-J9 for bitcoin-development@lists.sourceforge.net; Sun, 02 Mar 2014 21:11:47 +0000 Received: by mail-ob0-f176.google.com with SMTP id wp18so4412393obc.35 for ; Sun, 02 Mar 2014 13:11:41 -0800 (PST) X-Received: by 10.182.213.166 with SMTP id nt6mr1786502obc.53.1393794701244; Sun, 02 Mar 2014 13:11:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.152.71 with HTTP; Sun, 2 Mar 2014 13:11:01 -0800 (PST) In-Reply-To: References: From: Christian Decker Date: Sun, 2 Mar 2014 22:11:01 +0100 Message-ID: To: Wladimir Content-Type: text/plain; charset=ISO-8859-1 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (decker.christian[at]gmail.com) -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: 1WKDfm-000758-J9 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] 0.9.0 release candidate two 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: Sun, 02 Mar 2014 21:11:47 -0000 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 wrote: > > On Sun, Mar 2, 2014 at 7:34 PM, James Hartig 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 >