summaryrefslogtreecommitdiff
path: root/6d/8e84169f0f8e104869660e7b2e9d3e51bfadc1
blob: 4c800cd9a81e4cff7f96cf656e0e12976d039f4b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
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 <decker.christian@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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: <CA+s+GJAKJHHK31wzjrAJVdb6Rw8WRVc6b4eEjWrj0GxXH=aCnQ@mail.gmail.com>
References: <CABsx9T3j8rmQzJTdWX5M2kk=V7J3i6SFgL5fPCOfL1m0hT_-wg@mail.gmail.com>
	<CAM6j61t2mtXd-AvCUV3AFc2j2Z438o4C0P1NwuUR2H4Hz9eYqQ@mail.gmail.com>
	<CA+s+GJAKJHHK31wzjrAJVdb6Rw8WRVc6b4eEjWrj0GxXH=aCnQ@mail.gmail.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Sun, 2 Mar 2014 22:11:01 +0100
Message-ID: <CALxbBHWCzJo-G3Y+Lsd8g5Q-MdXg6Xk_1m0GZfz-v4oyAzETyQ@mail.gmail.com>
To: Wladimir <laanwj@gmail.com>
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 <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <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
>