From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WKDUs-0006Av-F3 for bitcoin-development@lists.sourceforge.net; Sun, 02 Mar 2014 21:00:30 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.83.43 as permitted sender) client-ip=74.125.83.43; envelope-from=fastest963@gmail.com; helo=mail-ee0-f43.google.com; Received: from mail-ee0-f43.google.com ([74.125.83.43]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WKDUr-0003CF-9Y for bitcoin-development@lists.sourceforge.net; Sun, 02 Mar 2014 21:00:30 +0000 Received: by mail-ee0-f43.google.com with SMTP id e53so3437691eek.30 for ; Sun, 02 Mar 2014 13:00:23 -0800 (PST) X-Received: by 10.14.203.197 with SMTP id f45mr6873958eeo.90.1393794023087; Sun, 02 Mar 2014 13:00:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.79.136 with HTTP; Sun, 2 Mar 2014 12:59:43 -0800 (PST) In-Reply-To: References: From: James Hartig Date: Sun, 2 Mar 2014 15:59:43 -0500 Message-ID: To: Wladimir Content-Type: multipart/alternative; boundary=047d7b343ac0a2e62304f3a5f5eb X-Spam-Score: -0.3 (/) 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 (fastest963[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (fastest963[at]gmail.com) 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1WKDUr-0003CF-9Y 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:00:30 -0000 --047d7b343ac0a2e62304f3a5f5eb Content-Type: text/plain; charset=UTF-8 Didn't mean that bitcoind was connecting over port 443. I didn't even get a chance to compile. I was literally just finished downloading the tar.gz file when my server was terminated. Still trying to convince them I wasn't attacking anyone so they can re-enable the server. Thanks, -- James Hartig Software Engineer @ Grooveshark.com http://twitter.com/jameshartig On Sun, Mar 2, 2014 at 3: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 > > --047d7b343ac0a2e62304f3a5f5eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Didn't mean that bitcoind was connecting over port 443= . I didn't even get a chance to compile. I was literally just finished = downloading the tar.gz file when my server was terminated.

Still trying to convince them I wasn't attacking anyone so they can re-= enable the server.

=
Thanks,
--
James Hartig
Software Engineer @ = Grooveshark.com
http://twitter= .com/jameshartig
=C2=A0
= =C2=A0



On Sun, Mar 2, 2014 at 3:56 PM, Wladimir= <laanwj@gmail.com> wrote:

=
On Sun, Mar 2, 2014 at 7:34 PM, James Hartig <fastest96= 3@gmail.com> wrote:
Heads up... downloaded the = linux tar.gz to my OVH box and got my server terminated. Screenshot from th= e email:

They claimed I was attacking=C2=A088.198.199.140 over port 4= 43.

Sounds very unlikely = that bitcoind would connect to port 443, let alone 'attack' anythin= g.

Anything in debug.log regarding that IP?

Wladimir


--047d7b343ac0a2e62304f3a5f5eb--